-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected presentation of IJ in Dutch #223
Comments
What font family have you assigned for Dutch publishing? Also can you attach your Formatter setting file to this thread? |
Also it is helpful to inform me the Formatter version. |
It's the result of a new Dutch 'IJ' replacement option. See https://www.antenna.co.jp/AHF/help/en/ahf-optset.html#text-replace-Dutch-IJ It can be disabled with this setting:
(Copied from an Antenna House USA Support response.) |
Nice follow-up! |
Thank you for the information. |
Yes, you need to specify
|
When we publish our Dutch (nl) content in PDF, the diaphram "IJ" presents in an unexpected way when capitolized:

<fo:block start-indent="inherited-property-value(start-indent) + 7mm" end-indent="10mm" font-size="inherit" id="unique_15_HEARTRATEALARMINTERFERENCEPoorCable-231C7152">DON'T WEAR A HIJAB IN THE BIJOU.</fo:block>
The same content looks as expected, with a distinguishable I and J when published in English.

<fo:block start-indent="inherited-property-value(start-indent) + 7mm" end-indent="10mm" font-size="inherit" id="unique_15_HEARTRATEALARMINTERFERENCEPoorCable-231C7152">DON'T WEAR A HIJAB IN THE BIJOU.</fo:block>
The fo:block is identical - and the text does not show the combined letters. The only difference I can find in the code is that English lists 3 font famileis, while Dutch lists one.
Please help me understand what is going on here.
The text was updated successfully, but these errors were encountered: