Comments on: OpenOffice.org Language Pack Revamp http://blog.shaunmcdonald.me.uk/2007/03/openofficeorg-language-pack-revamp/ My Random Ramblings Fri, 27 Jan 2012 07:49:10 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ghh http://blog.shaunmcdonald.me.uk/2007/03/openofficeorg-language-pack-revamp/comment-page-1/#comment-25 ghh Sun, 29 Jul 2007 07:15:00 +0000 http://smsm1986.wordpress.com/2007/03/31/openofficeorg-language-pack-revamp/#comment-25 Beyond technical issues, something needs to be done so that the user (presumed nontechnical) can choose to be a polyglot user (in my case 4 and 2 halves...). I used to know how it was done in antiquity (ooo1.x) and now, there is no documentation, no indications in the help, nothing. I don't wonder about user adoption levels.<br/><br/>Maybe you could influence the guys who do that? TIA.<br/><br/>Oh, being a techie as well, I second David Fraser's proposal, with the following addendum, why not suggest Java. It's already needed by ooo, it is (to all intents and purposes) compiled. , and (having done this before), a port of most things from C++ to Java is no really big deal. Developers might benefit from Java's very-late binding...<br/><br/>THank you for your attention.<br/><br/>George Herlin (ghherlin youknowwhat gmail punct com) Beyond technical issues, something needs to be done so that the user (presumed nontechnical) can choose to be a polyglot user (in my case 4 and 2 halves…). I used to know how it was done in antiquity (ooo1.x) and now, there is no documentation, no indications in the help, nothing. I don’t wonder about user adoption levels.

Maybe you could influence the guys who do that? TIA.

Oh, being a techie as well, I second David Fraser’s proposal, with the following addendum, why not suggest Java. It’s already needed by ooo, it is (to all intents and purposes) compiled. , and (having done this before), a port of most things from C++ to Java is no really big deal. Developers might benefit from Java’s very-late binding…

THank you for your attention.

George Herlin (ghherlin youknowwhat gmail punct com)

]]> By: David Fraser http://blog.shaunmcdonald.me.uk/2007/03/openofficeorg-language-pack-revamp/comment-page-1/#comment-24 David Fraser Wed, 04 Apr 2007 13:39:00 +0000 http://smsm1986.wordpress.com/2007/03/31/openofficeorg-language-pack-revamp/#comment-24 It would be nicer if the spell checker extensions could be reasonably written in a cross-platform language like Python :-) It would be nicer if the spell checker extensions could be reasonably written in a cross-platform language like Python :-)

]]> By: Anonymous http://blog.shaunmcdonald.me.uk/2007/03/openofficeorg-language-pack-revamp/comment-page-1/#comment-23 Anonymous Tue, 03 Apr 2007 14:47:00 +0000 http://smsm1986.wordpress.com/2007/03/31/openofficeorg-language-pack-revamp/#comment-23 AFAIK some language packs come with their own spell checker component for the language which of course is a C++ and thus platform dependend component. Thus when we want to have platform-independent language packs those can not include spell checker components anymore. Maybe we´d have to split those into spell-checker-extension for language XYZ plus language-pack for language-XYZ than. But this makes it more complicated for the user to locate what he/she must download to have full support for the combination of language and platform in use. This would leave the problem of course that as long as platform A does not build that spell-checker-lang-XYZ-extension it would not be available. AFAIK some language packs come with their own spell checker component for the language which of course is a C++ and thus platform dependend component. Thus when we want to have platform-independent language packs those can not include spell checker components anymore. Maybe we´d have to split those into spell-checker-extension for language XYZ plus language-pack for language-XYZ than. But this makes it more complicated for the user to locate what he/she must download to have full support for the combination of language and platform in use. This would leave the problem of course that as long as platform A does not build that spell-checker-lang-XYZ-extension it would not be available.

]]>