Karl Berry <[email protected]> writes: > listing options after ':' sounds like a better idea. > > If you decide to go down this road, it belatedly occurs to me that | > might be a better delimiter than :, as being perhaps less likely to > occur in file names. > > Also, as you imply, having --options after the delimiter sounds much > better than my half-formed idea of random new keywords. As in: > > texindex/ti.twjr|--language=awk --keyword=...
Thanks for the suggestion. Indeed, the format needs to be carefully thought out, if we embed such meta-information in file names. On the other hand, I fear that that might confuse wrappers like intltool and might break backward compatibility. So, my current idea is to have a separate file listing options, analogous to .gitattributes: *.twjr --language=awk --keyword= ... *.cpp --keyword ... where glob patterns are allowed to avoid repetition. The drawback is that we need to add another option (e.g., --options-file) to xgettext and a user needs to check if the option is available. Other ideas are welcome. > Implementing all that in a separate script sounds nicer than trying to > merge it into that already-too-complex .pot-update Makefile rule :). Yes, that sounds a good idea. Regards, -- Daiki Ueno
