View source for Thread:Support/Proposal to change default skin to Timeless/reply (8)

Jump to navigation Jump to search

Note Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries, see also documentation.

First page
First page
Last page
Last page

unable to edit

For some reason i'm unable to edit following pages.

It says "You do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors." How can i edit these pages?

Please past the new translations here. I will add the translation then to these messages.

Raymond13:30, 28 May 2020

Please replace & with ও

Done Done

Raymond19:09, 30 May 2020

Dear friend how can I change this page [1] and it's particles?
best regards

Mogoeilor (talk)12:15, 31 May 2020

Use Special:SearchTranslations to find the messages you need to change.

Nemo (talk)12:45, 31 May 2020

Changing Name

Hello; Please Changing my username to Sunfyre, thank you.

AzorAhai (talk)10:41, 29 May 2020

Done Done

Raymond11:31, 29 May 2020

Offline translator rights request

I would like to request offline translator rights to upload translations. I will send my first file by email right now.

L2212 (talk)18:39, 16 May 2020

We have received the offline file, and it will be processed before the next translation export on Thursday. We will also review your request for offline translator rights.

Thanks for your contribution.


Abijeet Patro (talk)14:02, 18 May 2020

Ok, thank you very much.

Best regards,

L2212 (talk)16:04, 18 May 2020

I've imported the file sent by you. You can see the changes here -

I've also given you offline translator rights. Please do remember to avoid large message groups and do not work offline for extended periods of time.

Thanks for your contribution.


Abijeet Patro (talk)13:52, 19 May 2020

Perfect, thank you very much again! Yes, I will make sure to remember it.

Best regards,

L2212 (talk)22:42, 19 May 2020

Date format

How to change date format in this message ($3 parameter)? I would like to change it from YYYY-MM-DD to DD.-MM.-YYYY.

MaGa (talk)16:14, 17 May 2020

Correction: target date format should be DD. MM. YYYY. (not DD.-MM.-YYYY).

MaGa (talk)15:50, 18 May 2020

Correct date format is {{#timel:j. n. Y.}} and not {{#timel:d. m. Y.}} see Pomoć:Vremenska funkcija (or via interwiki).

Bugoslav (razgovor) 23,59; 18. svibnja 2020. (SEV)21:59, 18 May 2020


MaGa (talk)15:20, 19 May 2020

We need to get this request as complete as possible, not just partially complete. Some of us at phab:T223988 requested the change of date format for Croatian, which revealed a hard-coded dot which produces formatting problems.

In the text Formatting and parsing dateTimes as strings, IBM Knowledge Center Home of IBM product documentation, last updated: 2020-04-03, accessed: 2020-05-19 — it is described what d. M. yyyy. and d. MMMM yyyy. mean. The two before mentioned forms are most appropriate in Croatian language translations. The form dd. MM. yyyy. is not a desirable solution.

Similarly, these are desirable solutions: %d. %m. %Y. or %d. %B %Y..

Even if there is some amount of mystery around what code the programmers would use, it is necessary to describe the problem in as many details as possible, in order for the better end result.

Bugoslav (razgovor) 23,29; 19. svibnja 2020. (SEV)21:29, 19 May 2020

Filtering recent additions by group

It would be great if we could filter recent additions by group. This feature would make it easier to track and translate new messages into the selected message group. For example, it would be easier for MediaWiki users to translate new MediaWiki messages, instead of messages from other projects and the like. What do you think about this?

BadDog (talk)17:30, 6 May 2020

Why would you prioritize translating new messages, if you are not close to 100% coverage?

Nike (talk)13:59, 10 May 2020

That is not the point. The point is: Why would I translate EOL messages if I'm not interested in that project. Instead, it is better to have filters that will hide these messages, so I could more easily translate *only* recent MediaWiki messages.

BadDog (talk)23:32, 12 May 2020

Why are you interested in recent messages?

Nike (talk)10:47, 13 May 2020
Hamilton Abreu (talk)02:57, 28 March 2020

Based on the message name I assume it's a noun: an edit summary that will be used as a log entry reason (but I'm not 100% sure)

Piramidion (talk)13:26, 28 March 2020

Confirming that "Edit summary" is a noun.


Abijeet Patro (talk)06:57, 30 March 2020

Extension:Translate question: how do I translate non-MediaWiki content?

I've installed Extension:Translate on my own wiki, and I want to translate some non-MediaWiki content (software interface text, in particular). How do I configure that, and what file formats are supported?

Also no, I don't feel like the project can/should be hosted on

User670839245 (talk)06:27, 12 May 2020

Dear Interface Administrator ...

First the bad news: it's a lot this time. The good news: I've made edit links with easy to copy/paste translations, and double checked everything.

Could someone please make these edit for me. Thanks a lot!



Wat jo yntype

Wat jo krije





[[Sidetitel]]<br />[[Sidetitel|Tekst keppeling]]

<a href='#'>Sidetitel</a><br /><a href='#'>Tekst keppeling</a>

[ Tekst keppeling]<br />[]<br />

<a href='#' class='external'>Tekst keppeling</a><br /><a href='#' class='external autonumber'>[1]</a><br /><a href='#' class='external'></a>

Kopke twadde nivo

Kopke tredde nivo

=== Koptekst ===

Kopke fjirde nivo

==== Koptekst ====

Kopke fyfte nivo

===== Koptekst =====


* Listrigel<br />* Listrigel


Nûmere list

# Listrigel<br /># Listrigel


Ynsletten bestân


Tekst byskrift


Sidetekst.&lt;ref&gt;[ Tekst keppeling], oanfoljende tekst.&lt;/ref&gt;

Sidetekst.<sup><a href='#'>[1]</a></sup>

Neamde referinsje

Sidetekst.&lt;ref name="test"&gt;[ Tekst keppeling]&lt;/ref&gt;

Sidetekst.<sup><a href='#'>[2]</a></sup>

Fierder gebrûk fan deselde referinsje

Sidetekst.<sup><a href='#'>[2]</a></sup>

Referinsjes werjaan

<ol class='references'><li id='cite_note-test-0'><b><a title='' href='#'>^</a></b> <a rel='nofollow' title='' class='external text' href='#'>Tekst keppeling</a>, oanfoljende tekst.</li><li id='cite_note-test-1'><b><a title='' href='#'>^</a></b> <a rel='nofollow' title='' class='external text' href='#'>Tekst keppeling</a></li></ol>

Sinjatuer mei tiidstimpel

--<a href='#' title='$1:Meidochnamme'>Meidochnamme</a> (<a href='#' title='$2:Meidochnamme'>oerlis</a>) 10 jun 2009, 15.54 (UTC)


<a href='#' title='$1:Meidochnamme'>Meidochnamme</a> (<a href='#' title='$2:Meidochnamme'>oerlis</a>)


Normale tekst<br />:Ynsprongen tekst<br />::Ynsprongen tekst

Normale tekst<dl><dd>Ynsprongen tekst<dl><dd>Ynsprongen tekst</dd></dl></dd></dl>
PiefPafPier (talk)11:28, 11 May 2020


Nike (talk)12:34, 11 May 2020

Jump to a specific message in list of messages

Is there a way to directly jump into a message in the list of all messages? I mean to be able to see the messages before/after it. For example the following URL shows the desired message, but filters out all other ones.

This could be useful for bookmarking the last string I was working on and quickly come back to it and continue the work.

Iriman (talk)09:30, 8 May 2020

Not at the moment. It would be easy to add anchors for each message, but they would be unreliable (affected by filters) and hard to discover how to use.

Nike (talk)13:57, 10 May 2020

Preview button malfunction on this page

By clicking the Preview button on this page browser asks me whether leave or stay on the page. If I choose leave, edits are gone.

Iriman (talk)09:24, 8 May 2020

Changing Name

Hi I'm requesting for change my name KaleemBhatti to Kaleem Bhatti please chanage my name

KaleemBhatti (talk)08:51, 28 April 2020

This is done. Changed the username to Kaleem Bhatti.


Abijeet Patro (talk)09:09, 1 May 2020

delete acccount

Hi, as I'm no more active in translation, please delete my account resp. do what comes close to.

- change my name: vanished-20200504 - delete my talk page and block my account. thank you very much

Jamali (talk)07:58, 4 May 2020

Proposal to change default skin to Timeless

I'm considering changing our default skin to Timeless. My reasons are:

  • Timeless has responsive design which works better on mobile devices (we get quite a few visitors from mobile devices, but not that many users), unlike the Vector skin. E.g. Google search has started penalizing sites which do not work well on mobile.
  • I like Timeless and I have been using it here for a while. Most glitches with Timeless have been fixed by now.


  • Manually set skin preferences would not change, and Vector would still be available as a choice.
  • Other option would be to install MobileFrontend extension, but that has not been tested and could break quite a few things.
  • Vector is going through modernization, so it could get better mobile support in the future.
  • Also tracked in phab:T248064

Please let me know what you think.

Nike (talk)11:41, 20 April 2020

Personally I would stick to the Vector skin (thus I'd appreciate installing MobileFrontend and Minerva skin for better mobile support anyway) but I don't see anything against Timeless as the default skin. Do whatever you want.

Rail (my talk | contribs)11:58, 20 April 2020

I would like keep using the Vector skin.

Winston Sung (talk)12:25, 20 April 2020

The design of the Timeless skin is good, maybe we can add it as an option in user preferences.

Winston Sung (talk)12:26, 20 April 2020

It's already in the preferences, and you can enable it.

Amir E. Aharoni (talk)12:34, 20 April 2020

I never used Timeless in a prodction system. So I changed here to Tineless and will try is the next days...

Raymond16:44, 20 April 2020

I also use Timeless here for a while; I hardly noticed the site notice about this thread… The font size is the same on Vector as well, but on Timeless it quickly gets covered by the top toolbar as I start scrolling. I think you should use the default font size so that users have a chance to notice it.

On-topic: I’m quite conservative, so even though I personally like Timeless, I’m not sure if the majority of the users do so. Also, the visual similarity to Wikipedia is IMHO more important than search engine optimization—are there users at all who come here from Google? This project is a rather background one, so I expect 99% of the users to come here from the translated projects’ sites (or experienced users using this wiki’s OpenSearch engine, arriving right to the message to translate).

Glitches: I still found three of them on Special:Translate for first sight.

  • “Translate” link in the More toolbox (on the right on wide screens). This is the default tab on Vector, which appears in the place of the Article tab. It’s visually needed on Vector and Monobook, but makes no sense on other ones like Timeless, Modern or Cologne Blue. I’m not sure technically how, but it should not be there on Timeless.
  • Language statistics, Message group statistics and Export. These three links are in the top right corner, all with default icons. This way the icons don’t have much purpose, but it’s particularly annoying on narrow screens, where only the icons appear, so the only way to tell them apart is by analyzing the URL, which is far from being user-friendly. I think this is a release-critical bug in terms of making Timeless default for all (often inexperienced) users.
  • Message documentation on mobile. Because of the narrow screen, the message documentation pane and the translation pane overlaps on mobile. The documentation pane can be collapsed, but only one-by-one for each and every message, while often it doesn’t contain any information. Maybe it could be fixed by switching to a vertical layout on narrow screens. This should only display the message documentation by default, not the translation helpers (other languages, machine translation etc.), again to save space, which could be expanded if needed. Also maybe remembering the state between messages would be helpful.
Tacsipacsi (talk)21:35, 21 April 2020

Thanks for the feedback. Regarding your point about message documentation on mobile, isn't that same problem also present in Vector?

I'll look into the two other glitches.

For translators, you are right. But developers looking for alternatives come via search engines.

Nike (talk)07:48, 24 April 2020

No, the message documentation windows (just like the user boxes mentioned below) have no such issues on mobile with Vector—since Vector is not responsible, mobile browsers use a so-called “virtual viewport” as a self-defense, which is much wider than the actual screen width (see Using the viewport meta tag to control layout on mobile browsers on MDN). This means that the text is maybe unreadably small, but at least the layout is not broken. Of course, this situation is much improved by the introduction of Timeless if Tux is made work well with narrow viewports.

For SEO: I see. This is a tough decision, however, as I still think that keeping consistency with Wikipedia is important, but I agree that letting developers find this site is just as important.

P.S. What about the site notice? Is there a reason not to increase its font size?

Tacsipacsi (talk)13:31, 24 April 2020

Regarding issues 1 and 2 (the navigation tabs), I see no easy way to fix it. I am not skilled enough to make distinct icons for them. I considered moving them elsewhere, but I have no control over where (filed Phab:T251258).

Regarding the 3rd issue, it would fall under Phab:T146134. Unfortunately I don't think I can fix it without re-doing the UI with a more responsive grid system, which is a lot of work.

Nike (talk)14:54, 28 April 2020

I also noticed that my user page looks not-so-perfect on a narrow screen: the Babel boxes become 100% wide if the screen is less than 480px wide, while the other user boxes don’t. I think the best solution for this issue is installing mw:Extension:TemplateStyles and creating a responsive TemplateStyles subpage for {{Userbox}}.

Tacsipacsi (talk)16:47, 23 April 2020

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Return to Thread:Support/Proposal to change default skin to Timeless/reply (8).


I don't like new skin and I think it should not be used as default (neither for new users). One reason is that it is more intuitive for Wikipedia editors to see same appearance here as it is on Wikipedia (Message, Discussion – Read, Edit, View history / More; What links here is moved to the right and was always to the left etc.). Also, Timeless skin is not full width. One thing I like with the proposed skin is that it is more interactive than current standard one (buttons).

Obsuser (talk)16:42, 24 April 2020

Good reasons, no objections here.

PiefPafPier (talk)18:11, 24 April 2020

I changed my skin to Timeless after seeing the ad.

It's mostly fine, but there are some issues. The most significant is perhaps this: The ULS control for changing the UI language is hidden under the user menu. It's not a thing that people often do once they settle on a language they want, but initially choosing the language for new users may become challenging.

Amir E. Aharoni (talk)05:55, 28 April 2020

Probably language selection should be part of the registration process. This not only overcomes this issue in case Timeless wins, but also, more importantly, makes even more users aware of the possibility to set their interface language. (And don’t be shy to tell all issues you found, so that Timeless will work as seamlessly as possible.)

Tacsipacsi (talk)11:40, 28 April 2020

It already is a part of the registration process, and I notice that a lot of people don't actually do it and stay with English, not just as the language in which they use the site, but also as the only language they know :/

Amir E. Aharoni (talk)15:36, 3 May 2020

I just use Vector on laptop with extended display for my translations, comparing pages, viewing reference pages and so on , so that I dont really use my tablette for that. Nothing against, till my environment remains available.

ChristianW (talk)15:23, 28 April 2020

I like that Timeless is truly responsive, but I really do not like its design. If the skin by default was changed to Timeless, I would switch it back. It might be a good test as to see which pages are responsive or not (and need TemplateStyles / CSS changes), but I feel like that should be mostly a power-user thing.

I also feel like, with its Wikimedia colours being displayed quite prominently in the design, it doesn’t make much sense to use the skin as it is for a project that isn’t, formally, one of Wikimedia projects. But maybe I am reading too much into this and the only effect of the change would be ‘huh, skin is different from Wikipedia/Wiktionary/etc.’, since many people will probably not associate those colours with Wikimedia.

stjn[ru]11:14, 29 April 2020

Question related to problem with message

Hello, I have GrowthExperiments installed on my test wiki. Why is tag shown in message on wiki? This message: MediaWiki:Growthexperiments-homepage-suggestededits-difficulty-filters-article-count/sr-ec is related.

On english version of site everything is fine, so I think that problem is with translation. Is something wrong?

Zoranzoki21 (talk)17:51, 2 April 2020

I don't see anything wrong with the translation. Can you give a screenshot of what you are seeing?

Edit: By tag I assume you mean the strong tags?


Abijeet Patro (talk)16:08, 1 May 2020

It is fixed by another user already. Thanks in each case!

Zoranzoki21 (talk)13:39, 2 May 2020

Update "Translating:MediaWiki/Credits" page

A thread, Thread:Support/Update "Translating:MediaWiki/Credits" page, was moved from here to Translating talk:MediaWiki/Credits. This move was made by Nemo bis (talk | contribs) on 2 May 2020 at 10:50.

Delete my account


Could you please delete my account ?

Thank you

Amaziɣ maziɣ (talk)14:11, 27 April 2020

The platform does not support user deletion. We can change your password, delete your talk page and block your account. Would it be possible to know the reason why you want to do this?

Abijeet Patro (talk)09:11, 1 May 2020

Request Offiline Translator Right

As Translating:Offline suggested, I need offline translator rights to upload translation. However, it does not say whether or not I should request the right before I send my first submission to the email address provided. To not get refused when I send the submission, I think I should request the right beforehand.

VulpesVulpes825 (talk)09:51, 28 April 2020

I've handled the imports and given you offline rights. Do remember to avoid large message groups and do not work offline for extended periods of time. Thanks.

Nike (talk)08:31, 30 April 2020

Understood, and thank you for the import.

VulpesVulpes825 (talk)09:44, 30 April 2020

help when 'Plural' syntax is not accepted

Hi all, concerning following message =>

I think a parameter $1 is missing as for the plurality but it is rejected saying it must be {PLURAL| ...

{{PLURAL:$1|zero=Vous n’avez encore fait aucune rephoto|one=<b>1</b> rephoto|<b>%1$d</b> rephotos}}

I cannot find the correct syntax. I checked it is ok with template => but cannot succeed; help please. Seems as if the original message was wrong (?). Thanks.

ChristianW (talk)12:12, 23 March 2020

As per CLDR data, French has only two plural forms. So the below should be enough,

{{PLURAL|one=<b>1</b> rephoto|<b>%1$d</b> rephotos}}
Abijeet Patro (talk)12:57, 26 March 2020

The source string was just fixed yesterday by Ajapaik developers. The zero version is now a separate message.

Nike (talk)13:03, 26 March 2020

Sounds good now; in french 0 or 1 follow the same way, 2 and over start plural, so according to the number of books on the shelf you say

Il n'y avait aucun livre   sur l'étagère. 
Il   y avait zéro  livre   sur l'étagère.
Il   y avait un    livre   sur l'étagère.
Il   y avait deux  livres  sur l'étagère. 

Thanks; done.

ChristianW (talk)21:04, 26 March 2020

You're lucky in that someone is even willing to listen to you. I've been trying to correct the Portuguese plural for years to no avail, despite the fact that even CLDR agrees with me. The first thing that they usually throw back at you is that you need to convince CLDR. Once you point out that CLDR is already correct and convinced, and agrees with you, and MediaWiki is wrong, they'll push onto you the job of correcting it yourself.

Hamilton Abreu (talk)02:22, 28 March 2020

The "zero" case can be treated specially in French: if you use a number in the translation, treat it as singular only.

But like in English, the message can also use the negation if the number is spelled in a sentence like "Il n'y avait aucun livre" or "il n'y a pas de livre" where sometimes such negative form implies a plural for the noun, depending on the meaning of the noun: "Il n'y a pas de livres" is also correct with the plural, applicable only to enumeratable things, and means "not one and not even more than one").

So the "zero" case may be added optionally to any translation, in addition to the 1st (singular) and 2nd (plural) forms.
This "zero" case should not be used at all if the number is displayed with digits as "0", which must be treated with the singular.

For some sentences where the number is a small integer quantity, you can specialize the translation to spell that number instead of formatting it with digits. This would apply only if the maximum number is small and spelled as a single word (0 treated specially with the "zero" case, or other integers from 1 to 16, or one of 20, 30, 40, 50, 60, 100 and 1000, each using a special case for these values and nàot depending on the default plural rules even if grammatical French rules still apply to these numbers: 1 may be special-cased but the translation should use a singular form for nouns, adjectives and verbs, all other special cases should use the plural form); all other values should be formatted using digits and the standard French plural rules:

  • if abs(n) <= 1 (including n=0.5 or n=0 or n=-1), then use the singular (1st form, used by default)
  • if abs(n) > 1 (including n=1.5 or when n is infinite), then use the plural (2nd form if it's specified, otherwise display the 1st mandatory form)
  • if n is unknown/unspecified, then use the plural (2nd form if it's specified, optional otherwise display the 1st mandatory form) without writing any number

Note that the 2nd form is also optional in French translations, as it may be the same when the form is grammatically invariant in some cases. For example,

  • "1 face" vs. "2 faces" (because the noun "face" has no mute mark of the plural in its singular form, you need a second form to mark the plural)
  • "1 dos" vs. "2 dos" (because the noun "dos" is already terminated by a mute "s" which then remains invariant in the plural)
  • Such cases with invariant grammatical plurals also occur in English (but much more rarely than in French, as English will most often repeat the 's' by inserting an extra non-muted 'e' pronounced as a schwa before this added 's' for its semi-regular forms of plural marks: "1 boss" vs. "2 bosses", but in French the borrowed term boss would remain invariant: "2 boss" because the French term "bosse(s)" is completely unrelated).
  • Invariant grammatical plurals also occurs in almost all languages with abbreviated units of measurement ("1 m" vs. "2 m"), and some translations may prefer using common abbreviations with a single translated form, rather than translating several plural forms: "1 meter" vs. "2 meters" in English, "1 mètre" vs. "2 mètres" in French.
  • Marking the plural in French for terms borrowed from other language is variable and depends on usage: you may use the normal French rules for derivation ("1 pizzaïolo" vs. "2 pizzaïolos", this is generally preferred) or the derivation from the original language ("2 pizzaïoli" from the Italian term, except this is generally not acceptable here as the orthographic term was already modified in French with the diaeresis in the singular, and this singular form should be the base for forming a regular plural), but the choice of marking the singular or plural must still use the French rules ("0 pizzaïolo" : must be singular). Another example (more acceptable): "2 misses" (irregular plural form taken from the English noun "miss(es)" for a woman borrowed as is, but not that we'll still write "0 miss" in French with the singular form chosen, vs. "0 misses" in English with the plural form chosen).

But if you add some other terms in the translation, you may see the difference of plural form in dependant adjectives or verbs that require marking the singluar or plural distinctly:

  • "1 dos courbé" vs. "2 dos courbés" : now you need the two forms in translations
  • "1 dos se courbe" vs. "2 dos se courbent" : now you need the two forms in translations
  • "1 dos à courber" vs. "2 dos à courber" : one form remains sufficient in translations; the verb "courber" is invariant as an infinitive as it has no subject with which to match a number); if you translate the second form, it should be identical to the 1st form intended for singular, also used by default.

If n is a rational fraction, and the full fraction is specified as the explicit numeric values of the numerator and of the denominator (like "⅘") the plural is marked in French only the term for the denominator but then the unit that follows is using the singular form when it is preceded by the preposition "de" according on this fraction: "½ litre" but "10/20 de litre", "¾ de litre". The French rule is:

  • if the absolute denominator is 2, don't use the preposition, but match the plural with the absolute numerator; the French term for the denominator "2" is the adjective "demi-" which is invariant before the noun it qualifies and attached to it by an hyphen: ("demi-" is prefered to the alternate ordinal "2e(s)=deuxième(s)" which is also possible and whose plural varies according to the numerator, but which is almost never used)
    "½ litre" = "1 demi-litre" (= "10/20 de litre" = "10 vingtièmes de litre"): the denominator is 2, so no preposition and then the numerator 1 is singular, so after "demi-", the "litre" will be singular.
    "3/2 litres" = "trois demi-litres": the numerator is 2, so no preposition and then the numerator 3 is plural, so after "demi-", the "litres" will be plural.
  • if the absolute denominator is not 2, use the preposition "de" before the singular noun;
    • the fraction may be spelled using ordinal numbers as nouns for the denominator: "3/12e(s) de litre" or "3 douxièmes de litres" ; when the denominator is spelled, it takes its plural form according to the numerator); The form "3/12e(s)" with an explicit ordinal mark including its own plural mark is needed (either use a suffix preferably in superscript, or use a more compact typographic fraction like "¾" without any suffix and without even any preposition "de" before the noun); the terms for fractional ordinals however are a bit different from rank ordinals, for these two denominators 3 and 4:
      "3s" or "tiers" (numerically invariant) for fractional ordinals, instead of the normal ordinal "3e" or "troisième" only used for (invariant) ranks.
      "4t(s)" or "quart(s)" (numerically variable according to the numerator) for fractional ordinals, instead of the normal ordinal "4e" or "quatrième" only used for (invariant) ranks
    • the fraction may also be spelled using a cardinal number for the denominator and if so the noun after it will follow the denominator: "3/12 litres"="3 sur 12 litres" (plural according to the denominator 12), or better, if you can, the units may be placed before the numerator from which it will match its plural: "3 litres/12"="3 litres sur 12" (plural according to the numerator 3)
    • This means that "¾ de litre" = "3/4ts de litre" = "3 quarts de litre" is correct (litre is singular after "de"), but also "3/4 litres" ("litres" is then plural according to the numerator 3): you cannot use the typographic "¾" and the legacy "3/4" interchangeably. But you can use the typographic "¾ de" and the legacy "3/4 de" interchangeably (with a singular noun).

These rules are almost identical in English (using the preposition "of") which also has specific terms for a few common fractional ordinals (always "half"/"halves", rarely "tier(s)", frequent "quarter(s)") used instead of ordinals for ranks (never "second(s)", most frequent "third(s)", frequent "fourth(s)", ).

However, using rational fractions is still not supported as distinct cases in translations for now, because there's no key for them. They may be used only for specific fractions that are exact as decimal numbers (fractions whose denominator is decomposable in a product of powers of 2 and 5, for which the plural case key would its decimal value as a single non-integer with a limited precision (0.25, 0.5, 0.75, 0.125, etc.); this could work with some translation libraries offering the support for non-integer values of keys n, or offering support for rational keys with the form m/n.

Verdy p (talk)00:28, 28 April 2020

Tajik (Arabic script)

Edited by another user.
Last edit: 14:33, 15 July 2017

Pleas create language Tajik (Arabic script) (tg-Arab) for Arabic scripts in Tajik language.

ToJack (talk)10:15, 15 July 2017

Dear developers that are interested in doing it: Like Chinese, Kazakh, Kurmanci Kurdish, Serbian and others, Tajik is also having LanguageConverter support, although it's incomplete as it can only convert between Cyrillic and Latin. The Meta-Wiki suggests a shareware to convert Tajik Cyrillic to Perso-Arabic script, but since it's not updated for 9 years I doubt if there's users that are still interested in adding tg-arab support to converter.

PS: the ISO 639-3 abh tells me Tajiki Arabic, one of dialects of Central Asian Arabic, I don't know if there's relations between abh and tg-arab

Liuxinyu970226 (talk)11:44, 15 July 2017

No relations between abh and tg-arab. Translations for tg-arab you can add from fa.

ToJack (talk)14:16, 15 July 2017

I edited your original description to make that as not ambiguous

Liuxinyu970226 (talk)14:33, 15 July 2017

Sorry about replying after such a long time. I noticed it only now.

Why is this needed? As far as I know, the Tajik language is written in the Cyrillic alphabet.

Amir E. Aharoni (talk)10:46, 17 April 2020

I'll need a reply to this before I can act. I'm closing this for now. If anyone ever has an explanation of how will Tajik in Arabic script is useful, feel free to reopen.

Amir E. Aharoni (talk)12:07, 25 April 2020

Support for lad-hebr on Ladino Wikipedia

Hi. On behalf of the current Administrators at Ladino (Judeo-Spanish) Wikipedia, we would like to ask a few questions about how explicit support for lad-hebr might work on our project. We don't see being able to ramp up full support for it just yet, and we are certainly not going to be asking to create a separate project for it. However, we have 48 main-space pages (including one variant of our home page), plus a handful of templates and categories, in Hebrew script. We're wondering if some limited support might be available, and perhaps if we can even test fuller support on one or two pages. Here are some preliminary questions:

  • If we currently enter a very small group of translations into the system here, will they work if we call them explicitly? Example: date translations (day of week, conventional month, Hebrew month). Right now, MediaWiki:Monday/lad shows the value "Lunes". The proper value for MediaWiki:Monday/lad-hebr (or whatever that would be named) would be לוניס. Currently, if I call {{#time:l}}, I will get "Lunes". As things are currently configured, if I entered "לוניס" in the right place here on translatewiki, then called {{#time:l||lad-hebr}}, could I get it to return "לוניס"?
  • Similarly, we wondered if we could try to assign the language code "lad-hebr" to the Hebrew-script version of our home page, לה פרימירה אוזֿה, or at least to a copy of it. We would then start with the fallback cascade of lad-hebr>lad>es>en. Slowly, as we added translations to lad-hebr, we could get that page to work properly as lad-hebr, with rtl rendering not dependent on a div block, and so forth.

Are such things possible, or does a more complete commitment to a relatively full interface translation scheme have to come first? StevenJ81 (talk) 18:50, 7 September 2015 (UTC)

And by the way: Why doesn`t Special:SupportedLanguages show Ladino?
StevenJ81 (talk)18:50, 7 September 2015

I'm just curious that why we can't have a Latin-Hebrew converter for Ladino.

Liuxinyu970226 (talk)02:44, 20 July 2016

It's possible, but not easy. There are several orthographies for Ladino in Latin script, and any converter would have to be able to detect which orthography is being used. (Alternatively, I suppose, any page in lad-latn would have to identify its orthographic system.)

The opposite is much more difficult. The mapping from any given Latin orthography to Hebrew is essentially one-to-one, with the caveat that initial vowels need special handling, and so do certain final consonants. But the mapping from Hebrew orthography even to a single, preferred Latin orthography is not. For example, the same Hebrew-script vowel is used for both i and e, and a different Hebrew-script vowel is used for both o and u.

StevenJ81 (talk)15:57, 29 July 2016

Sorry, forgot about it for some reason. No idea why haven't I done it till now. It's now enabled.

Amir E. Aharoni (talk)12:26, 17 April 2020
First page
First page
Last page
Last page