Quoting Daniel Burrows ([EMAIL PROTECTED]): > I like the idea of not hardcoding the set of known top-level sections, > but as I was looking over this I realized there's an issue I didn't even > think about earlier (or if I did I've forgotten). How will translators > deal with this? Right now I just use gettext to translate section > descriptions, but that won't work if the descriptions are drawn from an > external configuration file. > > It should be sufficient to arrange for these strings to be marked up by > xgettext, and to run gettext over them at runtime. Unfortunately, > xgettext will only process program source code -- but if the > configuration file was generated at runtime from a template by a shell > program, xgettext could be run on the shell script. It's a little gross > but should work just fine. > > Christian, is there a better way of handling this situation?
Frankly speaking, I don't know. This is quite out of my experteise field, I'm afraid.
signature.asc
Description: Digital signature
