When we create an HTML5 form from a PDF file we have a choice of how we handle the form names. We can either use an autogenerated value, or we can use the name of the Form from the PDF. The second is much more useful because it makes it easy to compare the PDF and the HTML5. There is, however, a slight catch (isn’t there always!).
Characters which are allowed in the PDF form name are not valid in an HTML5 form name (space, ‘.’, etc). So we need to replace these in the HTML version (we use underscore so dodgy name.1 would become dodgy_name_1).This works fine but it stops us being able to easily use the name to identify the PDF form.
But, we can easily add additional attributes to the HTML. So, we add a new value (pdfFileName) which will be ignored by the HTML5 parser, but allow any user to easily identify the original PDF form field used. Here is an example.
<input type="text" tabindex="12" id="Geb-Datum" value="" pdfFieldName="Geb.Datum" /> <input type="text" tabindex="34" id="Ehepartner_AHV-Nr" value="" pdfFieldName="Ehepartner AHV-Nr" />
At the cost of making the HTML5 file slightly bigger we get the ability to identify easily between PDF and HTML form components. Would any other PDF file information be useful inside the HTML?
Click Here to see all the articles in the PDF to HTML5 conversion series.
Latest posts by Mark Stephens (see all)
- 3 ways that the European Union is changing the way Companies write software in 2018 - January 31, 2018
- IDRsolutions product range update for 2018 - January 22, 2018
- 4 ways Companies can make remote working successful - December 21, 2017
- My experience of a Turkish bath (visiting Istanbul for DevFest) - November 24, 2017
- My 5 key takeaways from JavaOne 2017 - October 6, 2017