Hi, There is a big risk in using markups in properties files.
They are likely to go to a translation office were the people don't know about markups. May be they translate <strong> to <stark>. You could never be sure, that these markups apply at all. Depending were you insert it, your markup is taken literally. Both approaches will produce earlier or later massive testing costs. When application is display a longer text where some words are marked, I would consider to use ClientBundle TextResource or ExternalTextResource. Stefan Bachert http://gwtworld.de On 15 Apr., 14:21, salk31 <[email protected]> wrote: > What is the best plan for allowing/disallowing markup in i18n > messages? > > I'd be tempted to say no but one day the pointy haired boss is going > to say he wants a word in italics and I'd feel a bit silly saying > "no". > > Sorry if I've missed something but does GWT offer a solution to this? > > The best I can think of is that by default messages won't have markup > (so will be escaped) but if the message starts with a valid tag e.g. > "<span>" then I will turn off escaping for at least <strong>, <em> > etc... So not very good at all. > > Thanks > > Sam -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
