[Libreoffice-ux-advise] [Bug 117428] add an option to PDF export dialog to do ActualText per word

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=117428

--- Comment #6 from V Stuart Foote <vstuart.foote at utsa.edu> ---
(In reply to Khaled Hosny from comment #4)
> 1) Do we want this option or not

IIUC with
https://cgit.freedesktop.org/libreoffice/core/commit/?id=c688b01d9102832226251fc84045408afe392459
gets us /ActualText tags in the PDF at the Unicode Glyph cluster level where
needed.

This additional work would be to expand PDF export to include generation of the
/ActualText at Unicode Word boundaries for text in all scripts/fonts. Helpful
for fidelity of CTL script content by word, but also for extending our Tagged
PDF content in general to include tagged words for entire text. Good for a11y
and AT tools that can parse the tags.

So I think it is worth doing.


> 2) What exact wording to use, /ActualText is a jargon (it refers to specific PDF
> construct) that I’m not sure should be exposed in user UI.


True "Actual Text", a counterpoint to "Alternate Text" or "Extended Text"
commenting for accessibility, could include other lexical aspects of rendering
a document--e.g. exposing in PDF the meaning of an Emoji, from its Unicode
point name or drawn from a substitution table. 

But here if we were to enable/disable Unicode Word boundary tags by simply
adding it to the "Tagged PDF (add document structure)" check box the specific
PDF /Lang & /ActualText tags would not be needed in the UI.  "Tagged PDF" would
simply include actual text tagging by default.

The Help item for the checkbox would include details regards the Tagging of
text including /Lang tags and /ActualText tags mentioned for completeness--but
with no need to refer to them in the GUI otherwise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.