Skip to content

Update categories.txt (add spanish translations)#7574

Merged
biodranik merged 14 commits intoorganicmaps:masterfrom
muralito:patch-1
Mar 15, 2024
Merged

Update categories.txt (add spanish translations)#7574
biodranik merged 14 commits intoorganicmaps:masterfrom
muralito:patch-1

Conversation

@muralito
Copy link
Copy Markdown
Contributor

Signed-off-by: Muralito muralito@montevideo.com.uy

Signed-off-by: muralito <muralito@users.noreply.github.com>
@Jean-BaptisteC Jean-BaptisteC requested a review from a team March 12, 2024 05:39
Fix typo.

Signed-off-by: muralito <muralito@users.noreply.github.com>
Copy link
Copy Markdown
Member

@biodranik biodranik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! A few minor comments.

hi:4स्वस्थ भोजन की दुकान|4हेल्थ फ़ूड स्टोर
ru:Здоровая еда
tr:Sağlıklı Gıda
es:Alimentos saludables
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's sort this and other translations in the alphabet order if possible. Only en is always at the top.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while adding words i saw that the whole file is out of order in several places, and it complicates the search for an specific language.
do you want to sort them all or just this added line?

IMHO a sort of the whole file is needed, but i prefer not to do it in this PR.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whole file can be sorted later, if no any other PRs are editing the same file.

Copy link
Copy Markdown
Contributor

@patepelo patepelo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the changes seem very positive. I added some suggestions.

pt-BR:Loja de conveniência|4mercadinho|compras
ro:4Magazin mixt|minimarket|magazin
es:Tienda de barrio
es:Tienda de barrio|chino|provisión|almacén|minimercado
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove "chino". It's a popular word, but it's polemic since it's slang meaning "Chinese" as for the immigrants that frequently own the places, as well as the word "paki" for "Pakistani". It shouldn't be here at all. Besides, "chino" is used also for variety shops in other regions of Spain. And last but not less important, when a user wants to search for Chinese food, it would also interfere. I would add instead "Tienda de conveniencia" (spanish wiki), "Colmado"(spanish wiki), "Ultramarinos".

Copy link
Copy Markdown
Contributor Author

@muralito muralito Mar 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, i know it's polemic. We cannot control how the people use the words. In most of the cities of Argentina were i have been, if you look for a shop=convenience you ask to the person near you "¿Donde hay un chino?" ("Where is a "chino"?) you and all other people clearly understand that you are referring to a shop and not a demonym, so why not ask to OM "chino" and get the convenience shops? An app should speak the language of their users, and not viceversa.

Besides that, it's an accepted term by the RAE. See https://dle.rae.es/chino (8. m. coloq. Bazar o supermercado regentado por chinos. Compré el cuaderno en un chino. )

Yes, it will interfere with a chinese food restaurant, but that is because it is another accepted meaing of this word. (RAE 7. m. coloq. Restaurante de comida china. ). Same word refers to both type of elements. There is no way to not interfere. If you decide to show one, you decide to hide the other.

The other terms "Tienda de conveniencia","Colmado","Ultramarinos" are ok for me.

¡Agradezcamos las variantes y el poder de expresion de nuestra lengua! Let us be grateful for the variants and power of expression of our (spanish) language!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support you in making the language as universal as possible, but disagree to include it and any other slang language. I know it's inconvenient as well because sometimes it's hard to find the specific official word for these places, but there are.

If you would start including slang, you could also include "guita" or "plata" for money and that IMO is not appropriate for an app. Besides, it's already important that it interferes with the results for Chinese cuisine.

I won't strongly oppose this particular change. I'd let it be, but it would be positive if more native speakers could give their opinion.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In english there is this one term "slang", but in spanish we also have variants. The semantic of "slang" in english, is not the same as "coloquial" in spanish. "slang" is more llike "jerga". "Coloquial" is more like "informal" or "casual"

I also don't want to start including slang terms (like in "jerga"), but useful "coloquial" terms used by entire populations, to make OM more useful to more people,

I did not include "guita" or "plata" (nor most of the 20 terms with the same "cash" meaning - https://dle.rae.es/guita ) because i didn't see useful. If i need "plata" (money) i search for "cajero" (ATM). If people needing money uses "plata" or "guita" as a search term, i would consider them useful terms and ask for inclusion in the list. Just to improve usability, not for purity of language or being politically correct.

As for the interference with chinese cuisine, we should better discuss in other thread, because OM is not returning any useful results when I search for "cocina china" OM didn't show any of the 6 cuisine=chinese that i have < 20km from me. Same for "cocina mexicana" or any other type of cuisine. I opened an issue for that a few days ago (only was aware of "cocina mexicana" at that time.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support you in making the language as universal as possible, but disagree to include it and any other slang language. I know it's inconvenient as well because sometimes it's hard to find the specific official word for these places, but there are.

The problem is not about finding the specific official word. The problem is that if any es-* user searches for "chino" in OM, and OM didn't show the shop=convenience elements around the user, the app didn't worked as expected. It's not the user which needs to know which specific term we decide to include in OM to get the results, it's OM to try to understand whatever the user is searching for, and try to solve it in the better possible way.

The issue is not about which translation of shop=convenience should OM display to the user when it shows info about a shop=convenience, the user will learn which are these "OM official" terms using the app, but what meaning gives OM to the user input. OM is not forcing or promoting the user to use "chino" or "plata", but if the user put those search terms in the text input box, I think that it is useful that OM understand what the user wants and returns the desired elements.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@patepelo If users use slang to find objects on the map, then these keywords should provide reliable results. Imagine if Google didn't work with really used slang words.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it's not wrong to use slang in general, is just in this case that is polemic as explained for example in this article or this one

But let's suppose racism sensitivity is not a problem here. We encounter a second problem that is ambiguity, with these definitions:

  1. m. coloq. Restaurante de comida china.

--> (coloq. = slang) A restaurant that sells chines food

  1. m. coloq. Bazar o supermercado regentado por chinos. Compré el cuaderno en un chino

. --> (coloq. = slang) A supermarket or a variety store that's attended by Chinese people.

So if you were in Spain and you say let's search for "chino" in the app, a user here would expect to find a variety store. So now you have a search term that isn't too specific.

But as said. I'll let it be and vote abstain. It won't make of big difference.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So then "chino" should also search for variety store. And if the user needs specific results, he always can use more specific search terms.

The polemic discussed in those articles is another issue, because I'm not proposing that OM display an POI amenity=convenience or shop=variety_store as "Chino", OM should display them as "Tienda de barrio" or "Bazar", as it does now, so OM does not promote racism or racist terms in any way.

The problem here is not about racism, nor anti-racism, nor discrimination, nor politics, it is technical, it is about how OM understand users natural language and gives the users the results they need.

BTW, it could be seen the other way, as OM is not displaying these shops in the results when the user searches for them, it can be seen as if OM is avoiding directing customers to these shops and in consequence decreasing their income.

pt-BR:Loja de bebidas|bebidas alcoólicas
ro:Băuturi alcoolice
es:4Licorería|licor
es:4Licorería|licor|vinería
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also add "Bodega"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, please remove "vinería" since it was already used correctly for Winery. So the results are not mixed.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Analicemos mejor antes de intentar mejorar esto entonces (sorry for the spanish but it seems better to discuss this issues)

POIs involucrados al menos de alguna forma:

  1. shop=alcohol
  2. shop=wine
  3. craft=winery

terminos:
a) licorería|licor
b) vinería
c) bodega

Para mi 1) y 2) son muy parecidos, donde se venden bebidas alcoholicas, y 3) seria el lugar de produccion del vino, eso al menos en Cono Sur es "bodega". Si un lugar de produccion de vino, tambien tiene venta al público general de vinos (como suelen tenerlo), o de servicio de restaurant, estos servicios se mapearian por separado, como shop=wine y amenity=restaurant. Quizas los tres elementos tengan el "Bodega X" en su "name" pero son cosas distintas.

¿Algun otro termino que quieras agregar a esas listas? (despues vemos como las vinculamos)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would match different types with one word vineria )

muralito and others added 11 commits March 13, 2024 11:55
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Co-authored-by: Anton <antonwenemoser@gmail.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Signed-off-by: muralito <muralito@users.noreply.github.com>
Copy link
Copy Markdown
Member

@biodranik biodranik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

¡Gracias!

@biodranik biodranik merged commit ec4ba02 into organicmaps:master Mar 15, 2024
@muralito muralito deleted the patch-1 branch March 16, 2024 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants