Modify

Opened 3 years ago

Last modified 4 months ago

#14404 new enhancement

Support similar/alternative words when searching for a preset

Reported by: naoliv Owned by: team
Priority: major Milestone:
Component: Core Version:
Keywords: preset search alias i18n Cc:

Description

Could JOSM support some kind of "similar/alternative words" when searching for something in the presets?
For example, people here can call a highway=traffic_signals as "Semáforo", "Sinal de trânsito", "Farol", etc.

If we press F3 and try to search for it, we will be able to locate it using only the current translation (Sinal de trânsito). If somebody searches for "semáforo" they will not find anything.

JOSM:

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-02-21 01:04:28 +0100 (Tue, 21 Feb 2017)
Build-Date:2017-02-21 02:33:46
Revision:11590
Relative:URL: ^/trunk

Identification: JOSM/1.5 (11590 pt_BR) Linux Debian GNU/Linux 9.0 (stretch)
Memory Usage: 1367 MB / 10206 MB (824 MB allocated, but free)
Java version: 1.8.0_121-8u121-b13-3-b13, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1600x900, :0.1 1280x1024
Maximum Screen Size: 1600x1024
Java package: openjdk-8-jre:amd64-8u121-b13-3
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-13
VM arguments: [-Dawt.useSystemAAFontSettings=on]
Dataset consistency test: No problems found

Attachments (0)

Change History (13)

comment:1 Changed 3 years ago by Klumbumbus

Ticket #12830 has been marked as a duplicate of this ticket.

comment:2 Changed 2 years ago by Klumbumbus

Ticket #16375 has been marked as a duplicate of this ticket.

comment:3 Changed 10 months ago by Don-vip

Keywords: preset search alias added
Priority: normalmajor

comment:4 Changed 8 months ago by Klumbumbus

Ticket #18423 has been marked as a duplicate of this ticket.

comment:5 Changed 8 months ago by stoecker

A possibility would be to add a description entry to presets and also search these.

comment:6 Changed 8 months ago by richlv

How does this work currently in some cases then?
For example, If I search for "church", it shows among the entries "Geography/Land use/Graveyard", "Offices/Religion" and "Shops/Other/Gift/Souvenir".

comment:7 Changed 8 months ago by Klumbumbus

They contain the drop down box for key denomination which includes the value church_of_scotland.

comment:8 Changed 8 months ago by richlv

Thanks, got it. I'll collect the suggested matches here so we don't have to look all over the tickets.

  • "gallery" -> shop=art and tourism=museum - those are the suggested tags for things that are often labeled "art galleries".

comment:9 Changed 4 months ago by simon04

Keywords: i18n added

The poor-man's solution would be to write those aliases in parentheses of the preset name, such as <item name="Traffic Signal (aka. semaphore)" ...>

This allows individual languages to add aliases to names which do not have/need an alias in English. And we wouldn't have to adapt the i18n process.

comment:10 in reply to:  9 Changed 4 months ago by Klumbumbus

Replying to simon04:

write those aliases in parentheses of the preset name, such as <item name="Traffic Signal (aka. semaphore)" ...>

Nah, please not.

comment:11 Changed 4 months ago by Don-vip

That would require a lot of strings to become untranslated, I would prefer a rich-man's solution :)

comment:12 Changed 4 months ago by simon04

Those aliases are a bit orthogonal to the standard i18n process:

  • in English aliases might not be needed
  • in the foreign language aliases might not be needed

Thus, we cannot simply add <item name="..." aliases="foo,bar"> and mark aliases for i18n, can we?

comment:13 Changed 4 months ago by stoecker

Actually I think that whole idea makes not much sense. It's much like the HTML keywords. Somebody thought it a great idea, but it never made much sense. If something is so important, that it should be in the preset, then add it as descriptive text. Anything else is so much personal experience that you probably will never find two people agreeing that these keywords are right.

And hidden texts are black magic where nobody will understand why it works.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to naoliv
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.