Sigh... Help needed
Monday Jul 17, 2006
Documenting translation how-to for Solaris
I'm stuck. I started writing the message translation process on I18n community Sketchpad
a few days ago.
The plan was to document step-by-step process to 1)update existing
Solaris language
translations, 2)add a new language translation to Solaris, and 3)do the
same for documentation. I've never done Solaris
translation myself, but thought I could figure it out. How difficult can translation be? Well, I was wrong.
I unpacked the ON tarball G11n made available in June in G11n Download Center,
following the instruction in the Readme. While looking for any
sources for help, I stumbled over a Readme
that Ienup had written about ON message translations in October last
year. Great! So I tried to see if I can reference his instruction,
revise where needed, and figure out how it all works.
I got stuck when I saw the unpacked directory structure of ON tarball.
I didn't know where in this deep layer a translatable string could be
found. Without touching any files, I tried to generate MO files which I didn't succeed.
Why is generating MO files necessary to translator? I failed, but if I
succeed in building source tree, will I be able to easily identify
where my translations appear? Why do some files have duplicated English
files in the same directory structure and some others not?
So, long story short ;-), I need help answer these questions. Visit the Sketchpad and help me
make progress in the documenting process. My experience tells me that
most people in the community are more technically savvy than I am, and
yet my hunch is that easier way for people to participate will attract
more and wider range of contributors. Sigh...
|
|
|
|
