Bug 118785 - Add support for fo:text-align="right" and "left"
Summary: Add support for fo:text-align="right" and "left"
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.0.4.2 release
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Calc-Enhancements
  Show dependency treegraph
 
Reported: 2018-07-16 16:00 UTC by DM
Modified: 2023-05-06 18:52 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DM 2018-07-16 16:00:54 UTC
Using a standard western setup, in regards to .fods format fo:text-align="right" is not right-aligned, but fo:text-align="end" is.
This can be reproduced as follows:
1. Open a blank calc sheet in a std western setup
2. Enter some distinctive text in the first cell eg aaa
3. Save as a .fods then close it
4. Open the resulting file in notepad and search for your distinctive text then note the style id then jump to its style def using the find feature.
You'll see that right-aligning in Calc has been saved as fo:text-align="end". This will open correctly but (with it not open in Calc) if you now in notepad edit "end" to be "right" then save and open it in Calc, it will be left aligned. The spec does quite reasonably give "right" as a valid value.
Cheers, David
Comment 1 Xisco Faulí 2018-08-22 14:57:03 UTC
@Regina, any opinion here?
Comment 2 Regina Henschel 2018-08-23 11:43:35 UTC
fo:text-align="right" and fo:text-align="left" are valid attributes. So it is a missing feature.

The values "start" and "end" are used in Writer tables and in tables exported by Excel too. Therefore I think, it would be sufficient to convert "right" and "left" according actual writing-mode on import. In XSL-FO https://www.w3.org/TR/xsl/#d0e4611 they are converted for rendering purpose anyway.
Comment 3 Buovjaga 2018-08-24 16:40:17 UTC
NEW, then. Not sure, which meta bug this should go to.