The Tagger user interface looks ugly, fonts and controls (boxes) are not at the right place It can be started manually, by running the in the users local AppData folder, which can usually be found here:Ĭ:\Users\user.name\AppData\Local\AMANA\ app-1.7.1\ For instance, if updating from version 1.7.1 to 1.7.2, the version 1.7.1 is still installed. When updating the XBRL Tagger, one old version will always be preserved. How can I go back to an old version of the XBRL Tagger after updating it? You can find additional information on the installation process here. The XBRL Tagger does not link this binary in the source code, but rather calls the converter via command line and returns the resulting XHTML to the XBRL Tagger for tagging purposes. In order to install the pdf2htmlEx converter, please download pdf2htmlEx ZIP file under "Releases" and extract it to %appdata%\AMANAconsulting folder, like in this sample:Ĭ:\Users\user.name\AppData\Roaming\AmanaConsulting\pdfToHTMLEx\ being the current release tag from github, i.e. AMANA forked the converter and published a version under the GPL v3 version here: However, it can't be distributed with the XBRL Tagger, so users are requested to install it themself. T his converter is published under GPL v3 and free to use. In order convert a PDF document to XHTML and keeping all formats, AMANA recommends to use a third-party XHTML converter, called pdf2htmlEx. Why does the XBRL Tagger ask me to download pdf2htmlEx? The MSI Installer does not support the integrated update functionality. To solve this issue, just deinstall both versions, and install the Setup.exe (click-once installer) again. This happens, when BOTH Tagger versions are installed, the click-once installer Setup.exe and the MSI Installer. The Tagger update disappears: it has to be updated every time after the system restart To change the decimals settings, please open "Document" menu and click on "Settings" and then "Advanced settings" tab. It is required to incease the accurracy of the XBRL facts by setting the decimal attribute to -5 (millions with one decimal place) instead of minus -6 (millions). In the example on the left, the values are reported in millions, but with one decimal place. The reason is, that the XBRL report will have an accurrancy setting. If the document after all processing still has artifacts the "fallback mode" option in the Tagger can be used. Convert PDF to the stadard PDF 1/A with Adobe Preflight in the "PDF standards" tool.įor case 4 use "Sanitize Document" in the "Redact" tool and convert the document to PDF/X for correct colors.Export the PDF to postscript and create a new file from it in Adobe Acrobat Distiller DC,.Converted PDF shows wrong colors, visual artifacts or extra text fragments or pages.įor case 1-3 there are two methods to repair the document in Adobe:.PDF document has not converted at all in the Tagger.Converted PDF contains unreadable fragments.The converted PDF looks good, but the imported table is unreadable.If the conversion still doesn't meet the expectations or some tables cannot be tagged properly, the source file might need corrections. Please change the option "PDF unicode CMaps handling" to "Auto" and "Use autohint on fonts without hint"to "Use AutoHint" if the converted document does not look good.The converter has fine tuning options helping to resolve the issues:.If so, you should remove hidden text layers in the Adobe Acrobat DC " Redact" tool.The converter does not support PDF hidden text layers.If the converted document has wrong a color palette see step 1.To resolve this it is recommended to save the source document as PDF/X format in the Adobe Acrobat DC " Print Production" tool. In this case, the converted document can contain unreadable (weird looking) text.CID (identity H) fonts embedded to the source document.'r.Comments.Add r, "Das ist Seite " & counter & "!"Ī "SN_PAGEBREAK_" & counter, r Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=wdGoToNext 'r.Comments.Add r, "Das ist Seite 1!" 'Debugging-CodeĪ "SN_PAGEBREAK_1", r Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=WdGoToDirection.wdGoToFirst 'Wichtig, weil sonst Seitenumbrüche innerhalb von Feldern schief sein können.