[jira] [Created] (FOP-2539) Apache PDF issue with Symbol.ttf
Sushmitha created FOP-2539: -- Summary: Apache PDF issue with Symbol.ttf Key: FOP-2539 URL: https://issues.apache.org/jira/browse/FOP-2539 Project: FOP Issue Type: Bug Affects Versions: 1.0 Environment: Windox, unix Reporter: Sushmitha I have Symbol.ttf, configured the same in config file. Symbol font is not applying properly. Please find the below details FOP version - 1.0 OS - Unix, Windows XSL-FO desc: Abcdefgh α β γ Result - the charcters are not displaying properly and they are not human readable format fop.xconf:- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009211#comment-15009211 ] Andreas L. Delmelle commented on FOP-2539: -- Please attach a minimal FO file that reproduces the issue on your end for further analysis. The most usual suspect, based on the description, would be an encoding issue. That is: the actual encoding of the symbol characters in the XML FO file does not correspond to the one that is specified (= UTF-8, if not explicitly set). We cannot see whether that is the case here if you just copy-paste a fragment into the issue Description. > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009834#comment-15009834 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 11:41 PM: - Having a go at adding support for the Macintosh/Roman table -- which is fairly straightforward, since it is a simple 1-1 mapping -- I noticed that the situation there is very similar to the Windows/Symbol one, only there the codepoints for regular latin alphabet are _directly_ mapped to the symbol glyphs, i.e. without going via the 'private use area'. So, regular latin characters are also not supported in the Apple OTF implementation of the Symbol font. There are no glyphs "A", "b", etc. in that font. Since the code currently processes the Windows/Symbol mapping _only_ if there is no Windows/Unicode mapping available, that bit of code really does not do anything if the TTF contains both. Even if we were to process both mappings, then the one that happens to be processed first will take precedence, i.e. the code currently allows mapping _either_ codepoint U+03B1 _or_ codepoint U+0061 to glyph 'α', but not both, as is the case in both Windows and OS X when you type text in a text editor or word processor. To get back on topic for this particular issue: I still very much suspect this to be an encoding issue in the source file, maybe as the result of either copy-pasting text or reading from a stream with the default platform encoding. Notice that the user mentions both Windows and Unix as affected; if the default encoding on both platforms does not match, this is typically the result -- rule of thumb: *always* specify an explicit encoding when setting up Input/OutputStreamReaders/Writers. One could argue that Java makes it far too easy for novices to make mistakes here, leading to issues that can be a real pain to trace to their origin... ;) was (Author: adelmelle): Having a go at adding support for the Macintosh/Roman table -- which is fairly straightforward, since it is a simple 1-1 mapping -- I noticed that the situation there is very similar to the Windows/Symbol one, only there the codepoints for regular latin alphabet are _directly_ mapped to the symbol glyphs, i.e. without going via the 'private use area'. So, regular latin characters are also not supported in the Apple OTF implementation of the Symbol font. There are no glyphs "A", "b", etc. in that font. Since the code currently processes the Windows/Symbol mapping _only_ if there is no Windows/Unicode mapping available, that bit of code really does not do anything if the TTF contains both. Even if we were to process both mappings, then the one that happens to be processed first will take precedence, i.e. the code currently allows mapping _either_ codepoint U+03B1 _or_ codepoint U+0061 to glyph 'α', but not both, as is the case in both Windows and OS X when you type text in a text editor or word processor. To get back on topic for this particular issue: I still very much suspect this to be an encoding issue in the source file, maybe as the result of either copy-pasting text or reading from a stream with the default platform encoding. Notice that the user mentions both Windows and Unix as affected; if the default encoding on both platforms does not match, this is typically the result -- rule of thumb: *always* specify an explicit encoding when setting up Input/OutputStreamReaders. One could argue that Java makes it far too easy for novices to make mistakes here, leading to issues that can be a real pain to trace to their origin... ;) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009834#comment-15009834 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 11:33 PM: - Having a go at adding support for the Macintosh/Roman table -- which is fairly straightforward, since it is a simple 1-1 mapping -- I noticed that the situation there is very similar to the Windows/Symbol one, only there the codepoints for regular latin alphabet are _directly_ mapped to the symbol glyphs, i.e. without going via the 'private use area'. So, regular latin characters are also not supported in the Apple OTF implementation of the Symbol font. There are no glyphs "A", "b", etc. in that font. Since the code currently processes the Windows/Symbol mapping _only_ if there is no Windows/Unicode mapping available, that bit of code really does not do anything if the TTF contains both. Even if we were to process both mappings, then the one that happens to be processed first will take precedence, i.e. the code currently allows mapping _either_ codepoint U+03B1 _or_ codepoint U+0061 to glyph 'α', but not both, as is the case in both Windows and OS X when you type text in a text editor or word processor. To get back on topic for this particular issue: I still very much suspect this to be an encoding issue in the source file, maybe as the result of either copy-pasting text or reading from a stream with the default platform encoding. Notice that the user mentions both Windows and Unix as affected; if the default encoding on both platforms does not match, this is typically the result -- rule of thumb: *always* specify an explicit encoding when setting up Input/OutputStreamReaders. One could argue that Java makes it far too easy for novices to make mistakes here, leading to issues that can be a real pain to trace to their origin... ;) was (Author: adelmelle): Having a go at adding support for the Macintosh/Roman table --which is fairly straightforward, since it is a simple 1-1 mapping-- I noticed that the situation there is very similar to the Windows/Symbol one, only there the codepoints for regular latin alphabet are _directly_ mapped to the symbol glyphs, i.e. without going via the 'private use area'. So, regular latin characters are also not supported in the Apple OTF implementation of the Symbol font. There are no glyphs "A", "b", etc. in that font. Since the code currently processes the Windows/Symbol mapping _only_ if there is no Windows/Unicode mapping available, that bit of code really does not do anything if the TTF contains both. Even if we were to process both mappings, then the one that happens to be processed first will take precedence, i.e. the code currently allows mapping _either_ codepoint U+03B1 _or_ codepoint U+0061 to glyph 'α', but not both, as is the case in both Windows and OS X when you type text in a text editor or word processor. To get back on topic for this particular issue: I still very much suspect this to be an encoding issue in the source file, maybe as the result of either copy-pasting text or reading from a stream with the default platform encoding. Notice that the user mentions both Windows and Unix as affected; if the default encoding on both platforms does not match, this is typically the result -- rule of thumb: *always* specify an explicit encoding when setting up Input/OutputStreamReaders. One could argue that Java makes it far too easy for novices to make mistakes here, leading to issues that can be a real pain to trace to their origin... ;) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009834#comment-15009834 ] Andreas L. Delmelle commented on FOP-2539: -- Having a go at adding support for the Macintosh/Roman table --which is fairly straightforward, since it is a simple 1-1 mapping-- I noticed that the situation there is very similar to the Windows/Symbol one, only there the codepoints for regular latin alphabet are _directly_ mapped to the symbol glyphs, i.e. without going via the 'private use area'. So, regular latin characters are also not supported in the Apple OTF implementation of the Symbol font. There are no glyphs "A", "b", etc. in that font. Since the code currently processes the Windows/Symbol mapping _only_ if there is no Windows/Unicode mapping available, that bit of code really does not do anything if the TTF contains both. Even if we were to process both mappings, then the one that happens to be processed first will take precedence, i.e. the code currently allows mapping _either_ codepoint U+03B1 _or_ codepoint U+0061 to glyph 'α', but not both, as is the case in both Windows and OS X when you type text in a text editor or word processor. To get back on topic for this particular issue: I still very much suspect this to be an encoding issue in the source file, maybe as the result of either copy-pasting text or reading from a stream with the default platform encoding. Notice that the user mentions both Windows and Unix as affected; if the default encoding on both platforms does not match, this is typically the result -- rule of thumb: *always* specify an explicit encoding when setting up Input/OutputStreamReaders. One could argue that Java makes it far too easy for novices to make mistakes here, leading to issues that can be a real pain to trace to their origin... ;) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009459#comment-15009459 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 9:00 PM: Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? EDIT - The Arial.ttf that comes with OS X _does_ work apparently, and would render the first sample with proper baseline alignment between the regular latin characters and the greek symbols. was (Author: adelmelle): Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009366#comment-15009366 ] Matthias Reischenbacher commented on FOP-2539: -- I don't think that the user refers to the Base14 Symbol font, no re-mapping is required there. This is just a special "feature" of the Windows Symbol font which requires this non-standard behavior, when using characters in a Unicode range which actually aren't contained in the font. > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009397#comment-15009397 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 8:03 PM: See attached FO for an example that works without requiring any TTF embedding. I almost forgot that FOP does support font-selection... :) EDIT - Just noticed: Baseline alignment seems to be a bit off, though... :( Perhaps expected, not sure. I would have to dig deeper to say for sure. was (Author: adelmelle): See attached FO for an example that works without requiring any TTF embedding. I almost forgot that FOP does support font-selection... :) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009452#comment-15009452 ] Matthias Reischenbacher commented on FOP-2539: -- The release tag for version 1.0 has revision 1141997, 1.1 has 1398854. So Wingdings/Symbol font support was present in 1.0 release, but not anymore in 1.1. > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas L. Delmelle updated FOP-2539: - Attachment: symbol_test.fo See attached FO for an example that works without requiring any TTF embedding. I almost forgot that FOP does support font-selection... :) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009437#comment-15009437 ] Andreas L. Delmelle commented on FOP-2539: -- BTW - Noticed the user specified FOP 1.0 as the version... Were the changes referred to in the earlier comment applied before or after that release? > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009309#comment-15009309 ] Matthias Reischenbacher commented on FOP-2539: -- I had a quick look at this a while ago. Support for Symbol (or other Symbol-Windows fonts like Wingdings etc.) was originally added by Jeremias in http://svn.apache.org/viewvc?view=revision=891181 Glenn then remove it in http://svn.apache.org/viewvc?view=revision=1328579 See also: https://bz.apache.org/bugzilla/show_bug.cgi?id=50492#c7 The code fragment, Glenn had commented, was then re-introduced by: http://svn.apache.org/viewvc?view=revision=1514076 (see OpenFont.java) see also: https://issues.apache.org/jira/browse/FOP-2252 But the code fragment is in the wrong place, at least for making it work again for Symbol/Wingdings. If I remember correctly the characters of the Symbol/Wingdings font can be accessed via the code points in the private use area. So instead of using "a" you need to use
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009347#comment-15009347 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 7:49 PM: Interesting... I was thinking along the lines that, provided the font supports it, there are 'standard' Unicode codepoints for the specific characters mentioned here, i.e. GREEK SMALL LETTER ALPHA - U+03B1 (α) GREEK SMALL LETTER BETA - U+03B2 (β) GREEK SMALL LETTER GAMMA - U+03B3 (γ) etc. Must admit that I have not verified if those codepoints are supported by the Base14 Symbol font, though. If so, no need for mapping to any 'private use area' codepoints. Just make sure those symbols are encoded properly...? EDIT - Just confirmed that those codepoints are properly supported by the Base14 Symbol font, i.e. no font embedding would be needed (?) That said, characters 'A', 'b' etc. are NOT supported by the Base14 Symbol font, so would need to be put in an fo:wrapper to set a different font. Maybe that would not be necessary with the TTF variant, not sure... What I think may be happening here, is that the characters are encoded not as UTF-8 and not referenced via entities, but the parser takes them to be such, if the user is either not specifying the encoding explicitly or is using a boiler plate '' That would lead to strange looking characters, since the bytes would be interpreted incorrectly. No way to tell without looking at the actual FO file in a hex editor... was (Author: adelmelle): Interesting... I was thinking along the lines that, provided the font supports it, there are 'standard' Unicode codepoints for the specific characters mentioned here, i.e. GREEK SMALL LETTER ALPHA - U+03B1 (α) GREEK SMALL LETTER BETA - U+03B2 (β) GREEK SMALL LETTER GAMMA - U+03B3 (γ) etc. Must admit that I have not verified if those codepoints are supported by the Base14 Symbol font, though. If so, no need for mapping to any 'private use area' codepoints. Just make sure those symbols are encoded properly...? > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009459#comment-15009459 ] Andreas L. Delmelle commented on FOP-2539: -- Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009347#comment-15009347 ] Andreas L. Delmelle commented on FOP-2539: -- Interesting... I was thinking along the lines that, provided the font supports it, there are 'standard' Unicode codepoints for the specific characters mentioned here, i.e. GREEK SMALL LETTER ALPHA - U+03B1 (α) GREEK SMALL LETTER BETA - U+03B2 (β) GREEK SMALL LETTER GAMMA - U+03B3 (γ) etc. Must admit that I have not verified if those codepoints are supported by the Base14 Symbol font, though. If so, no need for mapping to any 'private use area' codepoints. Just make sure those symbols are encoded properly...? > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas L. Delmelle updated FOP-2539: - Attachment: symbol_test_2.fo This sample file does render as intended, so baseline alignment seems to only work properly in case we don't rely on font-selection, i.e. by splitting into two fo:inlines, and specifying the font-family on each individually. Could be a genuine bug... > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009459#comment-15009459 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 9:43 PM: Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? EDIT - The Arial.ttf that comes with OS X _does_ work apparently, and would render the first sample with proper baseline alignment between the regular latin characters and the greek symbols. EDIT 2 - Was a bit in an adventurous mood, so decided to debug the code to try and find out why the Symbol.ttf throws that error. Apparently, it fails at OpenFont.readCMAP, lines 426 and following. There are two CMAP tables in the file, but one yields Platform ID = 0 and Encoding ID = 3, the other has Platform ID = 1 and Encoding ID = 0. Hence, neither cmapUniOffset nor symbolMapOffset is set on lines 419, resp. 422. This in turn causes FOP to assume there is no CMAP table available, which causes the error. Now, checking the OpenType documentation, it seems that our implementation would only process the Windows variants (Platform ID = 3), and not the Unicode (Platform ID = 0) nor the Macintosh (Platform ID = 1)... Shame that so many developers only know MS Windows and do not test their code on different platforms... :) was (Author: adelmelle): Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? EDIT - The Arial.ttf that comes with OS X _does_ work apparently, and would render the first sample with proper baseline alignment between the regular latin characters and the greek symbols. > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying properly and they are not human > readable format > fop.xconf:- > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2539) Apache PDF issue with Symbol.ttf
[ https://issues.apache.org/jira/browse/FOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009459#comment-15009459 ] Andreas L. Delmelle edited comment on FOP-2539 at 11/17/15 10:05 PM: - Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? EDIT - The Arial.ttf that comes with OS X _does_ work apparently, and would render the first sample with proper baseline alignment between the regular latin characters and the greek symbols. EDIT 2 - Was a bit in an adventurous mood, so decided to debug the code to try and find out why the Symbol.ttf throws that error. Apparently, it fails at OpenFont.readCMAP, lines 426 and following. There are two CMAP tables in the file, but one yields Platform ID = 0 and Encoding ID = 3, the other has Platform ID = 1 and Encoding ID = 0. Hence, neither cmapUniOffset nor symbolMapOffset is set on lines 419, resp. 422. This in turn causes FOP to assume there is no CMAP table available, which causes the error. Now, checking the OpenType documentation, it seems that our implementation would only process the Windows variants (Platform ID = 3), and not the Unicode (Platform ID = 0) nor the Macintosh (Platform ID = 1)... Shame that so many developers only know MS Windows and do not test their code on different platforms... :) EDIT - Finally, just a heads up: the CMAP table with Platform ID = 0 and Encoding ID = 3 is properly processed if I alter the check on line 418. Result is then similar to using the Base14 font, i.e. no support for regular latin characters. The Macintosh/Roman table yields an error. Apparently, that table format is not yet supported by FOP's implementation. Very likely, if support for that is added, that would then also render the latin characters properly... was (Author: adelmelle): Was trying to check what the behavior was when the TTF was used, but unfortunately, the Symbol.ttf file that comes with OS X cannot be processed: WARNING: Unable to load font file: file:/System/Library/Fonts/Symbol.ttf. Reason: java.io.IOException: The font does not have a Unicode cmap table: file:/System/Library/Fonts/Symbol.ttf Happens with quite a lot of TTFs and TTCs on OS X. Not an expert, so not sure what is wrong about those files that makes FOP's font library not able to process it. I mean: I obviously get that it cannot find a Unicode cmap table, but would have to familiarize myself with the format to know whether that is really an issue with the file, or whether it just points to a deficiency in FOP's font lib... ? EDIT - The Arial.ttf that comes with OS X _does_ work apparently, and would render the first sample with proper baseline alignment between the regular latin characters and the greek symbols. EDIT 2 - Was a bit in an adventurous mood, so decided to debug the code to try and find out why the Symbol.ttf throws that error. Apparently, it fails at OpenFont.readCMAP, lines 426 and following. There are two CMAP tables in the file, but one yields Platform ID = 0 and Encoding ID = 3, the other has Platform ID = 1 and Encoding ID = 0. Hence, neither cmapUniOffset nor symbolMapOffset is set on lines 419, resp. 422. This in turn causes FOP to assume there is no CMAP table available, which causes the error. Now, checking the OpenType documentation, it seems that our implementation would only process the Windows variants (Platform ID = 3), and not the Unicode (Platform ID = 0) nor the Macintosh (Platform ID = 1)... Shame that so many developers only know MS Windows and do not test their code on different platforms... :) > Apache PDF issue with Symbol.ttf > > > Key: FOP-2539 > URL: https://issues.apache.org/jira/browse/FOP-2539 > Project: FOP > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windox, unix >Reporter: Sushmitha > Attachments: symbol_test.fo, symbol_test_2.fo > > > I have Symbol.ttf, configured the same in config file. Symbol font is not > applying properly. > Please find the below details > FOP version - 1.0 > OS - Unix, Windows > XSL-FO desc: > > Abcdefgh α β γ > > Result - the charcters are not displaying
