9:40 a.m.
Le 04/06/2016 à 17:44, Maren Hachmann a écrit :
Am 04.06.2016 um 16:55 schrieb Sylvain Chiron:
> Le 03/06/2016 à 17:28, Martin Owens a écrit :
>> I can say that you should consider any new website design to be frozen
>> and you can sort on any part of the design for the website for
>> incremental improvements. I've been ding that for the past few months
>> too.
>
> Do you mean ‘shouldn't’? That's OK.
- Sorry for chiming in, Martin.
Sylvain, what he means is that there are no current efforts going on for
a revolutionary redesign of the page. But we can make small changes to
improve the current design.
Okay… Strange language. That's understood.
We do only want to change those inside the cms pages. All other h2
and
h3 headings (unless there aren't any? You could check that first, to see
if this is necessary) must stay the same.
There are others actually, but they all redefine their own margin and size.
Wait… OK, you're right, there are many headings elsewhere — :).
There is no overriding rule here:
https://inkscape.org/en/*users/chat/
So I'll make different rules: ‘.wrapper h2’ and ‘.wrapper h3’.
Le 03/06/2016 à 19:48, Maren Hachmann a écrit :
If you do make this change, it would help if you could also take
some
time to remove (at least a few of) the paragraphs when the fix has been
released, so the pages will not look weird due to huge gaps between the
headings and the following texts.
I don't think there's a need to wait. I'll remove the paragraphs right
now except in the FAQ for which I'll wait.
> 2. It is quite hard to find the part we want when editing the
FAQ; could
> we subdivide the only text plugin in several text plugins, one for each
> section?
- That's an option. Before we continue to discuss if it is to be
implemented, please research if those plugins must then also be added to
all translations.
I think there's no link between text plugins in different languages.
Optionnally, only translators who want several text plugins could subdivide.
It may be that missing plugins will automatically be substituted by
their English counterparts (I think due to a bug in current django, this
does not happen, but as soon as they fix the bug, there could be a
problem - there was something about this in their bug tracker, I seem to
remember).
You mean that if we try to take the links from a text plugin to another,
we may get the English links (as the plugins will remain childs of the
initial text plugin)?
However… If we try to move the plugins from a text plugin to another, it
will simply remove the plugins' data and the plugins won't exist in the
second text plugin (I just tried on the sandbox)… Thus it would be a
very difficult task to subdivide as I thought…
I could imagine splitting the FAQ into its major 7 sections, but
having
a single one for each question would make editing a bit annoying (also
it's too much editing work to put that change in, as copy-paste for
links or images between plugins might not work as expected).
Yes, I was talking about a splitting for the major sections.
--
Sylvain
3:32 p.m.
New subject: Questions concerning the website's content
Dear Sylvain,
Am 04.06.2016 um 18:40 schrieb Sylvain Chiron:
Le 03/06/2016 à 19:48, Maren Hachmann a écrit :
> If you do make this change, it would help if you could also take some
> time to remove (at least a few of) the paragraphs when the fix has been
> released, so the pages will not look weird due to huge gaps between the
> headings and the following texts.
I don't think there's a need to wait. I'll remove the paragraphs right
now except in the FAQ for which I'll wait.
- I agree. Thank you for starting out on this!
> It may be that missing plugins will automatically be substituted
by
> their English counterparts (I think due to a bug in current django, this
> does not happen, but as soon as they fix the bug, there could be a
> problem - there was something about this in their bug tracker, I seem to
> remember).
- I just had time to look up the bug I was thinking of. Fortunately, it
was about specific *nested* plugins not showing up when the translation
doesn't have any plugins, so it's not relevant here.
However… If we try to move the plugins from a text plugin to another,
it
will simply remove the plugins' data and the plugins won't exist in the
second text plugin (I just tried on the sandbox)… Thus it would be a
very difficult task to subdivide as I thought…
- Yes, that's what I meant by "as copy-paste for links or images between
plugins might not work as expected". Nested plugins are saved as
children of other plugins. When removed from their original place, and
pasted into another one, I assume that they will be gone, because they
are deleted from their original place.
> I could imagine splitting the FAQ into its major 7 sections, but
having
> a single one for each question would make editing a bit annoying (also
> it's too much editing work to put that change in, as copy-paste for
> links or images between plugins might not work as expected).
Yes, I was talking about a splitting for the major sections.
- So I agree that's a lot of work. Only you can decide if it would be
worth the gain for you.
I can work with both situations, and I think Brynn can, too. It might
make work a tiny bit faster, but not enough so that I would want to do
the splitting myself. Maybe there's something else that would profit
from our time investment more than this? We've got enough bug reports
for inkscape-web to have work for a couple of months...
You seem to like javascript stuff, so maybe the inbox problems or the
TOC customization could profit from your work.
Before you start working on any bug, please add a comment there, telling
the others that you plan to work on it (so we don't work on the same bug
at the same time), and also sketch roughly what you'd do to fix it. We
can then give feedback, or add some more info to the report before you
start working on it. Sometimes, things have changed since the bug was
first reported, or we may know or plan something that you cannot know about.
Kind Regards,
Maren
2734
days inactive
2734
days old
inkscape-translator@lists.inkscape.org
1 comments
2 participants
participants (2)
-
Maren Hachmann -
Sylvain Chiron