-
Notifications
You must be signed in to change notification settings - Fork 18
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
Font of keyboard layout not used in render #7
Comments
Hi At present KLE appears to render in Segoe-UI, at least in the layout I'm building ... no custom fonts. Apart from issue above, most characters are rendered in Bold in kle_render, but some, typically in the AltGr slots, are rendered in Regular. There is also a visual difference in sizing ... perhaps the mapping between kle's 9 sizes and pixel size here needs tweaking? Or is it just a consequence of the different fonts? Lastly, font colour seems a bit random ... this may be because of kle assuming some values are inherited from previous keys... thanks, Ian |
I've just added some limited custom font support in ba3eea6. Part of why I've hesitated to do this is that matching keyboard-layout-editor's behavior for this would almost certainly require using a browser engine to handle styling arbitrary HTML elements with CSS, since that's how custom fonts are specified. Reliably supporting just However, given that other people use this project, having some way to use custom fonts, even if it's inevitably unreliable, is probably better than nothing. Therefore, you can now use
You may need to fiddle a bit with quotes and other syntax to get your own CSS to work correctly. Hopefully, people using KLE-Render find this good enough to work with, despite the limitations. |
Hi I get a different font with Unicode keys. Any thoughts? Cheers! |
Kanit does not have a lot of glyphs .. you're getting some fallback font. |
The render uses its own font it seems. It doesn't take into consideration if a custom font is used for the layout. Regardless if the layout is provided via gist link or .json file.
The text was updated successfully, but these errors were encountered: