"Delivery to our showrooms in %{list_of_locations}"
In Swedish and English, it works fine to just pass in @category.name or @locations.to_sentence. But in Finnish, instead of "in Foo" you might say "Foossa", using a suffix instead of a preposition (inessive case). And similarly, you might say "Fooan ja Baran" for "to Foo and Bar" (illative case).
And as I understand it, these suffixes are irregular - you can't just do @locations.map { |x| "#{x}ssa" }.
I'm very interested to hear how others handle this. Are there i18n conventions?
The best solutions I can think of is to have e.g. a category.name_inessive_fi column (and not have columns for Swedish and English, or leave them empty and fall back), and to do similarly for the locations or to have translation keys for e.g. stockholm_illative.
Henrik I think this is a general problem also for other languages as e.g. Swedish For example, "New %{attribute_name}" where attribute_name is name, decription, time etc should in Swedish be translated as "Nytt namn", Ny "beskrivning" etc As i understand it the only way to solve this problem is to have specific translations for each case of "New #{attribute_name}" , as otherwise you end up with writing some kind of grammar ,e.g rules for when to use Ny and Nytt. However, when it comes to langauge , there are allways exceptions that you are not aware of, according to my experience. There are no simple rules!
____________________________________________ Hans Marmolin St: Larsgatan 50, 58224 Linköping, Sweden Phone: +46708371202
> "Delivery to our showrooms in %{list_of_locations}"
> In Swedish and English, it works fine to just pass in @category.name > or @locations.to_sentence. But in Finnish, instead of "in Foo" you > might say "Foossa", using a suffix instead of a preposition (inessive > case). And similarly, you might say "Fooan ja Baran" for "to Foo and > Bar" (illative case).
> And as I understand it, these suffixes are irregular - you can't just > do @locations.map { |x| "#{x}ssa" }.
> I'm very interested to hear how others handle this. Are there i18n > conventions?
> The best solutions I can think of is to have e.g. a > category.name_inessive_fi column (and not have columns for Swedish and > English, or leave them empty and fall back), and to do similarly for > the locations or to have translation keys for e.g. stockholm_illative.
> -- > You received this message because you are subscribed to the Google > Groups "rails-i18n" group. > To post to this group, send email to rails-i18n@googlegroups.com. > To unsubscribe from this group, send email to rails-i18n+unsubscribe@googlegroups.com > . > For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en > .
That's a good point. In this case, the categories and locations are dynamic (in the DB), and are part of complex phrases with a combinatorial explosion of different variations, so translating them in full wouldn't work well.
On Fri, Jun 10, 2011 at 15:09, Hans Marmolin <hans.marmo...@klockholm.se> wrote: > Henrik > I think this is a general problem also for other languages as e.g. Swedish > For example, "New %{attribute_name}" where attribute_name is name, > decription, time etc should in Swedish be translated as "Nytt namn", Ny > "beskrivning" etc > As i understand it the only way to solve this problem is to have specific > translations for each case of "New #{attribute_name}" , as otherwise you > end up with writing some kind of grammar > ,e.g rules for when to use Ny and Nytt. > However, when it comes to langauge , there are allways exceptions that you > are not aware of, according to my experience. There are no simple rules!
> ____________________________________________ > Hans Marmolin > St: Larsgatan 50, 58224 Linköping, Sweden > Phone: +46708371202
> 10 jun 2011 kl. 11.26 skrev Henrik Nyh:
>> We have some translation strings like
>> "Search in %{category_name}"
>> or
>> "Delivery to our showrooms in %{list_of_locations}"
>> In Swedish and English, it works fine to just pass in @category.name >> or @locations.to_sentence. But in Finnish, instead of "in Foo" you >> might say "Foossa", using a suffix instead of a preposition (inessive >> case). And similarly, you might say "Fooan ja Baran" for "to Foo and >> Bar" (illative case).
>> And as I understand it, these suffixes are irregular - you can't just >> do @locations.map { |x| "#{x}ssa" }.
>> I'm very interested to hear how others handle this. Are there i18n >> conventions?
>> The best solutions I can think of is to have e.g. a >> category.name_inessive_fi column (and not have columns for Swedish and >> English, or leave them empty and fall back), and to do similarly for >> the locations or to have translation keys for e.g. stockholm_illative.
>> -- >> You received this message because you are subscribed to the Google Groups >> "rails-i18n" group. >> To post to this group, send email to rails-i18n@googlegroups.com. >> To unsubscribe from this group, send email to >> rails-i18n+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rails-i18n?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "rails-i18n" group. > To post to this group, send email to rails-i18n@googlegroups.com. > To unsubscribe from this group, send email to > rails-i18n+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rails-i18n?hl=en.
We've had this kind of problem with locations and categories too. It is a hard problem, especially when you have the combinatorial explosion. One way we've worked round it is by not having sentences, so something like %{attribute_name}: New. Probably won't help in this case but it's something to consider doing.
> That's a good point. In this case, the categories and locations are > dynamic (in the DB), and are part of complex phrases with a > combinatorial explosion of different variations, so translating them > in full wouldn't work well.
> On Fri, Jun 10, 2011 at 15:09, Hans Marmolin <hans.marmo...@klockholm.se> wrote: >> Henrik >> I think this is a general problem also for other languages as e.g. Swedish >> For example, "New %{attribute_name}" where attribute_name is name, >> decription, time etc should in Swedish be translated as "Nytt namn", Ny >> "beskrivning" etc >> As i understand it the only way to solve this problem is to have specific >> translations for each case of "New #{attribute_name}" , as otherwise you >> end up with writing some kind of grammar >> ,e.g rules for when to use Ny and Nytt. >> However, when it comes to langauge , there are allways exceptions that you >> are not aware of, according to my experience. There are no simple rules!
>> ____________________________________________ >> Hans Marmolin >> St: Larsgatan 50, 58224 Linköping, Sweden >> Phone: +46708371202
>> 10 jun 2011 kl. 11.26 skrev Henrik Nyh:
>>> We have some translation strings like
>>> "Search in %{category_name}"
>>> or
>>> "Delivery to our showrooms in %{list_of_locations}"
>>> In Swedish and English, it works fine to just pass in @category.name >>> or @locations.to_sentence. But in Finnish, instead of "in Foo" you >>> might say "Foossa", using a suffix instead of a preposition (inessive >>> case). And similarly, you might say "Fooan ja Baran" for "to Foo and >>> Bar" (illative case).
>>> And as I understand it, these suffixes are irregular - you can't just >>> do @locations.map { |x| "#{x}ssa" }.
>>> I'm very interested to hear how others handle this. Are there i18n >>> conventions?
>>> The best solutions I can think of is to have e.g. a >>> category.name_inessive_fi column (and not have columns for Swedish and >>> English, or leave them empty and fall back), and to do similarly for >>> the locations or to have translation keys for e.g. stockholm_illative.
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "rails-i18n" group. >>> To post to this group, send email to rails-i18n@googlegroups.com. >>> To unsubscribe from this group, send email to >>> rails-i18n+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/rails-i18n?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "rails-i18n" group. >> To post to this group, send email to rails-i18n@googlegroups.com. >> To unsubscribe from this group, send email to >> rails-i18n+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rails-i18n?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "rails-i18n" group. > To post to this group, send email to rails-i18n@googlegroups.com. > To unsubscribe from this group, send email to rails-i18n+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en.
On Fri, Jun 10, 2011 at 17:00, Chris McGrath <ch...@octopod.info> wrote: > We've had this kind of problem with locations and categories too. It is a hard problem, especially when you have the combinatorial explosion. One way we've worked round it is by not having sentences, so something like %{attribute_name}: New. Probably won't help in this case but it's something to consider doing.
>> That's a good point. In this case, the categories and locations are >> dynamic (in the DB), and are part of complex phrases with a >> combinatorial explosion of different variations, so translating them >> in full wouldn't work well.
>> On Fri, Jun 10, 2011 at 15:09, Hans Marmolin <hans.marmo...@klockholm.se> wrote: >>> Henrik >>> I think this is a general problem also for other languages as e.g. Swedish >>> For example, "New %{attribute_name}" where attribute_name is name, >>> decription, time etc should in Swedish be translated as "Nytt namn", Ny >>> "beskrivning" etc >>> As i understand it the only way to solve this problem is to have specific >>> translations for each case of "New #{attribute_name}" , as otherwise you >>> end up with writing some kind of grammar >>> ,e.g rules for when to use Ny and Nytt. >>> However, when it comes to langauge , there are allways exceptions that you >>> are not aware of, according to my experience. There are no simple rules!
>>> ____________________________________________ >>> Hans Marmolin >>> St: Larsgatan 50, 58224 Linköping, Sweden >>> Phone: +46708371202
>>> 10 jun 2011 kl. 11.26 skrev Henrik Nyh:
>>>> We have some translation strings like
>>>> "Search in %{category_name}"
>>>> or
>>>> "Delivery to our showrooms in %{list_of_locations}"
>>>> In Swedish and English, it works fine to just pass in @category.name >>>> or @locations.to_sentence. But in Finnish, instead of "in Foo" you >>>> might say "Foossa", using a suffix instead of a preposition (inessive >>>> case). And similarly, you might say "Fooan ja Baran" for "to Foo and >>>> Bar" (illative case).
>>>> And as I understand it, these suffixes are irregular - you can't just >>>> do @locations.map { |x| "#{x}ssa" }.
>>>> I'm very interested to hear how others handle this. Are there i18n >>>> conventions?
>>>> The best solutions I can think of is to have e.g. a >>>> category.name_inessive_fi column (and not have columns for Swedish and >>>> English, or leave them empty and fall back), and to do similarly for >>>> the locations or to have translation keys for e.g. stockholm_illative.
>>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "rails-i18n" group. >>>> To post to this group, send email to rails-i18n@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> rails-i18n+unsubscribe@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/rails-i18n?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "rails-i18n" group. >>> To post to this group, send email to rails-i18n@googlegroups.com. >>> To unsubscribe from this group, send email to >>> rails-i18n+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/rails-i18n?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "rails-i18n" group. >> To post to this group, send email to rails-i18n@googlegroups.com. >> To unsubscribe from this group, send email to rails-i18n+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "rails-i18n" group. > To post to this group, send email to rails-i18n@googlegroups.com. > To unsubscribe from this group, send email to rails-i18n+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en.
