Comment 4 for bug 73211

Yes, the bug is only with the Unicode mapping. The 8-bit encoding
seems well-established and correct.

And I can confirm that this package still has this bug on my system :(

On 9/6/07, Arne Goetje <email address hidden> wrote:
> >From the README file:
> -----------------------------------------------------
> Additional letters
>
> The encoding of the fonts is based on the model of the Cyrillic Asian
> encoding. The Russian alphabet occupies the place of
> the Latin-1 supplement in the Western (Windows CP 1252) encoding and its
> own Unicode positions in the Cyrillic (CP 1251) encoding. Additional
> Uralic letters can be found in three places - instead of additional
> characters in the Western encoding, instead of additional characters in
> the Cyrillic encoding and in their own Unicode positions (with the
> exceptions of those letters that are not found in this standard).
> Existing Mari and Udmurt fonts were taken into consideration while
> distributing positions, but incorporating their encodings did not prove
> possible. Eventually, Udmurt fonts were used as the starting point. See
> the test page for details.
>
> ----------------------------------------------------------------------------
>
> These fonts are for Uralic languages only! So, don't use these fonts for any other purpose.
> I will nevertheless contact upstream and propose a fix. IMHO the fonts have been wrongfully encoded and are therefor broken. Even when used in a Unicode environment, additional Cyrillic characaters should only show up in the U+00A0 - U+00BF range. At least, that's the mapping of CP1251 to Unicode.
>
> ** Changed in: ttf-uralic (Ubuntu)
> Assignee: (unassigned) => Arne Goetje
> Status: Incomplete => In Progress
>
> --
> MonoUralic contains incorrect encoding information
> https://bugs.launchpad.net/bugs/73211
> You received this bug notification because you are a direct subscriber
> of the bug.
>