I’m from the Philippines, and we use “Philippine English”. Skipping what “Philippine English” is, personally, I prefer to have <html lang="en-PH"> but at the same time, I want to avoid editing shadow tiddlers (less headaches when upgrading).
The best path is to create a new language pack, and while at it, I edited some strings to align more with our own variant of English. Based on the current TW version, as of this post, there are a total of 77 strings adjusted for Philippine English.
My questions then are:
Is TW going to accept the English (PH) language pack even though there were only 77 changes?
If not, how do I create my own language pack for my (or our) use?
For the second question, I can’t find information about it other than to open a request in Github or here in the forums so it’ll be added to the main TW language repo. But, that brings us back to my first question. ^_^;;
Since it is based on English, the correct way is to create a new language plugin $:/languages/en-PH with the dependents field set to $:/languages/en-GB( like de-AT, zh-HK and en-US ). Then you can add the 77 translations to the plugin.
For example, de-AT with dependents set to $:/languages/de-DE only has $:/language/Date/Long/Month/1 and $:/language/Date/Short/Month/1 that is different from de-DE, so the language only contain the two translations that is different from de-DE, other translations are inherited from de-DE.
I think you can fork TiddlyWiki5 repository and switch to a new branch en-PH based on master, and create the language en-PH under the languages folder to contribute a new language to tiddlywiki.
@youronlyone … The translators edition seems to be fine. It is OK if you only translated 77 stings if the rest is OK as it is. If elements are missing in a translation, the original en-GB strings are used.
Thanks for your contribution. – If you are able to add 2 more languages. Just go for it. The best way is to use an empty translators edition – change it – create a tiddlyhost edition and post it here or at GitHub.
Since en-GB is the default fallback, a language pack that depends on en-GB does not need a dependents field
That’s right. de-DE should contain all language-strings. – But also here, if there is something missing, it still will fall back to en-GB. So the core mechanisms make sure, that there will be some text, even if it is the “wrong” language.
So de-AT falls back to de-DE, which falls back to en-GB …
Hi @youronlyone I would be delighted to have a translation for Philippine English. @pmario has summarised the contribution process, but feel free to ask any questions.
