Difference between revisions of "Talk:Extensions/website/Translating"
| Line 1: | Line 1: | ||
[[User:Jsc|Juergen Schmidt]]: i would say English is a mandatory language and i would suggest that we integrate a check for that. English is more or less the default language for the whole OO.org project and it's important to reach a huge audience. | [[User:Jsc|Juergen Schmidt]]: i would say English is a mandatory language and i would suggest that we integrate a check for that. English is more or less the default language for the whole OO.org project and it's important to reach a huge audience. | ||
| + | |||
[[User:Jsc|Juergen Schmidt]]: localization of extensions is under the responsibility of the extension provider. We should take care of that. Especially commercial ISV's may have an opinion on that. I think the community can offer their help by submitting an appropriate issue and the provider can decide if it is suitable for them. I am not sure how we can handle this best. A web frontend where providers can put all their resources for an extension would be great -> reuse of the translation database if possible would be perfect as already mentioned. | [[User:Jsc|Juergen Schmidt]]: localization of extensions is under the responsibility of the extension provider. We should take care of that. Especially commercial ISV's may have an opinion on that. I think the community can offer their help by submitting an appropriate issue and the provider can decide if it is suitable for them. I am not sure how we can handle this best. A web frontend where providers can put all their resources for an extension would be great -> reuse of the translation database if possible would be perfect as already mentioned. | ||
Latest revision as of 07:46, 13 September 2007
Juergen Schmidt: i would say English is a mandatory language and i would suggest that we integrate a check for that. English is more or less the default language for the whole OO.org project and it's important to reach a huge audience.
Juergen Schmidt: localization of extensions is under the responsibility of the extension provider. We should take care of that. Especially commercial ISV's may have an opinion on that. I think the community can offer their help by submitting an appropriate issue and the provider can decide if it is suitable for them. I am not sure how we can handle this best. A web frontend where providers can put all their resources for an extension would be great -> reuse of the translation database if possible would be perfect as already mentioned.
