Re: [csswg-drafts] [css-text-3] Segment Break Transformation Rules around CJK Punctuation (#5086)

Thank you @MurakamiShinyu for sharing what TeX is doing. It has been polished with time and proven to work. and I agree with your argument.

I have a question may be to @fantasai?  What is the reason that the current rule requires both sides be space-discarding for not inserting a space?

The reason I ask is if the rule requires you to look ahead (the character after), it is hard to determine if one can insert a semantic line break or not at a particular place until you know what you would type next. Unless you are copying some text, you will be thinking what you type while you type. You would pose when your typing catches up your thought. It would be one of the best timing to hit a return key and give your brain a bit more time. You now know what you type and will start typing. At this moment you will notice, oh, oh, I should not have hit a return key after the previous word because a space will or will not be inserted and it is not what I wanted. Rules that require look ahead is OK for a batch processing but not great for typing while thinking.

This will not typically happen for English as having two or more consecutive space-discarding characters is (extremely) rare. However, this scenario happens often in case of Japanese as many nouns are spelled in Latin letters. An extreme case is technical documents. I believe the stuation is the same for Chinese probably with a bit less extent.

-- 
GitHub Notification of comment by kidayasuo
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5086#issuecomment-633875738 using your GitHub account

Received on Tuesday, 26 May 2020 08:08:21 UTC