Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index



On 05/02/2018 08:07 AM, toki wrote:
In order of accessibility:
* Plain text;
* MS Doc;
* MS Docx;
* RTF;
* ODT;


jonathon


Interesting list. I've always liked working with plain text files.

Do you have any information/opinion about various forms of markdown 
files (i.e. Markdown, RestructureText, AsciiDoc).

This semester, I played with making slide presentations using AsciiDoc 
and its "slidy" backend.

The source file might look something like:

===
Title
===

Slide Title
--------------

* A Bulleted item

** A nested bulleted item with *boldface* type.
** Another nested bulleted item with _italicized_ text.

Another Slide Title
--------------------------


After creating the document, I run it through AsciiDoc's converter and 
it creates a very simple slide presentation in HTML format. However, the 
source file remains plain text. Would a screen reader get tripped up by 
the various formatting tags (* A Bulleted item; _italics_, *boldface*)?

Virgil

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.