Translating talk:OpenStreetMap

This message cannot be translated. It keeps complaining about a syntax error due to the presence of the "zero" clause even though that is in the original message.

It might be because they are in the "wrong" order.

No, the order is completely correct (and chaing it would have no effect).

This is a known current bug of TWN, which no loger accepts the "zero" plural option for any language, because it restricts these options to only the numbered options for (default) plural rules of the language. It was valids in the past, but a change in TWN code caused this new caveat under a false assumption that extra values, than just option 1 for singular, and the last (implicitly numbered) option for default plural would be invalid.

But many messages in Mediawiki define specific values (such as "zero=", "one=", "99+=", or other numeric values like "10=", "100="); such cases occur as well in English, but are more frequent in languages that need additional context-specific rules than just the basic default rules).

Even languages that normally don't mark the grammatical plural have specific words or sentence forms in some cases (e.g. expressing zero by using a negated form or changing to another adjective or adding some extra particles). If we don't use these options, the only redering using digits only looks much less familiar and less friendly.

IMHO it's not to TWN to decide the maximum of forms that can be set with plurals (notably not for MediaWiki's {{PLURAL: value | alternate forms... | default form }}, but as well for plural rules used in Python, Java, Ruby or other languages, and i18n libraries such as ICU using CLDR data: if we specify "too many", these extra forms may be left unused by the target application but won't break the message: it must just provide at least the last default form; other forms will be used conditionally but using variable rules.

So TWN may just display a warning, allowing to reconfirm when saving again without other changes (the warning may just say that extra forms may be useless, and should as well send a warning if there are fewer forms than expected (notably in Slavic and Celtic languages or in Arabic, that have more than 2 forms)

What kind of crossing does this message refer to? A place to cross the road (like a pelican crossing) or a place where two roads cross (like an intersection)?

How can I add more plural variants? I can only write "1 point", "2 points", "few points" and "many points", however my language has specific variants for "3" and "4 points", how can I resolve this problem?

How can I add more plural variants? I can only write "1 point", "2 points", "few points" and "many points", however my language has specific variants for "3" and "4 points", how can I resolve this problem?

N'hallan ket treiñ ar frazenn-mañ. Klasket 'm eus treiñ anezhi met, n'eus forzh penaos, ne laosker ket ac'hanon da dreiñ anezhi ha n'ouzon ket perak?? Trechalet on.

What does mean "Locality"? Can you give an explanatory explanation? --Hedda (talk) 16:14, 17 June 2021 (UTC)

Locality is a tag used to name a place which does not have other distinct features than the name itself, see the OSM wiki for tag=locality.

The Potlatch 2 repository has been archived because of the imminent sunsetting of Flash Player.

There's now a successor, version 3, which runs as a desktop application and is mostly the same codebase: http://github.com/systemed/potlatch3

In due course I'd very much like to continue taking translations from translatewiki for this, but currently there's no build system configured to do this. I'd anticipate it'll be ready in a few weeks. You may want to consider pausing any translation pushes for now (they'll presumably be rejected by github anyway because the repo is archived).

It is not clear to which element the word "closed" refers to, and if this element is an Hebrew masculine, where "נסגר" would be applicable, or feminine object, where "נסגרה" would be applicable. Please advise.

For example, a node, a comment and a changeset would be feminine while a way and a relation would be masculine

Should the attribution text be translated at all? A global recognisable attribution might be better and translations could potentially lead to interpretation issues in different languages and under varying jurisdictions. For Danish (dansk) I've done that and also previously with the "(C) OpenStreetMap contributors" text but now I'm a bit doubtful whether it might be better if left in English. I see German (Deutsch) has taken the same approach of translating it.

Also, why the term shift from "map tile" in text to "base map" in attribution? Do we think people trying to understand copyright attribution relate more to technical tiles than the people seeing the final map attribution? Maybe the text could use "base map" for every mention of the rendered map? Overall I think the distinction between the terms "tile" and "data" is not very clear for the average data consumer trying to do the right thing. Maybe the whole page would be more comprehensible if it clearly divided usage and attribution requirements into "data users" ((C) OSM contributors @ ODbL) and "base map/rendered map/tiles users" (((C) OSM Foundation @ ?).

What are Changesets? What are they for? Does anyone know?

Short: a set of changes to existing objects or new objects to add to the OSM database

Long:

An OSM user performs changes to OSM data using software like JOSM and iD who utilises the OSM API to create and communicate to the OSM servers the wanted changes in blocks called changesets. Changesets associates otherwise unrelated changes to objects into a logical group with common metadata (user, date, changelog, software used, etc.) to avoid storing this data redundantly for each object and to ease administration (fx. a changeset can be reverted if it is determined that it contains unwanted edits).

Each changeset is given a unique reference number by the API, fx. my latest changeset is #83475681.

Long and technical: see OSM wiki

If you are unfamiliar with OSM and OSM terminology in your language, it might be a good idea to look at the terminology used in other related software.

For "changeset", it seems that both iD and JOSM uses the term "Änderungssatz", which also the webpage (this project) does;

• iD: https://github.com/openstreetmap/iD/blob/release/dist/locales/de.json#L636
• JOSM: https://translations.launchpad.net/josm/trunk/+pots/josm/de/+translate?batch=10&show=all&search=changeset

Is this a verb or a noun, would be great to know!

What does this mean, in which context is this string being used, it makes neither English nor in German any sense to me.

Most strings under Osm:Auth.providers shouldn't be up for translation. Brand names like Facebook, Google and GitHub are deliberately not localised. Wikipedia is rendered differently in other languages but the others should be removed. Also, Windows Live no longer exists, it's now called Outlook for that type of account.

Should be "ID"

So the original English string is incorrect too?

May be the (optional) full capitalization of "ID" is avoided here in OSM to avoid the confusion with "iD" (the core map editor on OSM website), whose name may also show as "ID" as a page title with the leading capital.

---

It's unfortunate that OSM chose the name "iD" for its map editor on the web, when the term "id" or "ID" also has many uses for something else in OSM (notably all object ID's: nodes, ways, relations, changesets, users, web sessions, pages/files on its wiki, bugsin its bugtracker...) and needlessly created that confusion, without really promoting the map editor with a distinct name (like Mapid, combining "Map" and "Rapid"). And for accessibility with aural contents, "id", "ID" or "iD" are not different at all in all languages (there's all spelled as two letters and no one will vocally spell the lettercase distinction).

Anyway "ID" or "id" are equivalent in English, but if this is an acronym or abbreviation for "identifier", the capitalization rules are not necessariuly allcaps in all languages. In Latin "id" (or "Id") is also an abbreviation of "idem" (not always followed by an abbreviation dot, but by a full stop), and it is also a common code for the Indonesian language, or for the Indonesian country.

OK, "Potlatch" was a poorname, but why no better name than "iD" was proposed to votes for the OSM map webeditor (could have been "osmed" or "wemap")

Capitalization rules in English are very confusive and often incoherent, they just add to ambiguities in a language that also intriduced many ampbiguities between verbs and nouns, allowing too many interpretations, And here it also adds difficutlies for full-text searches with significant results really related to the editor

Why this complex code in translation sources:

<span>&copy;</span>

The span tag adds nothing at all, and all can be a single UTF-8 character (note that in English it is glued to what follows without any (non-breaking)space, this is not appropriate to all languages:

©

per a que serveixen les instruccions que apareixen al voltant d'Openstreetmap?

Should be "ID"

Actions are performed, not accessed.

Where are the values of %{ago} variable stored? I want to correct Persian translation of them.

I there anybody here know about this?

Solved