GerardM added a comment.
Hoi,
We can only support scripts supported in Unicode. So what is the font to be
used?
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T180345
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To
GerardM added a comment.
Hoi,
No problems with Indian English, we also support Australian English. I can
imagine that there are differences in Indian English but that takes nothing
away from the legitimacy of this request.
Thanks,
GerardM
TASK DETAIL
https
GerardM added a comment.
Hoi,
Please explain what purpose it will serve.
Given that it is a natural language that is actually spoken, full service
in labels and descriptions will serve its potential audience. You can go
ahead and install this and once the language committee agrees
GerardM added a comment.
Hoi,
So you are fine having people work using a method that does not provide a
benefit for no good reason? When we can agree on the proposal that is on
the table, the work done in this restricted way will be of no use. That is
a travesty.
Thanks
GerardM added a comment.
There is no point in accepting an inferior method when another, a better
way is being considered. As I indicated this method does not bring any
benefits to the table.
Thanks,
Gerard
TASK DETAIL
https://phabricator.wikimedia.org/T234761
EMAIL
GerardM added a comment.
Hoi,
I fail to see what the benefit will be of this. I have put a proposal to
the language committee that will make the efforts useful and usable. I am
awaiting their response.
At this time for me there is a no.
Thanks,
GerardM
TASK DETAIL
https
GerardM added a comment.
Hoi,
There is a big difference between mono-lingual texts and the use in labels
and descriptions. The latter needs support in translatewiki.net as well.
The criteria for that are much more stringent.
Thanks,
GerardM
TASK DETAIL
https
GerardM added a comment.
Given the abuse, you make no argument that is acceptable. That and you are
wrong.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T155425
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Mbch331
GerardM added a comment.
A code is a must have.
TASK DETAIL
https://phabricator.wikimedia.org/T222020
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GerardM
Cc: Mbch331, jhsoby, GerardM, Aklapper, OwenBlacker, alaa_wmde, Nandana, Lahi,
Gq86
GerardM added a comment.
The language may be written in two scripts however, use what is standard and
standard use is Cyrillic given what Jon Harald mentioned.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T155367
EMAIL PREFERENCES
https
GerardM added a comment.
This is a language to be written in its original script. Clearly entitled to
be used in Wikidata.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T164580
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences
GerardM added a comment.
Yes,
I know these are fine.
Thanks,
TASK DETAIL
https://phabricator.wikimedia.org/T210293
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Michael, GerardM
Cc: WMDE-leszek, Tarrow, Mbch331, Lydia_Pintscher
GerardM added a comment.
Yes,
I know and consequently they are fine.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T210293
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Michael, GerardM
Cc: WMDE-leszek, Tarrow
GerardM added a comment.
Hoi,
When we go the way of allowing for languages that are not accepted in any
standard, we could use -x- However, it removes any possibility to question
the validity and the inclusion of anything used by such a code. So I
strongly urge us to refrain from non
GerardM added a comment.
One of the comitments of the Wikimedia Foundation is that we will comply with
standards. Vladimir fails to understand that the fact that "Chinese" has been
transcribed in hieroglyphs has no bearing on standards. First, Chinese is
probably to be und
GerardM added a comment.
Hoi Alexiev,
What you just did is a personal attack. It does not make an argument go
away. It does not help your point of view.
When some linguists take it up on themselves to express a language in other
scripts, they may. It does not change the notion that
GerardM added a comment.
Hoi,
You say it in your reply. The English word is Cadiz and the Spanish word is
Cádiz. There is no Phoenician in Latin script.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T155425
EMAIL PREFERENCES
https://phabricator.wikimedia.org
GerardM added a comment.
Hoi,
It would still be a word used in the rest of the text. Transliteration
differs depending on the language not on the script conversion.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T155425
EMAIL PREFERENCES
https
GerardM added a comment.
No problem having a monolingual code for tlb Tobelo
https://www.ethnologue.com/15/show_language/tlb/
TASK DETAIL
https://phabricator.wikimedia.org/T216798
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GerardM
Cc
GerardM added a comment.
No, it is is phn-Latn when it is used for use by Phoenicians.
Transliteration is different even within a script there are differences
depending for what language it is transliterated.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T155425EMAIL
GerardM added a comment.
Hoi,
When you transliterate a name of a language typically it is transliterated
for a specific language. It is not that language.even when you know that
the original is transliterated for a specific language.
Thanks
GerardMTASK DETAILhttps://phabricator.wikimedia.org
GerardM added a comment.
Hoi, according to the Wikipedia article there is one script; the Chakma script (Cakm). Eastern Nagari and Ajhapath are two orthographies using the same script? How are they related to the two peoples indicated to speak the language and in what orthography is the curriculum
GerardM added a comment.
Hoi,
The code phn is reserved for the Phoenician language. However, it is not
written in the Latin script. Consequently the question why it should be
accepted in the Latin script is real. What is the point?
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org
GerardM added a comment.
en-US is perfectly legitimate. The stuff about Alsatian is not.TASK DETAILhttps://phabricator.wikimedia.org/T154589EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lea_Lacroix_WMDE, GerardMCc: Jc86035, Liuxinyu970226, Jdforrester-WMF
GerardM added a comment.
Given that the codes should adhere to standards, what is the basis for these codes?TASK DETAILhttps://phabricator.wikimedia.org/T210293EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Nikki, Liuxinyu970226, GerardM, Aklapper
GerardM added a comment.
Hoi,
When I want to be pedantic (but factually correct) the code should be
el-CY. The standard for ISO-3166 has the codes in upper case. When there is
a need to distinguish Greek from Cyprus, yes, el-CY would be fine.
Thanks,
GerardMTASK DETAILhttps
GerardM added a comment.
Hoi,
In the past we have been where we are now with Wikidata and new language
codes with new Wikipedias. The result was mayhem, and everything was just
as the "community" decided. The result is the many Wikipedias that have
no community. As a result th
GerardM added a comment.
Hoi,
I understand the purpose of Phoenician in Phoenician. Having it in the
Latin script makes no sense to me at all
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T155425EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Mbch331
GerardM added a comment.
Hoi,
Artificial languages are not what we support by default. I am not in favour
for these particular cult languages. I will ask the language committee if
they see it any different.The fact that Tolkien wrote some poems is in
itself not enough.
Thanks,
GerardMTASK
GerardM added a comment.
Hoi,
Is there a purpose for these languages. My feeling is that as these languages are incomplete as languages there is little that they will add.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T185194EMAIL PREFERENCEShttps://phabricator.wikimedia.org
GerardM added a comment.
There is imho no problem, an individual language..
https://www.ethnologue.com/subgroups/zenati
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T184783EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Mbch331, GerardMCc
GerardM added a comment.
Hoi,
There is no problem with this language. It is not a macro language. Go with it.. PS it does use the Phoenician script.. Maybe that needs inclusion in the language tools but that is no prerequisite.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org
GerardM added a comment.
Hoi,
The language committee is responsible for the use of the codes used. As it is, multiple members have indicated that it is wrong to add these codes. Please desist.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
I understand how this could work for the dictionary part of Wikidata. I
understand how it could work for labels and aliases. Why do you think this
will work for descriptions?
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T187344EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
In principle the language committee has given permission for monolingual
texts. This is NOT given for labels, descriptions and aliases. That
requires involvement of native speakers. It requires an agreement of the
language committee.
What makes you think you can add
GerardM added a comment.
Hoi,
The defenitions are in the standard. The standard is the ISO639-3.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Badaa, ChristianKl, C933103, jhsoby
GerardM added a comment.
Please motivate.
Thanks,
GerardM
Op vr 1 dec. 2017 om 18:48 schreef VIGNERON <
no-re...@phabricator.wikimedia.org>
VIGNERON added a subtask: T181823: Add monolingual language code fro and
frm in Wikdiata.
*TASK DETAIL*
https://phabricator.wikimedia.org/T
GerardM added a comment.
Hoi,
What I find is totally unreadable.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T144272EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: C933103, Nikerabbit, Mbch331, Lydia_Pintscher, Zoranzoki21, Nikki
GerardM added a comment.
Because it is not one but multiple languages.TASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: ChristianKl, C933103, jhsoby, thiemowmde, Liuxinyu970226, Lydia_Pintscher
GerardM added a comment.
it is still a macro language and therefore not usable to identify a textTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: ChristianKl, C933103, jhsoby, thiemowmde
GerardM added a comment.
I think that we should stop with these stamp collections there is no argument why we want to do this, we have seen that the meaning given often differs substantially from what the standard is. It makes more sense to study the effect of the introduction of Wiktionary
GerardM added a comment.
Hoi,
The Alsatian issues precedes the language policy and as such it is a "fait
accompli". We have to live with it. A similar situation will no longer come
into being because it will not be approved.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T1
GerardM added a comment.
No mn-Mong is a combination of the language and the script. mn is a ISO-639-1 codeTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: ChristianKl, C933103, jhsoby, thiemowmde
GerardM added a comment.
Hoi,
The consideration has been only is it a valid code. The question asked is a
different one. What is the point to all these codes that probably do not
bring anything to Wikidata.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T144272EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
I asked in the past why codes were added. In principle, we could include
them all but there is no clarity why codes are proposed. As a consequence I
lost interest.
So I agree with Amir that some sanity would be in order.
Thanks,
GerardMTASK DETAILhttps
GerardM created this task.GerardM added a project: Wikidata.Herald added subscribers: PokestarFan, Aklapper.
TASK DESCRIPTIONhttps://www.wikidata.org/wiki/Q35490944?action=""> will not show the label for Q5 (human) and P166 for "award received" ..TASK DETAILhttps://ph
GerardM added a comment.
Did you try to add it using the language code?
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T161983EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Ladsgroup, GerardMCc: gerritbot, jhsoby, GerardM, MF-Warburg
GerardM added a comment.
Hoi,
I know very well what this is about. As a member of the language committee
I made the arrangements for other languages then the codes accepted for
localisation to be accepted for monolingual texts. You can ask Lydia if you
do not believe this.
It is with this
GerardM added a comment.
Hoi,
the specific problem is that there is clear and uncontroversial consensus
to transition nrm to nrf, and the actual execution is only blocked by
technical issues. Issues that are only pushed forward because it is not
deemed to be relevant enough.
The problem is that
GerardM added a comment.
Hoi,
Yes. There is a system in codes. When you have a subset that is not
associated with the superset, you destroy the credibility of the language
codes.
There is an outstanding request to rename wikipedias for this reason. We
should not make the current situation worse
GerardM added a comment.
Hoi,
Because they are a subset of nrf.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher, Verdy_p, gerritbot, Amire80, Nikki, jhsoby, GerardM
GerardM added a comment.
Hoi,
The issue is that the proposed code is a subset. The main item is
problematic and therefore this code is problematic.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences
GerardM added a comment.
Hoi,
Saying no when it is appropriate is constructive.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T155424EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher, GerardM, Bugreporter, Aklapper
GerardM added a comment.
Hoi,
The code NRM is used incorrectly .. as you know.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Verdy_p, gerritbot, Amire80, Nikki, jhsoby, GerardM
GerardM added a comment.
Hoi,
I think that hbo is quite ambiguous.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T155368EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Esc3300, Lydia_Pintscher, GerardM, jhsoby, Aklapper, Bugreporter
GerardM added a comment.
Hoi,
I am active in both Wikidata and in the Language committee.. There are more
people in there who have a valid opinion.
NB this is not primarily a Wikidata concern. It adds codes because the
language committee sees room for it.
Thanks,
GerardMTASK DETAILhttps
GerardM added a comment.
Hoi,
As mentioned elsewhere and not only by me, it is not.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Verdy_p, gerritbot, Amire80, Nikki, jhsoby
GerardM added a comment.
Hoi,
No you get it backward. At this time for this language we (WMF) identify
incorrectly. We should not make the mess even bigger.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T165648EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel
GerardM added a comment.
Hoi,
Given that there is a Wikipedia with the wrong code, it is not possible
imho to do justice to the language. WMF has never had a reason to sort it
out, now it has. Adding codes is not appropriate under these circumstances.
Thanks,
GerardMTASK DETAILhttps
GerardM added a comment.
Hoi,
In this case I think the language committee wants to be involved. This is
one of the longstanding issues we face and we do not want to muddle the
waters even more. So in this case it is not ok to move forward imho.
Thanks,
GerardMTASK DETAILhttps
GerardM added a comment.
OkTASK DETAILhttps://phabricator.wikimedia.org/T155430EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher, jhsoby, GerardM, Aklapper, Bugreporter, QZanden, Izno, Wikidata-bugs, aude
GerardM added a comment.
Hoi,
When you want a technical point, the code is a combination of two parts, to
standards. It is fr, the ISO 639 -1 code for Francais, the French language
and CA, the ISO 3166-2 code for Canada. Both should be spelled correctly so
the code should be fr-CA
Thanks
GerardM added a comment.
Hoi,
What is meant by the cn and hk? It probably has nothing to do with a script
.. a script has four characters. Consequently this is not about script in
the definition.
Thanks,
GerardTASK DETAILhttps://phabricator.wikimedia.org/T97882EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
First there has to be agreement on the use of codes like this in the
language committee.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T144272EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: jhsoby
GerardM added a comment.
Hoi,
For en-US we take it that it is standard English.. We do have en-GB among
others already.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T151186EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc
GerardM added a comment.
The name is capitalised according to Ethnologue but yes, it is a recognised language.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T151129EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: aude, GerardMCc: jhsoby, Jonas
GerardM added a comment.
This is NOT necessarily where the language committee gives its ok. It is not a different language.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T151186EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: GerardM
GerardM added a comment.
Hoi,
It does have a valid ISO-639-3 code. No problem here. I do not know how it
may become meaningful. It is an open question for several languages.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T98314EMAIL PREFERENCEShttps://phabricator.wikimedia.org
GerardM added a comment.
Hoi,
This is not a language with an ISO-639-3 code and therefore it should not
be created.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T144272EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: jhsoby
GerardM added a comment.
Hoi,
The Wikipedia article says different. Indeed Ethnologue is leading.. By the
way these others in the article are not dialects. They may be added as well
when there is a need.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127858EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
Exactly and according to the ISO-638-3 Noongar is a macro dialects and what
you call dialects are languages.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127858EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To
GerardM added a comment.
Hoi,
ISO 639-3 is about languages not dialects. They all have their own
ISO-639-3 code.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127858EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher
GerardM added a comment.
Hoi,
The Wikipedia article has it as a macro language and that makes it
problematic.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127858EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher
GerardM added a comment.
Hoi,
You are wrong. We do not accept macro languages for new purposes. Only when
a code is already in use, we let it ride. Reluctantly. The point of this is
that we do not and do not want to end existing projects.
Thanks,
GerardMTASK DETAILhttps
GerardM added a comment.
Hoi,
We do not accept anything new that does not comply with the policy. There
is plenty of old stuff that does not change as per the policy.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings
GerardM added a comment.
Hoi,
Yes, and zh is a language not a macro language. It is about new
recognitions and mn is a macro language. When the language policy were in
effect from the beginning, it would have been eng.wikipedia.org.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org
GerardM added a comment.
Please provide the source that backs you up. It has to be the ISO-639-3 as
it is what our policies is based on.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To
GerardM added a comment.
Hoi,
You are wasting your time searching for a result that is wrong on basic
principles. When a language is not a language why would you want it to be a
language ? Why seek in documents something that is self evident. Something
that is NOT a language should never be
GerardM added a comment.
Hoi,
It is so obvious that is not even in the policy.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: jhsoby, Nikki, thiemowmde, Liuxinyu970226
GerardM added a comment.
Hoi,
I am a member of the Language Committee of the Wikimedia Foundation. It is
stated policy that we do not accept macro languages. Lydia does read the
comments and she knows of its existence, its policies and for me it is not
personal. Is it for you?
Thanks,
GerardMTASK
GerardM added a comment.
Hoi,
That makes no difference. A language needs to fulfill some minimum
requirements and mn is not the code for a language.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T137810EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel
GerardM added a comment.
Hoi,
Sorry but your only option is wrong on principles. The code mn is for a
language code that will never get recognition from the language committee.
The way to distinguish between scripts is by using the ISO-15934 code and
consequently it should be mn-Mong if your way
GerardM added a comment.
I am fine with it :) Thanks, GerardMTASK DETAILhttps://phabricator.wikimedia.org/T146707EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Wikidata-bugs, GerardMCc: Lydia_Pintscher, GerardM, gerritbot, Aklapper, Matanya, JEumerus, jhsoby
GerardM added a comment.
Hoi,
Having a font has never been a prequisite for support in MediaWiki. It has
been a reason to support the development of a Freely licensed font or to
support talks on the licensing of an existing font.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org
GerardM added a comment.
Hoi,
The practise of dropping upper case in the ISO-15934 is a MediaWiki
practice that is incorrect. In the grand scheme of things it is only a
minor matter.
Mong is the correct code for the Mongolian script. The reason why mn-mong
is not there is that it does not make
GerardM added a comment.
Hoi,
mn is the code ISO-639 for the language, Mong is the CLDR code for the
script and CN is a code for the country where it is practices. The correct
LANGUAGE code is either khk or mvf because as a macro language that does
not have an existing project it is not eligible
GerardM added a comment.
Wikidata may support over 7000 languages; all the languages that are recognised are allowed.
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127435EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: thiemowmde, GerardMCc
GerardM added a comment.
Hoi,
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T98314EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Nikerabbit, GerardM, Liuxinyu970226, adrianheine, Jonas, Robin0van0der0vliet, Ricordisamoa, Amire80
GerardM added a comment.
This is a living language. No problem
Thanks,
GerardMTASK DETAILhttps://phabricator.wikimedia.org/T127435EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: Lydia_Pintscher, Liuxinyu970226, adrianheine, Nikki, MF-Warburg
GerardM added a comment.
non is a ISO 639-3 code therefore permissible by the language policyTASK DETAILhttps://phabricator.wikimedia.org/T137115EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GerardMCc: GerardM, Aklapper, afeder, Zppix, D3r1ck01, Izno
GerardM added a comment.
The language can be added because the hai code is an ISO-639-3 code. Only languages with an ISO-639-3 code may be enabled according to the language committee. Thanks, GerardMTASK DETAILhttps://phabricator.wikimedia.org/T138131EMAIL PREFERENCEShttps
GerardM added a comment.
Hoi,
Adding NEW languages or NEW scripts to an existing language is something
that has always been done after consideration by the language committee.
For languages that are known to exist in ISO-639-3 there is approval to add
them after a request.
Thanks,
GerardM
GerardM added a comment.
Hoi,
It is what we do in Wikipedia. It is the standard.
Do you really want to duplicate all labels for a language on this
assumption? Or are you saying that sr is the standard and the others are
when something is different in the same way as for American English,
British
GerardM added a comment.
Hoi,
When you compare a choice made and having to detect a script I am shocked
that it is only 10 times more difficult. We do not need to store in both
Latin script and Cyrillic. We should use the MediaWiki convention and store
in Cyrillic. That is an architectural
GerardM added a comment.
Hoi,
Detecting a script is easy... It is within a certain block of characters
and that makes it a particular script. Not hard at all. This is script
detection not language detection.
Thanks,
Gerard
TASK DETAIL
https://phabricator.wikimedia.org/T97882
EMAIL
GerardM added a comment.
Hoi,
For monolingual text we should never transliterate.
When we enter data in Wikidata on any other type of field, it should be
Serbian and the transliteration should be automatic.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T97882
EMAIL
GerardM added a comment.
Hoi,
We should NOT apply automatic transliteration between them for display.
THAT IS THE POINT. So we do not have this.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T97882
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel
GerardM added a comment.
Hoi,
It is simple. When a text is in Serbian, it can be in the Latin or the
Cyrillic script. When a text is only to be shown in one language, it should
also be exclusively in one script.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T97882
EMAIL
GerardM added a comment.
Hoi,
They are known. It is just that the software presents them in a way that is
controlled programatically. The purpose here is to show a language in a
particular script ALL the time.
Thanks,
GerardM
TASK DETAIL
https://phabricator.wikimedia.org/T97882
EMAIL
GerardM added a subscriber: GerardM.
TASK DETAIL
https://phabricator.wikimedia.org/T103092
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GerardM
Cc: GerardM, Ricordisamoa, Christian75, -jem-, I9606, Dank, Izno, RexxS,
Aklapper, Lydia_Pintscher
1 - 100 of 116 matches
Mail list logo