Bug 131192 - Comprehensive support for "start" / "end" text alignment
Summary: Comprehensive support for "start" / "end" text alignment
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: RTL-CTL RTL-UI
  Show dependency treegraph
 
Reported: 2020-03-06 20:51 UTC by Eyal Rozenberg
Modified: 2020-06-10 03:50 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 Eyal Rozenberg 2020-03-06 20:51:19 UTC
Libreoffice supports the following types of text (paragraph) alignment:

* Left: Align the leftmost character on each line to the left  boundary
* Right: Align the leftmost character on each line to the right boundary
* Center: Align so that the content on each line is equidistant from the left and right boundaries.
* Justify: Space so that each line except the last starts and ends at the left and right margin respectively; align last line to start

Note that I used the term "start" in there. Indeed, it is not "Justify and align last line to left" or "to right" - it is to the start of the flow of characters in the paragraph. This hints that the full set of alignment modes should be

* Left
* Right
* Start
* End
* Center

[ ] Justify all lines but last

Justification is not an independent mode - the last line can have any one of left, right, stand and end alignments.

When you're only working with left-to-right text, there is no distinguishing between "Start" and "Left", and between "End" and "Right" - that's how LTR text flows. But these are conceptually different. And when we change paragraph direction, Left/Right alignment should not be affected, while Start/End should be flipped.

It should be noted that:

* The UI doesn't fully match this functionality (in different applications).
* We get confused about file formats which do support Start/End, see bug 37128.
* This causes interoperability issues when other apps do use Start and End - but not consistently and not quite opaquely. See bug 118350.
Comment 1 eladhen2 2020-06-09 15:00:37 UTC
This is indeed lacking. 
Confirmed I guess.
Comment 2 Eyal Rozenberg 2020-06-09 15:19:24 UTC
El'ad, to confirm - you change the status to CONFIRMED...

I've done this now myself based on your input (although generally people shouldn't confirm their own bugs).