Issue 64444 - Only some punctuation in Asian Layout is compressed
Summary: Only some punctuation in Asian Layout is compressed
Status: CLOSED DUPLICATE of issue 90389
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-18 03:32 UTC by adah
Modified: 2017-05-20 10:01 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description adah 2006-04-18 03:32:23 UTC 
The option "Language Settings > Asian Layout > Compress punctuation..." is
really useful, and I like it. However, a big problem is that only some of the
punctuation marks are compressed, while many others are not. In the most
frequently used punctuation marks, "、" (ideographic comma) and "。"
(ideographic full stop)--when I look for the names, I happen to find out that
they are in the U+30xx area--are compressed, while "！" (fullwidth exclamation
mark, U+FF01), "，" (fullwidth comma, U+FF0C), "：" (fullwidth colon, U+FF1A),
"；" (fullwidth semicolon, U+FF1B), "‘" (left single quote, U+2018), "’" (right
single quote, U+2019), "“" (left double quote, U+201C), and "”" (right double
quote, U+201D).

Just imagine a document with more space after the comma than after the full
stop. This is often the case I encountered because of the above-mentioned issue.
Comment 1 Olaf Felka 2006-04-18 08:51:37 UTC 
@ sba: Please have a look.
Comment 2 michael.ruess 2009-09-21 09:28:59 UTC 
Maybe related to issue 90389?
Comment 3 Rainer Bielefeld 2013-07-18 04:25:41 UTC 
I mark this one as DUP of "Bug 90389 - CJK punctuation compression", because there we already have a patch.

@reporter:
Please feel free to reopen this Bug if you find evidence that we have an independent issue here  (for example because the fix for the other bug does not work for you).

*** This issue has been marked as a duplicate of issue 90389 ***