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

Attachment: pgpUhiZflRkPr.pgp
Description: PGP signature

___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to