From: NAKATA Maho <[EMAIL PROTECTED]> Date: Mon, 21 Feb 2005 16:05:26 +0900 (JST)
> how do you merge localized.sdf for languages which you have been > maintaing? Everything I do is visible in build system, see ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/build/build It contains: for ISOCODE in $SUPPORTEDLANGUAGES do [ -f ${FILES}/2.0/GSI_${ISOCODE}.sdf ] && MergeDevelGSI ${ISOCODE} done The function MergeDevelGSI is defined in ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/build/build.functions MergeDevelGSI () { ISOCODE=$1 DEBUG=$2 LOCALIZE=localize if [ "x$DEBUG" = "xdebug" ] then GSI=${BUILD}/debug_GSI_${ISOCODE}.sdf else GSI=${FILES}/2.0/GSI_${ISOCODE}.sdf fi [ ! -r ${GSI} ] && { echo "GSI file ${GSI} is not readable, fix it!" exit } ${LOCALIZE} -m -x -l ${ISOCODE} -f ${GSI} } > I heard from employees of SUN K.K. Japan that they are fixing at > database. The process, database to localized.sdf is not clear at the > moment. Even they don't know what's going on. Do you know something > about it? Yes, but only from the view of external. Ivo knows much more. > BTW: ja team is doing translation collab with SUN, but when the > efforts are merged to source is not clear. If someone find something > is wrong or mis-translated, they should raise an IZ. However, if they > don't see their fixes in next snapshot or something like that, they > can easily ost their motivation. Yes, this could be a problem. > As you know, I'm always waiting for cws to be integrated for my > FreeBSD patches :) This is different thing. This is only because you are lazy or do not have time to learn cws tooling ;-)) You can (once you know cws tools) do that yourself and ask me to QA that CVS. And this *could* be fast. -- Pavel Janík Actually, we've just rescheduled: the word now is that Emacs 21 will not be released before year 2005. -- Eli Zaretskii in comp.emacs about release of Emacs 21 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
