Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.1
-
Fix Version/s: 4.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:-
-
Assignee Priority:P2
Description
A customer reported the following issue:
***************
DecimalFormat for sk_SK locale returns the number "1,000.00" formatted as "1 000,00" with 0xa0 (no-break space) as a decimal group separator. IcePDF v4.1.0-pro (and also the other versions) library has problems with correctly displaying this character (it shows it, perhaps, as two space characters) while the Acrobat Reader shows the PDF file with such a number correctly.
So we have to use force here to convert all 0xa0 characters in the resulting formatted string to 0x20 (space) so that they were handled correctly with the IcePDF library.
http://www.fileformat.info/info/unicode/char/a0/index.htm
In addition, this bug occurs only when the Java SansSerif font is used and it occurs on both, Windows and Linux, systems.
***************
However, I am unable to verify the issue with 4.1.1 Pro since the PDF does not display correctly. Instead of seeing 65 536,00 displayed in the PDF, I only the see the number 6.
***************
DecimalFormat for sk_SK locale returns the number "1,000.00" formatted as "1 000,00" with 0xa0 (no-break space) as a decimal group separator. IcePDF v4.1.0-pro (and also the other versions) library has problems with correctly displaying this character (it shows it, perhaps, as two space characters) while the Acrobat Reader shows the PDF file with such a number correctly.
So we have to use force here to convert all 0xa0 characters in the resulting formatted string to 0x20 (space) so that they were handled correctly with the IcePDF library.
http://www.fileformat.info/info/unicode/char/a0/index.htm
In addition, this bug occurs only when the Java SansSerif font is used and it occurs on both, Windows and Linux, systems.
***************
However, I am unable to verify the issue with 4.1.1 Pro since the PDF does not display correctly. Instead of seeing 65 536,00 displayed in the PDF, I only the see the number 6.
There are always a pain the debug. I couldn't find anything wrong with how we where encoding the font. The only work around I could fine was to update the encodingLatin.txt encoding file to have a new entry for space where 240 octal is assigned across the board (win, mac etc.). This address the missing width problem assigning the space width rather then the default font width.
Marking as resolved.