Pascal, BRilhant idea to use layer for translations. This could help us to not have several versions of the same file, I mean, instead of a file ending with -FR, -BR, -EN, ... we can start to use just one file with many layer, each one for each language added. PS: Tumbleweed original version (english) have a mistake. In two boxes Tumblewwed have double "T" Em Seg, 2011-11-07 às 12:57 +0100, Pascal Bleser escreveu:
On 2011-11-04 22:56:13 (-0200), Jos Poortvliet <jos@opensuse.org> wrote:
I've just finished updating the posters we made last year at SCALE in the USA. They are ready for translation and I can then print a bunch in time for the openSUSE 12.1 release parties!
Who's up for translating them? download the svg files at the link below, translate them (open in Inkscape, edit the text) and mail them back to me...
I just checked in and pushed the french translations of the "light" ones, still have to copy/paste the "non-light" ones ;)
https://github.com/openSUSE/artwork/commit/50fca782510937e01923c7fdd6bf12f4e...
(saved them with the original file name, with "-FR.svg")
(I really wonder whether we shouldn't rather be using layers to avoid having to do the copy/pasting ... ?)
A few comments:
1. English is *very* compact ============================ If we want to be able to translate that stuff, we really have to be careful with the layout, because the English language is *very* compact as compared to most latin languages, especially french: something like "customize spins with OBS" becomes "adaptez vos distributions dérivées à l'aide de l'OBS" (not the actual translation in the posters, just an example)
So making a layout where you manage to barely get the English text into it is going to prove very difficult to be translated, at least without playing some tricks on the layout.
What I did was to lower the line height when it didn't fit (and it never did ;)), changing it from the default 1.25 to 1.1, and that usually is enough. When it isn't, I used a negative kerning on the text to make it less wide, which works too (but only to a certain extent, more than -0.20 wouldn't be easily readable).
See "Creating text" here: http://inkscape.org/doc/advanced/tutorial-advanced.html
or "Baseline Settings and Manual Kerning" here: http://www.ffnn.nl/pages/articles/media/inkscape-text-tricks.php
(those are very important and useful features for typesetting, everyone should read it and play with it a bit, it's really easy :))
So when someone makes the original work in English, please, pretty please try to not have it "barely fit" in there because that won't be possible for any latin language for sure. And also always use the default line height of 1.25: that'll at least give the option to translators to make it smaller and, hence, more compact, to be able to fit it all into the same bounding box.
2. Use Ctrl+Shift+T =================== When you translate, you typically want to see both the original (English) text and your translation side to side. If you just double-click the text object in Inkscape and type over it, it's a bit more difficult.
Instead, I found it easier to click on a text object, and then use Ctrl+Shift+T (or "Text" > "Text and Font" in the menu), then click on the "Text" tab on top. There you have a text box which is much more convenient to edit: just write the translation below the original line in English, and then remove the English bits.
Of course, you have to then adapt the layout to make it fit (see above, with manual font kerning).
3. It's a version control system ================================ Yes, sorry, I'm being anal on this again but... :) Typically, unless there is a very, very good reason to do so, don't use an "outdated" subdirectory or something like that, or "FINAL" in the filenames. That creates an unnecessary amount of files which 1) completely clutters the navigation of the repository, because there are tons of them 2) bloats the repository (it's already 2GB to clone)
Just replace the files !
You can always access older revisions, which is the whole point of a version control system in the first place :) (but only really easy to use if everyone uses meaningful commit messages ;))
cheers
-- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org