Closed
Bug 344780
Opened 18 years ago
Closed 18 years ago
Make better breaking spec
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(2 files, 3 obsolete files)
57.25 KB,
text/html
|
Details | |
6.12 KB,
patch
|
Details | Diff | Splinter Review |
I think that we should not break the line before '+', '=' and '-'. Because IE doesn't break the line in this point. And we allow to break after too. So, some table layout cases, we can see only '+' or '=' or '-' line. E.g., 2000-01 - 01T00:00 And '-' are used for date format in some locales. I think that we should not break both before and after if around of '-' are numeric.
Assignee | ||
Updated•18 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•18 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Assignee | ||
Comment 1•18 years ago
|
||
Attachment #229355 -
Flags: review?(jshin1987)
Assignee | ||
Comment 2•18 years ago
|
||
Assignee | ||
Comment 3•18 years ago
|
||
Or there is another idea. That is always not breaking the line between first and second character. But I worry that way, that may have some regression.
Comment 4•18 years ago
|
||
(In reply to comment #3) > Or there is another idea. That is always not breaking the line between first > and second character. But I worry that way, that may have some regression. > That would not fix the problem for the case of the '-' character. Currently hyphenated words break before the hyphen which is incorrect at least in English. hyphenated words are supposed to break following the hyphen.
Assignee | ||
Comment 5•18 years ago
|
||
(In reply to comment #4) > (In reply to comment #3) > > Or there is another idea. That is always not breaking the line between first > > and second character. But I worry that way, that may have some regression. > > > > That would not fix the problem for the case of the '-' character. Currently > hyphenated words break before the hyphen which is incorrect at least in > English. hyphenated words are supposed to break following the hyphen. Right. Thank you.
Comment 6•18 years ago
|
||
(In reply to comment #0) > I think that we should not break the line before '+', '=' and '-'. And %.
Assignee | ||
Comment 7•18 years ago
|
||
(In reply to comment #6) > (In reply to comment #0) > > I think that we should not break the line before '+', '=' and '-'. > > And %. > What case is a problem? If the previous character is numeric, not broken before '%'.
Comment 8•18 years ago
|
||
(In reply to comment #7) > (In reply to comment #6) > > And %. > > What case is a problem? > If the previous character is numeric, not broken before '%'. It shouldn't break after % if the next character is numeric (e.g. %xx in URLs). Also note that % is the modulo operator, so one could argue that it should be treated like *, +, / and so forth.
Assignee | ||
Comment 9•18 years ago
|
||
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > And %. > > > > What case is a problem? > > If the previous character is numeric, not broken before '%'. > > It shouldn't break after % if the next character is numeric (e.g. %xx in URLs). Right and good.
Comment 10•18 years ago
|
||
Breaking "$foo" is also inappropriate (see languages like Perl or PHP) and inconsistent with both IE and Opera.
Assignee | ||
Updated•18 years ago
|
Summary: Should not break the line before '+', '=' and '-' → Make better breaking spec
Assignee | ||
Updated•18 years ago
|
Attachment #229355 -
Flags: review?(jshin1987) → review-
Assignee | ||
Comment 11•18 years ago
|
||
better fix. 1. Don't break after '$' for some script. (IE only breaks if previous is numeric.) 2. Don't break after '%'. But keep to break before it for get param of URL. 3. Don't break around '+' for IE compatible. 4. Don't break around '-'. But keep to break if after char is an alphabet for long word or URL. 5. Don't break around '='. But keep to break if after char is an alphabet for long URL. 6. Don't break after '\' even if after char is alphabet for escape sequence. 7. Don't break around copyright mark(U+A9) for IE compatible. 8. Don't break around reserved mark(U+AE) for IE compatible. 9. Don't break before degree sign(U+B0) even if the before character is alphabet for IE compatible. And don't break after '.' that is bug of bug 255990.(I don't change this table.) We have other non-compatible cases. But I think that this patch is enough for daily use. (I think that we need refactoring for more compatible. Because current spec is difficult to keep the balance between Latin text and Japanese text. Note that current spec is based on Japanese Line Breaking spec(JIS X 4051).)
Attachment #229355 -
Attachment is obsolete: true
Attachment #229356 -
Attachment is obsolete: true
Attachment #229686 -
Flags: review?(jshin1987)
Assignee | ||
Comment 12•18 years ago
|
||
Comment 13•18 years ago
|
||
German quotation marks („x“) missing.
Assignee | ||
Comment 14•18 years ago
|
||
(In reply to comment #13) > German quotation marks („x“) missing. These are not below U+0100... I think that it is not a regression of bug 255990.
Comment 15•18 years ago
|
||
(In reply to comment #14) > I think that it is not a regression of bug 255990. Do you know where similar work has been done? It's trunk-only and probably quite new.
Comment 16•18 years ago
|
||
(In reply to comment #13) > German quotation marks („x“) missing. Dao, could you file a new bug on this, and mention the bug number here? Thanks.
Assignee | ||
Comment 17•18 years ago
|
||
(In reply to comment #15) > (In reply to comment #14) > > I think that it is not a regression of bug 255990. > > Do you know where similar work has been done? It's trunk-only and probably > quite new. > Wow, I see. The patch of bug 255990 isn't affecting to only below U+100.
Assignee | ||
Comment 18•18 years ago
|
||
(In reply to comment #17) > (In reply to comment #15) > > (In reply to comment #14) > > > I think that it is not a regression of bug 255990. > > > > Do you know where similar work has been done? It's trunk-only and probably > > quite new. > > > > Wow, I see. The patch of bug 255990 isn't affecting to only below U+100. > Ah, sorry. My previous comment may be wrong, I misread the code. I'll test it.
Assignee | ||
Comment 19•18 years ago
|
||
(In reply to comment #16) > (In reply to comment #13) > > German quotation marks („x“) missing. I understand why this happen. Because the patch of bug 255990 removed the CJK checking in nsJISx4051LineBreaker. So, the German quotations are affected the patch. I'll check the regression range.
Assignee | ||
Comment 20•18 years ago
|
||
The General Punctuations are override as open/close class. But they are not match to Germany. We should remove the override the specifications.
Attachment #229686 -
Attachment is obsolete: true
Attachment #229836 -
Flags: review?(jshin1987)
Attachment #229686 -
Flags: review?(jshin1987)
Assignee | ||
Updated•18 years ago
|
Attachment #229836 -
Flags: review?(jshin1987)
Assignee | ||
Comment 21•18 years ago
|
||
backed-out the original patch. I'll retry to fix it with UAX#14. If you have some ideas and suggestions, please tell me. -> FIXED(by backed-out)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•