Various translation issues

Thanks Akerbeltz. All the translation issues you pointed out are fully valid. Can you please report a bug to track this better. It would be helpful if you could include the line number and file name that they appear in if that is possible. We will fix them all in the next development cycle uNav version 0.59. We can't fix them for uNav 0.58 since we are in string freeze now and looking to push out a release soon.

Hope this answers your questions.

Thanks again for taking the time to translate uNav and keeping us informed of potential issues.

Hi Akerbeltz!
Thanks a lot for your feedback!

> Several strings refer to "clicking". Should these not be worded as "tapping" since it's for Touch?

Desktop version is comming :)) Tap will be so bad in Desktop. I think
"click" is generic and everybody will understand (?).

> PH

http://bazaar.launchpad.net/~unav-devs/unav/trunk/view/head:/qml/PoiListPage.qml
line 320.

> Convenience (is this a convenience store or a convenience stop?)
> College (this means two very different things in the US and the rest of the world, what kind of college are we talking?)

http://bazaar.launchpad.net/~unav-devs/unav/trunk/view/head:/qml/js/PoiCategories.js
Take a lot to the categories & Clause ;)

> Route so long (is this supposed to mean the route is TOO long?)

I'll fixed for next release.

> And several are tricky regard the use of placeholders:
> Current road becomes (this probably means something like A73 becomes M3; this needs a %s placeholder so locales where the target road has to appear elsewhere in the sentence can move this around)
> 260, 262, 266, 267, 268
> Enter the roundabout and take the exit %1
> Take the exit %1
> . Exit %1
> to take the %1
> toward %1

This will be fixed from the web API. Now is so complex to compose
these indication phrases and I can't fix them. My apologies for them.

A hug :)

Hi, sorry for the delay in responding, I was at a lexicography conference.

>Desktop version is comming :)) Tap will be so bad in Desktop. I think
>"click" is generic and everybody will understand (?).
I don't think merging those into one word is good. Generally, when the same string is used both on desktop and touch devices, the phrasing is "Click or tap..."

>http://bazaar.launchpad.net/~unav-devs/unav/trunk/view/head:/qml/PoiListPage.qml
>line 320.
I still don't know what that is, sorry ;)

>http://bazaar.launchpad.net/~unav-devs/unav/trunk/view/head:/qml/js/PoiCategories.js
>Take a lot to the categories & Clause ;)
Thanks but that does not answer the question. Wikipedia sums this up quite nicely:
In the United States and Italy, "College" formally refers to a constituent part of a university, but generally "College" and "university" are used interchangeably, whereas in Oceania and South Asia, "College" may refer to a secondary or high school, a college of further education, a training institution that awards trade qualifications, or a constituent part of a university.

I'm sure the categories are a lot of work (and will be so for a long time) but it would be good to get the basic ones unambiguous. Perhaps a wording like
School/College
University/College
would make the usage of the terms in question clearer?

Similarly
>http://bazaar.launchpad.net/~unav-devs/unav/trunk/view/head:/qml/js/PoiCategories.js
>Take a lot to the categories & Clause ;)
if this was kept in the long form "Concenience Store" it would be a lot clearer for everyone.

>This will be fixed from the web API. Now is so complex to compose
>these indication phrases and I can't fix them. My apologies for them.
I'm just trying to be helpful, no need to apologise :)
In addition to what I said above, can I just mention that the concatenation of these is really really tricky for translators? If there was ever a need for l18n, navigation is one of them because it involves so much inflection and case marking in many languages. I don't know if fixing this from the web API is going to address that or whether there needs to be a different approach. Just to give one example (in case you're not sure about what I mean):
Roundabout in our language is "cearcallan", "the roundabout" is "an cearcallan". If you exit the roundabout, it's "Fàg an cearcallan" but if you enter the roundabout it's "Rach a-steach dhan chearcallan". Other languages might change the ending or stuff like that.
I think it would be advantageous if we could collect all those phrases in the nav (from experience, there actually aren't THAT many) and then put it before a group of localizers to see the best way of making making these work for the devs AND the localizers.

Hi :)

Sometimes the design has a high weight. I'll not use "Click or tap" :)

The categories are not from Wikipedia. They are from OpenStreetMap:
http://wiki.openstreetmap.org/wiki/Nominatim/Special_Phrases/EN
Then, they are: Convenience Stores.
And this type of College: http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcollege

This is composition of the indication:
http://paste.ubuntu.com/15718151/
I don't know every possible composition. I know is so complicate a good concatenation, but it's the only way.

Thanks a lot for the feedback and translations |o/

>Sometimes the design has a high weight. I'll not use "Click or tap" :)
Design over end user friendliness doesn't sound that great an idea but your call.

>The categories are not from Wikipedia. They are from OpenStreetMap:
I didn't say they were from Wikipedia. I just used the explanation from Wikipedia to explain that "college" means totally different things in different parts of the world. In the US, if you are at college, you are in effect at university. But in the UK, if you are at college, you are definitely NOT at university.
I've read the info for OSM and they clearly did consider this, so a college is not a college in the US sense. But there should really be a comment for localizers on Launchpad because many will translate it wrong otherwise.

>This is composition of the indication:
Thanks. It seems that at the moment, it is fairly basic and I cannot see anything problematic (apart from what I reported above). And I *do* understand that concatenation is necessary. But there are ways of doing concatenation better. It often means more translations but the product will be better and the localizers less annoyed (I'm *not* annoyed just now). For example, I would suggest that when the nav becomes more complex with instructions, instead of just having
Enter %s
Leave %s
and somewhere else for % we have
roundabout
street
we offer translators different forms of each so they can inflect properly. I'm not an l18n expert from a dev perspective but I believe there is quite a lot of info available.