Menu

#614 Wrong rendering of Cyrillic texts

Next release
closed-accepted
5
2021-04-20
2021-04-17
Lalex
No

Hello.

Error occurs with the following version:

Version: 2.1.3
Compiler: GNU GCC 9.3.0
Compiled on: Mar 23 2020
Qt Version: 5.12.8
Boost Version: 1.71.0
System: Linux Mint 20.1

Error description (if it is an error):

Only three fonts (unicode, wgy-unicode, cyrillic_ii) show correctly Russian (Cyrillic) text on the working area. All other fonts draw rhombuses instead. (see image)

Additionally, I also converted other fonts with the ttf2lff utility and set paths to them in the settings, but they have the same problem.

The program supports only these three fonts in Russian (Cyrillic)?
How can I solve this problem?

Thank you for your help.

1 Attachments

Discussion

  • LordOfBikes

    LordOfBikes - 2021-04-18
    • labels: Cyrillic, Cyrillic texts, fonts --> Cyrillic, Cyrillic texts, fonts, lff
    • summary: Wrong randing of Cyrillic texts --> Wrong rendering of Cyrillic texts
    • assigned_to: LordOfBikes
     
  • LordOfBikes

    LordOfBikes - 2021-04-18

    We recently found out, that upper case letters in the font file name makes the font unusable.
    So first should be to rename converted font files to lower case only.
    There is also a very informative issue on GitHub about LFF fonts:
    https://github.com/LibreCAD/LibreCAD/issues/1252

    The rhombus is used when the character code for a letter wasn't found in the font file.
    Thus when renaming the font files doesn't solve the issue, there are no glyphs in the font file for the used character codes.

     
  • Lalex

    Lalex - 2021-04-20

    Thanks for the help.

    The following helped me:
    I renamed two supplied fonts (what were important for me) to lowercase: opengosttypea-regular.lff, opengosttypeb-regular.lff. These two funds were already installed with librecad. For all others I did it directly before conversion.
    Unnamed and new converted fonts work.

    Thanks a lot.

     
  • LordOfBikes

    LordOfBikes - 2021-04-20

    Great to hear that.
    Many thanks for reporting and confirming the workaround.

     
  • LordOfBikes

    LordOfBikes - 2021-04-20
    • status: open --> closed-accepted
     
  • LordOfBikes

    LordOfBikes - 2021-04-20

    I close the ticket, we track this issue already on GitHub.

     

Log in to post a comment.

MongoDB Logo MongoDB