Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong font is used #148

olcc opened this issue Jul 27, 2018 · 1 comment

Wrong font is used #148

olcc opened this issue Jul 27, 2018 · 1 comment


Copy link

olcc commented Jul 27, 2018

Hello, [cf.]

I recently learned how to build and use a custom font thanks to the documentation page:

I created a font called "MY_FONT" (in file "my_font.gds") and I used it successfully in a test file ("font_test.gds"). This means that I could insert a PCell, choose my custom font from the menu, and see that the graphic display is indeed using MY_FONT, because it is clearly different from the standard font. This worked as expected.


When I reopen the file, the font is back to the standard font!

  • The PCell parameter "Font" still indicates "MY_FONT", but it is not using that font. It uses instead the standard font.
  • This looks like a bug, can you test or tell what it wrong?

Best regards,

Olivier (Klayout version 0.25.3)

Copy link

Hi Olivier,

the issue is closely related to #139 where the same happened with libraries. The fix is very similar and will go into 0.25.4. The reason is that the font system is initialized after files have been loaded from the command line. Files that are loaded later don't have this issue.

So the workaround until 0.25.4 is simply: open the file with File/Open or File/Recent rather than from the command line (same as double-click on the file icon).

BTW: you can pull a pre-release build of 0.25.4 from or if you're on Windows. Please allow about one hour from the commit to the build.

Thanks for reporting this issue,


netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Sep 22, 2018
0.25.4          (2018-08-25):
* Bugfix: KLayout/klayout#121
       Issue with multiple reads of GDS2 layouts including PCells
* Bugfix: KLayout/klayout#134
       Error in cell.fill_region caused by big polygon with
* Bugfix: KLayout/klayout#139
       Libraries have not been reassigned when loading a GDS file
       from command line (does not happen on File/Open)
* Bugfix: KLayout/klayout#141
       Issue with RBA::QHostAddress (ambiguous overload) on Qt5
* Bugfix: KLayout/klayout#142
       Issue with RBA::RecursiveShapeIterator#region=
* Bugfix: KLayout/klayout#144
       The Salt package descriptions are not shown with Motif
* Bugfix: KLayout/klayout#148
       Wrong font is used
* Bugfix: KLayout/klayout#152
       Shapes#size reported a wrong shape count in viewer mode
* Bugfix: KLayout/klayout#153
       Application crash when editing guiding shape properties
* Bugfix: KLayout/klayout#155
       Program freezes after replacing nothing by something in
       Macro editor
* Bugfix: KLayout/klayout#157
       "Replace cell with ..." rejected cell names with a library
* Bugfix: KLayout/klayout#158
       Repaint issue on cell context
* Bugfix: KLayout/klayout#159
       Tech specific macros and DRC scripts were not shown in tech
* Bugfix: 8 bit indexed GIF images can be used for package icons now
* Enhancement: Provide a way to specify the type of a macro
       This feature is mainly useful for command line arguments.
       If you run KLayout with "klayout -b -r myscript"
       it will not be able to determine the type of macro without
       a suffix.

       You can now explicitly specify a certain type by
       giving the suffix implicitly like: "klayout -b -r myscript[rb]"
       This will read "myscript" but pretend it was "myscript.rb"
       and execute it as Ruby script.

       This feature is handy if you need to run a file with a
       specific interpreter but cannot modify the file name.
* Enhancement: Selection now shows PCell display names
       Before, the internal name was shown for instances
* Enhancement: There is an option in the View menu to show or hide markers
       Markers may hide layout under them. With this feature you can
       quickly disable all markers and the layout becomes visible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants