🚀 go-pugleaf

tytgat@esat.kuleuven.ac.be (John Tytgat) writes:

>>Argh! What about simply specifying that the text held in the icon is a
>>messagetrans tag? Then the template-loading code can lookup the necessary
>>text from the specified language-dependant messages file.

>Ok, but what about the practical implementation ? Do we specify a bit which
>determines the kind of text : plain text or messagetrans tag and define a
>path where the template, euh sorry, Glass editor can find the messagetrans
>files ? Or do we define more explicitly in the Glass file which languages
>are supported with explicit filenames (instead of a path) ?

I would say the easiest way is to specify a bit which indicates that the
text is actually a tag, and then in the application-side support code that
is supplied with the template editor, put in a method by which these
text items can be 'expanded'. Off the top of my head, I'd say a nice way to
approach this might be to register a messagetrans decoding function with
the support code, so it calls some user-defined function, passing in the
tag, and gets back a pointer to the actual string...

>I hope we never *have to* deal with messagetrans tags ourselves.  Automatic
>generation of such tags would be very helpful.

Yes. It would be a very good idea if !Glazier actually automatically generated
a messagetrans tag, and spat out a file of messages with the actual text you
typed in to the icon, automatically...

And as it's agoing to be a resource manager, it could also allow editing of
the messages file as well - easy to implement now that the ExtEdit protocol
is available... ;-) plug plug!

-- 
themasterofthearcanejwil1@cs.aukuni.ac.nzthismessagewassentonrecycledelectrons