Closed vreixo closed 10 years ago
Maybe is better to let the strings as they are and just wait for more important changes before touch them once again.
@vreixo I agree that this should be changed, so I'm re-opening the issue. I'd rather change the text and not have translations in the other languages than leave a confusing message in place.
How about Origin or destination is outside transportation network coverage
?
OK, I suppose that you're right, I was just a bit tired of working with translations :-) For me your proposal of string is good. In Spanish I think that I will write "Origen o destino están fuera del área cubierta por la red de transportes" but I suppose that your approach is better when writing in English.
I think that if we do it is better to do it right and also change in all the translations and ask @rjfv and @mentaer to translate or just review one more string once again. Maybe is easier to simply tell them the line, in this occasion, to allow them to see what they had written before and don't change their files. For the other languages, including English, I can make the changes.
@vreixo Sounds good. Let's wait to request translation until we put the beta out, just to make sure that we're done with any text changes. Don't want to spam our translators :).
I agree :-)
When a user taps on a place that is outside transport network boundaries (for example at the sea) but inside server limits, the error message is:
<string name="tripplanner_error_outside_bounds">Origin or destination are outside region limits</string>
I think that this can be very confusing, because if the user is having this message he is probably close to region limits, hence he will clearly see the line of region limits but he will notice that he should be inside region. I suppose that a good alternative will be to talk about "transportation network limits" or similar instead of region.
Also for doing this I thing that will be easier if I just change all files at once (because I also need to comment all the other translation files) and I refer the commit to this issue.