Open GoogleCodeExporter opened 8 years ago
This is a feature of http://gbcpreprocessor.codeplex.com/
Go Bible Creator USFM Preprocessor
NB. GoBibleCore does not include any procedures to make use of soft-hyphens.
Original comment by DFH...@gmail.com
on 12 Nov 2009 at 2:13
Before the processing of the SOFT HYPHEN (SHY) U+00AD can be added to the
GoBibleCore, there are more details that need to be defined on how it should
behave.
To quote the Unicode Standard, "A common default rendering is to insert a
hyphen
before the line break, but this is incorrect in many situations." This may be
acceptable for a first pass and if so it could be added to the current pending
changes that are in the wrapping code.
There are a couple of other Hyphenation code points defined in the standard and
how
those are to be treated also need to be determined.
Original comment by dhinton...@gmail.com
on 30 Nov 2009 at 11:09
During the past few days, I have been working again on the USFM files for the
Belarusian translation by Professor Vasilij S. Semukha. This is one of the few
translations I have come across for which the source text files contain a
significant number of soft hyphens.
Extracted from Character Frequency: (BabelPad)
00002D - HYPHEN-MINUS 901
0000AD SOFT HYPHEN 384
We therefore have an opportunity to progress this issue, providing we can
decide what (if anything) should be done to process soft hyphens in GoBibleCore.
One possible way forward would be to add a new item to the Go Bible
Preferences, so that the user can determine whether to hide soft hyphens when
they are present, or whether to overrule the normal behaviour of soft hyphens
and make them all visible.
UI-Show-Soft-Hyphens: (On|Off)
See also http://en.wikipedia.org/wiki/Soft_hyphen
Original comment by DFH...@gmail.com
on 5 Jul 2011 at 9:26
In my opinion, something like this does not deserve an additional UI option
and translation. Either we show soft hyphens or we don't. It *is* possible
to force GoBibleCore to handle soft hyphens as they are supposed to be
handled. The logic isn't hard, but obviously it would require more processor
cycles than what we are squeezing out of our mobile devices currently. It
isn't an either-or scenario.
This issue aside, what is your target for the next release of GoBible? I
know Java ME isn't exactly dead yet, but if we delay the next release too
long, it could be indisputably dead by the next release.
Original comment by daniel.s...@gmail.com
on 5 Jul 2011 at 9:54
Thanks for comments.
Let's target the end of your long vacation for releasing SymScroll and making
it trunk.
But first, I must get more actively testing it. See tow emails sent today.
I could also do with someone to lend me a touchscreen phone, so I'll ask around
at church.
Meanwhile, in regard to Java ME, ponder the famous quotation...
"The reports of my death have been greatly exaggerated." Mark Twain
and reread the post by our good friend Tim Jore
http://www.dsmedia.org/blog/global-church-does-not-have-smartphones-and-why-we-s
hould-care
Original comment by DFH...@gmail.com
on 5 Jul 2011 at 1:04
Original issue reported on code.google.com by
DFH...@gmail.com
on 23 Apr 2009 at 12:41