Support for italics in scripture text, e.g. as for words supplied by the translators in the KJV

[GoogleCodeExporter]

Is there a technical reason why Go Bible does not [yet] support italics?

Is this a lacking software feature, or more to do with mobile phones
themselves?

At present, workarounds are needed if one wishes to identify words supplied
by the translators that are not in the original Hebrew or Greek, as
implemented in the KJV 1769.

Original issue reported on code.google.com by DFH...@gmail.com on 24 Feb 2008 at 4:49

[GoogleCodeExporter]

Jolon writes,

There is no real reason at all except that it just hasn't been implemented.

I was going to put it in there but just didn't!

GoBibleCreator uses a special byte to indicate when Christ's words in red start 
and
end. I was going to use a similar character for italics. It wouldn't be 
difficult to
implement if someone wanted to do it.

[email to DFHMCH]

Original comment by DFH...@gmail.com on 25 Feb 2008 at 5:20

[GoogleCodeExporter]

Does the relevant JSR in Java ME actually support italics?

Original comment by DFH...@gmail.com on 8 Dec 2009 at 4:08

[GoogleCodeExporter]

>>Does the relevant JSR in Java ME actually support italics?

I'm not sure what JSR you are refering to. The getFont method takes a style 
[plain, 
bold, italic or underlined] as one of it's parameters. If you want an Italic 
font 
you would just use the appropriate parameter.

Original comment by dhinton...@gmail.com on 8 Dec 2009 at 10:03

[GoogleCodeExporter]

Another possibility is to enclose added text in [brackets].

This would work even for scripts that use characters which do not have italics 
as a
font attribute.  e.g. Chinese, Devanagari.

This [workaround] had been done even for one of the Go Bible apps that I made.
It was done during preprocessing while file format shifting to obtain the ThML 
file
that I used with GBC.

One of the issues surrounding this is whether a particular Bible translation 
already
uses [brackets] for some other purpose.
In the "no" case, then clearly it's feasible, and in theory, it could even be
automated, as instructed by an optional setting in the collections file.
In the "yes" case, there is potential confusion to readers.  Further thought is
therefore required.

OSIS has proper tags to denote added words.
For translation changes, use the <transChange>...</transChange> container 
element.
USFM has a suitable tag too.

Original comment by DFH...@gmail.com on 3 Jan 2010 at 3:46

[GoogleCodeExporter]

Jolon made this comment in the wiki page GoBibleDataFormat.

However, special markup like Christ's words in red should be described here. 
Christ's
words in red begin with the Unicode value 0x01 and end with the same value. It's
possible that other values such as 0x02, 0x03, 0x04 and so on may be used for
italics, bold, headings, etc. in the future.

This proposed enhancement concept should be reviewed.

Likewise - the possible use of 0x09 (Horizontal Tab) for poetry indentation?

Original comment by DFH...@gmail.com on 21 Apr 2010 at 6:40

[GoogleCodeExporter]

Some Bible translations use SMALL CAPS for the translation of the divine name 
YHWH in
the Old Testament. This is not a parameter handled by getFont() in Java ME.

A workaround is therefore usually required at the preprocessing stage.
The workaround must depend on the underlying text.

Original comment by DFH...@gmail.com on 28 Apr 2010 at 1:04

[GoogleCodeExporter]

Just see this: http://easysby.multiply.com/journal/item/23/Go_Bible_KJV
or http://www.mediafire.com/?jxijjdjztt3 for version 2.40

Original comment by easy....@gmail.com on 12 May 2010 at 9:41

[GoogleCodeExporter]

Yes - that's a workaround, but not a solution.

A solution should be faithful to how the KJV standard printed edition (1769) 
uses
italics.

Original comment by DFH...@gmail.com on 12 May 2010 at 11:01

[GoogleCodeExporter]

FYI, Chinese translations use different text markings:
1. Names are underlined with a SOLID line.
2. Words added in by translators are underlined with a DOTTED line, instead of 
italicised.

We can use and need different ways of marking up the text. Italicising words 
may be the best option for KJV, (and in fact, KJV makes a distinction between 
italics and oblique) but we could also consider underlines, highlighting, 
different font colours...

Original comment by daniel.s...@gmail.com on 3 Aug 2010 at 3:15

[GoogleCodeExporter]

How is this now implemented in the symscroll branch?

cf. What you showed me during your visit.

Are these build properties or user preferences?

If the latter, what new UI strings relate?

David

Original comment by DFH...@gmail.com on 26 Apr 2011 at 8:22