lukeme / gobible

Automatically exported from code.google.com/p/gobible
1 stars 0 forks source link

Displaying words longer than the phone display width - losing a letter at the breakpoint #71

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Someone has noticed that the problem of displaying long words is also a
problem on some Nokias - they lose a letter at the break point. So maybe
this is a problem with how Go Bible handles long words - rather than with
the Nokia or Sony Ericsson firmware. 

Having long words break at strange points is fine - but loosing a letter is
something that would be nice to fix if possible.

Original issue reported on code.google.com by DFH...@gmail.com on 4 May 2009 at 1:03

GoogleCodeExporter commented 8 years ago
I have confirmed that this bug can be reproduced, even for the KJV Go Bible, 
when
displaying Isaiah 8:1 using (for example) the Sony Ericsson K750i mobile phone.

In medium font, the name "Maher-shahal-hash-baz" is displayed correctly.
In large font, the breakpoint occurs after the first hyphen, and the next 
letter "s"
is missing. Viz.

1 Moreover the LORD
said unto me, Take
thee a great roll, and
write in it with a man's
pen concerning
Maher-
hahal-hash-baz.

This must be a software bug in GoBibleCore.

Original comment by DFH...@gmail.com on 9 May 2009 at 8:49

GoogleCodeExporter commented 8 years ago
This issue should be addressed for the next update to GoBibleCore.

Although the English Bible has few such long words, other translations do have 
more,
especially in Russian and German language Bibles (for example).

Original comment by DFH...@gmail.com on 9 May 2009 at 8:53

GoogleCodeExporter commented 8 years ago
The above typo' was mine!  The name should be "Maher-shalal-hash-baz".

Isaiah 8:3 repeats the long name, and the breakpoint there occurs just before 
the
last hyphen, with the letter "h" being omitted. Viz.

name
Maher-shalal-has
-baz.

Original comment by DFH...@gmail.com on 9 May 2009 at 10:17

GoogleCodeExporter commented 8 years ago
Dan has developed a fix for this, but it is not yet checked in.

Original comment by DFH...@gmail.com on 11 Nov 2009 at 8:07

GoogleCodeExporter commented 8 years ago
I confirm that this issue has been fixed in forthcoming version 2.4.0

Original comment by DFH...@gmail.com on 8 Dec 2009 at 2:59

GoogleCodeExporter commented 8 years ago

Original comment by DFH...@gmail.com on 8 Dec 2009 at 3:01