User talk:Siebrand

Hoi,

Het viel me op dat je "label" als vertaling van "tag" hebt toegevoegd aan de Nederlandse woordenlijst.

Waarom zouden we een Engels woord vertalen met een ander Engels woord terwijl ze allebei in het Nederlands zijn ingeburgerd? Zowel "tag" als "label" staan gewoon in de Woordenlijst Nederlandse Taal.

Bovendien is een tag niet hetzelfde als een label. De betekenissen overlappen misschien, maar niemand spreekt bijvoorbeeld van "HTML-labels" voor iets als <br/>. Dat zijn toch echt "HTML-tags". ("Labels" in HTML hebben te maken met formulieren.)

Volgens mij is het beter om ze gewoon allebei onvertaald te laten om spraakverwarring te voorkomen. Wat denk jij ervan?

Ik heb de voorkeur voor label.

Hoi, zou je hierop even met je mening willen reageren? M.v.g.,

Dear Siebrand,

I noticed the following: $html_inbox_show_alert , $html_inbox_folder_label and $html_collect_label are lacking translation on NOCC pt-br.

Att, Felipe

I see you have changed several OSM translations to use capital letters for the abbreviation "GPS". "GPS" used to be written with capital letters in Dutch. Nowadays, it is usually written "gps" without capital letters (or dots). In English, it is still written "GPS" with capital letters. I would like to keep this consistent between the Dutch translations. https://nl.wikipedia.org/wiki/Global_positioning_system

https://translatewiki.net/w/i.php?title=Osm:Traces.index.my_gps_traces/nl Also, for this translation, all other translations use "traject(en)" instead of "trace(s)". Another, more common translation is "track(s)" (used on the wiki and forum).

Hello Siebrand, what does "2010-19" mean here? Maro21 (talk) 00:37, 9 September 2019 (UTC)

Hi Maro21, I'm pretty sure that means 2010–2019. It's relatively common for these copyright notices to be updated to include the current year.

In my opinion, the OSM developers should not even use such abbreviated notation, which is clearly ambiguous or at least not abvious (compare "2000-09" and "2000-19", the first at least is a standard notation for month numbers in year , but what is month 19 in year 2000?). Looks like they were lazy when typing it, assuming that it was clear for them, but everyone wonders how to interpret it, or could incorrectly infer this means "2000-1-9" i.e. with a typo, or that there was a missing month, or that this meant the 19th day of the year, so on 19 January 2000).

A copyright statement is very formal and must be extremely clear. Such notation is never used in CLDR localisations in English and not found in any formal/legal documents. Anyway, all translations should absolutely not reuse this non -standard abbrevation and translate (transliterate, transnumerate) as if it was "2010–2019". This is what almost all translations have done already (correctly, e.g. Osm:Site.copyright.legal babble.contributors gb html/fr). But the official OSM website is still lagging there since long in its very important copyright page that every other site must link to.

Why don't they fix this non-sense that does not even have any meaning in UK whose laws strongly apply to this copyright notice ? Couldn't it be changed directly here in this wiki (or at least documented in the "/qqq" as long it is not fixed by OSM developers submitting their source pack to be translated here). Not fixing it even in English could have legal consequences, notably if someone claims in a court (and that's defendable) that OSM made a legally invalid copyright statement, and then wants to use and republish/resell OSM data with their own proprietary copyright by discarding/ignoring as well the licence conditions.

If some technical admin at OSM does not care about it, at least we should contact the OSM Foundation to force them to fix it (this is in the interest of the whole OSM community and all valid reusers of OSM data, including in commercial applications, or in organizations which could be threated by legal suites to pay a third party that was the first one to make a valid copyright statement, i.e. with a valid date).

Beste Siebrand,

Zou je willen helpen bij het opschonen van de documentatie voor OpenStreetMap? Het gaat dan vooral om de verwijzing naar de wiki. Ik heb hier een voorbeeld achtergelaten.

Groet,

Daniel

Hi, Siebrand, how are you? I'd like to ask you how can we remove a protection from a page, specifically this one. Because the expression Diklitera teksto is NOT Ido, it's Esperanto! I'm a collaborator in Ido-Wikipedia and also here, and I've noticed this error, but I cannot correct it, because the page is blocked from editing. I don't know if you are an administrator here, but need help from an administrator to remove the block and then to correct it.

Best regards,

Hello! I usually contribute in another project, such as Wikipedia. I don't really understand about technical stuffs in translatewiki. I tried to find someone to ask about, and I found you. So, I found an abuser's (AJBot2) contributing here, he's already global locked there. I want to make block request for him but i dunno how and where. His translations are mostly nonsense. Can you help me for this case? Thanks for your help.

Hi Siebrand,

Do you have any input on this discussion Thread:Support/Special:ContributionScores_does_not_dsiplay_accurate_figures ?

Sorry, not really. There may be caching involved, and it may be that the data model has changed in such a way that it is no longer correctly represented by the extension. I don't think I've ever developed much on the extension, so I recommend creating an issue report in phab:.

Hello Siebrand, can you change message from this to this? I have no editinterface right. Thanks in advance.

For the record the same permission error appears from Special:Translate e.g. at [۱]

You do not have permission to edit this JavaScript page because it may affect all visitors. Permissions for editing of sitewide CSS/JS/JSON files were recently separated from the "editinterface" right. If you do not understand why you are getting this error, see mw:MediaWiki_1.32/interface-admin.

Yes, please change that too. Thanks to @Nemo:.

Hello Siebrand, can we remove all messages from the code language "/ku". Because it seems that these messages have the priority over "/ku-latn". For example, changing this message (MediaWiki:August/ku-latn) has no effect because the kode "ku" (MediaWiki:August/ku) exists.

Hello! I was wondering today what happened with the prize of the 2015 rally. I have seen the project page and discovered that there is a list, but the list has dates from 2015, so I don't know if I'm in time, anyway I added my name because I appear as "Qualified". I hope your response. Regards!

OPEN This issue is open, waiting for action

Hello, Siebrand!

Jen Hammock here, from the Encyclopedia of Life. I’m the project manager at EOL these days, helping Jeremy Rice to keep up with our assorted collaborators. I’m hoping you remember us, and that you can direct me to the right contact if it isn’t you.

We haven’t been very active while we were migrating EOL to her new codebase, but we’re starting to work on internationalization support for the new platform, and were hoping the translatewiki community is still game to contribute some translations. We’ve got better integration now with other multilingual content. We’re leveraging species names from Wikidata, and descriptions from the different language Wikipedias, so we’re hoping to make it a more coherent experience for our non-English visitors.

If translatewiki is interested in working with us, I believe what I need to know is whom to arrange access for and direct to the updated interface text file. Can you advise, or refer me to someone?

Thanks!

Jen

We are certainly interested: translators were asking why we're still translating the old version. (Translations are supposed to be disabled unless they're pushed in active use within a short time.) Is the new code base radically different? If you use some standard i18n library and/or l10n format, things are much easier.

The interface developer tells me: nothing has changed except that the .yml files are now in config/locales instead of config/translations.

Does that help?

Thanks for your patience...

Hallo Siebrand, hast Du Zeit und Lust zu einer Skype-Gesprächsrunde, die per de:WP:WikiStammtisch veröffentlicht wird? Das habe ich im Vorjahr bereits in zwei Episoden gemacht: File:Wikistammtisch-episode-0070-wikimania-2017-review.ogg und File:Wikistammtisch-episode-0068-wikimania-2017.ogg Bitte schreibe mich auf meiner deutschen Benutzerseite an. --Sebastian Wallroth (talk) 08:07, 24 July 2018 (UTC)

Hello.Why does not NOCC appear in Arabic?Thank you

I don't know why Template:Unblock was deleted; a user account could be unblocked.

This appears to be irrelevant here. Please take your beef to where you were blocked.

strong oppose

Hi Siebrand, I've mistakely created it. Please delete it or do what's necessary is to be done. Thanks for your consideration ! Also, delete MediaWiki:Wikibase-otherprojects-Wikimedia Commons/mai

Hello
Dear Siebrand
please give translation rights to user:beyronvan [۱] for bqi inucubator.
best wishes. Mogoeilor (talk) 17:01, 20 January 2018 (UTC)

Hello, sorry for taking your time with this... For some reason the site is using the old interface for me (like this) (probably a bug in Chrome cache). The point is: if I clear the cache I will start using the new interface version, not a problem, but the old interface is best for what I'm doing. So, do you know a way to use the old version by default? Or it's just a crazy bug? Thank you.

The old interface (which is being gradually removed) is controlled by a cookie and you can disable it with an URL parameter ?tux=1 like Special:Translate?tux=1, just like you probably enabled it with a link tux=0.

You guys are awesome! Really thank you.

Why did you revert me?

I didn't like the italics.

But it's a creative work, so it is standard to italicize it in English, as with a book, film, or journal.

Not in translatewiki.net.

I don't see a manual of style. Can you direct me to one?

I'm sorry, but I think this wiki is not for you. Please find a manual of style to apply elsewhere elsewhere. We don't discuss for the purpose of discussing here.