- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Mar 2018 17:03:17 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Hyphenation usages in CJK`, and agreed to the following resolutions: * `RESOLVED: No change on issues #785` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Hyphenation usages in CJK<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/785<br> <dael> florian: In Japanese it uses mixed writing systems. Just because there's latin characters it doesn't mean it's English. It won't get language tagged as English, but they do expect hypenation.<br> <dael> florian: My take is it should just be in the hyphenation dictionary for Japanese. If people want a hypen the hyphen preperty does that if it's in the dictionary. For the rare word that isn't in the dictionary it shoudl be language tagged<br> <dael> myles: Is this just Japanese?<br> <dael> florian: If you're going to use german words, not tag them, and use them in English I'm going to assume it's common in English or the author did it wrong. English does not contain all words of all languages.<br> <tantek> Schadenfreude for non-English languages?<br> <dael> florian: It is somewhat common in Japanese to have words like that, but if they're common they should be in the dictionary. I dont' want a property to hyphenate words not in the language they're in.<br> <dael> florian: tantek's example is good.<br> <dael> florian: Trick with Japanese where you can't tell it by the script in English and German, you can tell it by the script. But if a Japanese person wrote Schadenfreude you can't tell it's not English.<br> <dael> florian: If i's common put it in the dictionary. If it's not known it's not known.<br> <dael> astearns: So florian you suggest don't do anything?<br> <dael> florian: Other then fix bugs in some browsers. In the case where the author doesn't want hyphens, but just breaks between all characters, there's word-break:break-all it's only going to give you places except where there shoudl never be a line break. 2 browsers break absolutely everywhere.<br> <dael> fantasai: Initial complaint is solved by browsers fixing impl of break-all keyword to conform to the spec and include words commonly used in Japanese that use latin characters. For words that aren't common and won't be in Japanese dicitionary authors will need markup to be appropriate.<br> <dael> fantasai: General conclusion is no change to the spec, but initial problem is solved by the three things florian outlines.<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/785#issuecomment-370366049<br> <dael> myles: spec doesn't say which hyphen opportunities exist. I guess I agree with florian. Impl have a lot of leeway on how to hyphenate.<br> <dael> astearns: I'm a little concerned about resolving without koji but I'm personally convinced about no change.<br> <dael> astearns: Objections to resolving no change on this?<br> <dael> RESOLVED: No change on issues #785<br> <dael> hober: florian do you have links to the bugs?<br> <dbaron> I think the relevant Gecko bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1358019 although I might be wrong<br> <dael> florian: I have not. I only wrote the test an hour ago. I'll make a proper test and submit bugs.<br> <dbaron> (and that was filed by fantasai)<br> <dael> florian: koji found this and he said he can't do it because it didn't work in some browsers. dbaron asked if it was some or all and I wrote this test and it's some. It was an ad hock test so I'll write a proper one.<br> <TabAtkins> (just btw)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/785#issuecomment-375019136 using your GitHub account
Received on Wednesday, 21 March 2018 17:03:20 UTC