search

mjdenham2 / and-bible

Automatically exported from code.google.com/p/and-bible
0 stars 0 forks source link

fonts.properties only works for modules with uppercase names #126

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
See emails sent to developer.

#BookInitials=fontname (either ttf or otf)

This works only for modules with uppercase names such as SBLGNT.

It didn't work for a module name with lowercase letters, such as Yoruba.

I had to change the module name to YORUBA to get the manually installed font to 
work.

Original issue reported on code.google.com by DFH...@gmail.com on 28 Oct 2012 at 9:46

GoogleCodeExporter commented 9 years ago 
I would like to investigate and fix this before the next release, so you 
hopefully you won't need to alter any module names.

David, if you send me font files (if re-distributable) and language codes I can 
put them into the central fonts properties file for automatic distribution.

Original comment by mjden...@gmail.com on 30 Oct 2012 at 10:31

GoogleCodeExporter commented 9 years ago 
Martin,

Some fonts specified in our module conf files may be free to use, but not 
re-distributable.

http://crosswire.org/wiki/Fonts lists various source for fonts.

Most of these you can download yourself.

I will email you the Antioch fonts that Steve Hyde sent me for displaying Khmer.

Attached is a list of fonts found in module conf files.

This information is from the repositories in my Xiphos InstallMgr.
I have most repositories covered, including those in beta and av11n, etc.
I have also included some modules that I have not yet submitted for release.

Duplicate lines have been removed.

David

Original comment by DFH...@gmail.com on 1 Nov 2012 at 3:46

Attachments:

GoogleCodeExporter commented 9 years ago 
See also 
http://crosswire.org/wiki/Talk:Localized_Language_Names#Xiphos_languages_file

Original comment by DFH...@gmail.com on 1 Nov 2012 at 3:48

GoogleCodeExporter commented 9 years ago 
Xiphos languages file is attached.

Original comment by DFH...@gmail.com on 1 Nov 2012 at 3:50

Attachments:

GoogleCodeExporter commented 9 years ago 
Just a further thought....
There may be some modules in our repos that do require a non-default font, yet 
the module devloper may not have specified a font in the conf file.

I.e. through ignorance or laziness.

Original comment by DFH...@gmail.com on 2 Nov 2012 at 3:06

GoogleCodeExporter commented 9 years ago 
I didn't plan to take all the fonts from the Sword list because sometimes 
Android fonts are better e.g. Hindi in Android 4 and sometimes non-existent 
e.g. Arabic in Android 2.

So if somebody with Android tests and decides that a certain font is required 
then I can configure it centrally.  Experienced users can always configure 
their own manually.

However, 'things change' in every Android release and font support is always 
being improved.

Original comment by mjden...@gmail.com on 2 Nov 2012 at 3:47

GoogleCodeExporter commented 9 years ago 
Hi David,

I can't reproduce this problem.  I am testing with NETtext because it has a 
mixed case name and it is working fine.

Here is my fonts.properties:
NETtext=SBL_grk.ttf

Then for a bit of fun I thought I would try:
NETtext=KOMTXT__.ttf
with this font: http://www.fontsquirrel.com/fonts/download/Komika-Text

Could there have been a problem with your configuration?  Could you try again 
using your mixed case module or is there something else you can suggest for me 
to test?

I have attached a screenprint of NETtext with a komika font - it looks pretty 
cool.

Martin

Original comment by mjden...@gmail.com on 10 Nov 2012 at 4:49

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Martin,

The original problem that prompted this issue was that I found no way to get 
the Yoruba module (that I've been developing) to work with the Linux Libertine 
font, so I simply followed your advice on both counts. First I tried with the 
added font, and without renaming the module to YORUBA. That didn't succeed, so 
then I tried with the name made uppercase. That did.

It's quite conceivable that something is rather unusual with how And Bible is 
configured in my tablet. For example, the path where these things are stored 
makes no reference to JSword, unlike the name of the directory given in 
FontFramework. (viz. sdcard/jsword/fonts )  On my system, the fonts path is 
this:

/mnt/sdcard/Android/data/net.bible.android.activity/files/fonts/ 

btw. After I first installed And Bible and other apps, sometime later I 
inadvertently re-formated my internal SDcard, thus necessitating the 
re-installation of all the apps I'd previously installed. Doh!

If your source code makes no reference to "net.bible.android.activity" as part 
of a path, then perhaps there is some strange effect as a consequence either of 
my tablet being a Storage Options Scroll Excel 7, or maybe the above mentioned 
app re-install?

Have you too tried displaying the KhmerNT module without having to make the 
module name uppercase?  i.e. by installing the Antioch Normal font, and 
specifying:

KhmerNT=AntiochText.ttf

David

Original comment by DFH...@gmail.com on 11 Nov 2012 at 6:25

GoogleCodeExporter commented 9 years ago 
The first documents I installed in And Bible were various English Bibles, 
including the KJV and the NETfree. These were followed by some French Bibles 
(as I can easily read French), and then examples from several more languages, 
including those modules which Peter & I had a hand in making, which use 
Arabic/Persian script.

Original comment by DFH...@gmail.com on 11 Nov 2012 at 6:31

GoogleCodeExporter commented 9 years ago 
David,

You shouldn't be using the sdcard/Android folder as that is updated by the app. 
 You should only make changes under sdcard/jsword.

Martin

Original comment by mjden...@gmail.com on 12 Nov 2012 at 4:17

GoogleCodeExporter commented 9 years ago 
I have tested the following fonts.properties for the KhmerNT module and it 
seems ok to me, not knowing Khmer.  Can you tell me if the attached screenshot 
looks fine - if it does I will update the default fonts.properties and 
distribute the ttf automatically so people will always use AntiochText.ttf with 
any Khmer module.

Here is the property in my fonts.properties:
#Khmer
km=AntiochText.ttf

See attached screen-print.

Best regards
Martin

Original comment by mjden...@gmail.com on 17 Nov 2012 at 2:04

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm no expert in Khmer - but it looks pretty good to the untrained eye.

And the font comes from the same stable as the Bible translation, so I imagine 
Steve Hyde will be delighted.

David

Original comment by DFH...@gmail.com on 21 Nov 2012 at 10:26

GoogleCodeExporter commented 9 years ago 
I eventually configured automatic Khmer font distribution.  You may need to do 
Menu/Refresh in the Download Documents screen if you downloaded documents 
recently, but after the automated or manual refresh the Antioch font will be 
associated with Khmer modules automatically.

Original comment by mjden...@gmail.com on 5 Dec 2012 at 9:08

GoogleCodeExporter commented 9 years ago 
I confirm the solution works OK even after I removed my local copy of the font 
& edited fonts.properties accordingly.

Original comment by DFH...@gmail.com on 5 Dec 2012 at 9:54

GoogleCodeExporter commented 9 years ago 
Are you planning to do likewise for [say] the Padauk font in connection with 
the BurJudson module?

Original comment by DFH...@gmail.com on 6 Dec 2012 at 9:40

GoogleCodeExporter commented 9 years ago 
Is the font re-distributable?  Is it tested using manual override?  Can you 
send me the font?

Original comment by mjden...@gmail.com on 6 Dec 2012 at 10:31

GoogleCodeExporter commented 9 years ago 
See http://crosswire.org/wiki/Fonts#Burmese.2FMyanmar

Padauk is released under the Open Font License.

Original comment by DFH...@gmail.com on 6 Dec 2012 at 1:14

GoogleCodeExporter commented 9 years ago 
I also confirm that fonts.properties in jsword\fonts does work properly for 
modules with mixed case names.

Original comment by DFH...@gmail.com on 6 Dec 2012 at 7:20

GoogleCodeExporter commented 9 years ago 
You asked, "Is it tested using manual override?"

Answer = Yes.

This is in the jsword\fonts folder.

My fonts.properties file now looks like this:

#BookInitials=fontname (either ttf or otf)
#fontname.fontSizeAdjustment=n (to make characters larger or smaller when 
fontname is used)

Yoruba=LinLibertine_Rah.ttf
BurJudson=Padauk.ttf

Original comment by DFH...@gmail.com on 6 Dec 2012 at 7:22