Jump to content

Translating talk:OpenStreetMap

From translatewiki.net
This discussion page previously used LiquidThreads. You can see and continue those discussions on the LiquidThreads archive page (all archives).

About Osm:Site.copyright.legal babble.contributors nl and/es

This website does not longer exist. Should it be still referenced from OSM?

The same question as in Translating_talk:OpenStreetMap#About_Osm:Site.copyright.legal_babble.contributors_nl_credit_html/el. maro21 (talk) 16:55, 20 December 2024 (UTC)Reply

This link points to the old forum? should the link redirect to Communities?

Id. could fit any table and most (I think all) people in Spanish can understand it. However, this is not a Spanish word; it should be "identificador". What should be used?

What is "low-tech field maps" ?

What is this fund?

Does this point to the old forum? or Communities?

The old forum or the new Communities?

About Osm:Site.help.welcomemat.description/es

I don't understand the original sentence in English.

Which part exactly? maro21 (talk) 00:34, 18 December 2024 (UTC)Reply

Spanish words

These are the words I used in Spanish for these English terms:

* “” / « »

* Authentication / Autentificación

* Block / Bloquear

* Click / Clic

* Commented / Comentada

* Diary / Diario

* Delete / Eliminado

* Fix / Corregir

* Issue / Incidencia

* Language / Idioma

* Link / Enlace

* Local Chapter / Capítulo Local

* Location / Ubicación

* Mapper / Mapeador

* Parking / Estacionamiento

* Policy / Normativa

* Redaction / Censura

* Report / Denuncia

* Retrieve / Obtener

* Submitted / Creada (Para las notas)

* Token / Token

* Trace / Traza

* Update / Actualizar

* Way / Vía

* Zoom / Acercar

La forma verbal para referirse al usuario es "tuteando".

Angoca (talk) 06:14, 12 August 2023 (UTC)Reply

Osm:Site.welcome.whats on the map.doesnt/tr

Osm:Site.welcome.whats on the map.doesnt/en
The expression "doesn't" can be easily translated into other languages, but it is not suitable for Turkish, which is an agglutinative language. Therefore, it is very difficult to translate the use of this expression alone. I translated it as "none" (tr. "yok") for now, but it's still not appropriate. Hedda (talk) 17:13, 8 September 2023 (UTC)Reply

Reported https://github.com/openstreetmap/openstreetmap-website/issues/5432. maro21 (talk) 19:40, 20 December 2024 (UTC)Reply

About Osm:Javascripts.map.base.tracestracktop topo/es

Where does this string appear in the OSM website?

It's a layer name, so in the layers. maro21 (talk) 00:26, 18 December 2024 (UTC)Reply

This message appear, before registration (for registration) or in general (login OR registration)?

About Osm:Site.copyright.legal babble.contributors nl credit html/el

The website doesn't exist anymore, and looks like it has been rebranded to GeoJunxion (based on OSM wiki)--Jimkats (talk) 00:44, 28 November 2023 (UTC)Reply

This has been reported in upstream: https://github.com/openstreetmap/openstreetmap-website/issues/3998 Nike (talk) 07:13, 28 November 2023 (UTC)Reply

This user is a importer

What is importer for OSM? Hedda (talk) 16:35, 3 December 2023 (UTC)Reply

I'm not entirely sure, as it isn't properly documented as term, yet (it's pretty new addition in the website), but I think it refers to an account that is designated for importing data into OSM. Similar to a bot account. Jimkats (talk) 18:06, 3 December 2023 (UTC)Reply

About Osm:Users.new.email help.html/en

I think this should be in future tense, because it is the explanation about what OSM will do with the email address.

There is "Your address is not displayed publicly, see our %{privacy_policy_link} for more information.". What do you want to change? maro21 (talk) 16:57, 20 December 2024 (UTC)Reply

About Osm:Site.key.table.entry.reservoir/ja

溜池か貯水池か。 これめちゃくちゃ難しいですね。日本では前近代からのものを溜池と呼び、近現代の工法によるものを貯水池と呼び分けている印象ですが、外国語の人はそんなこと知ったこっちゃないから困りますね。どうしたらいいんだろう? --Aphaia (talk) 15:45, 3 April 2024 (UTC)Reply

Please use Portal talk:Ja for Japanese language discussions. Nike (talk) 19:47, 3 April 2024 (UTC)Reply

Accessibility issue: Osm:Confirmations.confirm.click here/en, Osm:Confirmations.confirm.resend html/en

The current message text is:

For accessibility, “click here” should never be a link text, because the link text should always describe the link. A more accessible version of these messages would be:

Rationale from the W3C: Many blind people who use screen readers call up a dialog box that has a list of links from the page. They use this list of links to decide where they will go. But if many of the links in that list simply say "click here" or "more" they will be unable to use this feature in their screen reader, which is a core navigation strategy. That's why it's a failure of 2.4.9 to not provide any way of allowing them to know the destination from the link text alone. It is also true for people who tab through links. If all they hear as they tab through the document is "click here, click here, click here etc." they will become confused.

Reported https://github.com/openstreetmap/openstreetmap-website/issues/5431. maro21 (talk) 19:28, 20 December 2024 (UTC)Reply
This has been fixed. maro21 (talk) 22:28, 1 January 2025 (UTC)Reply

About Osm:Notes.index.all/pt

Where is this used? It's important to know its genre.

Oh, nevermind. I noticed it's related to notes. --AntMadeira (talk) 18:55, 3 December 2024 (UTC)Reply
I added documentation before your message. It's on the right side. maro21 (talk) 00:22, 18 December 2024 (UTC)Reply

About Osm:Site.help.welcomemat.description/es 2

Is the first part really a question? --Angoca 14:38, 21 December 2024 (UTC)Reply

You can decide if it should be a question in Spanish. You can translate it in other words. The sentece is used on https://www.openstreetmap.org/help?locale=en maro21 (talk) 18:36, 21 December 2024 (UTC)Reply
Finally, I understand the sense of the question. Would it be better something like "With an organization making plans to switch to/integrate/involve in OpenStreetMap?". English is not my first language, therefore I leave my comment here that can be ignored; probably it is understandable in English.
BTW, organisation with S in British English. Angoca (talk) 00:46, 3 January 2025 (UTC)Reply

About Osm:Application.share.mastodon.title/es

It should be: Share via Mastodon, as in the other options. Not "Share on Mastodon".

Could you exaplain why? Email, Bluesky, Facebook and Linkedin have via
Mastodon, Telegram and X have have on. maro21 (talk) 23:48, 23 December 2024 (UTC)Reply
Ok, I see there are two groups. What is the reason to have different way to name them? Just to adapt the translation to the same meaning. Angoca (talk) 00:15, 3 January 2025 (UTC)Reply
I'm not a native English speaker and I don't use these portals, maybe there is a difference. But the prepositions don't have to be the same in other languages. Translate so that it's correct and sounds natural in your language. maro21 (talk) 15:45, 3 January 2025 (UTC)Reply

About Osm:Messages.muted inboxes.show.title/es

Why the capital m on both words? This is similar and it does not have capital on the second word: Osm:Messages.mailboxes.heading.muted messages/es

This is one of styles in English - capitalizing every word, treating it as a title. maro21 (talk) 18:58, 3 January 2025 (UTC)Reply

About Osm:Site.any questions.paragraph 1 html/es

organiSation (with s)

en is American English, British English messages are under en-gb. maro21 (talk) 19:00, 3 January 2025 (UTC)Reply
To be precise: en should be American English but currently it's a mix of British, American and other [1] maro21 (talk) 23:41, 7 March 2025 (UTC)Reply

About Osm:Site.help.welcomemat.title/es

organiSation (with s)

en is American English, British English messages are under en-gb. maro21 (talk) 19:00, 3 January 2025 (UTC)Reply
To be precise: en should be American English but currently it's a mix of British, American and other [2] maro21 (talk) 23:41, 7 March 2025 (UTC)Reply

About Osm:Site.help.switch2osm.description/es

According to the discussion on "Osm:Site.help.welcomemat.title/es", this is American English, and it should be written organization, with z.

en should be American English but currently it's a mix of British, American and other [3] maro21 (talk) 23:41, 7 March 2025 (UTC)Reply

About Osm:Browse.version/en

The original English string "Version" should also contain the " #<%version_number>" placeholder as some languages translate the # sign and other strings also contain it translatable. Aceman444 (talk) 22:59, 4 March 2025 (UTC)Reply

I'm afraid that OSM website developers don't read this thread. You can report it to GitHub: https://github.com/openstreetmap/openstreetmap-website/issues maro21 (talk) 17:00, 5 March 2025 (UTC)Reply

About Osm:User blocks.helper.short.time in future title/en

This string is used in the user blocks list in the "End" column, which is in the future. The %{time_relative} placeholder in this string however filled using the strings like "Datetime.distance in words ago.x days" which are for times in the past (notice the 'ago' word). In some languages these strings take different forms depending on future/past meaning, especially when prefixed with the 'in ' word as in the string "User blocks.helper.short.time in future title". This needs to be reworked to allow different translation for the different contexts. --Aceman444 (talk) 23:25, 4 March 2025 (UTC)Reply

I don't understand. Could you give examples in your language? What is now and what should be. The "end" column is not always in the future - it depends if the block has ended or will end. maro21 (talk) 17:04, 5 March 2025 (UTC)Reply
When the "end" column shows time in the past, the string is correct.
I mean the %{time_relative} placeholder is filled with the string "in %{days}" when in future, and "%{days} ago" when in the past. Thus there are 2 different contexts, in which the same string %{days} (string code 'Datetime.distance in words ago.x days') is used. In my language there should be different forms for the word 'days', but this is not possible as there only exists 1 string 'Datetime.distance in words ago.x days'. I propose to add another string like 'Datetime.distance in words in future.x days' which would contain the future for this case and it should be used in %{time_relative} when showing a time in future.
The difference in my language looks like "5 days ago"="pred 5 dnami" and "in 5 days"="o 5 dni". Aceman444 (talk) 22:29, 6 March 2025 (UTC)Reply
Did you check on https://www.openstreetmap.org/user_blocks that it doesn't work for Slovak? In Polish the syntax is the same and it works. %{time_relative} is taken from [4] {{PLURAL|one=%{count} deň|few=%{count} dni|many=%{count} dní|%{count} dní}} - could check if this will work with this? maro21 (talk) 20:11, 7 March 2025 (UTC)Reply
Yes, I have checked the pages where the string is used. On that user_blocks page it is wrong.
The 'in' comes from the string 'Osm:User blocks.helper.short.time in future title' and then just %{time_relative} is appended to it, but this one is taken from the wrong strings (the 'ago' string variants). Aceman444 (talk) 18:01, 8 March 2025 (UTC)Reply
Hmm, it's strange because it looks like these strings for the future date don't come from Translatewiki. The translations for Polish are correct, but they're not on Translatewiki. I will report it. maro21 (talk) 20:18, 7 March 2025 (UTC)Reply
Check please if this date here is correct or incorrect "Končí o takmer 10 rokmi" https://www.openstreetmap.org/user_blocks/17361?locale=sk maro21 (talk) 21:05, 7 March 2025 (UTC)Reply
No, this string is incorrect in Slovak. Aceman444 (talk) 17:59, 8 March 2025 (UTC)Reply
It turned out that the strings for future dates don't come from Translatewiki, but from https://github.com/search?q=repo%3Asvenfuchs%2Frails-i18n%20takmer&type=code
Check if a correction there will get the job done. maro21 (talk) 20:52, 8 March 2025 (UTC)Reply
How did you find out? If this was the case, then where are the strings like 'Osm:Datetime.distance in words ago.x days' used? It seems the OSM page duplicates these strings from Rails. But they also contain the word 'ago', which the Rails versions do not. And the 'ago' word is displayed on the OSM website, so I am not sure the Rails versions are actually used. But if they were, they would need invasive changes to fix the problem, which I cannot do. They would be easier done in the OSM strings, but of course would need changes too to the OSM website code and publishing the 'in the future' versions of all those strings (days/months/years, etc.).
Of course, if Rails only has the "distance_in_words" variant of the time strings, and does not distinguish between the 'in the past' and 'in the future' contexts and word forms, then it has this same problem in all projects using it. Or the projects override those strings and ignore them, or somehow twist their phrases weirdly so that the existing Rails strings fit into them. I will think if this is possible to do in the existing phrases OSM offers. Aceman444 (talk) 13:07, 9 March 2025 (UTC)Reply