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 Free
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 "u
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 yo
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 la
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.
>
>
