The chars you see in the canvas in the image are from the True Type font I carefully specified among the Text Layer parameters:
The char not represented in the canvas is “ó”.
The font includes “ó”:
The font file is in the same folder that the SIF file is into:
Anyway, everything works fine EXCEPT that non-ASCII char. If you encode “ó” in UTF-8, then decode in Latin-1 (ISO-8859-1, or ISO-8859-15 including “€”), that’s what you get: Ã³
So that’s very probably what is happening: the canvas is trying to show the text AS IF LATIN-1, but it’s UTF-8 encoded actually. The superscripted three is the char that Intensa Fuente doesn’t include, but I don’t need ³ at all. I need the acute o!
*** How can I make Synfig Studio use UTF-8 when decoding the Text parameter in a Text Layer? ***
This one is a minor inconvenience I can live with. The enconding problem is the one I can’t solve.
Moreover, the changes produced by enabling the Cairo-related preference doesn’t affect the final FLV rendering: then, I recover my font election & lose my non-ASCII chars because of the encoding mismatch.
The setting in Preferences… dialog we mentioned in previous post is used in WorkArea only, when you render your sifz document, the render uses the font you defined in Parameters Panel. I have no experienced on Windows platform, on Linux platform, I put the font file in the same folder where my .sifz document, and the corresponding value of Font Family Parameter is ./wqy-microhei.ttc. As you can see, there is not issue on the WorkArea, Preview Window as well as the rendered frame.
So you don´t have any issue, I see. Thanks for documenting your settings & outputs so well.
However, I’m still suffering the same problems:
With Cairo rendering:
–> Non-ASCII chars: OK. BUT…
–> Font: A default one that I’m unable to change using the Font Family parameter. I have tried absolute & relative paths, “/” vs “”, putting quotes around the value, with & without “.ttf” extension… anything that have come to my mind! BTW, does Cairo need a “.ttc” file? I note your font file is a “collection”, while mine isn’t.
–> Moreover, I’m unable to Render to an FLV file using Cairo.
Without Cairo rendering:
-> Font: OK (font file name, without path or extension, as Font Family parameter value). BUT…
-> Non-ASCII chars: NO WAY! Shown as when UTF-8 chars are interpreted without taking into account that encoding.
Which piece of software is the one rendering the text when it’s not Cairo?
Is it the same one for WorkArea, Preview, and Render to an FLV file?
How can I tell it “take UTF-8 into account”?
I’m lost and desperate. I should be writing a document for my pupils to learn Synfig, but I’m unable to even make Synfig work properly.
*** Isn’t anyone else trying to make Synfig animations with Spanish text in them? ***
First things first, thanks for responding, d.j.a.y.
Thanks, so Cairo is a path that I shouldn’t take.
Yes, we will have to use only English in Text Layers.
But this would solve nothing, it’s not a font issue!
They are not going to provide my pupils with a good first impression about Synfig. Especially having into account that I have already written that we need an external program to add sound to the Synfig-generated animation!
As a work around you can always create the missing letter(s), in this case just the O with the accent, in Inkscape, convert it to paths and export it as sif to be used as a normal vector shape layer in Synfig. It’s just a work around but at least you will be using two open source programs .
edit: or even faster: just type a normal “o” and make the accent in synfig. Two seconds of work.
there is not problem on Linux platform as you can see in attached screenshot.
The point for Windows, I guess is to figure how to specify the font file, so that synfig’s render can take it. Did you try an absolute path like: C:\xxx\xxx\xxx\myfont.ttf ? (I have tested, it doesn’t work as expected! )
Thanks, Darkspace65, but I’m not looking for a workaround for a problem preventing me from getting the animation I really need to produce, my role now is a different one: I have to explain how Synfig works to my pupils. Well, Synfig doesn’t work in this case. It’s a better option in my case just saying: “let’s work in English”.