I agree with Kevin. Depending on your compile encoding, Java can process UTF-8 source, however, given the fact that many people simply stomp over file encoding by using US-ASCII or ISO-8859-1, When asked, I usually recommend using the '\unnnn' notation for these constants.
On Thu, Jan 8, 2009 at 00:53, Ian Boston <[email protected]> wrote: > NP, I will do. > Ian > > On 7 Jan 2009, at 21:32, chico charlesworth wrote: > >> Feel free to replace "รค" in the SpiDatabaseBootstrap class with either "a" >> or "\u00e4" (there's 4 occurences), or let me know if you prefer that I >> resubmit the patch. >> >> 2009/1/7 Kevin Brown <[email protected]> >> >>> Non ascii in source is always a pain. Id vote for escaping appropriately. >>> >>> On Jan 7, 2009 7:47 AM, "Ian Boston" <[email protected]> wrote: >>> >>> What is the policy on UTF-8 on constants. >>> >>> Should it be allowed, should it be escaped ? >>> >>> The patch on SHINDIG-782 has raw UTF8. IMHO... it should not, but I >>> wanted >>> to check. >>> Ian >>> > >
