On Sun, Oct 09, 2005 at 12:37:38PM +0200, Christian Stimming wrote: > Am Sonntag, 9. Oktober 2005 03:46 schrieb Chris Shoemaker: > > > > xgettext appears to now support finding strings in Lisp files. Would > > > > be worth checking to see if this works with the scheme variant of lisp. > > > > I would expect it does. If so we could dump the intl-scm directory > > > > altogether and use xgettext directly. > > > > > > I noticed that, too. And that's what I was planning on looking into. > > > > Indeed, xgettext does seem to correctly parse our scheme files. > > > > From looking at xgettext's NEWS file, I gather that this has been > > supported since Version 0.14.2 - February 2005. IIUC, the only people > > who need to run xgettext are the packagers, i.e. the developers. So, > > is this version sufficiently old enough that people are in favor of > > dropping our "use perl to collect Scheme strings into C file so > > xgettext can find them"-trick? > > As for my development system, which is suse9.3 so already quite recent (its > successor suse10.0 was just released this week), the bundled xgettext is > 0.14.1. I would therefore prefer sticking with the old method for something > like the upcoming 6 more months.
What does 0.14.1 do with .scm files? output nothing? fail loudly? output crap? The error I was seeing is on FC3, with xgettext 0.14.1. I don't get the error with FC4, using xgettext 0.14.3. > > And except for this very weird encoding error, this "trick" for collecting > the > strings from non-C-files is working really well and is done for other things > as well (glade, for example, although already automated by xgettext itself). So I guess you don't see the error I reported with SUSE 9.3 and xgettext 0.14.1? -chris > It is a workaround, but IMHO not one of the worse ones but a rather elegant > one. > > Christian _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
