When you convert a PDF to XHTML (this occurs when documents are saved to the server from the Tagger for creating ESEF reports) some issues with fonts can arise. If you use the settings below the XHTML file will not have font issues and you will avoid “Hidden facts”.
Settings in CtrlPrint
1. Check the option called “Elimination of Hidden Facts for PDF”. (According to the regulations “Hidden facts” are not allowed in an ESEF report.)
2. Choose “Ignore” under “PDF unicode CMAPs handling”.
Settings in InDesign
1. All numbers that are tagged need to have the OpenType setting “Default Figure Style” to avoid “Hidden facts”. This setting only effects the digits in the report.
To apply this setting you can manually choose “Default Figure Style” in the number columns or you can apply the setting in the Paragraph Style under “OpenType features”.
2. Use 0 kerning on the tagged numbers for best results. (Seen in "Character" panel below.)
Other conversion problems
Other problems that can occur when you convert the PDF to XHTML are:
If you have applied effects (opacity, multiply etc.) on text in the InDesign document it will go back to default after the conversion to XHTML. If you want to work with effects you need to create outlines of the text.
If you have text hidden behind an object in InDesign the text will become visible when you convert to XHTML.
When converting and tagging a PDF report in the XBRL Tagger, some facts (tags) might become hidden. The reason for this is that the Inline XBRL Specification does not allow individually formatted numbers to be tagged. E.g. when the font requires special spacing between single characters by using HTML tags like <span>, the number is then no longer taggable. In order to preserve the spacing and formatting of the PDF in the XHTML report, the XBRL Tagger moves the tag to an unformatted hidden section of the document and includes a link to the visual original number.