Way browsig with slovenian locale is failing #2087
Comments
Author: tom[at]compton.nu It's browse.way_details.also_part_of that is the problem. I've added bogus versions of the 'two' and 'few' subkeys in r16613 that will need to be translated properly. |
Author: StefanB Thank you for fixing it. One could think that ":other" would handle all other (not specifically translated ) forms. I guess i18n mechanism could be more robust after all :) |
Author: tom[at]compton.nu Well we can fix the custom pluralizer to fall back to :other if you want... |
Author: StefanB Well, there are also cases in English where one would want eg: :zero :other plural forms, but this isn't handled properly by i18n plugin afaik. It sure would be nice to have this supported, specially with so many plural forms as we have (and which are the same in some circumstances). I'm not sure how our simple custom pluralizer could know what translations it has before picking one... |
Author: tom[at]compton.nu The :zero one is optional - if you don't have it then it uses :other instead. That is handled specially for all languages before invoking the language specific pluralizer (which is why I removed the :zero handling from your one). I'll have a look at whether the custom pluralizer can be made to do fallback... |
Author: TomH Fixed in r16633. |
Author: StefanB witty! When i was translating i18n plugin i went for .rb instead of .yml in hopes that also sl pluralization could go in there, so that it is all in one place, not spread in several files across plugin, making it easier for others to reuse and possibly not getting lost with plugin upgrades. |
Reporter: StefanB
[Submitted to the original trac issue database at 9.19am, Tuesday, 21st July 2009]
http://www.openstreetmap.org/browse/way/27028715
throws an error, but doesn't show enough info to fix it without seeing the logs.
My old ubuntu laptop with all the needed setup died so i can't reproduce this locally in near future.
I fixed the suspected interpolation error in [16596], but am not sure if this is already deployed or there is some other problem.
This issue is a spinoff of #2079.
The text was updated successfully, but these errors were encountered: