> > Miguel Ángel Arruga Vivas <[email protected]> writes: > > if there is no problem.
Sorry for my silence these days. There were (personal) problems. Murphy's law: It can be worse. Always. Daiki Ueno <[email protected]> writes: > > Miguel Ángel Arruga Vivas <[email protected]> writes: > > With those changes[2] the developer will be able to test the > > extraction of a new tag from a new widget with --keyword=tag_name to > > extract the whole content, including "standard" attributes, without > > recompiling xgettext. Just the same as using a function in your source > > files of any language that calls internally gettext. > > This is a good feature. However, I don't think it is a hard requirement > for GtkBuilder support we are talking about. Can't this feature be > implemented separately from the patch? I think so, I will send a patch ... > > Also an open RFC unrelated to xgettext's internals: Could we remove tag > > checking and just look attributes for GtkBuilder files? I have not read > > any restriction about attributes, so It may be a convention, but > > attributes "translatable", "context" and "comments" are called 'regular > > translation attributes'[7] and also 'usual "translatable" and "context" > > attributes'[8]. > > Yes, it is actually what intltool does (and I think it's a good idea). ... with this idea ASAP. Best regards, Miguel
