16:04 mmmm___ > regarding bug 5951 (the new build target). I looked inside createPot.py. This looks like a tool like gettext. Where is it called from? 16:04 soup > Chandler bug #5951: A new build target for i18n in Chandler makefiles Product: Chandler, Component: Build System, Severity: normal, Assigned to: [EMAIL PROTECTED], Status: ASSIGNED, Url: http://bugzilla.osafoundation.org/show_bug.cgi?id=5951
16:05 bkirsch > it is a command line call 16:05 bkirsch > you call it from the command line 16:05 bkirsch > direclty 16:05 bkirsch > ./tools/createPot.py 16:05 bkirsch > again it is basically gettext 16:05 bkirsch > a starting point for refinement in the .7 16:05 bkirsch > release16:06 mmmm___ > yes but you do not want to call this manually to all py files. so how do we avoid the need for a build targer?
16:06 bkirsch > no it does all the work for you 16:06 bkirsch > it scans all the po files in the chandler domain 16:06 bkirsch > you just run it 16:06 bkirsch > try it 16:06 bkirsch > you'll see what it does 16:06 bkirsch > creates a chandler.pot 16:06 bkirsch > in the $CHANDLERHOME directory16:07 bkirsch > again it is just to create the chandler translation at the moment
16:07 bkirsch > it needs refinement 16:07 mmmm___ > ok. so do you suggest that I add the XRC code here? 16:07 bkirsch > now that we are figuring out how to store and load pots 16:07 bkirsch > well probally not 16:07 bkirsch > since it uses the OS gettext 16:07 bkirsch > not the python version 16:07 bkirsch > I would suggest a separate file 16:08 bkirsch > for the xrc parsing 16:08 bkirsch > and then a utility script 16:08 bkirsch > that can invoke both of them 16:08 bkirsch > that way we keep the logic separate 16:08 bkirsch > again the generation of the .pot file 16:08 mmmm___ > sounds good. 16:08 bkirsch > happens very infrequently16:09 bkirsch > it is not something developers will need to do on their own
16:09 bkirsch > to use Chandler 16:11 mmmm___ > so we could have process_xrc.sh in tools/ folder? 16:12 mmmm___ > or tools/gettext_xrc.sh might be better? 16:14 bkirsch > sure your choice 16:15 mmmm___ > ok. will cook something up.
The log extract was taken from http://wiki.osafoundation.org/script/getIrcTranscript.cgi? channel=chandler
On Jun 1, 2006, at 4:48 PM, Mike Taylor wrote:
As part of the work for bug 5951 (https://bugzilla.osafoundation.org/show_bug.cgi?id=5951) I would like to propose that we add a gen_i18n.sh script to chandler/tools/ that performs the necessary steps to gather and generate i18n related data.This script could have parameters to handle any different parts of the process (which to be honest I don't think any one of us knows what they are completely :)This would 1) let me add a simple target to the make file and 2) have a script that anyone can run.I'm proposing this on the list to gather feedback on if this is a good idea and also to gather info on what steps are needed for the script.--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
