On Wednesday 14 January 2009, Chris Cannam wrote: > I'm not so worried about that part. It's converting and subsequently > maintaining the actual translation files that concerns me most.
I'm worried about all of the above, and I'd be less worried if we could wait for Qt 4.5 to come out, with .po support. March. Probably April or May before everyone could reliably get a copy without compiling it by hand, I'd guess. Probably too long. So I guess we have to convert from .po to .qwhatever and rewrite the maintenance tools (po-stats and messages.sh need to be replaced with something else.) > I'm sure whatever problem it is that we currently face can be worked > around far more easily than by switching away from i18n altogether. If you have any clue how to do that, be my guest. I turned up bupkis for hints where to even start poking around. > However, I think that i18n is the only thing we still use from the KDE > libraries, so it's probably no bad thing to switch in any case. I agree it makes sense just to make a clean break. Especially to shut up all the whining GNOME fanboys. I have no objection, and will help as much as possible, but I don't think I can offer a lot of legwork solving this particular problem. -- D. Michael McIntyre ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
