Re: [Inkscape-translator] Website Update: Changes for editors and translators
- I had just a few minutes ago received a mail from Brynn where she
told me about the missing permissions for editing the new plugin. They are available now.
Nice.
About the nesting: Can you give some more details (or maybe make a bug report with screenshots when you're certain it's a bug at bugs.launchpad.net/inkscape-web)?
It looks flagrant to me but if you want… Here is a screenshot (made with GIMP — :P): http://i.imgur.com/qBq3GYx.png Looks like a title cannot unnest twice at once (e.g. h5 then h2 causes the h2 to be nested in the previous h2).
- That's at least 20 times less than it was before! :D
Oh! I thought the button didn't work at all before. This explains that.
- The title looks great - only the page was empty. The gallery (like the
board page) is a special case. In such cases, look at how things are done in the advanced settings for the page in languages where it works, then do it the same way in your language. It's fixed now for French.
Thanks. But I cannot access the advanced settings of the page in the other languages… The menu is not present.
Another remark: if https://inkscape.org/fr/news/ is translated to e.g. https://inkscape.org/fr/actu/ then the ‘Read more’ links don't work. It is also strange that ‘Read more’ is not translated. And we can't either translate the title ‘Latest news’. And the news are sorted by date of translation, not date of publication (which is bad because I lastly translated the Hackfest 2015 article)… And I can't access the articles' translation anymore. (Should I open bug reports for all that?)
I see that now plugins can be edited by a single click. That's not really helpful… The previous double-click allowed to select the text for Link plugins, and to edit it avoiding any bug.
And the dialog to edit a plugin is sometimes too big and I cannot access the validation buttons! (Try when your edit dialog is maximized.) That's bad. -- Sylvain
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
Sylvain
Le 21/03/2016 13:26, Sylvain Chiron a écrit :
- I had just a few minutes ago received a mail from Brynn where she
told me about the missing permissions for editing the new plugin. They are available now.
Nice.
About the nesting: Can you give some more details (or maybe make a bug report with screenshots when you're certain it's a bug at bugs.launchpad.net/inkscape-web)?
It looks flagrant to me but if you want… Here is a screenshot (made with GIMP — :P): http://i.imgur.com/qBq3GYx.png Looks like a title cannot unnest twice at once (e.g. h5 then h2 causes the h2 to be nested in the previous h2).
- That's at least 20 times less than it was before! :D
Oh! I thought the button didn't work at all before. This explains that.
- The title looks great - only the page was empty. The gallery (like the
board page) is a special case. In such cases, look at how things are done in the advanced settings for the page in languages where it works, then do it the same way in your language. It's fixed now for French.
Thanks. But I cannot access the advanced settings of the page in the other languages… The menu is not present.
Another remark: if https://inkscape.org/fr/news/ is translated to e.g. https://inkscape.org/fr/actu/ then the ‘Read more’ links don't work. It is also strange that ‘Read more’ is not translated. And we can't either translate the title ‘Latest news’. And the news are sorted by date of translation, not date of publication (which is bad because I lastly translated the Hackfest 2015 article)… And I can't access the articles' translation anymore. (Should I open bug reports for all that?)
I see that now plugins can be edited by a single click. That's not really helpful… The previous double-click allowed to select the text for Link plugins, and to edit it avoiding any bug.
And the dialog to edit a plugin is sometimes too big and I cannot access the validation buttons! (Try when your edit dialog is maximized.) That's bad. -- Sylvain
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
I just discovered that there is an option for CKEditor to deactivate copy-pasting of formatted text.
Do you (and the others) think we could use this as a workaround for our plugin copy problem?
The disadvantages would be that if you *really* need to copy a plugin (to move it from one position in the page to a different one), you need to do this in the source mode. It will also remove all headings, italics, etc. from any copied text.
I'm thinking that this is a high price to pay. But what do you think?
Maren
Le 21/03/2016 21:16, Maren Hachmann a écrit :
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
I just discovered that there is an option for CKEditor to deactivate copy-pasting of formatted text.
Do you (and the others) think we could use this as a workaround for our plugin copy problem?
The disadvantages would be that if you *really* need to copy a plugin (to move it from one position in the page to a different one), you need to do this in the source mode. It will also remove all headings, italics, etc. from any copied text.
I'm thinking that this is a high price to pay. But what do you think?
Maren
Yes, there's no problem to go to the source code sometimes; I did already use it because it is safer.
+1 to deactivate. -- Sylvain
Am 22.03.2016 um 00:12 schrieb Sylvain Chiron:
Le 21/03/2016 21:16, Maren Hachmann a écrit :
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
I just discovered that there is an option for CKEditor to deactivate copy-pasting of formatted text.
Do you (and the others) think we could use this as a workaround for our plugin copy problem?
The disadvantages would be that if you *really* need to copy a plugin (to move it from one position in the page to a different one), you need to do this in the source mode. It will also remove all headings, italics, etc. from any copied text.
I'm thinking that this is a high price to pay. But what do you think?
Maren
Yes, there's no problem to go to the source code sometimes; I did already use it because it is safer.
+1 to deactivate.
I'll also ask around the editors, as they would also be affected by this. What do the others think?
Le 21/03/2016 21:16, Maren Hachmann a écrit :
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
Now, editing the Front shield shows a blank dialog. What should I do? I want to update this! The translation is inconsistent! A full stop is missing at the end of the last frase ‘Découvrez comment profiter de tout le potentiel d'Inkscape’. -- Sylvain
Am 22.03.2016 um 00:30 schrieb Sylvain Chiron:
Le 21/03/2016 21:16, Maren Hachmann a écrit :
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
Now, editing the Front shield shows a blank dialog. What should I do? I want to update this! The translation is inconsistent! A full stop is missing at the end of the last frase ‘Découvrez comment profiter de tout le potentiel d'Inkscape’. -- Sylvain
- Yes, the permissions were a little scattered about. Their names aren't very logical. Try again to make this critical change ;)
Kind regards, Maren
Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
As a translator I do not see a big problem with this, since translation work rarely involves moving a lot stuff around, at leas for my personal workflow, not sure how others do it though. My guess is editors and original content writers are probably not gonna like this as much as we do, since they probably do a lot more heavy editing and shuffling content around.
Copying from source seems like an acceptable workaround (as stated by Sylvain I already do it some times as it seems safer and cleaner), so I would not mind that at all.
On 21-03-2016 20:16, Maren Hachmann wrote:
Am 21.03.2016 um 17:25 schrieb Sylvain Chiron:
Also, it is still not possible to edit/update the Front Shield (which is out of date in French).
- Will work now, thanks for the info.
I just discovered that there is an option for CKEditor to deactivate copy-pasting of formatted text.
Do you (and the others) think we could use this as a workaround for our plugin copy problem?
The disadvantages would be that if you *really* need to copy a plugin (to move it from one position in the page to a different one), you need to do this in the source mode. It will also remove all headings, italics, etc. from any copied text.
I'm thinking that this is a high price to pay. But what do you think?
Maren
Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Dear Sylvain,
Looks like a title cannot unnest twice at once (e.g. h5 then h2 causes the h2 to be nested in the previous h2).
- Thanks for investigating. Yes, please make this a bug report - this needs to be fixed by someone who knows some js.
- The title looks great - only the page was empty. The gallery (like the
board page) is a special case. In such cases, look at how things are done in the advanced settings for the page in languages where it works, then do it the same way in your language. It's fixed now for French.
Thanks. But I cannot access the advanced settings of the page in the other languages… The menu is not present.
- Right, seems another bug. When you're in edit mode on some page, it works when you then switch to the English page for the gallery. So: - switch to edit mode anywhere where it works - go to English page - Page -> Advanced settings - Look into the first tab, copy the way it's done there into the French tab (and yes, I know the tab doesn't look active... but you'll see that the page has stopped loading - another bug.)
(these two are django-cms bugs, not ours...)
Another remark: if https://inkscape.org/fr/news/ is translated to e.g. https://inkscape.org/fr/actu/ then the ‘Read more’ links don't work. It is also strange that ‘Read more’ is not translated. And we can't either translate the title ‘Latest news’. And the news are sorted by date of translation, not date of publication (which is bad because I lastly translated the Hackfest 2015 article)… And I can't access the articles' translation anymore. (Should I open bug reports for all that?)
- Yes, please do. Brynn has just discovered a similar thing, so we may put them together into a single bug later.
I see that now plugins can be edited by a single click. That's not really helpful… The previous double-click allowed to select the text for Link plugins, and to edit it avoiding any bug.
- I agree. I couldn't find where this was introduced, though - if it's a django-cms specific thing, or a ckeditor thing. Please make a bug report so we can investigate further. It doesn't appear as if there's a setting for this. Probably a touch-screen compatibility thing (django-cms wants to be touch-screen compatible, and forgets the others over this, imvho)
And the dialog to edit a plugin is sometimes too big and I cannot access the validation buttons! (Try when your edit dialog is maximized.) That's bad.
- I agree this is annoying. It's probably another side-effect of django-cms efforts of trying to become touch-screen compatible.... You can make a bug report for us, and maybe, if you can spare some time, research in django-cms bugs for an existing report, or add a new one.
Kind regards, Maren
participants (3)
-
Duarte Ramos -
Maren Hachmann -
Sylvain Chiron