View source for Thread:Support/Adding a new language/reply (3)
Hi admins! Could you please add the Yola language? I'd like to translate for it! I'm a fluent speaker, and there is a growing revival movement, regarding the classification, it is a living language as it is currently used, and is used as the primary means of communication within the revival movement. My source is both firsthand, and through the information avaialable on Gabble Ing Yola.
ISO 639-3: yol
Yola language - Yola taalke (yol)
(For MediaWiki): English, Scots (Note: Neither of these languages are mutually intelligible with Yola but they are equally as distant and form the closest living relatives, the Anglic family.)
Note that for Glottolog, this is classified as an regional dialect of English spoken on the East coast of Ireland, close to Fingalian, both falling into Southern Irish English. In this classification, Yola is far more distant from Scots than from standard English and all international dialects of modern English.
But may be you're looking into an old version of Yola (dating before the distinction of Middle English, at end of the Middle Age), when Old Anglosaxon coexisted with other Celtic substrates spoken in Irland and Scotland.
But I don't think that Scots (as it is used today) is related to Yola, so "for MediaWiki", the standard English [en] or Irish English [en-IE], are still the nearest "hat language" form, not Scots. May be there's a recent local redevelopment with more borrowings from Scots (or more likely from Celtic Irish, or in the reverse direction from other Low Germanic languages like Frisian or Dutch), in order to renew or reinforce this old dialect in a renewed modernized form? If so, there's a confusion about the term "Yola" (up to 1850 or recent redevelopment), and the proposed use of the ISO 639-3 [yol] code (which currently clearty falls into the Germanic family, not the Celtic family)...
And so may be this is the same kind of confusion that also exists betweeen Scots (Germanic-based), and Celtic Scottish (Scottish Gaelic), caused by the difficulty to distinguish them clearly by a simple name.
Anyway, the language was "officially" declared "extinct" in the 1850's. It survived for liturgical purpose only and in traditional songs and litterature. Its last active speaker, a priest that used it in his public summons at church, died around 1998 (reportedly without any other active user, except possibly people that remember some old songs and have kept some written or audio records). And the attempt to revive it seems to be very recent, by a single(?) person promoting it since last year on the web (is that you or are you in close contact there?), even if it has some documentation in English Wikipedia (but more about its historic aspect, notably before the Norman invasion and the introduction of modern English, first used in vernacular speech as the "Hiberno-English" variant). The ISO 639-3 code [yol] was recently added, probably for handling historical/traditional texts kept in archives.
That language visibly (from its known old written records) shares more features with Frisian than with Scots, even if both Yola and Scots have a similar history and have both been in contacts with Celtic languages, which were more prevalent than modern English used in the same regions, between coastal Ireland, western Scotland and in most parts of Wales, where Frisian people came before the invasion of Normans and later the progressive normalization with modern English (which almost completely "erased" the relicting usage of Middle English dialects, and which also surpassed Celtic languages, i.e. Irish, Welsh, Manx, and Scottish Gaelic, that became minority/secondary/cultural languages). Scots however was more preserved than other Frisian-like dialects of Middle English, because the introduction of Modern English in Scotland was much slower and there was a strong resistance (still existing today in UK whose unification has been contested since long) which also helped to preserve Scottish Gaelic.
Anyway, I see you've created Portal:Yol, I categorized it and added its name in a subtemplate, so that it shows correctly in the portal. For now it is still marked disabled (because using the generated link to the translation interface would not bring to the translation to Yola but to any other (unrelated) user language selected by the user (which could be English or everything else, like French, Irish or anything else depending on current user's preference, so using this link to start "translating" would actually damage existing translation to these other languages). Be careful when using links to the translation interface that the final target page will correctly display the intented language before submitting any translation (unfortunately, translatewiki.net still does not bring any warning: the final target language is not even any one of relevant fallback languages, so this can cause confusion for tentative translators).
Hi! Thank you for responding! In order to not flood the support page, I've left any additional comments on your talk page, Best regards
Wait here for a reply from site admins, if and when they will decide to enable the translation interface (this does not mean that the portal is not useful, at least it can be used to register some other interested users that want to develop it: they can use their Babelbox on the user page to show their support, or can register directly in the portal if they want to translate to it).
But most often, before enabling it, they will need a demonstration site that can be used as a reference accepted by a sufficient community of contributors : e.g. a lexical source or wordlist in Wikisource (this can be the English edition of Wikisource), collecting translated terms in Wikidata, not necessarily creating a beta Wikipedia, it could also be a specific beta edition of Wiktionary, or any other open-source project needed to support the Yola culture and teach it). It can also be some official support in a linguistic department in an Irish University or another cultural institution (ministry, public library, etc.), or a local governement (e.g. at town/city/county level).
Don't hesitate to provide relevant links of such efforts and existing support in the Portal page (but beware about copyright restrictions: don't copy-paste protected contents).
In that case, I'll add the corrections to the additional comments you left in your first reply here so the site admins have a better understanding of the language, I only sent them to you because I thought you were an administrator, sorry about that.
"A.) Yola is not a celtic language, it's a Germanic language that is an offshoot of Early Middle English, with some Irish vocabulary influence (around 40% of words)
B.) There are no recent developments in the language that borrow from Scots, I only listed Scots alongside English because it is another member of the Anglic Family, as it also split from Middle English, meaning that they would both be sister languages in the linguistic sense.
C.) The language is incredibly well attested in writing so there is no need for borrowing from other languages, reconstruction, or otherwise, and the English Wikipedia isn't representative of all the historical documentation of Yola, those are highlighted examples.
D.) There were no other active users in 1998 when Jack Devereux unfortunately passed away, only in the sense that Jack Devereux was known as an avid speaker of the language, even after his death Yola continued to see extensive liturgical use among the Kilmore Choir, the Yola farmstead, and in other local events and song reciting.
E.) The Norman Invasion time-period doesn't constituite the majority of the Corpus of Yola literature, most Yola literature is from the range of the late 18th century to the end of the 19th century.
F.) And lastly I only repeat the mention that the Yola revival did not start last year with a single person, the Yola revival has been an ongoing process since the founding of the Yola farmstead in the early 1990's, they hosted Yola classes, and delivered speeches in the language etc. Sorry for the bombarding of writing, I have no absolutely no grievances with you and merely want to clear up any misconceptions on the Yola language. I do hope you understand my good intentions, and I wish you all the best."
How to replace wrongly translated spelling of a word appearing in language list for language code anp
It is observed that Angika translation of Angika (Code - anp) is being shown in the language list as अङ्गिका . The same should be written as अंगिका .
I am not getting the right link as to where the spelling can be corrected.
Show me the method to replace wrongly translated spelling of a word appearing in language list. Else change the same from अङ्गिका to अंगिका .
Have you already searched the word in Special:SearchTranslations?
Yes, I have searched the word, अङ्गिका and the same was not found in search results.
You may be interested in viewing the previous activities for the same issue;
Hi! I can fix it, bit I usually try to verify language names. Are there any other places where this name appears, for example a dictionary or some other websites?
Oh, I found the reason for the mistake. I'll fix it. Wait just for a few days. Sorry it took so long.
Thank you so much @Amire80 It is everywhere right from Meta to Incubator website of Wikimedia / Wikipedia. I am attaching herewith the screenshots of few websites.
Hello, everyone! I'm excited to share that I am almost finished with a script I've been working on for the past month, called the Terminology gadget. What it does is that it lets translators define translations for English terms that are stored in a central place, and will be shown to others who translate into the same language. You can read more about how it works on Project:Terminology gadget.
I am hoping that this gadget can be enabled as a default gadget for everyone on Translatewiki, but before we can consider that, I need help with testing it to see that everything works as it should. So if you would like to help test it, please enable it in the preferences, and let me know of any bugs/errors you find, or if anything is confusing/difficult to use.
I'm excited to hear what you think!
Bug report: Nothing happens for creating aliases. Steps to reproduce:
- Visit Portal:Zh-hant/terminology.json
- Click "Add term"
- Fill "English term" with "settings"
- Check "This is an alias for another term"
- Select "setting" for "Alias for"
- Click "Save"
Thanks for testing it out, Xiplus! This should be fixed now. Let me know if you find something else. :-)
Not sure if the Translate Extension already has such a feature, if that is not the case, your work or the concept at least should definitely get upstreamed! By the way, I believe the option of creating project-specific terminology entries to be worthy of consideration.
It doesn't, I wouldn't have spent all this time making this if it did. 😜
Yeah, I thought about making project-specific terminology an option when I first started, but it adds a whole extra layer of complexity, not only in the script (where it wouldn't actually be that complicated), but also for those entering/using the definitions in the script. So I think it is better to handle that in other ways, e.g. by specifying in the definitions that "this translation applies to X project or in Y context".
Hi, I found a bug with this gadget: the cross to quit doesn't work.
Another bug report: $VARIANT doesn't work in the "Usage notes" field. We also want this to work so translators can see notes in their preferred variant.
@Tranve: Where/on what page doesn't it work? I only see $VARIANT being used in usage notes on the terms "set" and "setting" in Portal:Zh/terminology.json, and when I checked those in Portal:Zh-hans/terminology.json and Portal:Zh-hant/terminology.json, as well as on  for both variants, it seems to be working like it should.
Weird, now I can't reproduce this problem either, and I have no idea why... Maybe we should mark this issue as fixed now and continue discussion if it arises in the future.
@Tranve: Cool! Do you happen to remember how the error manifested itself? Did it show the wrong variant, or something else? If it showed the wrong variant, it could have happened if you were on Special:Translate and switched between hans and hant in the upper right-hand corner. I need to figure out a way for the script to reload when the users switch language (there is already a thread about that on the gadget talk page, but it's not really an easy fix).
Hello everyone! Most of the bugs have been ironed out now. I'd be very happy if some more people would help test it, and report back here (or on its talk page and let me know if you find something that seems off. :-)
It's a great gadget indeed. However, it would be more helpful if a "category" feature is introduced into it.
For example, our current glossary table sort all terminologies by project.
If we can do it with the gadget, hopefully we can eventually replace this page with the terminology gadget's definition page, which can help avoid duplications (there are two glossary tables currently!) and out-of-sync content.
Unless there is some standard body or community defining an encoding for those dialects, and that have registered a documented code for it, you cannot encode dialects of what is still considered the same language. BCP 47 allows compleing a language code (from ISO 639) with extra fields : a script code (from ISO 15924), a region code (two letters from ISO 639-1 or 3 digits from UN M.49), an "extlang" field (specific to BCP 47 but for most reasons, kept only for capabilities and frozen since it was actually used for extending ISO 639 when it was too fuzzy, and it has been replaced by ISO 639-3), and a code for dialects (5 to 8 letters or digits, no suppporting standard for now, all that exists is some codes registered in the IANA database for some dialects).
Wikimedia has registered for itself a few nonstandard codes (that are not part of BCP47 or ISO 639) for some "languages", which are in fact not languages in ISO 639 but dialects, and that also violates BCP 47, such as "roa-tara" (for Tarantino, which is a dialect of Napolitan encoded [nap] in ISO 639 and BCP 47). BCP 47 does not defin any way to infer such relation. However those codes exist in Wikimedia only because there were an agreement in Wikimedia communities to support them like this (even if this violated the BCP 47 format requirements, in fact that code was added BEFORE BCP47 was revized with the publication of ISO 639-3: today it would certainly not be encoded this way in Wikimedia, using a 3-letter code that was defined in ISO 639-2 as an "exclusive" code for the "Romance" language subfamily and not the 3 letter-code "nap" of Napolitan, complemetned by a non-registered "extlang" field which in fact violates BCP 47 as if "tara" was a script code).
The best code you may use, with any formal agreement by a standard body, is to use "private-use" extension after the base language code, such as "scn-x-salen" or "scn-x-cmcal" (with the "x" prefix for private use, after which the subfield can be letters or digits and have no constraints other than using one or more subfields that are 1 to 8 letters or digits, separated by a single hyphen).
But you'll notice that this is "private use" and this still required a private agreement: to be eligible for use here on this wiki, you'd first need to publish this private agreement and who supports it. Without it, there's no way to use such codes in this wiki, which is not even targetting only Wikiemdia projects: here we need such formal and public agreement (after discussing it and establishing a consensus). And this wiki is not the proper place to get this consensus: so you need to find a sponsoring community or standard body listing such code (and documenting it for public use, without licencing restrictions to get the basic documentation).
If you look into "Glottolog", you'll find it is uses its own private codes for dialects for local use; if you look at other lingusitic lists, they use their own private codes as well (different from those used in Glottolog): there's no standard agreed even between them... And for now we've have never seen any draft for a possible future standard list if dialects (the last attempt to make it in ISO 639 in a new part was abandoned: we are too far from being comprehensive enough, and in fact there's LOT of disagreements even between linguists about what are "dialects", and how they are separated in regional space, or in time/epoch, or in social usage: even the same speaker may have several "registers" of speech, possibly non neutral and politically oriented, depending with whom they are talking and how their speech will be recorded and reused).
As well, BCP 47 codes using region codes (such as "fr-ca" or "en-gb") are deprecated: country codes are not very relevant and are politcally oriented with boundaries that do not correctly represent the effective regional separation of language variants. Even "British English" has its own variants, such as Oxford English, or Bootlings; there are many vernacular variants existing for most languages (and notably the largest ones spoken by more than about a few dozens of thousands people), this is unavoidable and very varaible over time and epoch (because people are moving, dying, opinions and usages are diverging or converging in different directions with clusters being constantly splitted or merged and following their own genetic history whose classification becomes more and more fuzzy over time).
We are currently working on the Chinese glossary table, and have merged all entries into Portal:Zh/Glossary/General. Now we request these following:
- Move Portal:Zh/Glossary/General to Portal:Zh/Glossary, without redirection
- Delete these following pages:
Hello, Houston. We had a problem. I translated ~500 core messages. Yesterday I've got message "Language code sjn is not valid.". What happened?
The language code: Sjn is actually not supported by translatewiki. We recently fixed a long standing bug where translators were allowed to translate to unsupported & invalid language codes. While sjn is valid, it is not supported by translatewiki.
I'm informing one of our staff who will review if support for this can be added to translatewiki.
Hey, I hope you haven't forgotten about my problem. I would like to fill out the application required to add a new language section on Wikipedia in Sindarin (sjn). I have previously translated 500 core posts and hope to continue translating in the future.
The line for which constructed languages in scope for translatewiki.net is a bit fuzzy. We have Esperanto and Volapük but not Klingon for example. Is Sindarin being used as a general purpose language?
Please tell me what happen for my comment. https://translatewiki.net/w/i.php?title=Special:AbuseLog&wpSearchUser=Xiplus
Hi, when I write Mon dictionary articles in many languages I understand, I find annoying English numbers, I would like to request that these be change into Mon numbers. This is because when I was writing a modern Mon dictionary article for the Mon language, the mix of Mon and English could be a learning mistake for people studying the dictionary, so request to change English numbers from Mon numbers.
- Sample photo
In 2016, Mon, Pali, English, Burmese, Thai, Japanese I myself have published a dictionary of 6 languages, I am still the only one who writes multiple dictionaries for Mon Wiktionary, I love Mon Wiktionary because Mon Wiktionary is a dictionary for learning Mon vocabulary for modern youth and many people, thanks.
This is definitely NOT a problem of translation on Translatewiki.net.
Numbering format for ordered lists is not handled directly by this wiki, but is part of MediaWiki. In fact Mediawiki just uses standard HTML5 to generate list items; HTML5 is then rendering list items based on CSS properties, depending on the "list-style-type:decimal" (see https://www.w3schools.com/cssref/pr_list-style-type.asp, or https://developer.mozilla.org/fr/docs/Web/CSS/list-style-type).
The decimal type should work for most scripts having decimal digits, but the browser must have support for decimal number types in each relevant script, and the page must be properly marked with the appropriate language tag to decide how to render decimal numbers.
The problem you have for Mon (ISO 639 codes : [mnw] for Modern Mon, [omx] for Old Mon) is that this language is not natively recognized by browsers to use the traditional digits of the Burmese/Myanmar script (ISO 15924 code: Mymr) that you want for the Mon language. In addition, the Myanmar/Burmese language uses the Burmese/Myanmar script, but it does not take its own traditional decimal digits by default. As well there are some Mon variants used in Thailand (or that were used in the south of the old Mon kingdom when that part also spoke Old Mon but are now found in epigraphic relics in Thailand, later reproduced there by the local Mon minority) and written now with the Thai script (plus, most Mon people are now monolingual in Burmese or Thai languages only, with only minor knowledge of their Mon language, but some of them are attempting to revive the modern Mon language with lot of difficulties; and they are using modern digits). all modern Monic minorities speak variants that are mostly intelligible with each other, even if they are written in different scripts, and for practical reason, they do not use the Burmese digits (which are modern creations coming from North Burma before the Mon majority were overwhelmed by Burmese/myanmarese in "South Burma" people or by Thai). Burmese digits or Thai digits or Latin digits are all foreign to Mon speakers, even if today's Burma/Myanmar got their "native" script from Mon (but Burmese also have used various other scripts as well in the past). So the choice of decimal digits to use for Modern Mon language is not clear...
So you need to explicitly use the "list-style-type:myanmar".
This can be done on the default CSS stylesheet for the Mon wiki; or by using an HTML container specifying this style. (note that ordered lists in Mediawiki markup don't use any tag, only "#" at start of lines for each numbered item; and MediaWiki autogenerates the "ul" container element and the "li" element for each item of the list, so you cannot style these elements directly, unless you use plain HTML tags and not the simpler MediaWiki syntax). Mediawiki for now does not suppport any way to add custom attributes (such as style="", id="", or start="") on list items or on its autogenerated "ol", "ul" or "dl" container ("ol" for ordered lists using numbered items, or "ul" in unordered lists using bulletted items, or "dl" for definition list using definition terms and indented definition text) written with the wiki syntax (even though it is possible for tables, table captions, table cells and table rows).
Note that "list-style-type:myanmar" in CSS styles will work on modern browsers only, not all webbrowsers..
I can understand up to eight kinds in Mon language, I am currently working on a lot of Mon language.
- You can watch the video of the consonant script that is currently used by the Mon people.
- File:Consonants mnw.webm
- At this link you can learn the alphabet and arithmetic commonly used by the Mon people today.
- If you want to learn Old Mon script and Mon Thaiมอญไทย script or ไทยรามัญThai Raman, you can learn at this link, I wrote a little bit in that link, Mon Thai script can be understood by Mon people in Burma but there is no font yet.
- You can see the Mon Thai script photo here.
I am also a music writer and interested in learning many languages, I also have a passion for upgrading languages that are lacking in modernity, thanks.
I actually started doing this already, but I made a mistake along the way, and it wasn't deployed. I'll fix it soon.
Thank you very much sir, I wish you a happy new year.
Typo in English source (a letter 'i' is missing in "participants": https://translatewiki.net/w/i.php?title=Special:Translate&showMessage=isa-3d6a01-No_partcipants_has_contributed&group=wikimedia-tools-isa
Thanks for noticing! Pages in message namespaces don't get categorized like normal pages. We should figure out a way to do that, or to list those page some other way.
You can still list pages in the message namespaces (whose contents are not normal Mediawiki pages and cannot be modified by inserting a deletion request template) by posting a message to the Support page. For now, there's no other way for users to add metadata to mark and track those message pages for discussion (even if this wiki supports some metadata extensions, with SemanticMetaWiki or page content types, those extensions are still not defining any way such maintenance requests).
I'd like to change my username to Mannivu so it can be consistent with my MediaWiki account. Thank you!
Duplicated messages of their zh-hant version. Should be untranslated.
Hi, I guess my request to become a translator has been forgotten. May I remind you of it. Thanks.
Hi! I gave you the permissions.
I'm not sure what happened... The usual process is to create the account on the main page and to submit some test translations, but for some reasons your account was created without inviting you to do test translations.
In any case, since you appear to be an experienced wiki editor, I've given you the permissions. Welcome and happy new year! :)
Dear administrators! Could you add an aleut language (cyrillic script & latin script)? I'd like to translate wiki to it.
ISO 639-3: ale
Aleut language - Unangam tunuu - Унаӈам тунуу (ale)
Scripts: cyrillic, latin...
(For MediaWiki): English, Russian.
Thank you. Best Regards
Yes, cyrillics used by aleuts in Russia, latin script used by aleuts in the USA.
Very sorry it took so long.
It's now enabled.
I have spent the last year restructuring the code for Waymarkedtrails. The website part is moving into a separate repo: https://github.com/waymarkedtrails/waymarkedtrails-website
I'd like to move the translation files to the new website repo. The new repo has a similar structure for the translations. The base directory for translations is: https://github.com/waymarkedtrails/waymarkedtrails-website/tree/master/src/i18n Each language has its own subdirectory with two files:
- helppages.yaml is exactly the same as it was in the original repo.
- messages.yaml replaces the old gettext translations. It is now also in yaml format with markdown content, i.e. exactly the same format as helppages.yaml. I have left the messages themselves intact where possible and converted the translations. I have also left the header with the translatewiki in place.
The qot/ and qqq/ languages remain in their previous functions as source and place for comments.
Is it possible to move the translation process over to the new repository like this? I have already given the translatewiki.net user write access. If there is anything else I can do to help, let me know.
Thanks for reaching out. We should be able to move to using the new repository.
How often are the translation being migrated from https://github.com/waymarkedtrails/waymarked-trails-site to https://github.com/waymarkedtrails/waymarkedtrails-website. Is it easy to do? Basically, we'd not like to lose any translations that have been made.
That's good to hear. Thanks, Abijeet.
I have a script with which I can sync translations coming in to the old repo. It's fairly easy to do but it is still a manual process (with the usual implication that I have to remember to run in). The translations are up to date right now with the latest commit from Dec 13th.
We've migrated translatewiki to track the new repository.
Previously there was a symbolic link from "no" to "nb" to avoid imports from Waymarked Trails. Shall we remove it?
Awesome, thank you.
The links are no longer necessary. Language aliases are now handled in the code.
There was a commit this morning to django/locale/scn/LC_MESSAGES/django.po in the old repo which I haven't synced yet. Do you want me to do that manually or will it be in the next commit from your side?
This user inserts random english text in his telugu translations, is it normal?
I have deleted all of their changes, but I'm not able to block them at the moment – getting a "fatal exception" when I'm trying to do so.
In 2021, I was the founder of the Wikipedia Pa'O languages(blk) and Wikipedia Western Pwo Karen languages(pwo). I have a lot of responsibility to continue working on the Pa'O language and Western Pwo Karen language in this Translatewiki, but I'm the only person working on this Pa'O language and Western Pwo Karen language and will be late for work, because I have a lot of work to do.
- Wikipedia Western Pwo Karen languages Page Link= https://incubator.wikimedia.org/wiki/Wp/pwo/%E1%80%9C%E1%80%B6%E1%81%AC%E1%80%98%E1%80%BB%E1%80%B6%E1%81%AD%E1%80%80%E1%80%BB%E1%81%A9
- Western Pwo Karen Language Name Request
Request to change (ဖျိၩ့ / ဖျိၩ့ၡိ) name to (ပှဖျိၩ့ၡိ), the translation of this (ပှဖျိၩ့ၡိ) is as follows. ပှဖျိၩ့ၡိ=Pwo Karen ၦဖျိၩ့ၡိအလၨဆၧချဲၩ့=Western Pwo Karen language This (ပှဖျိၩ့ၡိ) is commonly used Vocabulary, this (ဖျိၩ့ / ဖျိၩ့ၡိ) is completely misspelled, thanks.
Can you please clarify some things?
- Do you want to add support for translating into Westenr Pwo Karen (pwo)?
- Who is going to translate? You are already translating to a lot of languages. I really recommend that you focus on a few languages that you know well, because when you translate to a lot of languages at once, you are not completing any projects, and the quality may suffer, too. I recommend that you bring in people who know these languages as users to this site.
- Where do you see the current names that look incorrect to you?
- What is the source for the correct names?
I will translate slowly for Western Pwo Karen(pwo), because I am the only person currently assisting in the Western Pwo Karen language. Do I have to do nothing for Western Pwo Karen? So who will help for Western Pwo Karen? I have discussed with many people for Western Pwo Karen language assistance, they have many technical difficulties for Western Pwo Karen language assistance. most people are not interested in writing Western Pwo Karen, I are working with Naw Khu Mae to develop this Western Pwo Karen language. Naw Khu Mae cannot translate using this Translatewiki., this is because the internet in Burma blocks wiki. I am working in consultation with Naw Khu Mae, a Western Pwo Karen language expert., I came to this Translatewik to work for many languages, I have a lot of work to do, thanks.
OK, I understand. This answers my questions 1 and 2.
How about questions 3 and 4? Where do you see the current names that look incorrect to you, and what is the source for the correct names that you suggest?
- My answer
- I will translate as much as I can for the current Pa'O language and Western Pwo Karen language, it depends on my free time to translate all the messages, I also have a lot of songwriting work for NMB48 company, so in my spare time I will continue to translate for Pa'O language and Western Pwo Karen language.
- The (ဖျိၩ့ / ဖျိၩ့ၡိ) name used in the Portal:pwo is misspelled, the spelling is (ပှဖျိၩ့ၡိ), not (ဖျိၩ့ / ဖျိၩ့ၡိ), would you like me to send you evidence of this name?
- The (ကညီစှီၤကျိ) name used in the Portal:ksw is misspelled, the spelling is (ကညီစှီၤကျိာ်). not (ကညီစှီၤကျိ), I would like Admin to take a closer look at the evidence I sent Admin yesterday.
- There is still a lot of work to be done. I am currently trying my best to get Pa'O language approval on the Wikipedia project. Most locals in Burma do not understand much about Wikipedia project, they only understand Facebook, it is not an easy task to invite local people in Burma to use the Wikipedia project. I spent almost three years discussing the inclusion of Pa'O language and Western Pwo Karen language in the Wikipedia project. I am still in discussions for another Rakhine language, Rawang language, Northern Thai language, it's been almost four years since our Facebook discussions, thanks.
How to convert Arabic numbers 0-9 to Balinese script numbers ᭐-᭙ ?
Hi, as far as I'm aware this is not possible with standard MediaWiki functions. However, it would be rather easy to create a Lua module for that on the Balinese Wikipedia – do you want any help with that?
I actually think it's possible. Nike, can it be done by adding $digitTransformTable to MessagesBan_bali (when it's created)?
I am part of the OpenStreetMap.org operations team.
Please can the following be done:
- Remove: en-gb translation (it is widely out of date, has incorrect licence translation and causes us issues etc)
- Remove: All non english translations text from key intro_3_1_html and credit_2_1_html (And clear cache?), we changed EN a long time ago, but incorrect old translations were used in most cases.
Is there a better place I should be raising these issues?
Apologize for the delay in responding to this.
- You'd like to have ALL en-gb translations removed
- You'd like all translations for the following removed,