Yeah, styles… oops!
Last example it’s only with styles!
See the SyT01.htm, the code listed in my previous post…
.sif?
Yes, but, in this case, every translator must generate a new image, and this, for every image ;that weighs down on the server!
Styles, if there are no problems with .pdf export, are very light in weight.
If we can find a tool that do what we want we can close the code in a wiki|html table/cell that we can place where we want in the wiki page.
e.g.:
wiki/en [default]
…
table-cells-img <- no code or code with no strings->
/table-cells
…
wiki/it
…
table-cells-img <- code with strings->
/table-cells
…
For code I intend the specific lines of code needed for the coords and strings to put over images.
Proposed rule:
The first translator who has time to implement the image structure write/generate the code and paste it also in /en standard version [without translated strings] so the code is shared to all the other users.
English version remain the master always for all translators.
I don’t have good translation of Loopyness for Spanish, maybe you can look to how was it translated at es.po.
Anyway, ther parameter is useless. Just don’t translate it if you don’t know the translation.
-G
Doc pages are to collec the pages for the manual. The other pages are Reference, Glossary or Tutorials which don’t have the Doc category inside.
Please don’t add Doc to those layers that aren’t Doc in the English version if not you’ll never will get the translated version to get listed on the language bar: wiki.synfig.org/wiki/Region_Layer wiki.synfig.org/wiki/Doc:Region_Layer/it
As example see: wiki.synfig.org/wiki/Outline_Layer
and watch how the empty Outline_layer/it is listed on the language bar and not your Doc:Outline_Layer/it
Also , notice at the bottom of the page, that your Doc:Region_Layer/it has its category badly set, because you included the language (/it) in the category:
{{Category|Layers/it}}
produces:
Category: Layers/it/it
at the bottom.
For example the page: wiki.synfig.org/wiki/Doc:Getting_Started/es
has those categories:
{{Category|Manual}}
{{Category|Tutorials}}
{{Category|Tutorials Basic}}
which produces:
Categories: Manual/es | Tutorials/es | Tutorials Basic/es
at the bottom:
The language is automatically added by a macro when the category is inserted to a page that is a translation. The categories should be the same than the English verison so it can be collected properly for the pages that includes a CategoryContents macro: wiki.synfig.org/wiki/index.php?t … ction=edit
my fault, I added an extra “space” between past and keyframes in the source code, I will fix it soon.
In your case, please just ignore the blue bars. Sorry for the confusion caused.
SyStudio File|Dispositivi di Ingresso >>Input
" File|Impostazioni… Impostazioni di Synfig Studio|Visualizza >>Image Sequence Separator String
Only these few red highlighted strings were not translated
Where’s the / my fault?
How can I resolve This?
When it will be possible see Syinfig translated into Italian under Windows?
(In my head is whirling with the idea of doing a site on Synfig in Italian and so, Synfig translated in italian would be much appreciated … )
Localizations are ignored for Synfig on Windows. This is packaging problem and no one is working on resolving it at the moment. The problem is related with environment variables. The hint on this can be found on gimp case - en.kioskea.net/faq/9158-gimp-cha … e-settings
K.
… )