Copy link to clipboard
Copied
Hello Adobe Experts,
All are waiting for the update feature on the Endnotes round-tripped options.
Most of the time we received the files from client in both format of the footnotes and endnotes so footnotes no issues while exporting the RTF file and import into InDesign.
But the Endnotes there is issue while export the RTF the end note text comes out the normal text there is no linking withe citations. And the client requirement the end notes should the be linked into the RTF.
Is there any udpates done in the Adobe InDesign 2024 version. Or yet to develop this request from Adobe.
Also please suggest anyother options to get rid this request.
Export the InDesign to RTF the endnotes should be linked in RTF file, while click the endnotes citaion it is go the refecence text in the MS word.
Note: I'm using Javascript to Expor the InDesign to RTF. Round trip RTF to InDesign again.
Please anyone suggest your valuable ideas or tricks.
Thanks,
Sundar
Copy link to clipboard
Copied
This is a feature request. You need to post this in the InDesign User Voice website. There is can be read by product managers and voted on by users. It will not get anyone's attention in this forum:
https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests
Copy link to clipboard
Copied
As Steve notes, this is a feature request and should go in the Feature Request forum so that others can add their votes, and the discussion is seen by the development team.
I'll just note that Endnotes are by far the most fragile entity in InDesign files; while they seem to work in most documents created for print (references and notes stay linked, numbering is automatic, process basically "works") almost every attempt to export them, through any process, has a limited and fussy path to success. The situation gets worse in the common case of importing a Word or RTF file wherein end notes were created in a different app.
There are some fixes, such as purging and rewriting the INDD or IDML file, but some files retain faults that simply can't be fixed with reasonable effort. I'd agree that this whole shaky schema needs a thorough overhaul at the code/document structure level. As this problem goes back many years, though, I wouldn't hold up any production schedules waiting for a fix.