I'm using Type 1 central european fonts with 256 characters with WinAnsi encoding. I have correctly embedded current Type 1 fonts in my output pdf file, but all of characters which has in UTF-8 encoding code gather then 255 are missing in my pdf (replaced by '#'). Other characters are correctly maped to the target WinAnsi encoding. Is there problem in FOP with WinAnsi encoding using in the Type 1 fonts?
I suspect this is the FAQ "Some characters are not displayed, or displayed incorrectly, or displayed as '#'", see http://xml.apache.org/fop/faq.html#faq-N10402 Please supply a small self-contained FO file demonstrating the problem if you think otherwise.
Created attachment 5246 [details] Includes userconfig, sample FO and font
When I'm using True Type fonts everything is OK. Problem is only with Type 1. I had spent a long time with reading bugs and documentation (also FAQ) and testing, then I wrote this bug. Certainly I have tested replacing characters with entities (Č for example), but i think, that parsing a and stream interpretation is OK, because there is no problem with True Type fonts and also with Type 1 fonts are national charakters well maped from UTF-8 to WinAnsi and and embedded font is used, only (as I wrote) only chracters that are multibyte in UTF-8 are missing (It is no odds which encoding is input stream).
I forgot reopen bug.
So FOP don't respect encoding in embedded fonts. When True Type is user there is no problem because True Type is UTF, but when you have Type 1 fonts with another encoding then WinAnsi, you will fail. I rewrote some classes and regenerate CodePointMapping class with new encoding and now there is no problem for using any Type 1 with my encodings.
batch transition to closed remaining pre-FOP1.0 resolved bugs