[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2019-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #10 from Eike Rathke --- (Just collecting info and material here for a later README or such) oxttools, Tools for creating language support oxt extensions for LibreOffice https://github.com/silnrsi/oxttools -- You are

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2019-04-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #9 from Stephan Bergmann --- (In reply to Eike Rathke from comment #8) > I'm not quite sure about the oor:op="fuse" vs oor:op="replace" attribute, > i.e. what would actually happen if there are multiple entries for one name.

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2019-04-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #8 from Eike Rathke --- The example has an error in that it adds the node under which is wrong, instead it should be a separate item with a

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2019-04-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #7 from Eike Rathke --- Presumably this is how it's supposed to work: In dictionaries.xcu have ... nod-TH Default US English UI name Your favorite

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2019-04-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #6 from Eike Rathke --- @Martin: The download of the sample from scriptsource.org meanwhile appears to be broken, could you please add documentation here how to actually use the new ExtraLanguage Name and ScriptType

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 martin_hos...@sil.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 Stephan Bergmann changed: What|Removed |Added CC|

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 Commit Notification changed: What|Removed |Added Whiteboard|

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #3 from Commit Notification --- Martin Hosken committed a patch related to this issue. It has been pushed to "master":

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #2 from martin_hos...@sil.org --- I've been asked why the changes to a core file like languagetag.hxx? The way much of the core applications are set up for language is via the use of LanguageTypes which are a 16-bit id after

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 --- Comment #1 from martin_hos...@sil.org --- An implementation patch is available for review https://gerrit.libreoffice.org/#/c/30882/ There is no need to support sequence checking, since sequence checking has to be built into code

[Libreoffice-bugs] [Bug 103855] Add a language code via an extension

2016-11-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103855 martin_hos...@sil.org changed: What|Removed |Added Blocks||103857 Referenced Bugs: