Hello,
if you can translate to any of the following languages:
ar as be cs cy de es ka km kn ko ky mn ne nn qu ro si sr to ur uz yo yue
zh zu
you can help by joining the current CLDR localisation round (see below
for some statistics). If you added translations in the past, simply
logging in will add them to this round as well. If you do not have an
account, see:
https://translatewiki.net/wiki/CLDR
Best,
Federico
-------- Messaggio Inoltrato --------
Oggetto: CLDR Survey Tool announcement: 2 weeks until vetting starts
Data: Wed, 28 May 2025 04:00:07 +0000 (UTC)
Mittente: CLDR SurveyTool
This message is being sent to you on behalf of Annemarie Apple (Google)"
(Google) - user #2303 From: Annemarie Apple (Google)
To: Everyone
Organization(s): All
Locale(s): ar as az be cs cy de es ka km kn ko kok ky mn ne nn qu ro si
sr to ur uz yo yue zh zu
Reminder, we currently only have 2 weeks remaining of submission before
starting vetting. It looks like your locale has more than 150 items in
either missing or provisional.
Please prioritize missing and provisional items since you will not be
able to add new data items once we start the vetting period on June
11th. Thank you!
Current overall progress in case it is helpful:
https://docs.google.com/spreadsheets/d/1515Ntysw61Rhy1ybv-NdUr81wXXQuzLElsC…
Do not reply to this message, instead please go to the Survey Tool.
https://st.unicode.org
Hello,
As the title suggested, I would like to volunteer myself to become a member
of the language support team for my native language “Tausug” [tsg].
My user ID is Zetareyy.
Thank you,
Your regards,
Zetareyy
The new round of translation submission is about to start in the CLDR
survey tool. If the email from the survey tool went to spam, please try
and add the sender email address to your webmail address book.
You can already find suggestions for things to translate in the
dashboard, report and forum. I've added a couple screenshots in:
https://translatewiki.net/wiki/CLDR#Finding_other_things_to_do
We got some new translators at the hackathon but we still need
translations for some priority items in the following languages:
Uzbek, Asturian, Fula, Tongan, Hausa, Konkani, Yoruba, Zulu
If you know someone who can help, please direct them to the CLDR page above.
Best,
Federico
-------- Messaggio Inoltrato --------
Oggetto: CLDR SurveyTool message from admin
Data: Fri, 10 May 2024 23:58:23 +0000 (UTC)
Mittente: CLDR SurveyTool
This message is being sent to you on behalf of admin" <admin@> (Survey
Tool) - user #1 SurveyTool Message ---
Submission is planned to start on May 15. Before that date you should
read the new contents at https://cldr.unicode.org/translation and make
sure you can log in.
--------
Survey Tool: https://st.unicode.org/cldr-apps
----------
This email was generated automatically as part of the CLDR survey process
http://www.unicode.org/cldr
If you have any questions about it,
please contact your organization's CLDR Technical Committee member,
or: surveytool at unicode.org
TO UNSUBSCRIBE: You must permanently disable your account to stop
receiving these emails. In Survey Tool, log in and choose Lock My
Account from the main menu. You may request a password reset if needed.
I was pinged on a Unicode repository
https://github.com/unicode-org/unilex/issues/10#issuecomment-1872496490
asking for a WMF perspective on license compatibility. I gave my
personal answer but I'm notifying the list in case someone does want to
answer in name of WMF as Unicode member/user. (Also cc'ing Hugo, Stephen
and Richard as I mentioned them.)
As my answer turned out to be rather long I'll copy it here for the
archives' benefit.
----
@srl295 Thanks for the ping. I wasn't aware of this issue but I'll give
a quick reply. I've only read the discussion above and the README. I
can't speak for WMF, let alone Unicode (I don't remember whether WMF is
even a member now), but I can tell about the usage of Unicode components
in MediaWiki software and Wikimedia wikis.
The issue description highlights some confusion on the licensing of this
project. Meanwhile the LICENSE has been updated to the Unicode license
v3 which has been recently approved by OSI on 2023-11-17:
https://opensource.org/license/unicode-license-v3/ . So there's no doubt
this repository is opensource. Maybe this can be explicitly mentioned on
the README, as not everyone is able to recognize the license text as its
own OSI-approved Unicode v3 license.
MediaWiki can and does use software under Unicode license all the time,
for example in the [CLDR
extension](https://www.mediawiki.org/wiki/Extension:CLDR), which is
primarily GPLv2, under the understanding that the CLDR data inside was
under a BSD-like license. (Apertium linguistic data is also
[usually](https://wiki.apertium.org/wiki/Contributing_to_an_existing_pair#Co…
under GPL.) As long as Unilex can be used in GPL software, there are
probably ways it can benefit all Wikimedia wikis through MediaWiki.
However @hugolpz seems most concerned about usage in Wikidata and other
Wikimedia wikis _content_. From the README it sounds like this
repository mostly wants to collect uncopyrightable factual information.
In the EU, there might still be problems with database rights. A general
opinion from the WMF on how to handle these is at
https://meta.wikimedia.org/wiki/Wikilegal/Database_Rights . In short,
it's complicated, and it's easier to incorporate a dataset into Wikidata
when it's already under CC-0. If there's some doubt on whether the data/
directory here as a whole is a dataset
If you want to cooperate with Wikidata lexemes in the future, it's worth
considering how to make it easier. As for LinguaLibre, as far I
understand it helps produce some recording which might be considered
copyrightable, and it wants its outputs to be available under CC BY-SA,
so it benefits from its sources being as permissive as possible.
Finally, I see that [many
files](https://github.com/search?q=repo%3Aunicode-org%2Funilex+SPDX-License…
carry a `SPDX-License-Identifier: Unicode-DFS-2016` header, which makes
it easier to follow the [Reuse](https://reuse.software/) guidelines.
Note Richard Fontana's suggestion for trivial files at
https://github.com/fsfe/reuse-docs/issues/62#issuecomment-1200305896
(and my personal opinion below it).
So in conclusion my personal suggestions are:
* mark the repository even more clearly as being under OSI-approved
license Unicode v3;
* keep marking the individual files copyright status, and consider even
more permissive licenses like MIT-0 (or 0BSD or CC-0) when adding
uncopyrightable files;
* keep in mind possible copyright needs for Wikidata and Wikimedia
Commons in the future, and ask help from WMF legal (legal(a)wikimedia.org)
on any possible/needed clarifications for CC-0 and CC BY-SA
compatibility (fyi @slaporte).
----
Cheers,
Federico