Support

From translatewiki.net
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
NoteProblems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? Feel free to post a reply to bump the thread to the top. The thread summarization feature is broken, see Phab:T245109. Very old threads have been archived.


Contents

Thread titleRepliesLast modified
[rmc] Activate new language: Carpathian Romani - ''romaňi čhib''407:06, 3 December 2020
Error on Wikimedia:Citationhunt-instructions details/zh-hans221:40, 30 November 2020
Publishing the translation failed412:48, 30 November 2020
Add Covid Ratio612:11, 30 November 2020
Obsuser and his translations309:15, 30 November 2020
attribution options?109:04, 30 November 2020
Courtesy vanish me208:57, 30 November 2020
Add new page MediaWiki:Source-code108:52, 30 November 2020
Translatewiki.net does not have a mobile view (MobileFrontend and MinervaNeue)315:44, 29 November 2020
[Wp/trv]Translation of MediaWiki (most important messages)421:08, 22 November 2020
Support Saraiki language621:06, 22 November 2020
[kcg] New Language Addition (Tyap / Katab, A̠lyem Tyap)009:06, 20 November 2020
Language name correction (Southern Luri/luz)116:35, 18 November 2020
Grammar215:33, 18 November 2020
Minor web site enhancements412:22, 13 November 2020
MediaWiki:Notification-bs-pageassignments-user-group-add-summary215:41, 12 November 2020
Translations by ChoiChong009:15, 9 November 2020
Delete MediaWiki:Dberr-info/hif-latn208:18, 9 November 2020
RC Wikidata207:44, 28 October 2020
Error on MediaWiki:Wmobile-copyright/en323:24, 26 October 2020
First page
First page
Previous page
Previous page
Last page
Last page

[rmc] Activate new language: Carpathian Romani - ''romaňi čhib''

Hi, I have the projekt to iniciate Carpathian romani wikipedia in the Incubator. Because this language still have no wikimedia projekt, I would like to start the translation on translatewiki for wikimedia's projekts. Language in writen in latin characters so LTR. Thanks

Adehertogh (talk)13:57, 26 November 2020

Hi!

I can probably add it.

Are there any other websites in this language?

Is it distinct from the language at https://rmy.wikipedia.org ?

Amir E. Aharoni (talk)12:31, 30 November 2020
  • Vlax Romani [rmy] is another Romani language, spoken more to the South (mainly in the Balkans and some Southern parts of Hungary and Southwest Romania or Moldavia, or Macedonia and Northern Greece). It is the most spoken Romani language. It is usually written in the Latin script (rarely with the Cyrillic script except in Macedonia, or the Greek script except in Northern Greece).
  • It is distinguished from Central Romani or Carpathian Romani [rmc], spoken more to the North (mainly in the Northern parts of Hungary, and in Slovakia, Poland and most parts of Bulgaria and Romania and Western Ukraine; its southernmost area is in Serbia). It is most frequently written with the Latin script, but may be written with the Cyrillic script in Servia, Bulgaria and Ukraine.

It is not clear which Romani language is used in Wikipedia, it is very likely that it is effectively the Vlax variant as it is the most developed one with a written tradition.

Central Romani however has suffered from the split of scripts used in its area. Today, both languages are in contact and probably mixed/confused in Hungary where this Indo-European language is very distant from the dominant Finno-Uralic language Hungarian (but with some better proximity with Slavic languages: Slovenian, Serbian, Bulgarian, Ukrainian, Polish). Some contacts are also in Romania.

Central Romani (like all Romani languages) has made lots of borrowings (lexically and grammatically) from the domaininat languages they were in contact with, but with many more differences for Central Romani because there's big differences between domainant languages in its area; Central Romani has also been a lot influenced by Turkish (during the Ottoman Empire), but less than Vlax Romani.

However the main distinction between the two languages is their date of migrations: Central Romani is more ancient and borrowed more words from Persian, and some older borrowings from Armenian and Georgian, then later from Turkish, whereas Vlax Romani has been influenced by Turkish for a more longer time.

The two Romani languages have clear phonetic differences from their very different times of migrations (and with contacts with different old empires). Today however they are now a lot influenced by the dominant language. And in Hungary it is sufficiently dictinct to have kept its original distinction than everywhere else in the Latin-Romanic, Germanic, and Slavic areas.

Both languages were not written at all for centuries, and most efforts for writing them and develop an orthography first occured in the former Yugoslavia and in Bulgaria and Ukraine (during the USSR regime) only in the XXth century (after WW1 and the collapse of the former Ottoman Empire), so they were written in the Cyrillic script (for a short time). Today most efforts are using the Latin script (but there's still not been any attempt to develop a common orthography, orthographies being mostly driven by conventions used for the dominant languages): Hungarian and Polish use very different systems for the Latin script, so do the orthographies of Central Romani.

For Vlax Romani it is simpler. because there's some good degree of agreement between Croatian, Slovenian, Latin-Serbian, Slovakian, along with German and Italian during the former Austro-Hungarian empire (Macedonian and Albanian or Turkish did not contribute a lot and there was a strong resistance with the former Turkish empire; Romani people have migrated a lot to escape the ruling of former empires when they were too much brutal against minorities, and as their languages were no written, the tradition were kept orally and Romanis have always been very protectful for their oral culture and keeping united; this is still true today in every country where they live now, in well-defined communities but without clear borders).

So Central Romani / Carpathian Romani (rmc] still has no real support in Wikipedia like Vlax Romani. Its development as a written language is very recent, since the democratisation of Eastern Europe and notably in Romania at end of the 1990's. Vlax Romani was less threatened since longer time in Italy, Switzerland, France and Spain, along the Mediterranean Sea coasts where Vlax Romani people were constantly relocating (and in Germany and Austria only after WW2, some now being travelling as well into Egypt and even in America).

Getting access to litteracy has been long for all Romanis, and it is still difficult for them to get good education in schools not well prepared to receive people constant travelling across countries. However the internet and mobile networks are changing things radically for them: they can now communicate more easily and get some support internationally to preserve their culture in the written form.

Given all this, [rmc] merits its own development, distinctly from Vlax Romani [rmy]. However [rmc] may need to be supported in two scripts: Latin and Cyrillic (for use in Bulgaria, and possibly Ukraine). For religious use however the Latin script is favored (most Romanis are fervent Roman Catholic today, rather than Orthodox Christians, and the Bible has been the best written reference for them, beside oral celebrations).

Verdy p (talk)03:59, 1 December 2020

I don't have such linguistic knowledge as Verdy p, but working and communicating with Romanis from Slovakia, I can tell that they do not understand vlax romani. An other important point is the recent strong influence of the majority language in the romani language which of course differs from every country. In Slovakia and Czechia, romani use a Czechoslovak standardized writing which is different from the international one, unknown by romani except by few specialist. Spoken with several people, we choose to use the Czechoslovak standard to Start the wikipedia project to be understood by the largest northern central romani people and get the latest audience as possible. As reference there is the today's most complete Slovak-Romani dictionary (isbn 978-80-970999-0-9). But in the future, I would be good to support the two Latin scripts Czechoslovak and international.

Adehertogh (talk)21:50, 2 December 2020

Note that independantly of the ISO 639 classifgication of Romani languages, they are **independant** ofd their written forms which vary greatly: Traditionally these languages have been used orally, witgh strong enough differences in their oral forms to be encoded separately. Its classification however complicates a lot if you take the written forms, because they have *no* standard. As well the oral languages are constantly adapted locally with the dominant language with which they coexist, so much that there are many things borrowed unformally: these broowing may be lexical (and often persist in their tradition) but also grammatical (these are much less persistant, and the same people may change these depending on where they are or travel: so beside the "pure" language spoken by the community themselsves in their own families, when they travel and communicate with others, they constantly adpt their language to other speakers, including with the various gipsy or travellers communities). It should be noted that Romanis people are very frequently multilingual, because they travel a lot across countries (that's why it is often hard for them to adopt a nationality in Europe, and why they are also often discriminated, for not adopting any national standard; still there are some Romani communities that have been settled and have stopped migrating: these settled non-migrant communities are most common in South-Eastern Europe (notably in Romania and Bulgaria, but as well in some other places much further, such as Egypt and US, where they have more or less adopted some national standards, and then started to develop a strong local dialect very influenced by the local language such as English and Arabic).

In the United Kingdom, the Romani travelers have largely settled and their inherited familial language has then adopted the local English language so much that their language initially forming a very distinct dialect has become a minority language then threatened: Welsh Romani for example is now considered almost extinct: it iinitially adopted a local form based on the regional Welsh language, but as Welsh itself was threatened and remlaced by English, the Welsh Romani has disappeared, and there remains just English with some Romani terminology more or less adapted. Angloromani also has almost disappeared as well. Now Ropmani travelers may come to Britain, but most of them are Vlax Romani or Central Romani people which may cross the English Channel only for a few months, or for temporary familial or festive or religious events (they will often come from France, Belgium or Germany).

Anyway this topic is about [rmc] (Central/Carpathian Romani): yes it is very distinct from Vlax Romani [rmy]. But it's almost impossible to assert which language it is precisely in the writtern form. As well most Romani peopl use the Latin script, but this= is not universal: the Cyrillic and Greek scripts are used as well (there was an attempt done in Russia, Belarussia and Ukraine) to develop a standard based on Cyrillic, and sometimes iot may be used for a few Romani languages: this Cyrrilic form may have been used during the USSR, where Romani people were isolated from Western Europe, but now they are in contact again with other Romani people in Romania and Turkey, and now throughout the European Union where they can travel freely: the Cyrillic script is now almost no longer used except in Western Russia where there is a significant Romani community settled since long.

(I don't know if Romani people settled in Egypt use now the Arabic script; but it is very likely to occur if they have converted from Christianism to Islam).

Verdy p (talk)07:06, 3 December 2020
 
 
 
 

Error on Wikimedia:Citationhunt-instructions details/zh-hans

Hi, I'd like to request a review of Wikimedia:Citationhunt-instructions details/zh-hans please.

The original text is "Click %s to go to Wikipedia and {link_start}fix the snippet{link_end}, or %s to see another one. Good luck!", with two "%s" placeholders. The current translation only contains one "%s", which is not expected in the code. I can't read the translation but I wonder if the "or %s to see another one" part of the original message is missing?

Please let me know if there's another preferred way to report translation issues, I wasn't too sure. Thanks!

Surlycyborg (talk)18:35, 26 October 2020

I have marked the message as outdated. Currently missing parameters are only a warning, should we make this an error?

Nike (talk)09:13, 30 November 2020

Thank you! Yes, I think it would make sense to make it an error please. I suppose that means those strings will never be exported to the repository, right?

There's just a couple of things to watch out for, because this string handling code in Citation Hunt is not great:

  • As you can see from the example above, there are two kinds of syntax for parameters in some strings ({this} and %s).
  • Due to out of date translations, some strings now have _too many_, rather than too few parameters (e.g. https://translatewiki.net/wiki/Wikimedia:Citationhunt-instructions_details/pl has three %s, which we handle in the code, but it really should be two at this point).

But if those are OK on TranslateWiki, it's all good on my end.

Surlycyborg (talk)21:40, 30 November 2020
 
 

Publishing the translation failed

Hello. Nias community needs to translate all the most used messages on the interface to make Wikipedia and Wiktionary approved. There is only one untranslated message there, but we can't translate it. When I try to publish the translation, it always says, "Publishing the translation failed: You do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors." Can somebody tell me how to make it published? Thank you. Rano (talk) 04:07, 29 November 2020 (UTC)

Rano (talk)04:07, 29 November 2020

Hi Rano, please post the message name and the translation here. An administrator will publish it then.

Raymond15:52, 29 November 2020

MediaWiki:Copyright/nia to Nias language The translation is "Te'asogö nösi tou $1, hatö na fabö'ö niwa'ö."

Rano (talk)11:21, 30 November 2020
Raymond12:28, 30 November 2020

Thank you.

Rano (talk)12:48, 30 November 2020
 
 
 
 

Add Covid Ratio

Could you please add Covid Ratio (source) to translatewiki? Thanks!

David (talk)22:11, 22 November 2020
Edited by 2 users.
Last edit: 07:47, 23 November 2020

Do you manage this site ? Anyway it is focusing only US with few statistics per county. I don't think it's worth the value compared to international sites (including Wikipedia that follows lot of statistics).

And there's not a lot to translate: the country names ? They are in Wikidata. The rest is jsut a few messages. If the site author wants to make it a long term project for statistics independantly of country and division levels, may be, but the UI is too much in alpha stage and limited in scope. May be that site would want a few translations for other languages of US.

Such site is only useful if it tracks accurate data sources with regular updates and sources, but for now there's not even any indication of sources, so I would better trust official sites: WHO... or even Google (which in fact just uses and participates to the statistics project on Wikipedia/Wikidata for this topic, as this is a good place to collect and keep lot of sources and organize them...). and there are now tons of other websites for local statistics in each country, and for various platforms (web or mobile).

Verdy p (talk)23:44, 22 November 2020

Yes I maintain the site. I'm totally open to adding more states/locales, but I do not have the time to go through each state's data source. As I mentioned in the footer the data comes directly from the Florida Department of Health, there isn't a more official source for county-level data than that. If any other developers would like to add other locals, please submit a PR on the GitHub repo. If you know of an API that gives out county-level data for the entire country, I would love to use that instead. :)

David (talk)00:32, 23 November 2020

Oh... I did not even see this was even more limited to Florida only! Really, you should first ask for help on English Wikipeia at least to see if you get support for extending it to other US states, and possibly other countries. But I bet most won't be interested as Wikipedia already has a more complete dataset (and accurately checked, with all sources compared, not just one which uses one state-level method, and not the exclusive one at federal or international level). You should know that such statistics is highly sensitive to the methodology used, and there are many criterias (the WHO site gives some hints about their varaibility and what they are about, there's no single way to count things, including in one given country, and governmental sources are not always accurate on everything, frequently with underestimates!)

Such project is in fact not maintainable by a single person from his chair at home, it absolutely requires huge cooperation, at nation and international scale and requires monitoring as well other indicators. Even Google renounced to do that itself ! The best you can do however is to help the Wikipedia project if they are missing some data sources, in order to collect and track more (you MUST absolutely give the sources, as many sources use different methods or may be out of sync with others, using different time-frames for their measurements, and also frequently correcting their figures later).

Then you can use the data collected in Wikipedia and Wikidata to make a translatable app if you wish (exactly what Google did itself!).

Verdy p (talk)14:23, 23 November 2020

English Wikipedia, nor Wikidata, maintain county-level data which is necessary to preform the calculation.

I'm not sure why I have to defend an applicaiton I wrote. If you don't want to translate the 7 strings, then just say so.

David (talk)14:44, 23 November 2020
 

Even if I were to expand the data set (which I have yet to find a suitable one), the UI would still need those strings translated.

David (talk)14:51, 23 November 2020
 
 
 

Hi David,

Thanks for showing interest in adding your project to Translatewiki. I've created an issue on our issue board and gathered all the information we currently have - https://phabricator.wikimedia.org/T268987

For now, these are the things we need from you, 1. Description of the project 2. A logo, if possible

In addition, please see the concerns I've listed on the ticket.

Regards,

Abijeet Patro (talk)12:11, 30 November 2020
 

Obsuser and his translations

Can someone block User:Obsuser? He's edit warring, behaves stubbornly, does not respect the agreements made between Serbian translators regarding translations, and translates too literally. For example, the changes he has made in this edit only make it difficult to understand the text. He translated "Intended blockee" as "Намењено да се блокира" (Intended to block) -- which is very unclear in general, let alone in the Serbian standard language. The previous translation was "Блокирани корисник" (Blocked user) -- which was a very natural option. Due to the same pattern of behavior, he was blocked on Serbian Wikipedia permanently more than a year ago. User:Kizule can confirm this since his mother tongue is also Serbian. Thanks in advance!

BadDog (talk)19:10, 20 October 2020

I can confirm all things which BadDog said. He (Obsuser) still doesn't understand what teamwork means.

Kizule (talk)20:05, 20 October 2020

Bump. He is like an "energy vampire" who works only on his own and consumes the energy of us who are trying to contribute.

He persistently wants to translate literally, on incomprehensible way.

And, my god, without consulting with someone else.

Kizule (talk)16:15, 25 October 2020

I only see one recent thread on their talk page. Was it about this topic?

Nike (talk)09:15, 30 November 2020
 
 
 

attribution options?

Jen here from https://eol.org/ . I would like to display some form of attribution to the translators who have contributed to our project, in our About pages. I thought perhaps a word cloud similar to what is available at https://translatewiki.net/wiki/Special:SupportedLanguages/id. Is this consistent with translatewiki policy? If so, is there a recommended data service we should use?

Thanks!

Jhammock (talk)19:24, 26 October 2020

Most projects thank "translatewiki.net translators". Some do collect all the names from their translation files and present that list as well.

Nike (talk)09:04, 30 November 2020
 

Courtesy vanish me

Please courtesy vanish me, i accidentally created this account and then started doing some random stuff.

-Ipkap21:59, 13 November 2020

Just don't use your account here. Deleting an account is not possible.

Raymond09:51, 21 November 2020

I think the best we can do is to rename the account to a random string and prevent logins.

Nike (talk)08:57, 30 November 2020
 
 

Add new page MediaWiki:Source-code

Some files on Wikimedia Commons have source codes published on their description page. It would be nice to have a {{int:source-code}} template to be used on headings as =={{int:source-code}}==; its use would allow translated texts such as "código fonte" in Brazilian Portuguese.

Joaopaulo1511 (talk)06:38, 26 November 2020

That should be translatable in Commons directly. They have a special message group for that kind of messages. Maybe you can request it to be included there, if it isn't yet?

Nike (talk)08:52, 30 November 2020
 

Translatewiki.net does not have a mobile view (MobileFrontend and MinervaNeue)

Hello, I saw that translatewiki.net does not have a mobile view composed of the extension MobileFrontend and the MinervaNeue Skin. Please you can to add a mobile view to translatewiki.net? Thanks.

Rodney Araujo (talk)14:02, 20 November 2020

MobileFrontend is a rather expensive extension to maintain, so I don't think the translatewiki.net staff has enough resources to provide this option. However, work is ongoing to switch to the Timeless skin, which is more responsive and should address most concerns: Thread:Support/Proposal to change default skin to Timeless. I suggest that you enable the Timeless skin in your preferences and report any issues you find.

Nemo (talk)16:30, 26 November 2020

I suggest that MobileFrontend and Minervaneue must be enabled to translatewiki.net, is because is more responsive in mobile devices. And also I opened a task in Phabricator at https://phabricator.wikimedia.org/T268340.

Rodney Araujo (talk)15:31, 29 November 2020

And I disagree, for the reasons above.

Nemo (talk)15:44, 29 November 2020
 
 
 

[Wp/trv]Translation of MediaWiki (most important messages)

Edited by another user.
Last edit: 07:37, 20 November 2020

Hello, we want to translate the content (Wp/trv) of MediaWiki (most important messages).One of the sentences (Content is available under $1 unless otherwise noted.) is not allowed us to publish our translation. And the reason is you do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors.We would like to know how can we solve this problem?

Mecytan (talk)03:50, 20 November 2020

This is not strictly for Mediawiki as what you wanted is to translate the Wikipedia Incubator for Portal:Trv (Taroko, Seediq): the UI of the wiki effectively comes for Mediawiki (so the Incubator wiki itself does not allow modifying it locally), but this could have happened for other projects as well. You have two solutions:

  • contact a local wiki adminsitrator to make a change for you (it will be kept specifically on that wiki by adding another level of protection that will block reimports from Translatewiki.net, where it may be translated differently in a more generic version not specific to Wikimedia).
  • or find the relevant message on this Translatewiki: if you can't edit it here, then propose the translation to this Support, and an admin will submit it for you: please link the message

I've try to locate it, and found 4 resources (here in English, two for MediaWiki itself (they must be generic):

and two for Wikimedia-specific contents:

Note that the reason given ("raw HTML") is not relevant as there's no raw HTML in fact. But that protection was required for legal reasons, because these messages are required on many pages (for legal reasons) and they must not be altered without careful check and approval by site admins.

So you have to give the translated text to put into

Verdy p (talk)07:43, 20 November 2020
 

@Mecytan: If you want to add the translations here in translatewiki please post your translations here. I will add them for you.

Raymond09:50, 21 November 2020

@Raymond: Thanks for your help. The translation is "Rahuq nan ii o niqan kingal duri pgkla, aji saw kiya do ruwan ruwahan patas dmuuy kana $1 gaya mgay biyax kklawa." Please help us to add the content.

Mecytan (talk)13:15, 21 November 2020

I have created MediaWiki:Copyright/trv for you. Please check the content. If you need further help please add the message name and the translation here.

Raymond17:47, 21 November 2020
 
 
 

Support Saraiki language

Edited by author.
Last edit: 10:04, 16 October 2017

Language Saraiki is mainly written in Arabic script. So Skr and Skr-arab be merged. In wikimedia and other sites Skr-arab be deleted. Because Saraiki is just one language. In interface language and internationalization only one langauge be shown. Interface of Urdu words be adjusted as they are adjusted in SKR_Arab. All translations be converted to Skr i.e., Skr-arab be renamed as skr. so that one language Skr-arab be deleted from Special:SupportedLanguages. In language selector of Wikimedia Saraiki is Written two times. Kindly Skr-arab be deleted.

Saraiki (talk)15:33, 27 July 2017

Merging messages between two variants can be easy for sysops by using Special:mergehistory, but I'd love to know what's your actual wanted code (aka merge which to which)? Merge skr to skr-arab? Or vice versa?

Liuxinyu970226 (talk)00:57, 1 August 2017
Edited by author.
Last edit: 12:34, 28 September 2017

In interface language merge Skr-Arab in Skr، In interface language the all work as stood as in Skr-Arab be adjusted as Skr, and the word Skr-Arab be deleted in the the internationalization of the the language. Wiki is only in Skr. Please this conflict be removed. Saraiki. (talk) 10:45, 1 August 2017 (UTC).

Saraiki (talk)10:45, 1 August 2017
 

Sorry, for technical it will be too complicated to do this. However, it doesn't matter because the "skr-arab" code will remain internal, and you'll see "skr" in the actual sites.

Amir E. Aharoni (talk)16:42, 12 November 2020

In summary we jsut want to make sure that [skr] is an alias for [skr-Arab] by default, just like [zh] is in alias for [cmn], or [en] is an alias for [en-Latn].

Like for all aliases, they are to be treated equivalently, except for the purpose of fallbacks with BCP47 rules, where the extra script code can be used as a guide to select one of several possible languages using the same script. This does not mean we create duplicate data for localization, but that where data is missing, fallbacks will resolve differently for languages that may have different scripts, even if one of them is the current standard or the most frequently used.

  • e.g., English is not written only with the Latin script, it may still be written with Deseret, so [en-Dsrt] is still a distinct variant, but if it's missing it will fallback to [en]
  • for Serbian, the Cyrillic script is the default so [sr] can be aliased to [sr-Cyrl] (or [sr-ec] only in Wikimedia wikis which violates the BCP47 standard here) and we don't need to have the two datasets for [sr] and [sr-Cyrl] (they should be identical), but we can still have [sr-Latn] which fallbacks to [sr] (and thus, also to [sr-Cyrl] because it is equivalent by its alias), however it can also fallback first to [sh-Latn] which will itself fallback to [hr-Latn]).

We can consider that for fallbacks, preserving the script is preferable to preserving the base language; so the two aliased codes are not completely equivalent: they are only equivalent in translation datasets, but not in applications that will use them with their own fallback chains to decide the order of resolutions.

If no fallback is needed (because a translated resource is found in any one of the two aliased datasets, which are in fact just the same one), using one code or the other does not matter. So in this TWN wiki, nothing needs to be changed except making sure that there's only one dataset open, the other being locked, or "redirected" to the other code.

So I would recommend keeping [skr-Arab] here, and keep [skr] closed/locked, with a possible redict. On the [skr] portal, we can display the shorter code, but as well all variants including [skr-Arab] as the default variant. The short code will be locked, all translations will be made in the unambiguous [skr-Arab], except if another script is used, like [skr-Cyrl].

Verdy p (talk)20:28, 12 November 2020

It should be noted that [skr] was just approved by the languages committee of the WMF, for creation of Wikipedia at least. For now all Wikimedia projects are still in Incubator.

Here on this wiki, it will remain [skr-Arab] (which is already enabled), even if there are 3 other scripts (including an historic Indic abugida, Multani, which was specifically used for that language; plus Devanagari and Gurmukhi, or Latin transliteration sometimes used today.) This won't block the import and creation of the new Wikimedia wikis (using mainly the Arabic script) as they work already in Incubator: the code [skr] can then remain disabled on Translatewiki.net (and because it was already disabled, there's no need to merge an inexixtant [skr] dataset with the existing [skr-Arab] dataset).

Verdy p (talk)21:02, 22 November 2020
 
 
 

[kcg] New Language Addition (Tyap / Katab, A̠lyem Tyap)

See the request made by Kambai Akau on Category talk:User languages.

Verdy p (talk)09:05, 20 November 2020

Language name correction (Southern Luri/luz)

Hi. The Southern Luri language(luz) name is misspelled and needs to be corrected. How can I change it from "لئری دوٙمینی" to "لری دۊمنی"?

Sahh (talk)19:15, 17 November 2020

It's the name built into MediaWiki for the "#language:" parserfunction, and its source is the name imported from Unicode CLDR, where it was vetted. It seems that the name is correct is I look at Wikipedia which cites it as well. The difference being in the optionaml notation of vowels, which may be simplified (your proposal) or more advanced. I do not see a typo, and the CLDR vetted data is considered reliable (a defacto worldwide standard for translation of language names, beside the ISO 639 standard and the IANA database for BCP47 that just give English names). If I look at Glottlog and the Linguist list, we see several orthographic variants for the native language name (they vary depending on authors, sources, or time, or location of the author using an orthographic system from several possible countries).

Verdy p (talk)16:35, 18 November 2020
 

Hi, I have noticed two small errors in the original while I was translating SWViewer:

https://translatewiki.net/wiki/Wikimedia:Swviewer-about-frame-data-ref-2/en

Should say "This data is available to the public."

https://translatewiki.net/w/i.php?title=Wikimedia:Swviewer-about-frame-data-desc/en

"Appication" instead of "Application"

Best,

Jan Myšák (talk)22:27, 10 November 2020

Shouldn't data be plural only (and collective, uncountable) in English so that it should be:

These data are available to the public.

To speak about a single data element or to count them, you need another noun: "piece(s) of data", "data element(s)", "data item(s)"

Verdy p (talk)20:08, 12 November 2020

These have been fixed.

Nike (talk)15:33, 18 November 2020
 
 

Minor web site enhancements

  1. The page Translating:New_project in its last paragraph has the expression "e-mail" (as a possible way to contact staff at translatewiki.net). A reader whom I sent to look around suggests to make it a link.
  2. If you follow the link "Translating talks for projects" at the beginning of the "Support" page, you get a list having more than a handful of irrelevant and outdated pages included. Can that be changed? --Purodha Blissenbach
09:16, 8 July 2011

Bump.

Nike12:31, 28 July 2011
Edited by another user.
Last edit: 12:22, 13 November 2020

So fix it, Niklas, instead of bumping this?

Siebrand10:49, 2 August 2011

I've forgotten what is our default email address.

Nike13:44, 3 August 2011

translatewiki at translatewiki.net.

Siebrand14:33, 3 August 2011
 
 
 
 

MediaWiki:Notification-bs-pageassignments-user-group-add-summary

The last revision to this message I see is “You have been added to group $4 that have pages assigned to them”.

This message needs a documentation update, a GENDER magic word for “You have been” (so the name of the current user account must be passed as a parameter) and possibly a PLURAL magic word for $4 if it still can be a comma-separated list of groups.

EDIT: I noticed similar errors in other messages: MediaWiki:Notification-bs-pageassignments-user-group-remove-body, Notification-bs-pageassignments-user-group-remove-subject, MediaWiki:Notification-bs-pageassignments-user-group-add-body, MediaWiki:Notification-bs-pageassignments-user-group-add-subject. All of these are marked as outdated in the translation tool.

The group manager's username (the person who is adding or removing the addressee from a group) is omitted and probably isn't necessary in any language, but the addressee (the currently logged user who's reading the notification) is mandatory.

Thank you, and I hope my explanation isn't confusing.

ArenaL5 (talk)20:33, 10 November 2020

Maintainer per email informed. Hopefully he will answer here.

Raymond08:50, 12 November 2020
 

Thanks for this feedback! I have created an internal ticket to address this. Will be fixed soon. Reference is ERM21752.

Osnard (talk)15:41, 12 November 2020
 

Translations by ChoiChong

A thread, Thread:Support/Translations by ChoiChong, was moved from here to User talk:ChoiChong. This move was made by Nemo bis (talk | contribs) on 9 November 2020 at 09:15.

Delete MediaWiki:Dberr-info/hif-latn

Please delete MediaWiki:Dberr-info/hif-latn, its just a copy of the English version of the message. Thanks, --DannyS712 (talk) 02:24, 24 October 2020 (UTC)

DannyS712 (talk)02:24, 24 October 2020

Not this alone :-( I looked through the file and see some hundred "translations" into English. Any chance for an automated comparison and deletion process?

Raymond15:21, 25 October 2020

So I really quickly hacked a script together:

var notTranslations = {};
Object.keys( maybeTranslations ).forEach(
    function ( key ) {
        if ( maybeTranslations[ key ] === englishVersions[ key ] ) {
            notTranslations[ key ] = maybeTranslations[ key ];
        }
    }
);

and then retrieved the list of messages in notTranslations. I got a list of 520 different messages that exactly matched the English version - I couldn't find a way to collapse the list if I were to paste it here, so I dumped it on my sandbox on metawiki - format is message name and then the text - see https://meta.wikimedia.org/w/index.php?title=User:DannyS712/sandbox&oldid=20632414

DannyS712 (talk)08:07, 9 November 2020
 
 

RC Wikidata

I'm searching for the MediaWiki-page that shows "Show/Hide Wikidata" in the Recent Changes. Anyone know which one that is? --Ooswesthoesbes (talk) 09:52, 20 July 2017 (UTC)

Ooswesthoesbes (talk)09:52, 20 July 2017
Edited by 0 users.
Last edit: 01:02, 27 July 2017
Liuxinyu970226 (talk)01:02, 27 July 2017
Edited by 0 users.
Last edit: 10:42, 31 July 2017

That might be it. Thank you!

Ooswesthoesbes (talk)10:42, 31 July 2017
 
 

Error on MediaWiki:Wmobile-copyright/en

Hi, can someone change MediaWiki:Wmobile-copyright/en to use quotation marks rather than apostrophes in the links as they're currently broken

Thanks

Nintendofan885T&Cs apply14:25, 26 October 2020

Single quotation marks are valid in the HTML syntax for attributes.

Remember that this resource is NOT written using the Mediawiki syntax, but the plain HTML syntax, so even if it does not render correctly on this wiki, this is only because this wiki attempts to parse it as Mediawiki (where even the <a href="URL">text</a> is not permitted by the wiki; so if it was written using the MediaWiki syntax and rendered by MediaWiki, it would be .[URL text] instead; this is not the case here).

So changing the ASCII single quote to ASCII double quotes would not change the way this message is rendered here on this wiki. Keep it in plain HTML: the message is intended to be rendered only locally by the Mobile app (which uses its own internal HTML renderer with its own embedded browser component, and does not parse the Mediawiki syntax, this text is emitted as is) and NOT on a MediaWiki server...

Nothing is broken here!

Note: you are still free to change these quotes in translations, as long as you use a valid HTML syntax (so don't change the ASCII < and > delimiting the HTML opening and closing tags. As well only use a plain URL (which you may need to change if it has to link to another translated page on the same target site, and keep the "https://" protocol unchanged).

And you are free to use the the quotation marks and apostrophes and all other punctuation appropriate in the target language for the text part of the link. You can test your translation by copy-pasting it in a plan-text file saved in ".html" format, and open it in your browser (unfortunately, the source message is not "meta-tagged" as using the HTML syntax; that's something that Translate wiki should propose to indicate its expected syntax, but that would also involve importing the source message with metadata in the package).

Such message, given it contains plan HTML, should also be modifible only by admins (to avoid injection of dangerous HTML code, such as link to spammed sites, or injection of bad javascript attempting to steal data or break the privacy in the Mobile app). This is something that authors of the Wmobile app should change: they can preprocess this message to generate the HTML code they will inject in their app (without the need to integrate a MediaWiki parser phase in the app itself), and only use Mediawki syntax on this wiki. But anyway this wiki is itself protected and renders the plain HTML link code, so this wiki remaing protected.

Verdy p (talk)18:01, 26 October 2020

Oh, I thought it was broken because the links broke when I clicked on them (it went to http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License')

Nintendofan885T&Cs apply20:38, 26 October 2020

This is a parsing bug of MediaWiki on this wiki; this won't occur with a regular HTML parser. As I said, plain HTML links are not supported by Mediawiki as Mediawiki incorrectly includes the "trailing" quote in it. That's something that MediaWiki should fix as these quotes in HTML are never taken into account, unless they are URL-encoded in HTML.

Note that in HTML both the single quote and the double quotes are valid delimiters for attributes, and which ones are valid as part of the quoted value depends on which delimiting paired quotes are used:

  • If attribute values are between double quotes "...", litteral single quotes ' in the embedded value don't need to be encoded, but double quotes in attribute values have to be HTML-escaped as &quot; (or only if the value is an URL, they can be URL-encoded as %22, which won't need any HTML-escapes)
  • If attribute values are between single quotes '...', litteral double quotes " in the embedded value don't need to be encoded, but single quotes in attribute values have to be HTML-escaped as &#39; (or only if the value is an URL, they can be URL-encoded as %27, which won't need any HTML-escapes)

Note that any single quote or double quotes by IS valid in any standalone URL (except for the leading protocol part or the host/domain part, it is valid anywhere in the optional parts: the path, the query string, fragment identifier) or any URI. Inside a standalone URI, there's no support at all for the HTML-encoding, or for the URL-encoding (which depends on the protocol and the target host/domain part in its own URL parser, but noit at all of the HTML-parser!!!).

Here MediaWiki (on this wiki) does not parse the HTML completely correctly and so it does not use the correct HTML-parsing for delimiting attributes, and then it considers the value as if it was between double quotes (no check is made about which effective delimtier is used in the HTML attribute, so it incorrectly accepts the single quote as part of it, then it takes the wrong decision).

This is effectively a bug of MediaWiki (which could be reported given that the MediaWiki should still parse HTML correctly and should be an extension of it), in its own custom parser. But as I said, this message is *not* to be parsed by MediaWiki and will be parsed by a regular HTML parser which makes the correct decision. The bug is bisible on this wiki when viewing the translated page, but it does not affect the application.

Verdy p (talk)23:17, 26 October 2020
 
 
 
First page
First page
Previous page
Previous page
Last page
Last page