Jump to content

Support

From translatewiki.net
Support — Problems? Questions? Suggestions? Write your message below. — See also the FAQ or try to catch us in IRC or in Telegram.
Archives
2023
  • Jan
  • Feb
  • Mar
  • Apr
  • May
  • Jun
  • Jul
  • Aug
  • Sep
  • Oct
  • Nov
  • Dec
2024
2025
  • Jan
  • Feb
  • Mar
  • Apr
  • May
  • Jun
  • Jul
  • Aug
  • Sep
  • Oct
  • Nov
  • Dec


Delete non-translations in hif-latn

Smcnarayan contributed a number of “translations” that are characterwise the same as the English original, and these non-translations somehow went unnoticed for seven years (maybe because most of the translations are different from the English originals, so they at least look like valid translations – I don’t speak Fiji Hindi, so I can’t tell for sure). The following 64 messages repeat characterwise the English originals:

While some shorter ones may actually be correct in Fiji Hindi as well, longer ones like MediaWiki:Api-error-filetype-banned-type/hif-latn certainly aren’t, and we don’t lose anything by deleting the shorter ones either: the same English message steps in. So could someone delete these messages?

I also think that quite a few of the other edits are non-translations, but I couldn’t find an easy way to find those using Pywikibot. Here’s what I did; if someone has an idea for finding further non-translations, I’d welcome it. 

>>> site = ... # got a pywikibot.Site object for Translatewiki
>>> contribs = list(site.usercontribs('Smcnarayan'))
>>> messages = [c['title'].partition('/') for c in contribs]
>>> msgs = [msg for (msg, slash, lang) in messages if lang == 'hif-latn']
>>> len(msgs)
640
>>> contents = {msg: (pywikibot.Page(site, msg + '/hif-latn').get(), pywikibot.Page(site, msg + '/en').get()) for msg in msgs}
>>> bad = [(id, en) for (id, (hif, en)) in contents.items() if hif == en]
>>> len(bad)
64

Tacsipacsi (talk) 22:51, 19 October 2024 (UTC)[reply]

Could someone do something about this? —Tacsipacsi (talk) 21:42, 20 November 2024 (UTC)[reply]
I deleted the unchanged messages which are equal to english source. Xqt (talk) 13:03, 9 December 2024 (UTC)[reply]
Thanks Xqt for deleting the exact duplicates, and thanks Thakurji for fixing many of the translations, so that they didn’t have to be deleted. One exact duplicate still remains: Wikimedia:Gapfinder-article-flag-not-notable/hif-latn is the same as Wikimedia:Gapfinder-article-flag-not-notable/en, although this message seems to have been removed from translation in the meantime. However, I think it’s still worth being deleted: should that message ever become translatable again, we’ll have a wrong translation; and the purpose of keeping untranslatable message doesn’t apply here either: translators shouldn’t get the suggestion that the translation of Not notable for $1 Wikipedia is Not notable for $1 Wikipedia. —Tacsipacsi (talk) 11:22, 21 December 2024 (UTC)[reply]
Done Done Xqt (talk) 14:01, 22 December 2024 (UTC)[reply]

review request

Can somebody please review this patch because such i18n aren't very useful. Thanks. Xqt (talk) 12:43, 9 December 2024 (UTC)[reply]

Done Done already, thanks Xqt (talk) 19:19, 11 December 2024 (UTC)[reply]

Enable translation to the southwestern/"Chippewa" dialect of Ojibwe (ciw)

I would like to translate into the southwestern dialect of Ojibwe

ISO 693-3 code: ciw

Native name: Anishinaabemowin or Ojibwemowin (the specific region would be zhaawani-ningaabii'ani-ojibwewakiing)

JGHFunRun (talk) 20:03, 11 December 2024 (UTC)[reply]

Do you actually know this language? Amir E. Aharoni (talk) 17:39, 25 December 2024 (UTC)[reply]

authorization to upload PO files

Hi. I need authorization to make offline translations. Can you give it to me? Túlio (talk) 13:00, 13 December 2024 (UTC)[reply]

@Tuliouel: Hi, the process for getting access to do that is outlined in Translating:Offline. Jon Harald Søby (talk) 21:10, 13 December 2024 (UTC)[reply]
Really? I thought I had just read that and had followed the exact instructions in it! Túlio (talk) 22:14, 13 December 2024 (UTC)[reply]
@Tuliouel: Did you already e-mail some offline translations to translatewiki at translatewiki dot net? Jon Harald Søby (talk) 09:26, 19 December 2024 (UTC)[reply]
Yes, I did. Túlio (talk) 18:31, 19 December 2024 (UTC)[reply]

Preferences broken

As of yesterday, I can no longer change my interface and translation language from Dutch in the selector at the top. Any selection appears to be ignored.

Probably related: when visiting Special:Preferences the following appears instead of the preferences:

[c36555909417252ce3c73d81] 2024-12-13 14:35:01: Fatale fout van type "Wikimedia\Assert\PreconditionException"

McDutchie (discussion) 14:39, 13 December 2024 (UTC)[reply]

Confirmed. Raymond 13:17, 14 December 2024 (UTC)[reply]
See phab:T381982. —Tacsipacsi (talk) 11:24, 21 December 2024 (UTC)[reply]
Thanks. It appears to be fixed now. McDutchie (discussion) 23:50, 21 December 2024 (UTC)[reply]
Yes, the faulty patch was reverted for now. It’ll be reapplied in a hopefully fixed version in 2025. —Tacsipacsi (talk) 12:17, 22 December 2024 (UTC)[reply]

admin

Hello, I don’t know who to ask, we have a small language section, and there was only one administrator who has not been active for a year, accordingly there is no bureaucrat in our section, our section has no administrator, I am the only user who has been involved since the beginning of the creation of the section, I I would like to become an administrator, how can I apply to become a section administrator Къарачайлы (talk) 11:54, 16 December 2024 (UTC)[reply]

Please see m:Steward requests/Permissions. Amir E. Aharoni (talk) 17:26, 16 December 2024 (UTC)[reply]

Translated untranslatable messages

{{Msg-meta}} (used in {{Msg-mw}} etc.) uses MediaWiki:Quotes (“test”) to render messages. As far as I can tell, it seems to work in English as well as other languages to show text wrapped in some variation of "quote" marks. Despite that, if you go to Special:Translations/MediaWiki:Quotes, it tells you that it is not actually a translatable message. Current translations can therefore only be seen at Special:PrefixIndex/MediaWiki:Quotes.

This behaviour is different from Special:Translations/MediaWiki:Parentheses, Special:Translations/MediaWiki:Brackets etc. which do display the translations. Why is Quotes in particular handled like that, and is there any reason why it does not behave like other similar optional messages? stjn[ru] 17:29, 18 December 2024 (UTC)[reply]

Maybe Quotes (page does not exist) should be added to MediaWiki:Betawiki-messages? That way it will be shown to translators when translating the Translatewiki.net group (there are already a few messages there used in TWN templates), and Special:Translations/MediaWiki:Quotes will work as it should. Jon Harald Søby (talk) 16:01, 25 December 2024 (UTC)[reply]

About Phabricator:phabricator-config-dc6ff45a1e325e0e/fr

This is the second time I find a russian translation instead of a french translation in Phabricator translations. I fixed it of course, here is a link to the previous version: https://translatewiki.net/w/i.php?title=Phabricator:phabricator-config-dc6ff45a1e325e0e/fr&oldid=12036558.

I suspect there are more, but I cannot read all 19,410 Phabricator messages in translatewiki to fix them.

Could someone help me find them ? —Preceding unsigned comment added by Mahabarata (talk • contributions) 22:34, 20 December 2024 (UTC)[reply]

Fortunately Russian uses the Cyrillic alphabet, so I could just run git grep -P '[А-Яа-я]+' '*/fr.json' in the Phabricator Translations Git repo to find any supposedly French translations that contain Cyrillic characters. The result: there’s only one message left, Phabricator:phabricator-config-4499d894d192c25b/fr. —Tacsipacsi (talk) 11:43, 21 December 2024 (UTC)[reply]
Thanks, I fix it.
Looking at translations of Saimongoltinio, the author of the russian text, I found another russian text in Phabricator:phabricator-config-25eeedb05ca36a08/fr — translatewiki.net. This message has an English page at Phabricator:phabricator-config-25eeedb05ca36a08/en — translatewiki.net but this message is not on translatewiki. Why? Where is it? And at this "place", maybe there are other russian texts you didn't find with your request: could you help me to find them? Mahabarata (talk) 13:49, 25 December 2024 (UTC)[reply]
The English message was removed in phab:rPHTR384a44afbad07deb17590ddd68a17cdf6f8cabea, the translations a few hours later in phab:rPHTR170173c7bf2ddd81a92a6e328cacb6034bedaecf. If you don’t see the documentation and the English text when you open the message for editing, that means that probably the message is no longer used anywhere (so the answer to “Where is it?” is “nowhere”), and was only kept to use it as an aid in other translations (as discussed above). So fixing the translations just wastes your time, but it may make sense to request their deletion in order to remove them from the translation aids.
Since these messages are no longer exported to any repository, the way I used to find the previous one doesn’t work (there is no Git repo to run the command in). It may be possible to go through the edits of Saimongoltinio with a program, but given that they’ve had only 83 edits so far, simply searching for /fr on https://translatewiki.net/w/i.php?title=Special:Contributions/Saimongoltinio&target=Saimongoltinio&limit=500 is more effective. —Tacsipacsi (talk) 15:44, 25 December 2024 (UTC)[reply]
Ok, thanks. Mahabarata (talk) 12:20, 26 December 2024 (UTC)[reply]
When looking at the English text, I remembered another similar message that I translated a few days ago. After a search, I found that the first (and no more used) message was replaced by this one Phabricator:phabricator-config-00ae349f1ce0e6f9/en — translatewiki.net Mahabarata (talk) 12:36, 26 December 2024 (UTC)[reply]

i.php

Is there any reason to call the main PHP script i.php instead of the standard name index.php? I’ve tried to hot load Navigation Popups several times over the years, every time to find out that it breaks badly because it cannot extract the page title from URLs like https://translatewiki.net/w/i.php?title=Support. —Tacsipacsi (talk) 11:48, 21 December 2024 (UTC)[reply]

While not commenting on the wider issue, Navigation Popups gadget should be fixed to use mw.config.get( 'wgScript' ) variable instead of assuming things are always /w/index.php. Seems like something that could be fixed. stjn[ru] 13:28, 21 December 2024 (UTC)[reply]
Navigation Popups uses mw.config.get('wgScriptPath') + /\/(index\.php|wiki\.phtml)/ (roughly speaking; of course you can’t actually meaningfully concatenate a string with a RegExp). Switching to mw.config.get('wgScript') would lose the ability to recognize old wiki.phtml links (which still do exist in the wild, e.g. an enwiki search gives almost 20,000 results across namespaces). Paths other than /w are properly handled by using the config, it makes assumptions only about the file name. —Tacsipacsi (talk) 14:49, 21 December 2024 (UTC)[reply]
For comparison, enWP search for index.php gives more than one million links. I understand what you’re saying, but I don’t think this is enough of a justification to make assumptions about wiki URLs that end up wrong. stjn[ru] 15:40, 21 December 2024 (UTC)[reply]
Of which probably quite a few have nothing to do with MediaWiki. But even assuming that all the million links point to a MediaWiki wiki, it means that about 2% of non-clean links use the old endpoint, which is an impressive number given that index.php was introduced in mw:MediaWiki 1.2, over two decades ago, and just seven months after the very first MediaWiki release. I don’t think it’s a very wild assumption: when one downloads MediaWiki, they get an archive that they can put wherever they want (so the path may vary) and that contains an index.php file (so the file is the same unless one actively changes it). —Tacsipacsi (talk) 16:52, 21 December 2024 (UTC)[reply]
I proposed a change to Navigation Popups that should fix this issue. Jon Harald Søby (talk) 20:02, 22 December 2024 (UTC)[reply]

Request to Activate Lampung Api language

Dear Translatewiki Team,

I am writing to request the activation of the Lampung Api language on Translatewiki.

ISO 639-3: ljp

English Name: Lampung Api

Native Name: Lampung Api

It has approximately 1,3 million speakers across Indonesia.

It is written in Latin script and Lampung script (Native name: Had Lampung/Kaganga) which is not yet added to Unicode standard.

Portal: https://translatewiki.net/wiki/Portal:Ljp

As a contributor and advocate for the Lampungese community, I believe enabling this language will significantly support localization efforts and promote the preservation and usage of Lampung Api in various digital contexts. The activation of this language will allow contributors to translate software interfaces, helping to make technology more accessible to Lampungese speakers worldwide. If there are specific requirements or steps needed to proceed with this activation, please let me know, and I will gladly assist. Thank you for considering this request. I look forward to your response and the possibility of working together to bring the Lampung Api language to Translatewiki.

Best regards, Dede DedeKurnn (talk) 05:01, 23 December 2024 (UTC)[reply]

Hi,
Thank you for the request.
How different is this language from Komering (kge)? There is a Wikipedia in it at https://kge.wikipedia.org . Amir E. Aharoni (talk) 18:17, 25 December 2024 (UTC)[reply]
Komering (kge) is a dialect of Lampungic language family, and sometimes included in Lampung Api, sometimes treated as an entirely separate language. Komering people see themselves as ethnically separate from, but related to, Lampung people. Both Lampung Api and Komering is mutually intelegible, but somewhat different in spelling, pronunciation, and vocabulary. Both use different kind of traditional script for writing, Lampung use Kaganga/Had Lampung, while Komering can be written with Jawi (Arabic script) and Komering script. You can read more about the details here: https://en.wikipedia.org/wiki/Lampung_language DedeKurnn (talk) 00:30, 26 December 2024 (UTC)[reply]
We also have Wikimedia Incubator program for Lampung Api and Lampung Nyo, and as a native speaker I actively write articles in Wikimedia Incubator for Lampung Api language.
https://incubator.wikimedia.org/wiki/Wp/ljp/Main_Page DedeKurnn (talk) 00:45, 26 December 2024 (UTC)[reply]
@Amire80: Just wanted to add as an active editor (under User:Swarabakti) in kge.wp. Lampungic itself is pretty diverse dialectologically in terms of phonology, lexicon, and even morphology (but less so in syntax). That said, studies in early 2000s (cf. Anderbeck 2007 and Hanawalt 2007 in the "Lampung language" article on en.wp) have clarified the relationship between these varieties and proposed the three-way division currently adopted by ISO 639-3 (down from 9 separate codes). You can read them to get a clearer picture of the differences but in short:
  • Nyo dialects clearly constitute a distinct, cohesive dialect cluster within Lampungic, but the other varieties form a large dialect chain stretching from Kayuagung down to Kalianda, with no clear boundaries between them.
  • Within this dialect chain, Hanawalt (2007) considers Komering to be sufficiently distinct on both linguistic and sociological grounds, but possibly also Kayuagung (formerly coded [vky], currently under [kge]), Daya, and Jabung (the last two now under [ljp], though some Daya people consider themselves ethnically closer to Komering).
  • Anecdotally, I can say that the phonological, lexical, and morphological differences between these varieties are almost comparable to e.g. that of distinctly coded languages within the Southern Batak subgroup (Toba [bbc], Angkola [akb], Mandailing [btm]), only that the clustering is less clear — a classic case of dialect continuum, really.
Note also that both Lampung Api and Lampung Nyo enjoy greater institutional support in Lampung Province than Komering does in South Sumatra Province; since there are 1) province-wide mandatory school subjects on the two varieties, which are (AFAIK) considered equally "standard", 2) an undergraduate minor and a graduate study program on Lampung language in the local state university, and 3) an active contemporary literary scene with regular publication (cf. the "Lampung literature" article on id.wp). Jawadywn (talk) 19:21, 30 December 2024 (UTC)[reply]
Thanks for the details. We'll add it soon. Amir E. Aharoni (talk) 02:47, 1 January 2025 (UTC)[reply]

Error message in my mailer

In my mailer (I mean on my page "Special:NewMessages"), I have an error message:

[011d1dc076e5088bd957a916] 2024-12-25 14:12:30: Erreur fatale de type « Wikimedia\Rdbms\DBQueryError »

What does it mean? Mahabarata (talk) 14:19, 25 December 2024 (UTC)[reply]

It's temporarily broken. It will be fixed in early January latest. Nike (talk) 14:22, 25 December 2024 (UTC)[reply]
https://phabricator.wikimedia.org/T382472 Nike (talk) 14:22, 25 December 2024 (UTC)[reply]
Ok, thanks. Mahabarata (talk) 14:26, 25 December 2024 (UTC)[reply]

OpenHistoricalMap and Fuzzybot

FuzzyBot just imported new texts for old messages with many errors, one example here:

« Projects:Ohm-api.notes.rss.title/fr » : historique des versions — translatewiki.net (see the 2 newer versions: openhistoricalmap becomes openstreetmap).

This message is not marked on translatewiki as untranslated or outdated so this bad import is invisible on translatewiki.

Apparently it is not the first time FuzzyBot creates this mess (see first and second version in the link).

I have no time to read all 2901 messages of this projet to fix them so I suggest reverting these latest auto changes and doing something to prevent another big mess of Fuzzybot. Mahabarata (talk) 21:42, 26 December 2024 (UTC)[reply]

It's not FuzzyBot's fault. Upstream has done these changes: https://github.com/OpenHistoricalMap/ohm-website/pull/261#issuecomment-2562714833. Nike (talk) 08:16, 27 December 2024 (UTC)[reply]
Ok, thanks for this explanation and sorry for my wrong accusations. Mahabarata (talk) 13:23, 27 December 2024 (UTC)[reply]
@Mahabarata, I second you. It takes two steps to prevent readers given uncorrect translations.
Before translation, we need a step to verify if the updates at external sites is reasonable to users including Wikimedians.
My worry is why translators are the first and the last to wipe clean "the bottom" of FuzzyBot and the mess? Is there anybody else who will receive pings and notes what is going on? My inbox has messages like below, and both are imported not matching sentences from what you call the source, but by our Bot:
> There are new phrases awaiting review at TranslateWiki:
> == !recent (ja; untranslated messages) ==
> * 1288:Ohm-site.copyright.legal_babble.more_1_1_html
> * 1288:Ohm-site.welcome.rules.para_1_html
-- Omotecho (talk) 22:11, 30 December 2024 (UTC)[reply]

Database error due to 300+ messages on this page

After clicking on New messages, which shows the content of this page as I'm watching it, the following database error occurred. 

[7d7cbc0c40dc390d9c5ca38a] 2024-12-28 09:35:32: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"

I'm hoping this isn't something that happens to everyone clicking here and watching this page (usually with <20 messages) Cigaryno (talk) 09:40, 28 December 2024 (UTC)[reply]

@Cigaryno: Special:NewMessages is part of the LiquidThreads extension, which we used to use as the main discussion platform here, but we have now moved back to using normal wiki talk pages (enhanced by the DiscussionTools extension). Most of the pages that used to use LiquidThreads have been archived, except mainly some user talk pages. You can safely ignore that link – if you want to follow any specific talk pages, just used the watch feature, and if you want to follow specific discussion, use the subscribe feature next to the header for that topic. Jon Harald Søby (talk) 15:26, 28 December 2024 (UTC)[reply]
It happens for everyone visiting Special:NewMessages (see above), but, as Jon says, very few people will want to open it in the first place. —Tacsipacsi (talk) 15:05, 29 December 2024 (UTC)[reply]
Okay, thanks for this. Afterall, Echo is what can notify about this page if watched. Cigaryno (talk) 16:03, 30 December 2024 (UTC)[reply]

FuzzyBot mulfunction and mass imports jambles (OHM)

Who stops or roll backs those imported contamination by FuzzyBot? What is wrong with its codes? There are mass destruction by it, at least for OpenHistoricalMap: a sample below. Newly imported sets reads: "(Importing a new version from external source)". Actually the FuzzyBot has been contaminating and inserting jambles.

  • check from or earlier than timestamp 14:45, 26 December 2024.

Here is a sample:

Happy holidays, Omotecho (talk) 19:09, 28 December 2024 (UTC)[reply]

Nothing is wrong with the code of FuzzyBot, simply someone changed/created a lot of translations in the OHM source code. See above. —Tacsipacsi (talk) 15:07, 29 December 2024 (UTC)[reply]
Forget that someone... The rightiousness of our code does not proof we are safe from problems troubling us, as far as it is our FuzzyBot. Wonder if you are suggesting we would need somebody to judge the imported contents are correct/reasonable, or not? -- Omotecho (talk) 22:17, 30 December 2024 (UTC)[reply]
As explained in the the thread above, the changes were too massive to review. The other option would be holding back all translation updates, or disabling OHM translations temporarily. Nike (talk) 09:42, 31 December 2024 (UTC)[reply]

[mui] Language name and mainpage

Currently the native name is written as "Baso Palembang", although most sources on this language use "e" instead of "a" in the first syllable to represent the schwa [ə] sound, cf.:

  • Zulkifly, H. U. A. (2007). Kamus sederhana bahasa Palembang / Komus ringkes baso Pelembang [A simple dictionary of Palembang language]. Tangerang: DPC Kerukunan Keluarga Palembang.
  • Amin, Baderel Munir et al. (2010). Tata bahasa dan kamus baso Pelémbang [Grammar and dictionary of the Palembang language]. Palembang: Yayasan Madrasah Najahiyah.
  • Tadjuddin, Zuhdiyah Malik et al. (2024). Buku baso Pelêmbang: Sekolah Dasar (SD) / Madrasah Ibtidaiyah (MI) kelas 4 [Palembang language textbook: Primary School / Islamic Primary School, 4th grade]. Depok: Multisarana Nusa Persada.
  • Panji et al. (2024). Komus lengkep baso Pelembang [A comprehensive dictionary of Palembang language]. Palembang: Anugrah Jaya.

The second "e" vowel is an [ɛ] and is variously represented as "é", "ê" or "e" (in which case it would be the same glyph as the schwa). Following the regional Language Agency recommendation (Trisman et al. 2007, Pedoman ejaan bahasa Palembang), I prefer using "é" to represent this sound (thus "Pelémbang"), since "ê" or "e" are more commonly used to represent schwa in Indonesian linguistic tradition. The baso 'language' qualifier can be excluded as it is pretty clear that it refers to the language variety in this context.

Also, for the MediaWiki translation of "Mainpage/mui", formerly a literal, almost 1:1 translation Laman Luan is used, but this is a term that is virtually unknown to most speakers. I tried changing it to the more idiomatic translation Muaro Lawang ('front door') but apparently I need extended permission to do that... Jawadywn (talk) 20:07, 30 December 2024 (UTC)[reply]

Thanks for the detailed explanation and sources. We'll change the name soon—it may take a few days because of the holiday season.
I've updated the "main page" messages.
Happy new year! :) Amir E. Aharoni (talk) 02:46, 1 January 2025 (UTC)[reply]
Thank you and happy new year, too! Jawadywn (talk) 06:47, 1 January 2025 (UTC)[reply]
Actually, I have a couple of questions.
I found "Pedoman ejaan bahasa Palembang mention" online, and I see that it mentions the letter é, but doesn't use it when actually writing the name "Pelembang", for example, on pages 33 and 42. So maybe it's not necessary at all?
Or if a 2024 school book (Tadjuddin, Zuhdiyah Malik et al.) says "Pelêmbang", then maybe that is better? My inclination is usually to go with what school books suggest, but I understand that it's not always the best thing. Amir E. Aharoni (talk) 00:45, 5 January 2025 (UTC)[reply]
@Amire80: Alright, here's the thing. The Pedoman says that the usage of the accent mark is optional to distinguish between pepet [ə] and taling [e]/[ɛ] (they consider the latter two sounds as the same), cf. in page 3 where they use it in éjo [ɛd͡ʒɔ] 'to struggle', séwét [sɛwɛt] '(a piece of) cloth' and sengé [səŋe] (not [səŋɛ]) 'grin (n.), to grin (v.)'.
As for the schoolbooks, they actually distinguish three sounds spelled with "e" in the Pedoman, which are:
  • "e" for [ə],
  • "ê" for [ɛ], and
  • "î" for [e].
So the examples above would be written as êjo, sêwêt, and sengî. Similarly, they also distinguish between "û" [o] and "o" [ɔ], e.g. in jerû [d͡ʒəro] 'inside' and jero [d͡ʒərɔ] 'deterred', both of which would've been written jero if we follow the Pedoman.
If we consider popular usage, most speakers barely use any diacritics at all, but if they do, they will usually only use "é". Google Search isn't a representative corpus but a quick browse there for the terms "Pelémbang" with an accent "é" has around 5.380 results, while "Pelêmbang" with a circumflex "ê" has only 7 results, all referencing the newly published schoolbooks.
FWIW, last November, me (as User:Swarabakti) and the local community of Wikimedians in Palembang actually managed to collaborate with Prof. Zuhdiyah (Malik Tadjuddin is a patronym) and the other authors of Palembang-language schoolbooks and dictionaries in a workshop for Wiktionary and Lingua Libre.
During the event, we actually brainstormed several alternatives for the orthography to be used in Wikimedia projects, ranging from not using diacritics at all (as is still common among the speakers), using only one glyph with diacritic to separate the taling sounds [e~ɛ] (which would be "é", following the option given by the Pedoman and the default diacritic people use when in need), or using three glyphs with uniform circumflex diacritics ("ê", "î", "û") as in the schoolbooks.
Eventually we settled with a pragmatic compromise of using the same orthography as the schoolbooks, but with "é" instead of "ê" for [ɛ] (see for example the Indonesian Wiktionary entry for ajén 'to respect'). This is not without precedent, as a similar system ("é", "î", "û") is used in Amin et al. (2010), of which Prof. Zuhdiyah herself is actually a co-author.
So yeah. I think what I did not convey previously is that the language is still in the process of standardizing the written form, and there is no single agreed orthography as of now. While the Zuhdiyah et al. (2024) schoolbooks' version has the most potential to be the standard, it is not (yet) adopted officially; currently the local govt only mandate "Palembang language" as a subject without requiring a specific standard, syllabus, or materials to be taught... Jawadywn (talk) 16:26, 8 January 2025 (UTC)[reply]
OK, I guess it's convincing enough :)
We'll do it soon. Amir E. Aharoni (talk) 19:17, 8 January 2025 (UTC)[reply]

Ottoman Turkish language

I really want Ottoman Turkish to come back because I saw it enabled on Wikidata but not on TranslateWiki. BlueHatMario (talk) 02:41, 1 January 2025 (UTC)[reply]

Being enabled on Wikidata doesn’t mean that it was ever enabled on Translatewiki, nor that it should be. This is especially true for old languages: Wikidata accepts extinct languages, as data like inscriptions may be written in them, but (as far as I remember, I don’t find the policy at the moment) Translatewiki supports (with a few exceptions) only living languages, since that’s what helps making software accessible for people – probably all or almost all people who would use the software in Ottoman Turkish can also use it in Modern Turkish as well. As far as I understand w:Ottoman Turkish#Legacy, while it’s taught in schools, this teaching is more like Latin and Ancient Greek in European schools, not like a living foreign (or native) language. —Tacsipacsi (talk) 10:39, 2 January 2025 (UTC)[reply]
If Ottoman Turkish does get enabled on TranslateWiki, then the fallback language should be Turkish. BlueHatMario (talk) 14:00, 2 January 2025 (UTC)[reply]
Ottoman Turkish will not get enabled on translatewiki for localization. The policy is on Translatewiki.net languages: it must be a living language and a general purpose language. It's enabled on Wikidata, but not for user interface, but for collecting historical data like names and words. Amir E. Aharoni (talk) 15:30, 2 January 2025 (UTC)[reply]

Balkan Gagauz Turkish

I really want Balkan Gagauz Turkish to be used because it's not enabled or used on TranslateWiki. BlueHatMario (talk) 15:52, 2 January 2025 (UTC)[reply]

Can you write this language? Amir E. Aharoni (talk) 16:05, 2 January 2025 (UTC)[reply]
adımda ailêm arkadaşım artırmak âmcası attıktan ağlıyordu ağacın altında alırdım âdâm attıktan atmosfêreydi sıkıntısı arkadaşlarında gêçirmeyi yüreyîme sêvdiim dêiştirmek âldıımdâ dêprêsiona yüreyime yoktu ormanın kênârında yürüyordum eğlencelî sêçti yolcularla erkeğê arkadaşım dêprêsiona dêprêm etmeye değerlerini dêprêsiona düşünyorum öğrencîler yêtiştirdîi yürütêç erkeklêrin ôlduğu profesyonêl yolculûklarını yoluylâ reâktörü temîz têşekkürlêr yêtiştirdîi yêtiştirmê tarafından tariflêrini sâdecê tükênmez teşviktê ölüm gürültülü giyilên temîzlenir temîz têşekkürlêr tercîh sâdece çıllık saldırgân sektörleylê dêiştirdim terörlerî rastgelê rengî güreşî yumuşak güçlüydü görüyorum onnarı uykuya dêprêm kullanılır kızgın kürtlêr kârarları katılmıyorum katlardan kahvaltısı küçük köyümuzdê kultürümdê kahvaltı küresel ôlduğun korkutcu BlueHatMario (talk) 18:24, 2 January 2025 (UTC)[reply]
This language is very similar to Azerbaijani/Turkish and I can say that I didn't understand anything from this text. It looks like it is random words. Nemoralis (talk) 00:58, 5 January 2025 (UTC)[reply]
It's not. I got them from a memo. BlueHatMario (talk) 02:25, 5 January 2025 (UTC)[reply]

Text replacement request

Can someone please replace all the instances of msg-mw to msg-wikimedia in message documentations related to Translating:Wikipedia Year in Review? See, for example, Wikimedia:Wp-year-in-review-badge-template-wizard-desc/qqq. A bunch of them are currently in Category:Message maintenance/msg-mw because of this typo, and I don’t want to do it by hand because it’s a lot of messages. But I also don't have access to ReplaceText myself. stjn[ru] 15:52, 3 January 2025 (UTC)[reply]

@Stjn: Done Done Jon Harald Søby (talk) 17:37, 3 January 2025 (UTC)[reply]
@Jon Harald Søby: a number of these also seem to have names like Wikimedia:Badge-100k-desc/qqq and Wikimedia:Talk-2/qqq, are they not part of the group or are those names with no prefix erroneous? stjn[ru] 18:06, 3 January 2025 (UTC)[reply]
Ah. It seems to be another case of ‘non-translatable messages being left dormant after they stop being translatable’. Maybe we should do something about it already (a check for some could be added to {{Msg-meta}} directly if I knew what to check for, since /en subpage also exists in these cases). stjn[ru] 18:42, 3 January 2025 (UTC)[reply]

On every message there is link to "Ask for more information". It suggest you can use it to ask for explanation. But in MediaWiki messages it leads to phabricator where we can report bugs with them to have, for example, rewording original text or add better documentation, but it is not support centre for questions.

The title should be reworder or target page changed to this or purpose of the place should be clarified, especially it is about questions or reporting bugs.

Example problem: phab:T382748 Woytecr (talk) 15:22, 5 January 2025 (UTC)[reply]

User:Hadĵnix contribs

Please delete his contributions his knowledge of Serbian language is not good. He has a problem with grammar and properly forming sentences. Milićević (talk) 11:03, 6 January 2025 (UTC)[reply]

OK, this can be done easily using the Nuke function. However, I wanted to check something first: There are relatively few of them, and it was long ago. Are they all completely bad? If they are not all bad, perhaps the bad ones could be simply fixed? They are all in the IABot project.
If it's all awful, I can delete. Amir E. Aharoni (talk) 18:00, 6 January 2025 (UTC)[reply]
Please delete, i already fixed a lot of his translations on MetaWiki and MediaWiki.org and have no desire to clean up after him anymore Milićević (talk) 18:47, 6 January 2025 (UTC)[reply]
OK, I deleted and removed translation rights. Amir E. Aharoni (talk) 20:56, 6 January 2025 (UTC)[reply]

Update MediaWiki Credits

Can we please update Translating:MediaWiki/Credits? It is updated ~5 years ago. Nemoralis (talk) 00:01, 7 January 2025 (UTC)[reply]

Hopefully @Nemo bis can do it. In this edit, he left "instructions" on how to do it, but I think you'd have to download all (?) supported extensions for that to work, and I'm not sure I want to do that, hehe. Jon Harald Søby (talk) 10:25, 7 January 2025 (UTC)[reply]
We have all the extensions cloned on the translatewiki servver. Nike (talk) 10:32, 7 January 2025 (UTC)[reply]

Bug: no documentation and English text

Something happened, and now, when I edit the page in the wiki editor, neither the original text in English nor documentation is displayed! maro21 (talk) 22:50, 7 January 2025 (UTC)[reply]

@Maro21: Hi! I'm afraid you have to be a bit more specific. Which page? Jon Harald Søby (talk) 08:46, 8 January 2025 (UTC)[reply]
Any page with a translation string. For example [1]. There is "Information about message (contribute)" and "Message definition (Url Shortener - User interface)" below. But it works now, thanks for fixing :). maro21 (talk) 17:50, 8 January 2025 (UTC)[reply]
Retrieved from "https://translatewiki.net/w/i.php?title=Support&oldid=12879414"
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy