IP.Content and Language String Translation in 4.0

[TracyIsland]

Since we made the plunge into the sometimes murky waters of language translation, we are finding some surprises and disappointments.

After reading your blog on >language translation for 4.0 , I wanted to add some other suggestions, and perhaps others have made or will make additional suggestions.

#1 - for sites like ours, which has an English default language and 16 other language packs, it is cumbersome to add a language string. Currently, adding a language string involves repeating the same process in every language pack. Would it be possible to have an autopopulate feature, so that if a language string is added in one language pack, it is added to all, or .. perhaps if there is some reason not to do that, to offer admins the ability to select some or all language packs where the same language string should be added?

#2 - The referenced blog entry makes no mention of ip.content and on the spot translations. We use a number of ip.content blocks. Currently, the only way to make those ip.content blocks translateable is to add a language string, and then change the block template to reference that new language string. Certainly it would be difficult to offer "on the spot" translation for the body of the block since you can't predict what will be inside but couldn't you at least provide that instant translation for the elements of the block that are part of the ip.content block construction process? So the block title could be translateable?

Thanks,

Brian

[bfarber]

Since we made the plunge into the sometimes murky waters of language translation, we are finding some surprises and disappointments.

After reading your blog on >language translation for 4.0 , I wanted to add some other suggestions, and perhaps others have made or will make additional suggestions.

#1 - for sites like ours, which has an English default language and 16 other language packs, it is cumbersome to add a language string. Currently, adding a language string involves repeating the same process in every language pack. Would it be possible to have an autopopulate feature, so that if a language string is added in one language pack, it is added to all, or .. perhaps if there is some reason not to do that, to offer admins the ability to select some or all language packs where the same language string should be added?

#2 - The referenced blog entry makes no mention of ip.content and on the spot translations. We use a number of ip.content blocks. Currently, the only way to make those ip.content blocks translateable is to add a language string, and then change the block template to reference that new language string. Certainly it would be difficult to offer "on the spot" translation for the body of the block since you can't predict what will be inside but couldn't you at least provide that instant translation for the elements of the block that are part of the ip.content block construction process? So the block title could be translateable?

Thanks,

Brian

We haven't talked much about IP.Content at all.

That said, something like the block title will use our "Translatable" from helper, which allows you to translate it to any language.