JeffK
My feedback
10 results found
-
388 votes
Hi,
We have been able to reproduce the issue and it is currently under investigation.
—
Adobe InDesign Team
JeffK
supported this idea
·
-
25 votes
Hi,
Thank you for reporting the issue. It is currently under investigation.
—
Adobe InDesign Team
An error occurred while saving the comment JeffK
supported this idea
·
-
5 votesJeffK
supported this idea
·
An error occurred while saving the comment JeffK
commented
Agree that this is an important issue. Working with CJK texts which require ruby cannot be done.
-
25 votes
The fix of the issue is now available in the latest InDesign 2024(v19.0.1.205). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign Team
An error occurred while saving the comment JeffK
commented
This is quite problematic in our environment as well - where we typically need to keep multiple versions of InDesign installed, and we interact with them using scripts/custom software. Previous ID versions all have their own unique ID.
JeffK
supported this idea
·
-
9 votes
Thank you for reporting the issue.
We are currently reviewing it.-InDesign Team
An error occurred while saving the comment JeffK
commented
Update: Based on our testing (with using conditional text) this issue appears to have been resolved in InDesign 2024 (19.0.0.123 or higher; currently pre-release at the time of my comment). With thanks to the InDesign support team who connected and worked with us on the issue.
An error occurred while saving the comment JeffK
commented
As far as my team can tell -- this rendering problem with Arabic text happens whenever there is a U+FEFF (i.e. ZERO WIDTH NO-BREAK SPACE [BOM, ZWNBSP]) present on the same line as text in which the diacritic rendering is corrupted.
It appear that using things like conditional text, or footnotes etc. leaves a U+FEFF in the Story text. In the case of conditional text, when the condition is enabled (text made visible), then the diacritics render OK again. This appears (to us) to be because the U+FEFF is not longer present in the paragraph text stream (it is not present when the conditional text is visible).
*** This is really a serious bug. *** It makes typesetting Arabic properly nearly impossible with any features like conditional text or footnotes in use. We're currently needing to do massive workarounds to continue our work.
Would someone from Adobe be able to investigate this with us? Please do let us know how we can connect.
An error occurred while saving the comment JeffK
commented
I've tried to attach a sample .indd document to demonstrate the problem -- but the attachment is not received when I post comment (it is not displayed with the post).
JeffK
supported this idea
·
An error occurred while saving the comment JeffK
commented
Would there be any update on this issue from Adobe, or anyone?
My team is just facing the same issue. In our case the text we are typesetting has various Conditional Text elements in it. When the conditions are not enabled (the conditional text not visible) then there are various rendering problem with the harakats (diacritics/vowels).
In the attachment I am showing screenshots with lam + alef + hamza + fatha. The text in red is rendering incorrectly. It is using a font called "Scheherazade New" (SIL font - find on Google fonts). With an older version of this font, the rendering is OK (text in green). An additional copy of the characters is show in Adobe Arabic font, which is rendering incorrectly (text also in red).
In the attachment, the image below the red line shows all 3 example rendering OK. In this case the "Conditional Text" in the paragraph has all been made visible.
I think this issue is similar to the others reported here, since it relates to other content being present in the paragraph text (conditional text, footnote reference, anchor) which causes rendering problems.
This is a significant problem. Solutions involving manual intervention are a big challenge for a large amount of text (hundreds of pages).
-
15 votes
An error occurred while saving the comment JeffK
commented
I would also be interested in knowing whether an update to InDesign and Harfbuzz could incorporate Graphite support. This would enable needed support for some language and scripts.
JeffK
supported this idea
·
-
3 votesJeffK
supported this idea
·
-
28 votes
The fix of the issue is now available in the latest InDesign 2024(v19.5.0.084). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign Team
JeffK
supported this idea
·
-
63 votes
An error occurred while saving the comment JeffK
commented
Very helpful proposal.
JeffK
supported this idea
·
-
454 votes
Thanks for the suggestion. We have started to explore this feature. Will share more details soon
Thanks
AbhinavJeffK
supported this idea
·
The team I work with is experiencing the same problem. We are unable to successfully place tagged text with ruby. Projects we are working on requiring ruby text are blocked.
Installing and using the debug version of InDesign is not an option many of our users would be comfortable with.