Italian translations


Yeah, styles… oops!
Last example it’s only with styles!
See the SyT01.htm, the code listed in my previous post…

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.

wiki/en [default]

<- no code or code with no strings->


<- code with strings->

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.




please which is the meaning of Loopyness?

Which is the difference between


in the manual index?

In italian version my pages are all Doc:

:question: :question: :question:




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.


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:

As example see:
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/it
at the bottom.

For example the page:
has those categories:
{{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: … ction=edit



So, resuming:

-Pages like the english ones + /it at the end
-Category always like english version
-Navigator and internal links with /it at the end

That’s true?

Anything else I miss?


  • Page names like the English ones but with the /it at the end
  • Page links always like the English ones (using the {l|internal link|Text shown} macro).
    (Category is juts like other any page)
  • Navigator (as any other macro) always with the English version.
  • Link and macros like the English one.
  • If the /it page exists it will use it if not it will use the English one. This way the links are never pointing to a non existing page.



Oh! Thanks a lot for your response.

I need some help about translating new transifex strings.

  1. See the image, what is the meaning of the two light blue bars in english version?
    How can I reproduce them?

  2. What is the meaning of “Seek to begin” in the context:
    Try to start/begin
    Searching the begin [of something]





Which image?

I’ve translated to Spanish as “Go to begin” and “Go to end”.


Oops, here the image…

Note that an image without the blue bars is already present.




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.



thanx jcome, no problem!

The core Transifex is locked by you? I wait…

Is it possible to display the translating file on which I work in the translation page of Transifex?
I can see it only in the browser’s address bar…

Nice day to all.



not me :wink:


Well, but now it’s free.



Hi all,

I’ve found taht in page there is the {{l|Paste Canvas}} link.

This is redirected to Paste Canvas Layers page.

How should I translate it?



You have to put
{{l|Paste Canvas Layer|Incolla Tela}}
instead of
{{l|Paste Canvas|Incolla Tela}}
to be able to redirect to the translated page.

Maybe the translation macros could consider to use the translated redirected page (



Hi all!

Italian translation has been completed.

Notice that in English version of Synfig / synfig-studio
there’s a mistyping error : Aniamte loop instead o Animate loop.




Hi, BottyE!
You did that right in time, because I was applying translations right now.
The typo is fixed, thank you!



I’ve just made a round on Synfig in order to verify translations consistency.

I’ve found these “problems”:

Translations that are not visible in Synfig 0.63.05

SyAnimation File|Apri >>Open
" File|Anteprima Opzioni Anteprima >>General Settings|Time Settings||Begin Time||End Time

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 :exclamation: :question:

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 :smiley: … )




Hi, Bottye!

  1. As I see here - … nguage/it/ - everything is translated at the current status. The translations will be included into next release.
  2. 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 - … e-settings


Hi Zelgadis, thanx.

  1. I hope so, because last time some words were no loaded, maybe for bad invisible chars!?

  2. I’ve saw the hint, but it doesn’t work on xp for Synfig :

set lang=it
start C:\Programmi\Synfig\bin\synfigstudio.exe

Seeing the EV (environment variables) it seems that the hint is not inherent.
(this is for 7 but is similar on xp).

Same problem is also present for other languages under win, I suppose…

I could try to understand the problem (I don’t know when!)
if you help me extracting the portion of synfig code used for localizations.