From: address@nospicedham.not.available   
      
   Alex,   
      
   > With all the messages buried in the source stream, managing them becomes   
   > difficult at scale or if multiple target languages are to be supported.   
      
   Last night I came to the realization that you where most likely talking   
   about a program which would display messages in the language the user has   
   selected as his preference.   
      
   In that case, what is than the problem for the programmer to decide *not* to   
   use in-line strings for those ?   
      
   ... even though using the standard "by label reference" doesn't solve   
   anything in that regard.   
      
   In other words, why have you tried to point out a problem that should be   
   solved by (an implementation of) literal strings when its not at all limited   
   to just them ?   
      
   Also, why *at all* try to wrangle a literal string implementation into   
   something a regular label already does ( "=a(label)" ) ?   That doesn't make   
   much, if any, sense.   
      
      
   And although there are multiple solutions available involving the standard   
   "by label reference" method, *none* of them are easy to manage if you do not   
   want to have to reassemble the whole source when you have only replaced the   
   language strings (read: have placed them in their own file).   
      
   Though if you do not care about having to reassemble the whole program   
   (creating seperate executables, one for each targetted language) than a bit   
   of pre-processor magic on the literal strings will ofcourse solve the   
   multi-language problem just fine.    
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)