Hi !
Android 4.1 has a better glyph support for Japanese users (renders Japanese-specific versions of glyphs WHEN system language is set to Japanese).
I use a lot Japanese (reading / writing) and what see when system language is NOT set to Japanese is the Chinese glyphs characters instead of Japanese ones. Often those are the same as the Japanese glyph but in some cases they are not.
But if I set the system language to Japanese the glyphs are the good ones. So, it's not so convenient to set system language to Japanese every time I need to read or write in Japanese !
It looks to be done with a fallback fonts list that gets switched with the UI locale. Inside of /system/etc/ there are two XML files: fallback_fonts and fallback_fonts-ja. In the ja one the order of MTLmr3m.ttf font is placed before DroidSansFallback.ttf. The MTLmr3m.ttf file is the Motoya Japanese font and the DroidSansFallback.ttf is the fallback font that has the simplified Chinese glyphs.
The fix to allow Japanese instead of Simplified Chinese with a non-Japanese UI would be to copy the fallback_fonts-ja file to fallback_fonts. Before doing that it would be a good idea to copy fallback_fonts to something else like fallback_fonts.backup so that you could restore it later. However, before doing any of this you would also need to root your device since the /system directory can't be edited otherwise.
Click to expand...
Click to collapse
This is what I found (here => http://forum.koohii.com/viewtopic.php?pid=181580#p181580 ) and what I done.
I even tried to edit the fallback_fonts file to put MTLmr3m.ttf font before DroidSansFallback.ttf. But in any case, once I reboot my Nexus 7, the Japanese font are not read anymore (juste leaving blank).
Does anyone have a solution to use the MTLmr3m.ttf file (Japanese font) instead of DroidSansFallback.ttf without setting the system language to Japanese ?
Thank you !
I use Android in English but also need full Japanese support, to read and type. To achieve that, I replace Android's ( rather poor ) DroidSansJapanese.ttf with IPAPGothic and doing so I get a good proper font. Easy, just renaming IPAPGothic as DroidSansJapanese.ttf and putting it in :
/system/fonts/DroidSansJapanese.ttf
Then to avoid Android using the font DroidSansFallback.ttf, I replace as you mention the following file defining fonts with my own :
/system/etc/fallback_fonts.xml
I don't touch anything else and it works for me on 4.1 and 4.1.1. Android uses IPAPGothic for Japanese in my devices and DroidSansFallback.ttf for other languages needing glyphs. I also replace DroidSansFallback.ttf with a better font that supports full Traditional Chinese and Korean, by the way.
Here's the fallback_fonts.xml file I use in case you want to check it or use it directly. ( If so, rename .txt to .xml and also remember to make sure permissions for the files you put in system/ are rw-r--r-- )
Hope it helps.
Edit : this is a bit of a hack to preserve naming from Android 2.2 and 2.3 ( DroidSansJapanese.ttf as it is called in those versions ) and don't erase the MTLmr3m.ttf font in Android 4 in case I need it for anything or Google changes something later on, but again, it works for me, so maybe worth a try.
When I took a look at your fallback_fonts.xml, I saw that you put the DroidSansJapanese.ttf at the top of the "list".
And when I tried the solution I explained in my first post, I put it just before DroidSansFallback.ttf at the end of the list.
So I thought I could try to put MTLmr3m.ttf at the top and let DroidSansFallback.ttf at the end of the list. (yes, I wanted to use MTLmr3m.ttf, because it was done for Japanese people... so it's sound good for me^^).
A reboot later and the right Japanese font / glyph (not the Chinese one) was used by the system in every apps !! :victory:
Thank you Ultramanoid, you really helped me ! :good:
Thank you very much, Ultramanoid!
I now have hopes to make Taiwanese-specific kanjis work.
Related
I managed to extract the greek language files from another rom and I want to change my phone's (with new cingular rom), interface language to greek. The singular rom has only english. I copy the greek mui files to windows folder and I change some registry settings to include the greek language. I managed to have the greek T9 and, after an authedication message a mui file loaded and some of the menu entries( a few) changed to greek. Speecifically in settings menu I have the 4th entrie: Extended screen and in more... 7th 9th 9th entries in greek, but all the others in english.
This if I understand well, I think means that a greek mui file is registered and loaded, but all the others don't. Of course must do something more to fully change the interface, but I dont know what to do.
Any help or directions will be appreciated.
Thanks!
EDIT:
After a little farther research I found that some of the greek exe.mui files loaded and all these programs are full translated. But the dll.mui files I don't know how to test them. Some programs, like commanager, sim manager, camera, work, but the user interface like start menu and softkeys, and programs like WMP dont.
I think it doesnt work because some of the system files are stored in the ROM (read-only) of the device. You cannot overwrite these files or change some values on the ROM so imho thats why it doesnt work 100%.
Sollution is edit the ROM and flash it... but its not possible yet.
I know that it's no possible to flash the rom yet, but I read today in the forum that it's possible to flash only the os.nb. Maybe I will try it, but cause all these tools here are for other devices I don't know what to use. I used the nbhextract tool and core kitchen to extract the mui files, and I take them from the dumped directories. Maybe I can put them in the cingular os.nb and flash only this. But I did for first time this and I'm a little bit confused with all these different tools, roms, devices, and procedures.
Hi to all,
my system font (like in the volume tab) is different form the stock ROM. I've searched forum for "system font", and read few of them, but noone mentioned the issue. can I change the system font somehow?
Thns
Search for NueFont
Thx... I didn't know, what am I looking for
Tried looking for Nuefont, but found nothing usefull. Are you sure it is NueFont?
I Have this font only when i'm changing volume...
If you're using a ROM which does not include Manila (or includes a custom version of Manila), you might be missing some font files (encoded in the _manila files). You can simply add the font files back into \Windows\Fonts (and not worry about the _manila files) in order to restore the fonts, but you'll need to know specifically which font the application is trying to use.
For the HTC Diamond-style volume changer and USB2PC connection dialog, the fonts needed are "HelveticaNeue LT 35 Thin" and "HelveticaNeue LT 55 Roman" (again which should be loaded properly if you're using Manila). I've attached them in the zip, so drop them into your \Windows\Fonts folder (no need to change the filenames) and see if that fixes the issue.
FONT
Thanks for help, however it didn't help. I've copied the font in win dir, in win\font dir... nothing happend. I've got advice to look in the registry in HKLM\sofware\MS\fontlink\systemLink, if there is two values... there was just one, so I filled the second one. Didn't helped...
Don know what to do...
nuefont will let you change the system font. you'll find it here http://www.nuerom.com/BlogEngine/page/nueFont.aspx
Thanx a lot.
Just in trouble to handle CJK fonts in PROven-3.1 rom.
DANDANA said:
nuefont will let you change the system font. you'll find it here http://www.nuerom.com/BlogEngine/page/nueFont.aspx
Click to expand...
Click to collapse
I am aware that there are other ways to edit the fonts on our phone, by replacing renaming the default font. This is NOT what I would like to accomplish.
Since the Galaxy S is the first android phone to use Flipfont, I think we should take advantage of it. It gives us a nice preview of the font in the built in menu option and is thus superior to the other methods.
I originally purchased the Bauhaus font from the market and made a backup of it through ASTRO. After pulling the file from my phone and putting it on the computer I started editing the file with Apk Manager 4.8 found here
Steps preformed
Copied original apk into place-apk-here-for-modding folder
Run script.bat and choose option 9 ***this maybe where the issue is as I may need to choose option 10 and include the dependancy if there is one for the flipfont apk.
replace bauhaus.ttf with a .ttf font of my choosing
edit all XML, yml and smali files to include the font name or font.ttf depending on the entry in the original file *** I did not change any of the other coding so again this maybe where the problem is, as I may need to change something else to have the font act properly.
Edit the last folder name in the smali folder tree from bauhaus to the name of my font
Replace font with custom font and replace the preview image with my own
Compile apk
Sign apk
Rename apk
install apk on my phone
After putting the apk on my phone and installing the file it shows up as expected in settings>Sound and Display>Font style. The font thumbnail shows up properly as does the font preview. The preview does show up a little larger then the other fonts and may be a sign that the font is not optimized properly or that I missed something in the XML.
After applying the font and restarting, the phone is extremely slow and the font does not show up, it shows the default font instead.
If anyone that knows more about XML or apk editing/creation can help it would be great.
I have included the edited font apk if you would like to download it and run it through Apk Manager 4.8. If you want to try it with the bauhaus or one of the other fonts you will need to buy it from the market and back it up. (trying not to break any rules here.)
CAUTION THE FOLLOWING FILE IS NOT MEANT FOR USE AND WILL CAUSE YOUR PHONE TO RUN SLOW!!!
Download Font APK
here is my contribution to the fonts package. I find these to be usable fonts in the Vibrant Android system.
When you wrote the apk and after installing a font, how it had slowed down the system on you and didn't change the font, well did you try writing a different font into it? i ran into a couple of fonts that said were applied using typefresh, but when the phone rebooted, it was just slow, and had gone back to the default system font.
renegadedj said:
here is my contribution to the fonts package. I find these to be usable fonts in the Vibrant Android system.
When you wrote the apk and after installing a font, how it had slowed down the system on you and didn't change the font, well did you try writing a different font into it? i ran into a couple of fonts that said were applied using typefresh, but when the phone rebooted, it was just slow, and had gone back to the default system font.
Click to expand...
Click to collapse
Well I have tried two different fonts so far, both .ttf and they both caused the system to slow down/hang when applied and restarted.
I will try some of the fonts you supplied and see if it makes a difference.
There must be something about certain fonts that causes the problem. I need to see if I can track that down as it will be important for writing the tutorial.
[EDIT][More info] Ok I took a closer look at the font that came with the Bauhaus akp
In the discription of the font it list:
OpenType Layout, Digitally Signed, TrueType Outlines
I know that opentype is a new format and that alot of the fonts for OpenType that I find are made by Monotype, the same people that make the fonts available for download. I think this may have something to do with it or maybe Im just grasping. :ºp
ritalin said:
Well I have tried two different fonts so far, both .ttf and they both caused the system to slow down/hang when applied and restarted.
I will try some of the fonts you supplied and see if it makes a difference.
There must be something about certain fonts that causes the problem. I need to see if I can track that down as it will be important for writing the tutorial.
[EDIT][More info] Ok I took a closer look at the font that came with the Bauhaus akp
In the discription of the font it list:
OpenType Layout, Digitally Signed, TrueType Outlines
I know that opentype is a new format and that alot of the fonts for OpenType that I find are made by Monotype, the same people that make the fonts available for download. I think this may have something to do with it or maybe Im just grasping. :ºp
Click to expand...
Click to collapse
well you may be on to something, because TypeFresh does not allow me to see ANY OpenType Fonts (.otf) and only TrueType. :-D
Ok so I was curious and did a little test. I took the bauhaus font from the apk and opened it up in FontCreator 5. I then took on of the fonts that had previously given me an issue and opened it up as well. Then I copied all of the fonts for each key from the problematic one and replaced the fonts in bauhaus with them. I saved the file with a new name and then went through all of the steps to create the APK file.
After the file was installed, I selected it and then rebooted. HAZA, it works. Well it kinda works. The font size is way too big, and its still running slow. I have a feeling that the proformance hit is caused by the size of the font.
I am going to resize all of the letters, numbers and symbols in FontCreater and try again. Will post back with results.
Few steps forward, few steps back.
First off I will say that the font is a little hard to read and too light, but this is just for testing so its not that big a deal right now.
Ok so I got hold of a font that about the same size as the Bauhaus font. After doing everything in the above posts and installing the font, the restart was a LITTLE bit faster. It still seems to choke for about a minute or so after the desktop first appears and the pass based lock screen is sometimes unresponsive on first try. Overall its running much better, but still not perfect.
Also some words see to get clipped off for no reason as you can see in the image attached on the text for the Astro bluetooth icon. Not sure why this is happening.
Use Morelocale 2 from Market for additional languages in bulds that lacks your language.. I found my, serbian, lang there. Great work.
mcdoc said:
Use Morelocale 2 from Market for additional languages in bulds that lacks your language.. I found my, serbian, lang there. Great work.
Click to expand...
Click to collapse
Thanks. But you do know a way to fix arabic support? Eventhough I can chose arabic, the letters are detached.
Thanks
I applied the following to AmeriCanAndroid r3.06 and it worked for me. Try it and tell us if it works for other roms.
For Arabic letters messing up at the beginning of some words check out the following links that fixed the problem for me. Just follow the instructions carefully and good luck.
Arabizer files: (You will need to recopy these files after each rom update)
http://www.ce4arab.com/vb7/showthread.php?t=300641
Then install any Arabic supported keyboard of your choosing. MultiLing Gingerbread Keyboard with the Arabic plugin is my favorite at the moment but this one is also good:
Arabic Gingerbread Keyboard:
http://forum.xda-developers.com/showthread.php?t=935789
MultiLing Gingerbread Keyboard:
https://market.android.com/details?id=com.klye.ime.latin&feature=search_result
All credit goes to the individual developers; Great work everybody!!
alqali said:
I applied the following to AmeriCanAndroid r3.06 and it worked for me. Try it and tell us if it works for other roms.
For Arabic letters messing up at the beginning of some words check out the following links that fixed the problem for me. Just follow the instructions carefully and good luck.
Arabizer files: (You will need to recopy these files after each rom update)
http://www.ce4arab.com/vb7/showthread.php?t=300641
Then install any Arabic supported keyboard of your choosing. MultiLing Gingerbread Keyboard with the Arabic plugin is my favorite at the moment but this one is also good:
Arabic Gingerbread Keyboard:
http://forum.xda-developers.com/showthread.php?t=935789
MultiLing Gingerbread Keyboard:
https://market.android.com/details?id=com.klye.ime.latin&feature=search_result
All credit goes to the individual developers; Great work everybody!!
Click to expand...
Click to collapse
Thanks man. But i was not able to push those files for some reason. I had root.
Any idea of a flashable ZIP or maybe a simple APK?
Before I continue please note that I had nothing to do with the development of any of these or other files. I just found them and they worked on my device to fix the discussed problem. Therefore the best advice you can get would come directly from the developers of the files themselves.
That being said, I will describe what I did in order to get them to work for me.
1) follow the link to the ce4arab website (in my previous post) and register (free) in order for the download files to be visible and downloadable. Note: website is completely in Arabic.
2) Download and extract the 3 files in the compressed file. When you extract the files they will be in folders that refer to the exact folders to be moved to on the phone's root. For example root/system/framework/framework.jar
3) Running Android, connect your HD2 to the computer and copy these files to the phone's SD card (doesn't really matter where). Then disconnect your device.
4) Now run Root Explorer (download from the market or somewhere else) which will enable you to move these 3 files from your SD to the phone's root. Each file goes to the specific folder on the root. Note: Just to be on the safe side, I backed up my existing root files (just copied them somewhere on the SD card) before I overwrote them with these modified files.
5) Now reboot and install your preferred Arabic enabled keyboard.
Note: after any rom update you will need to repeat this procedure again.
Thanks goes out to all the great developers for this great device.
Ya I know that, but I simply wasnt able to move the file using root explorer because there was already existing files and for some reason, I was not able to overwrite the files (although I have root).
Thanks anyways.
I really don't know why you are unable to overwrite the files. The only thing I can think of is that Root Explorer doesn't have superuser permission on your device. So it is stopping you from overwriting system files. Different roms deal with this differently so first try the general superuser permission fixes (google these) and if that doesn't work, include the name of the rom you are using into your google search words. I am running AmeriCanAndroid 3.06 and Root Explorer was granted superuser permission automatically. So I am guessing that your rom handles this differently.
Note: Superuser is an app that enables you to grant special permissions to specific apps. It should be in your app tray.
I am trying to change my default font to one that will read a number of diacritical characters not covered by the default Nexus 7 system font. I have read a number of threads that offer advice that seems incomplete and am looking for someone's list of actions that will definitely do this job or that can point me to a definitive guide to doing this.
My tablet is rooted, running 4.2.2. I have been downloading apps and fonts:
ASK keyboard to show these characters,
Font Installer and
Type Fresh,
ASK Pali font file,
DroidSansFallback.ttf and
Dejavu-fonts-ttf-2.33.
I had not looked into /system/fonts before now so I have nothing to compare its present population with, but it contains 41 .ttf files (Roboto, Droid and some others) and I have 21 Dejavu fonts waiting to be moved there!
I understand the default font is 'Roboto', but
what font will do what I want (have all diacritics)?
Will I need to swap between them in the normal course of events, and how?
Or rename some font to replace the default?
Is there a modifiable config file that names the default file?
Thanks for reading this far!
But what happened? Font Installer doesn't work for you?
RoberGalarga said:
But what happened? Font Installer doesn't work for you?
Click to expand...
Click to collapse
The bottom line is that all the Droid (and Roboto) files are in /system/font but the (originally missing) diacritic characters are not accessible via the ASK keyboard which show only squares when pressed appropriately.
I have loaded the Droid, Dejavu and Roboto fonts into my Mac and opened them via its Font Book app. When installing 'Roboto', the Font Book reported an error: it was a duplicate of Droid Sans Fallback, so it seems that that is what Font Installer does. Pity this is not made clear.
The required characters are in there, it seems, but are not found by the keyboard. I'll contact the developer thereof now (he groaned).
Thanks for the nudge!