Now, LireOffice can use Ch (It should be a full-width "Character") as units for First Line Indent. It is a great feature that MOST CJK users use 2 Ch in their documents! :) However, "Ch" unit is fixed in deault font size (mine is 12). When Using different font size in different paragraghs, "Ch" should be variable to fit the actual font size of 2 full-width characters.
Created attachment 46191 [details] The fixed size of 2 Ch. See the fixed size of 2 Ch indent.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Because the unit is "Character", the indent or others should be variable along with the font size. It is not solved at dev3.5 yet.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) Thank you for your help! -- The LibreOffice QA Team
Still reproduced in LibreOffice 4.3.5.2 on fedora 21.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
*** Bug 97208 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
The bug still exists in the most recent version.
A workaround for Chinese users: Use CM (厘米) instead. 四号：0.98 厘米 小四：0.86 厘米 五号：0.74 厘米
See also: https://tieba.baidu.com/p/5516848517
I suggest Ch should be identical to em all the time while it used as units.
Addording to UAX 11 East Asian Width (https://www.unicode.org/reports/tr11/tr11-31.html#Overview): “For a traditional East Asian fixed pitch font, this width translates to a display width of either one half or a whole unit width. A common name for this unit width is “Em”. While an Em is customarily the height of the letter “M”, it is the same as the unit width in East Asian fonts, because in these fonts the standard character cell is square.” So we should making "Ch" unit identical to em unit.
Dear Cheng-Chia Tseng, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to QA Administrators from comment #14) The bug still exists in the most recent version.
Check the Format - Paragraph - Indent - Automatic, the first line of paragraph would indent two characters and would follow the font size. I think technically it is possible.
Even using English the "Enable char unit" is not precise either. When checking "Enable char unit" can it just use relative unit like "em"? https://www.w3.org/Style/Examples/007/units.en.html
Khaled, any idea about this? Font size seems to be calulated not correctly.
(In reply to Heiko Tietze from comment #18) > Khaled, any idea about this? Font size seems to be calulated not correctly. What's wrong with it?
This is still producible on current master. Anyone interest in this one, or could some devs give some code pointers and advices? I am adding Miklos Vajna to cc. Could you please advice? I am working bug 129448, they are related, but *this* one seems to be different and I do not know where to start, and I am not sure whether this is as easy as bug 129448 for me to work on.
By the way, with the fix for bug 129448 (patch currently under review: https://gerrit.libreoffice.org/c/core/+/125627), the first line indent will not be effected by line space, thus when first line indent is set to Auto, then it will always be precisely 2-characters indent, and the indent will be updated upon font size change. *This* bug is a little different as it only relates to when the "Use character units" option is enabled and one inputs an first line indent of e.g. "2 Ch" in the Paragraph Properties dialog. In other words, this bug is about the manually set first line indent, not Auto first line indent.
Created attachment 176991 [details] Test ODT Document As shown in this test document, the first line indent for the 1st paragraph is correctly 2-characters, whereas it is wrong in the 2nd paragraph.
Created attachment 176992 [details] screenshot showing the problem Attached is a screenshot illustrating the problem, as well as a comparison with MSO Word 2010.
It would be good to research what is that "ch" unit, I'm not familiar with that. Is that intentionally depending on the font size or is there a fixed conversion factor between ch and e.g. twips?
One ch unit means one character unit, which equals to the height of the character of the current paragraph using the font of the current paragraph style. In Chinese language there is a long standing convention that in a paragraph the first line indent should be 2 characters.
The series of commits which added the "character unit" are: https://cgit.freedesktop.org/libreoffice/core/log/?qt=grep&q=cjk-character-units
(In reply to Kevin Suo from comment #10) Another workaround for Chinese users: Insert U+3000 IDEOGRAPHIC SPACE ( ) (known as 全角空格) twice at the beginning.
(In reply to Kevin Suo from comment #25) > One ch unit means one character unit, which equals to the height of the > character of the current paragraph using the font of the current paragraph > style. > > In Chinese language there is a long standing convention that in a paragraph > the first line indent should be 2 characters. This is also documented in the Requirements for Chinese Text Layout by W3C. https://www.w3.org/TR/clreq/#first_line_indents
*** Bug 123938 has been marked as a duplicate of this bug. ***
I'm sure that it may cause by Line Spacing, which will mess up first line indent using Character with CJK language if it's not on Sing Line. In my memory, Libreoffice did add the feather of first line indent using Character on 6.x version. But I find it only work on Sing Line. If I change to other Line Spacing, the characters of first line won't be aligned, and it will make no sense. Testing on Libreoffce 7.3, still not fixed
Some code reference: the CJK character units seems added by: https://cgit.freedesktop.org/libreoffice/core/log/?qt=author&q=amwang
It seems that the ch and line units are implemented only when text grid is enabled, without the grid it defaults to a fixed value for both units.
This bug is a fairly large task, so I wanted to briefly review the current state as I understand it. Comments are appreciated. 1. The Ch unit For the purposes of CJK typesetting, we want a variable-length unit equal to the advance measure of a Han ideograph in the current font. In CSS, this unit is called 'ic'. In Microsoft Word, this unit is called 'Ch'. From what I've seen, Ch is set as the default length unit when an Office CJK language pack is installed, so Word documents that use Ch as a unit are likely very common. A unit called Ch was added to LibreOffice in 2010. Unlike the previous examples, this unit is hard-coded as equal to 210 twips. That hard-coded value is used unconditionally, regardless of font, style, or context, including if text grid is enabled. I suspect this was originally intended as a short-term fix to ease importing Word documents that use Ch units along with a specific default font/size. I wasn't able to locate any discussion or non-source artifacts concerning this design, so unfortunately I can only speculate. Regarding standards: For length units, the ODF 1.3 specification only refers to a list of recommended units in §5.9.13 of the XSL 1.0 specification. The Ch unit is not mentioned at all, so we seem free to redefine Ch as we need. The standard does not seem to prohibit us from persisting or consuming Ch as a unit. Regarding impact: A change to Ch would have no impact on existing Writer documents. Writer does not persist the Ch unit. Writer reports an error when parsing a document that contains the Ch unit. Currently, the Ch unit is an artifact of the user interface only. (Note that the example attachment above does not contain Ch units. They were automatically converted to cm.) In the interest of compatibility with other programs, I recommend changing Ch from a fixed unit to a relative unit, formalized as equivalent to CSS 'ic'. I also recommend that we do not implement a compatibility flag, as such a flag will have no effect. 2. Relative units in Writer Per ODF 1.3 §20.225, fo:text-indent only requires support for a single relative-length unit: percent. The standard neither prescribes nor proscribes support for other relative-length units, but does seem to recommend em (transitively via XSL 1.0 §5.9.13). Currently, Writer supports percent in fo:text-indent. Writer does not support em, or any other relative-length unit. Percent may be used in the paragraph style editor, but it is ignored in the paragraph properties dialog. This code change could end up being quite large, especially considering that once we start changing unit support for some attributes, we will likely want to keep it consistent across all of them. In order to manage the complexity for this code change, I recommend the following general breakdown: - Start with a separate task(s) to add *em* support to fo:text-indent, as em is already recommended by the standard. - Build relative Ch support on top of that change. - File separate bugs against the remaining attributes, so they can be tackled one-by-one.
(In reply to Jonathan Clark from comment #33) > In the interest of compatibility with other programs, I recommend changing > Ch from a fixed unit to a relative unit, formalized as equivalent to CSS > 'ic'. I also recommend that we do not implement a compatibility flag, as > such a flag will have no effect. I agree with you, and I think it's time to replace such legacy codes. > Currently, Writer supports percent in fo:text-indent. Writer does not > support em, or any other relative-length unit. Percent may be used in the > paragraph style editor, but it is ignored in the paragraph properties dialog. I think this require some new codes to provide essential algorithms first.
(In reply to Jonathan Clark from comment #33) > Per ODF 1.3 §20.225, fo:text-indent only requires support for a single > relative-length unit: percent. The standard neither prescribes nor > proscribes support for other relative-length units, but does seem to > recommend em (transitively via XSL 1.0 §5.9.13). Although the language of the standard can be read to imply em support, the XML schema does not allow use of the em unit. ODF does not currently support any font-relative length units. This feature has been proposed for addition to a future version of ODF. The proposal is tracked here: https://issues.oasis-open.org/browse/OFFICE-4165
Jonathan Clark committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6f16beca51c86e0decfde71236174b5e45a9e904 tdf#36709 Refactor Converter to separate parsing from unit conversion It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jonathan Clark committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/43cd683230bc05d294b1bd64f1e7932feccdd3fb tdf#36709 Add loext:text-indent supporting font-relative units It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jonathan Clark committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d3a59f7a915f9cc0864f2c76ccf90b6cd6fea339 tdf#36709 sw: Writer layout for font-relative first-line indent It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jonathan Clark committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2cb039f570379213ffc9469a132f5b24f425b7be tdf#36709 editeng: Layout for font-relative first-line indent It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jonathan Clark committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/78a18a5dc6986c9f5612f26d164c62202a1b94f8 tdf#36709 GUI changes for font-relative first-line indent It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 197627 [details] Font-relative indentation in 25.2 Screenshot illustrating CJK font-relative paragraph first line indentation in Writer.
Font-relative paragraph first line indentation is now implemented. Indentation can be applied in the paragraph style dialog by entering a quantity followed by either 'em' or 'ic'. For example: To indent the first line of a paragraph by 2 ideographic characters, enter "2 ic" in the first line indent textbox. Please note that the existing 'Ch' unit has not changed, and still refers to a hard-coded constant width. Revising this behavior will be tracked as a separate bug.