Summary: | Short language codes don't work as Locale identifiers for dictionaries | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Rimas Kudelis <rq> |
Component: | Linguistic | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | aurimas, gautier.sophie, jmadero.dev, serval2412, timar |
Version: | 4.0.1.1 rc | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 64382 |
Description
Rimas Kudelis
2013-06-28 19:46:28 UTC
Andras: I was comparing with other dictionaries, eg http://opengrok.libreoffice.org/xref/dictionaries/an_ES/dictionaries.xcu and saw that it's possible to put several values. So, could we change: <value>lt-LT</value> to <value>lt lt-LT</value> ? Or is it less "naive" than this? In (In reply to comment #1) > Andras: I was comparing with other dictionaries, eg > http://opengrok.libreoffice.org/xref/dictionaries/an_ES/dictionaries.xcu > and saw that it's possible to put several values. > So, could we change: > <value>lt-LT</value> > to > <value>lt lt-LT</value> > ? Or is it less "naive" than this? In fact, that's what I did upstream for now. But I haven't got feedback yet about whether it works or not... In any case, that would be a temporary workaround for bug #64382, not a bugfix, and certainly, not a bugfix for this bug. just for my information, why is it just a workaround and not a bugfix? (In reply to comment #3) > just for my information, why is it just a workaround and not a bugfix? Because maybe you can write <value>foo bar baz lt lt-LT</value> there, and all but lt-LT will be just ignored. (In reply to comment #3) > just for my information, why is it just a workaround and not a bugfix? Because the problem is that valid two-letter codes do not work in LibO, and I believe that they should. I explicitly mentioned that it the last sentence of the initial comment by the way. :) If you're right and if I understand well, it means http://opengrok.libreoffice.org/xref/dictionaries/an_ES/dictionaries.xcu is wrong too, since we can see: 6 <prop oor:name="Locations" oor:type="oor:string-list"> 7 <value>%origin%/an_ES.aff %origin%/an_ES.dic</value> and in this case, what's the meaning of "string-list" here? Sorry Julien, but I don't understand your question. Rimas, the question was more for Andras but I meant : the xml file defines this field as "string-list", so we may expect being able to put several values like in http://opengrok.libreoffice.org/xref/dictionaries/an_ES/dictionaries.xcu So if it doesn't work, how does "string-list" work? Should it be: <prop oor:name="Locations" oor:type="oor:string-list"> <value>%origin%/an_ES.aff</value> <value>%origin%/an_ES.dic</value> (In reply to comment #8) > Rimas, the question was more for Andras but I meant : > the xml file defines this field as "string-list", so we may expect being > able to put several values like in > http://opengrok.libreoffice.org/xref/dictionaries/an_ES/dictionaries.xcu > So if it doesn't work, how does "string-list" work? > Should it be: > <prop oor:name="Locations" oor:type="oor:string-list"> > <value>%origin%/an_ES.aff</value> > <value>%origin%/an_ES.dic</value> Oh, I think you misunderstood Andras' comment. I think his point was that from <value>foo bar baz lt lt-LT</value>, 'lt-LT' will be the only value treated as valid, because it conforms ll-CC form. Any updates here? Sophie I thought you might have an opinion on this one. Set to New because both Rimas and Andras know better than any one what they are talking about :) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.