I understand why the world is the way it is, but still it should have been obvious all along that it is not ideal for the government to data in a file format owned by a company. Even worse, a foreign company.
Do note that xlsx, docx, etc, are all just .zip files with XML files inside. If such a file is corrupt, extract it, and check what you can salvage.
That being said: Still controlled by MS, and thus a potential threat to the EU.
Most—certainly not all, but most—documents that are written in Microsoft Word, or in LibreOffice Writer, would be better off as either markdown plain text files, or as LaTeX.
CMV.
Hear hear
90% of everything I read/write is either plaintext, explicit .md, or some .md-adjacent proprietary markup language (Atlassian, BBcode,…)
I don’t think it’s really possible to have a reasonable argument against a vendor agnostic open standard in most cases.
*with accessibility tags applied.
I’m afraid I’m not sure what you mean here. Both markdown and LaTeX are plain text. They’re easily read by a screen reader. Though unless the screen reader is specially-designed for LaTeX support, it may be difficult to comprehend. That’s on the screen reader though, not the document format.
I assume they mean stuff like image descriptions that you can add in Microslop Word (don’t know about LibreOffice). It’s quite a neat feature that wouldn’t work with markdown (might work with LaTeX), because these image descriptions are not visible to someone reading a document.
Image descriptions are a thing in markdown. Images are inserted into markdown documents with this syntax:
Cool, didn’t know that one yet!
Both Lemmy and Piefed support it, though weirdly unlike the alt text field when submitting an image post, this syntax only adds alt text, so only screen readers will see it—users can’t view the text on hover.
Correct, accessibility also differentiates between titles and content, to better assist readers who use a screen reader.
I replied to the other user showing how markdown image descriptions work. Titles are added with hashes.
# title ## subtitle Text ### sub-sub title Etc.Screen reader should pick that up.
It’s a bit trickier in LaTeX (depending on layout), given they convert to an untagged pdf by default using pdftex. For defaults such as section/subsection etc I think some auto-tagging has been added, but my memory is not great.
Issues crop up when you need to hack something (e.g. indenting parts of a proof using the quote environment to aid readability, creating more complex tables, or just using coloured text to indicate element relations), and here manual tagging is a must!
Sure, but 99% of MSO/LibreOffice users would quit after about 45s of trying to put together a document in LaTeX.
Sure. And 90% of those are writing stuff that would be better off as markdown.
Great news!
When are we going to have the equivalent for PDF documents, with the ability to comment, fill and sign, as in AdobeAR?
Nice! A huge blow to those still trying to push Microsoft
Microslop?
