Page 1 of 1

Client-side Abbreviations [App Suggestion]

Posted: Fri Apr 12, 2013 11:00 am
by berestovskyy
Hi!
In some languages the word ending depends on the form of a subject (gender, conjugation etc.).

I suggest we put the full street name w/o any abbreviations into the map data and use it for TTS/search purpose. But in order to display it on a screen, App abbreviates the words or even eliminates them completely using internal abbreviation table. For instance:

1) Aleja Świętej Anny -> al. sw. Anny
2) Ulica Świętego Tomasza -> sw. Tomasza
3) Estakada imienia generała pilotów Mateusza Iżyckiego -> Estakada Mateusza Iżyckiego

So, the abbreviation table for polish data would be:
Aleja -> al.
Ulica -> null
Świętej -> sw.
Świętego -> sw.
imienia -> null
...

What do you think?

Re: Client-side Abbreviations [App Suggestion]

Posted: Fri Apr 12, 2013 5:46 pm
by AlanOfTheBerg
Moving this to the Localization forum for better visibility to topic discussed.

Re: Client-side Abbreviations [App Suggestion]

Posted: Fri Apr 12, 2013 6:51 pm
by berestovskyy
In Polish, for instance, words "świętego" (saint m.) and "świętej" (saint f.) both have the same common abbreviation -- "sw." Same rules applies to other Slavic languages, including Russian. So we have to either invent uncommon abbreviations for every single case, or TTS will always offend the saint slavic women :D

Client App could also skip some words. Here is another polish real world example:
Estakada imienia generała pilotów Mateusza Iżyckiego
translation: Overpass named after a general of pilots Mateusz Iżycki

This quite a long name would look absolutely OK to me if it were displayed on a screen just like:
Estakada Mateusza Iżyckiego
translation: Mateusz Iżycki's Overpass

Thanks for your understanding!

Re: Client-side Abbreviations [App Suggestion]

Posted: Fri Apr 12, 2013 9:25 pm
by berestovskyy
Regarding all saints. Well, I just wrote two cases, but in slavic languages there are lot's of them. Here is a quote from Wikipedia:
Nouns have grammatical gender, number, and are declined for 7 cases;
Adjectives agree with the noun in case, number, and gender;
Verbs have 2 aspects, 3 tenses, 3 moods, and 2 voices.
For the same "saint" we have 7 cases x 2 number x 3 genders = 42 forms :shock: That's why we have just one common abbreviation for all "saints" -- "sw."

Regarding TTS you're right! It's better to pronounce a short name as well. So, the final proposal is:

1. We always name the street completely and officially for accurate search.
2. The client App omits some words announcing the street name.
3. The App omits some words or abbreviate them for displaying.

An example:
Full name: Estakada imienia generała pilotów Mateusza Iżyckiego
For TTS: Estakada Mateusza Iżyckiego
To display: Est. Mateusza Iżyckiego
or even: Est. M. Iżyckiego

Ok?

Re: Client-side Abbreviations [App Suggestion]

Posted: Thu Apr 18, 2013 1:05 pm
by berestovskyy
Agree! And we already have a mechanism for that -- alt. names. All you need is to mark which alt. name goes where: search, tts or display ;)

Re: Client-side Abbreviations [App Suggestion]

Posted: Thu Apr 18, 2013 3:09 pm
by berestovskyy
What do we do then? Uservoice?

Re: Client-side Abbreviations [App Suggestion]

Posted: Fri Apr 12, 2013 5:51 pm
by deeggo
There is a possibility to do this the other way round. You can use abbreviations in streetnames in the editor and ask Waze to replace those with the full word for pronunciation.

Re: Client-side Abbreviations [App Suggestion]

Posted: Sat Apr 13, 2013 7:24 am
by deeggo
Note to self: never study Slavic languages. ;-)

Re: Client-side Abbreviations [App Suggestion]

Posted: Thu Apr 18, 2013 12:48 pm
by Dekis
berestovskyy wrote: An example:
Full name: Estakada imienia generała pilotów Mateusza Iżyckiego
For TTS: Estakada Mateusza Iżyckiego
To display: Est. Mateusza Iżyckiego
or even: Est. M. Iżyckiego
It would be very nice if there where three street names. One for search, one for map and one for voice prompt.

Re: Client-side Abbreviations [App Suggestion]

Posted: Thu Apr 18, 2013 3:03 pm
by Dekis
berestovskyy wrote:And we already have a mechanism for that -- alt. names. All you need is to mark which alt. name goes where: search, tts or display ;)
Аgree completely :)