6 ms·
It's surprisingly common for government agencies to request that you send them Word documents or install some proprietary software.
by kragen 5y ago
It's surprisingly common for government agencies to request that you send them Word documents or install some proprietary software.
- pabs3 5y agoThat LibreOffice can create/edit Word documents means that particular requirement would be fine under the proposed bill. Installing proprietary software obviously wouldn't though.
- int_19h 5y agoIt would still require that the documents open correctly in LibreOffice, no? Which might be difficult enough to ensure in practice for .docx that it would be easier for the state to mandate using ODF.
- pabs3 5y agoMandating using ODF would indeed be much better, but of course that mandate doesn't prevent interop issues from occurring.
- int_19h 5y agoWhat I meant is that if there's a law that says that interop with F/OSS must be possible, it'd probably make more sense for government agencies to internally mandate the use of ODF for all outputs, than for them to test and fix every .docx that they produce for compatibility with LibreOffice. ODF might not be free from interop issues, but I'd expect the baseline to be much better.
- kevin_thibedeau 5y agoOr PDFs that can only be used from Acrobat reader.
- bruce511 5y agoPdfs open in Firefox just fine. So I presume your emphasis is on only. Are there any features in a pdf that lock it to Adobe reader? Is anyone (govt? ) using that feature.
- josephcsible 5y agoSome PDFs really don't work at all except in Acrobat. One example is USCIS form I-9: https://www.uscis.gov/sites/default/files/document/forms/i-9.pdf https://www.uscis.gov/sites/default/files/document/forms/i-9...
- tyingq 5y agoInteresting. Does not open right in Chrome, but is opening with Firefox for me.
- nybble41 5y agoThe I-9 form an XFA application, not something anyone sane would recognize as a proper PDF. It's all JavaScript and XML-based forms stored as opaque streams inside a PDF container and has almost nothing in common with standard PDF files beyond the container format. It works in Mozilla because Mozilla's pdf.js supports XFA as of Firefox release 91. Most PDF readers do not support XFA, which is quite reasonable considering its rarity and the fact that it has been deprecated for several years. An HTML form would have been a far better fit for this purpose.
- kevin_thibedeau 5y agoJavaScript for form entry even though PDF already has an older form mechanism.
- nonameiguess 5y agoLots. My wife and I are in the process of trying to become licensed as foster/adoptive parents in the state of Texas and quite a bit of the paperwork we have had to fill out will open fine in a browser, but can only be edited in Adobe Reader. I just had to fill out a form to get a new common access card to work as a federal contractor for the US DoD and it wasn't possible to save edits to the form except with Adobe Reader Pro. Even the free version of Adobe didn't work. I could read the form fine, but if I can't fill it out, I can't submit it. A lot of this is just issues with skeuomorphism. There is little reason any of these workflows need to use pdfs at all, except that it represents a smaller feeling change from the legacy paper workflows compared to migrating to a purely web-based workflow that uses html forms instead of editable pdfs. Heck, I think I remember the FAFSA being fully html-based forms over 15 years ago when I first went to grad school, but I'm not totally sure.