FontForge does not support your encoding (utf8) (was: ... please keep testing TL 2012)
On Thu, May 24, 2012 at 10:15 PM, Philipp Gesang wrote:
Ok, will try again later.
You may try again in the morning when the packages will be updated.
The file seems to be present here.
For me too, it’s even in the database. But still the format can’t be generated.
Here’s a paste of the log: http://pastie.org/3962742; my mail from earlier today is still being held back by mailman.
Totally weird. Let's wait until tomorrow and see then. But the best of all is the following line: FontForge does not support your encoding (utf8), it will pretend the local encoding is latin1 I realized that it might not even be the first time for me to see that message: http://www.ntg.nl/pipermail/ntg-context/2011/058800.html but it is totally puzzling. Now I realized that if I replace LC_ALL=sl_SI.UTF-8 with LC_ALL=sl_SI.utf8 in my environment I get that message as well (but I have no clue whether it influences anything). Mojca
On 2012-05-24 22:52, Mojca Miklavec wrote:
On Thu, May 24, 2012 at 10:15 PM, Philipp Gesang wrote: Totally weird. Let's wait until tomorrow and see then. But the best of all is the following line: FontForge does not support your encoding (utf8), it will pretend the local encoding is latin1
Don’t you always get this on stderr when running luatex? It’s harmless and was always there. Have a look at the list in “noprefs.c” to see that my locale en_US.utf8 isn’t there. Though I don’t have clue as to why on earth it should default to latin1 ... Regards Philipp
I realized that it might not even be the first time for me to see that message: http://www.ntg.nl/pipermail/ntg-context/2011/058800.html but it is totally puzzling. Now I realized that if I replace LC_ALL=sl_SI.UTF-8 with LC_ALL=sl_SI.utf8 in my environment I get that message as well (but I have no clue whether it influences anything).
Mojca ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
On Thu, May 24, 2012 at 11:09 PM, Philipp Gesang wrote:
On 2012-05-24 22:52, Mojca Miklavec wrote:
On Thu, May 24, 2012 at 10:15 PM, Philipp Gesang wrote: Totally weird. Let's wait until tomorrow and see then. But the best of all is the following line: FontForge does not support your encoding (utf8), it will pretend the local encoding is latin1
Don’t you always get this on stderr when running luatex?
No, never.
It’s harmless and was always there. Have a look at the list in “noprefs.c” to see that my locale en_US.utf8 isn’t there.
I would say that the proper name *is* actually UTF-8, not "utf8".
I don’t have clue as to why on earth it should default to latin1
My guess: because an arbitrary input is valid latin1, but not necessary valid UTF-8. Mojca
On 2012-05-24 23:20, Mojca Miklavec wrote:
On Thu, May 24, 2012 at 11:09 PM, Philipp Gesang wrote:
It’s harmless and was always there. Have a look at the list in “noprefs.c” to see that my locale en_US.utf8 isn’t there.
I would say that the proper name *is* actually UTF-8, not "utf8".
True, some rogue setting in my .xinitrc caused the lowercased setting, now that I removed it the Fontforge complaint is gone. Thanks for being that attentive.
I don’t have clue as to why on earth it should default to latin1
My guess: because an arbitrary input is valid latin1, but not necessary valid UTF-8.
True, although I don’t think there’s many systems left still running a latin1 locale. Good night Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
On 05/24/2012 17:20, Mojca Miklavec wrote:
I would say that the proper name *is* actually UTF-8, not "utf8".
I don’t have clue as to why on earth it should default to latin1 My guess: because an arbitrary input is valid latin1, but not necessary valid UTF-8.
Mojca
As a data point, on my FreeBSD 9.0 systems the locale is indeed en_US.UTF8 not .utf8. Bill Meahan K8QN "The pessimist complains about the wind; the optimist expects it to change; the realist adjusts the sails." -- William Arthur Ward
participants (3)
-
Bill Meahan -
Mojca Miklavec -
Philipp Gesang