On 4/30/08, Benjamin Bentmann <[EMAIL PROTECTED]> wrote: > > Roger Ye wrote: > > e.g., in Linux, if LC_ALL=en_US.UTF-16 has been set, > > one will be very confused in case of option [b], when maven uses another > > encoding such as utf-8 > > > > Confusion, that is exactly my point. If one of your co-workers has > "LC_ALL" set to a different value, won't he be confused why the build is > failing for him when you just tell "works for me"? The same POM should > deliver the same build output, that's just what I consider of "highest > weight".
we can survive if we explicitly set the source file encoding in the project pom.xml, this is visible and the overriding logic is reasonable. and always respecting platform default encoding is the correct way to make > > an application encoding-transparent > > > > I feel I misunderstand you. From your description, I imagine a world were > text editors don't bother to ask users for an encoding but simply always use > platform default encoding. In such a world, I wonder how people would > collaboratively work on the same sources. the context of this statement is within a standalone system, I think this is exactly what the notepad.exe does, notepad surely works, in its place. so the application developer don't need to worry about converting > > back-n-forth between several encodings/charsets, > > ditto Considering the internet and its wonderful aspect of bringing people all > over the world together, I really believe it is time that application > developers *do* worry about encoding and converting file contents to pull > down the walls that our different locales or OS impose. > > Imagine two open-source projects, one using UTF-8 and the other Big5. How > would people participate on these projects (using the same machine) if we > expected applications to always stick to one system-wide encoding setting? by explicitly setting the source file encoding in each project's own pom.xml, as UTF-8 and Big5, respectively. surely this will be a problem for you if you don't explicitly specify the encoding and please note with option [b] there'll be no answer if you still insist not to explicitly set encoding. by the way you're actually telling me that the two projects both have explicit encoding, this is not the case of the VOTE which discuss project without explicit encoding. IMO, e.g., networking related applications, have to deal with encoding, > > this is by nature, since network is used to connect > > people from different places. > > > > Let's remember that Maven is just sitting next to a "networking related > application", i.e. source control management. That why I suggest explicit encoding in pom.xml, Regarding SVN/CVS, I think the repository should have of strong type in case of encoding, whether explicit or implicit. e.g. if the SVN repository is using UTF-8, then it's strange if the file checked out is in another one about this I don't know much of SVN/CVS, this is an interesting topic I'd like to know more. Nice to discuss here Roger
