There is one character missing from the default font: U+A9CF - pangrangkep.
How could I show this character other than by using bitmap image?
The same character as image. (bad resolution, too small? what’s the best size?)
Some users might also want the displayed font to be the standard font in their local area, which are different depending on the region, due to the sheer size of people who uses this script. Certain font might not be acceptable in some area. (on-screen keyboard and touch layout) How do I change both fonts in the on-screen and touch layout?
In touch layout, setting the keyboard font and display font in the package file (.kps) doesn’t change the displayed font when i tried it in the Android app. I’m using the latest version (21 March 2021, i think). Why?
This is a newer version of the default font for Javanese Sccript in Android. but i still see the default font.
I don’t have problem with the touch layout, actually, but on-screen keyboard. and strangely U+A9CF showed up correctly in touch without changing anything. maybe because it defaulted back to Windows’ Javanese Text
shown under longpress
doing as you suggested, indeed changed the touch layout’s font, but not the osk.
also the third option: touch layout - desktop was greyed out without explanation.
On Windows, the font has to be installed in order for it to be used in the On Screen Keyboard. Normally, you’d include the font in a package and it would be installed as part of the keyboard package. I’m not sure if that’s what’s going on here or not?
Are we talking about 1) the missing U+A9CF in the default font in Keyman Developer, 2) changing fonts in osk and touch, 3) setting keyboard and display font in .kps and compile it doesn’t have any effect on mobile (Android), or 4) others?
Changing Keyboard Fonts > Keyboard Properties > OSK’s Font size doesn’t seem to change anything in the developer. I changed it to 8 pt, 16 pt, all the same. Is this intended?
I don’t want to change the font in the Latin layers, just the Javanese script layers. I don’t think this is possible, does it? Many fonts that could display nice Javanese scripts have bad / incomplete Latin sets.
Also, does changing the font here affect the .kmn file, or just me / my Keyman Developer?
I was responding to (2) the issues with changing fonts in OSK. The OSK and the touch layout currently have separate implementations and font controls are different for the two.
Fonts are always a bit of a struggle. Every time I work on the fonts, I run into different consistency issues across platforms. The ideal is to include a font in the keyboard package and refer to that font in OSK and the touch layout definition, as well as ensure it is set correctly in the package details.
On Keyman Developer 14.0.270 stable, the font selected for OSK should reflect right in the Developer. To take a step further, you can compile the keyboard and then test install to see its effect.
The font selected for OSK will be for all layers in the OSK, not any specific one. More often than not, a keyboard is for a language and one font usually suffice. We do not recommend to have more than one language in one keyboard.
What is chosen for which should reflect so accordingly, if not, please help file a bug on our github. The desired font should be included in the keyboard package (i.e. .kps) just in case it does not exist in the OS on which the keyboard is being installed.
No, Javanese is one language with two (some might say three) written scripts. Some other languages in Indonesia have these duality too. Balinese, Sundanese, Bugis, Batak, etc. As well as non-Indonesian languages, such as Central Asian languages.
I changed the size from 10 to 20 to 100, to no effect, after being installed. I tested with Noto Sans Javanese as well as normal Latin font, such as Calibri. Does changing font size works for you guys?
We do not actually recommend having a keyboard that supports every script a language might use. We recommend one keyboard for a script such as Javanese (perhaps for multiple languages), but create another keyboard for the other script(s) used. That way your fonts can be geared for that one script AND you aren’t mixing language tags.