When exporting to HTML, the process removes all text anchor naming from InDesign and renames them chronologically (e,g. _idTextAnchor002). This is very frustrating when you want to keep nice, logical names for user navigation, or set an anchor to be referenced externally. Currently, make new anchors links in the document changes other anchors links (i.e. if you place an anchor link between the 1st and 2nd link, that link takes on the id and name for the 2nd link, and all other links get pushed so 2nd becomes 3rd, 3rd becomes 4th). This is terrible if users what to share anchor links, as an update can possibly change where the anchor points to.

I would like the Text Anchors to keep the name set in InDesign. Being able to select/deselect this option when Exporting HTML would be a good implementation, if there was potential for naming conflicts on export.

Currently I'm using in5 to insert HTML5 into InDesign and then export it out as HTML5. I'm also using CircularFlo to insert HTML5 into InDesign and export it out as EPUB3. The funny thing is that the HTML5 that I'm importing to InDesign actually all came from the HTML5 output from Adobe Captivate. It is a little bit ironic that I want to combine Adobe files and make them work together but I've to use external parties plugin to do that. I'm very sure that in the future more and more people will be inserting HTML5 into InDesign either to export as HTML5 or EPUB3. Thus the users will greatly appreciate if we can import HTML5 directly to InDesign and have the option to export the project as HTML5 and/or EPUB3. Thank you very much.

When editing an individual paragraph, character or object style, there is a very useful option to turn off the "include classes".

However, in the "Edit all export tags" panel, the option to turn off the "include classes" is absent. The "Edit all export tags" panel is already quite nice, this would be a very useful addition and save time otherwise spent opening and editing styles individually.

I am trying to move away from sending our journal articles to a vendor for conversion and towards exporting html directly from our journal articles with minimal cleanup. This would help me generate cleaner html to upload to our website and save valuable production time.

During HTML export, if we want optimized images, we are only given 4 resolution options (72, 96, 150, 300)-see attached screenshot.

Sometimes we only want certain aspects of optimization to occur. For example if original placed image is a TIFF, we definitley need InDesign to export it as a JPG for the web. BUT we don't necessarily always want the resolution of the image to be altered.

So it'd be nice to add an "ORIGINAL" or "NATIVE" option to the resolution dropdown menu. This would allow us to export the images at their original resolutions, while still converting to differnt filetypes and compressing.

Also a "CUSTOM" option would be nice—so we could enter our own resolution if needed.

This would give us much more flexibility for exporting, which would be hugely helpful for getting our content into the perfect formats for websites.