Folder /Fonts at device system directory is used to quickly install custom fonts for Android apps like FBreader, and Mobi's OfficeSuite. Hopefully, an LO editor/viewer on Android will also support the installation of fonts at this directory.
In order to do this do you need a rooted device? Can you explain a bit more how you add fonts this way and on what device you do it? Setting to NEEDINFO - once you provide the info please set to UNCONFIRMED. Thanks!
Setting this one as enhancement.
(In reply to Joel Madero from comment #1) > In order to do this do you need a rooted device? Can you explain a bit more > how you add fonts this way and on what device you do it? > > Setting to NEEDINFO - once you provide the info please set to UNCONFIRMED. > Thanks! No need to root to enable this feature in FBREADER and OfficeSuite, so I assume LO can be configured to have this feature without rooting. Basically, one creates this font folder called Fonts at the home directory of the device add you can add to otf and ttf fonts to the folder and they will be read by the app. No need to root.
(In reply to miggoycor from comment #3) > No need to root to enable this feature in FBREADER and OfficeSuite, so I > assume LO can be configured to have this feature without rooting. > > Basically, one creates this font folder called Fonts at the home directory > of the device add you can add to otf and ttf fonts to the folder and they > will be read by the app. No need to root. Seems like a plausible mechanism to add more fonts to an Android device. I'll toss this enhancement in NEW for now and let the devs make the final call on whether following the same convention as FBREADER and OfficeSuite is a good, bad, or ugly idea ;-)
To help with thinking about this, real users need some way of co-ordinating their fonts across platforms. Thus my standard font set must be available across all of my devices. This is easy to achieve on a Linux box (or other OS box) but not readily achievable on a non-Samsung Android device which has not been rooted. The /Fonts folder is readily user accessible.
/Fonts path is *definitely NOT* accessible to normal user without root. In fact, such a path does not exist and cannot be created without (a) modification to ramdisk, (b) some filesystem to actually mount there (could potentially be a bind mount). Most likely, user suggesting this path actually means subdirectory "Fonts" within external storage, which is likely available at /storage/emulated/{user id}/
*** Bug 109114 has been marked as a duplicate of this bug. ***