Hi Alberto,
we should move this discussion in a seperate thread, it does not have
anything to do what Eike adress in his presentation @OOOCon ;)
Alberto Escudero-Pascual wrote:
Hi Ivo,
Thanks for you answer.
First of all I want to clarify that is not a pure simplistic critic to
the "OOo 2.0 way" and any of you... let's take it from there. I get the
sense that everyone gets a bit defensive (including me:) when we discuss
the dark sides and it does not help.
I don't understand. What dark sides we have discussed and what do not
happend?
Localizing OOo should be as simple as localizing Skype or Google!. If we
I agree, but remember in OOo are a lot of more strings than "What do you
want to search today?" and a "Search" Button. We have a bunch off
different resource types ( res files , officecfg , readme , help ... )
[...]
For example, posting a one line "patch" that could be already in the
source from the beginning can take 15 minutes
see below ( -Include as many L.... )
...downloading a build system three/four days.
see below
Some quick suggestions...
- Integrate online PO translation in OpenOffice.org, if you do not like
Pootle create something else.
Our curent resource system is not yet able to handle WYSIWYG
translation. Solving this would also reduce the download / build times.
This already has been adressed but we have not yet a solution for that.
- Include as many languages as possible by default in the source code
limiting the number of patches to submit.
This sounds somehow strange to me. This imply we know all languages that
will be included in the near future or include ALL languages that are
spoken on this planet. The "Ethnologue" from 1996 knows 8717 languages,
400 of them are already dead. Then you have a factor for dialects and/or
different regions. This will consume 5 years of Eike,Ivo,Pavel's life to
integrate all known locales, patches , etc... You need several months to
translate those 250000 (?) strings and 4* 15 minutes for patch creation
is to much?
- Create a good OOo 2.0 glossary including IT terms and definitions
Pavel created a script that filters all words that occur 4 times or more
often in the translation. Does that meet your requirements ? David also
mentioned that they currently test a "poconflict" tool, that detects
different translated words. Is there realy a need for such glossary if
you use a po based translation memory system?
- Include or encourage the inclusion of localization toolkits and guides
with every OpenOffice.org release.
In the released binary or within the source code? I am not sure if it
make sense to couple them but may be a download, unpack and ready to
translate package reduce some stress from collecting all needed things.
- Create a template webpage(s) to submit patches for localization issues
ONLY.
Like enter iso code here and your ms-id in the next text column ? I
could image a "demo" patch, but everything is documentated in Javiers
docu. Those patches are not equal, there are too many dependencies ( CTL
yes/no, has msid yes/no, win98 relased language yes/no, ... ). I think
there is no way arround reading this document, because you must know
what you do.
Maybe the main difference in our points is that I am thinking in what is
left to do. No flames to you as you are mostly thinking in keeping the
thing rolling...
I do not rate this as a flame, I just want to point out that we have to
discuss things. We all want to improve this process. And yes there is a
lot of work left!
btw you can verify that your message has been send into the mailinglist
here:
http://l10n.openoffice.org/servlets/SummarizeList?listName=dev
Cheers,
Ivo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
