On Vr, 2008-09-19 at 00:01 +0200, Robert-André Mauchin wrote: > Shaun McCance a écrit : > > > > So the file looks like HTML, plus a plain text alternative, > > and a few images, all packed into an mbox file. Why can't > > we just have source HTML and PNG files, and have a script > > that automatically generated the mbox file? Then we could > > easily translate it with xml2po. > > > > -- > > Shaun > > > I was thinking that doing it at runtime would be very painful. Could we > generate theses Inbox files at build time with a simple shell script and > some gettext magic. > We should add this script into POTFILES.in, and call it during make. > > A draft is attached, but it would be good if a developer could do that > for us. > > Regards I had something similar in mind, but started out with Python. I _think_ (but will need some confirmation) that we'll need to do a little bit more than this. Having the whole file as one unit in the PO file will make it an extremely daunting task, especially to maintain in case of a change in the English. My idea is not complete at all, but I attach it as well. You'll see a few extra goodies mentioned (some implemented), such as properly encoding the header entries, so that we have valid from and subject fields in the non-ASCII case. I also think we should try to avoid translating the HTML and plain version separately. (Guess if I'm from a small localisation team.) The basic idea is using Inbox.in as a big Python string with variables that are substituted in the strings.py program, that uses plain gettext in Python, and therefore even supports translator comments. As a bonus we could even generate the date of having a variable for the date at build time to have it current instead of static in the file. This is not yet integrated in the build system, but I guess somebody might be able to help with that. I hope it is of help somehow. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/vrot-mango
Attachment:
Inbox.in
Description: application/mbox