GNOME Bugzilla – Bug 124703
Continuation lines in strings problematic in gnomemeeting
Last modified: 2004-12-22 21:47:04 UTC
The way strings are divided in gnomemeeting/po/cat-id-tbl.c causes some problems for intltool and gettext tools. For instance, part {"\ GnomeMeeting is an H.323 compliant program for gnome\n\ This program is not supported by Microsoft(c).", 98}, is better written like {"" "GnomeMeeting is an H.323 compliant program for gnome\n" "This program is not supported by Microsoft(c).", 98}, I've tested this and it works fine with intltool, but I didn't compile it. I'll attach a patch that fixes this. I may commit it if you don't have any other solution on mind (because this is a generated file, I suspect you may want to fix the po2tbl script mentioned in the source file).
Created attachment 20727 [details] [review] Patch to make cat-id-tbl.c play nicer with intltool
Hi Danilo, I don't know where your head version of GnomeMeeting comes from. I have no cat-id-tbl.c file in my HEAD version. Also, it doesn't appear in the CVS view : http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&dir=gnomemeeting/po Moreover, it seems to contain very old messages that do not exist anymore. Sorry, but I'm confused. Can you give more details?
It's probably a problem with my checked out copy: I tried removing the file, and cvs up'ing it, and it reappears. I also usually do a "cvs co gnomemeeting" in the parent directory, and it usually purges the nonexisting files (apart from those that I or intltool added, for which it prints a question mark), but this one was persisting. I've checked out a fresh copy from CVS, and it doesn't contain these problems. Ah well, sorry for the false alarm. The actual culprit is a missing [encoding: UTF-8] (or whatever) from POTFILES.in. Feel free to mark this as NOTABUG.
Try to do a cvs up -Pd, perhaps (Im not a CVS expert) that it would remove the file. That is something weird. Anyway, for POTFILES.in, what is the exact syntax? If you have CVS access, you can commit the POTFILES.in fix yourself. Thanks!
> The actual culprit is a missing [encoding: UTF-8] (or whatever) from > POTFILES.in. Bug 124857 is slightly related to that issue.