You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to develop a Hunspell dictionary for my mother tongue, Persian. Unfortunately, there is no prebuilt Hunspell dictionary in Adobe Indesign for the Persian language. I have done the dictionary and affixes files for it and my glossary is almost complete. Here is my problem: the Hunspell dictionary in Indesign behaves a little bit differently in Indesign in comparison with other environments that support Hunspell e.g. Firefox and Chrome browsers. In Persian, many words have Zero Width Non-Joiner (ZWNJ). Although the words in my dictionary do have ZWNJ, the Indesign is not able to detect them and acts as if there is no such character. How can I overcome this problem?
The text was updated successfully, but these errors were encountered:
I did report the issue to Indesign, but it didn't come to any conclusion. In fact, they've been reporting the Indesign problem with the ZWNJ character, but the problem still exists. Maybe that's because the ZWNJ is only needed and used in the Persian language and not any other languages, so it's not a common issue for most people.
I have been trying to develop a Hunspell dictionary for my mother tongue, Persian. Unfortunately, there is no prebuilt Hunspell dictionary in Adobe Indesign for the Persian language. I have done the dictionary and affixes files for it and my glossary is almost complete. Here is my problem: the Hunspell dictionary in Indesign behaves a little bit differently in Indesign in comparison with other environments that support Hunspell e.g. Firefox and Chrome browsers. In Persian, many words have Zero Width Non-Joiner (ZWNJ). Although the words in my dictionary do have ZWNJ, the Indesign is not able to detect them and acts as if there is no such character. How can I overcome this problem?
The text was updated successfully, but these errors were encountered: