Please also notice the current plural rule file is 10 years old. See phab:T369469.
User talk:Amire80
Since Google Translate has improved significantly, we can now publish translations with minimal changes. However, we still need to make adjustments of at least 80%. Is it possible to reduce this percentage?
Please ask on Talk:CX. That's a much better place for such questions.
Hi, Amire80! I'm trying to add a Brazilian Sign Language (bzs) option to Wikidata, in order to add labels, descriptions and aliases of items in that language. After some research, it seems to me that it has something to do with this "Universal Language Selector", but I can't find where and how to request a language addition. Brazilian Sign Language has a page on TranslateWiki and many Wikidata lexemes and it uses the exact same script as American Sign Language (ase), which is already supported by Wikidata (people can select it at the top of the Wikidata pages). Can you give me some orientation on this matter?
I actually don't think that the Universal Language Selector extension is involved in it very much. Moreover, Brazilian Sign Language (bzs) is already included in that extension.
The best help page for your case is probably d:Help:Monolingual text languages.
Oh, ok. I'll do something on Phabricator then. Thank you!
Hey friend, I've reached out to IKhitron first with some translation request, and he recommended to ask you for a review. Would you be able to help out?
Thanks for the request. I'm still dealing with the aftermath of a big move to a new country so my schedule is a bit erratic, but I'll try to find some time.
Reading/Web/Accessibility for reading/Community prototype testing - done. It was mostly good, but I've made some corrections.
 |
The Translator Barnstar |
| Thank you so much for your contributions to various extension repositories! Osnard (talk) 13:28, 13 July 2023 (UTC) |
Thank you, I'm happy to help :)
Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:17, 4 January 2022 (UTC)
אני מקוה שאני פונה לאיש הנכון.
לפי מה שהבנתי הינך עוסק הרבה בתרגום ההודעות כאן.
אשמח לדעת האם קיים עותק מתורגם של הקובץ הזה לעברית לפי הבדיקה שלי בויקיפדיה העברית זה מחזיר את השפות בתרגום לעברית. אשמח לעזרתך. תודה וערב טוב.
שלום,
אלו לא הודעות, אלא שמות של שפות שכתובים בשפות עצמן. תרגומים של שמות שפות לעברית (ולשפות אחרות) אפשר למצוא באתר הבא:
הוא קצת קשה לניווט, ויש שם לא מעט טעויות (אפשר לתקן אותן, אבל התהליך קצת מעיק), אבל לא נראה לי שתמצא מקור מקיף יותר מזה.
בוקר טוב לך ותודה על המענה המהיר.
כונתי כנראה לא הובהרה מספיק. הקובץ שקישרתי אליו אחראי למיטב הבנתי על הצורה שבה המערכת מפענחת את השפות. ראה לדוגמה כאן את קטגוריית הציטוט האדומה (norwegian), לעומת הערך המקביל כאן שתוכנו שווה אבל קטגוריית הציטוט היא בעברית (נורבגית). כשביצעתי תרגומים בקובץ הנ"ל זה שינה את זה לצורה הנכונה (בשפות אחרות זה עבד לי (אנגלית לדוגמה) השפה הספיציפית הזו לא הצלחתי למצוא בקובץ) בגלל זה שאלתי אולי אתה יודע היכן נמצא הקובץ הספיציפי הזה שויקיפדיה העברית משתמשת בו.
בתודה מראש. והמשך יום נעים.
אולי אם יתקינו במכלול את ההרחבה CLDR, זה יעזור.
w:Template:Infobox_book/wikidata, wikidata:Wikidata-driven Wikimedia template, wikidata:User talk:ElanHR/Proposals/Schema for describing templates and their fields and Wikidata:Sister projects
As you say there, the code has to be copied from one wiki to another. To resolve this, a common templates repository is needed.
The common repository is Wikidata. It must be taken as a task in Wikidata.
No, it isn't. It may be a repository for metadata about parameters, but not for the code of the template itself. It's not possible to transclude a template stored in Wikidata into the Spanish Wikipedia or into any other wiki.
So we need a CodeSister site to store the templates itself and take the metadata about parameters for TemplateData in Wikidata. It would be donde the first step: store medata parameters for TemplateData in Wikidata.
An user answered me:
SSastry (WMF) (talkcontribs)
The current wikitext model requires the processed template output (= wikitext) to be merged into the top-level page before the output of the full page is converted to HTML. This is the preprocessing model where a transclusion ({{some-tpl|..args..}}) is evaluated. This preprocessing will fetch other templates where necessary, and so on recursively. I should go look at the code to be sure, but in the current model, every one of these template fetches will be resolved to a target. And, so if template target resolution goes through a global template repository, then it is likely every recursively referenced template will be impacted by that. An alternative model of course is to change the code so that during template preprocessing, all template references resolve on the local wiki where the top-level template target resolves to.
<tangent>Parsoid is eventually trying to get to a model where a transclusion is processed independent of everything on the page and so the output of the transclusion is always HTML / DOM (or if we are able to arrive at typed templates, then it will be some typed value, with the default being HTML/DOM always). In addition, we are trying to get to a place where Parsoid doesn't care what component generated it as long as the types match up. So, both the above preprocessing systems would be compatible with Parsoid. And, at some level, extension are no different than templates in that regard. Everything produces a typed value. So, you can build whatever transclusion system you want as long as you adhere to the type contract. Getting to this point is a bit slow since we are still trying to get to Parsoid being the only wikitext engine.
For example, Scribunto could be considered to be a different templating model from the native wikitext templating model. They look the same on the surface because editors have adopted a mechanism where the module #invoke calls are hidden behind a typical wikitext transclusion.
So, from the ideal Parsoid POV, the qn. of global templates vs local templates or some-other-form-of-templates is an implementation decision of the implementor and they can all coexist as long as they can be appropriately namespaced / disambiguated. But, of course from a product POV, wikis might choose to pick a single mechanism.</tangent>
Hope that helps.
Hello, thank you for your interesting remark on crosswiki templates. I have never understood why langwikis (especially enwiki) don't like it international and prefer staying insidewiki only. Just see the mess about covid data : each wikis has its table, its data, so you would have to edit xxx to show same data among wikis... I edited this template https://fr.wikipedia.org/wiki/Mod%C3%A8le:A%C3%A9roport-Statistiques Someone didn't like my using template LangSwitch on enwiki. So perhaps https://www.mediawiki.org/wiki/Template:Translatable_template would be a better solution to store translation of templates but is it accepted on enwiki and how to implement its use ?
I do agree that COVID data sharing across languages works extremely badly, and that it's indeed one of the best examples of the need for better technology for sharing templates, tools, and data across wikis. Unfortunately, I don't expect your suggestion to be easily accepted by the community with the current state of technology, and that's why I am promoting the idea of creating a Global templates repository. This will take the sharing of tools and data across wikis to the next level, allowing things that the communities want to be local to remain local, and to easily share the things that people want to share. It won't happen tomorrow, and it will take a long time to get this implemented, but the recognition that this is necessary is growing :)
Your comments would be very welcome on Global templates/Discuss, as well as on the talk pages of Global templates/Proposed specification, short version and Global templates/Proposed specification.
In fact, the very people opposing my use of LangSwitch is the same opposing your idea...
Hello there, I think I've succeeded in developing the template about airport patronages cross wikis, thanks to the I18n templates. However, I really wonder how to translate documentation, such this way Wikidata ? Perhaps you'd have a way to enabling translation tool somewhere ?
I cannot give you a very good solution right now, but maybe the Translatable modules project, which is in development now, will be useful in a few months.
Where is the template itself?
I was trying to help translate into French that one https://ru.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:WE-Framework
One of the difficulties of the airport patronage documentation is that for instance nederlands template documentation has to be inside the very template (so that if you update copy-paste the original code, the nl documentation would disappear again). eg there nl:Sjabloon:Luchthaven-Statistieken
Yeah, that's the difficulty. There's currently no unified framework to do this. It has to be developed.
Hmmm..... Just have a look at that discussion ... https://nl.wikipedia.org/wiki/Help:Helpdesk#Dokumentatie_sjabloon
Oh, that's an interesting link! Give me some time to go through it properly.