Release SourceCodeEscapers

[GoogleCodeExporter]

Tasks:

- Figure out the proper names for everything. (Internal bug 3102010, comment 10 
has some principles for this.)

- Determine which of the escapers for each language we actually want. One 
possible decision is that we want *none* of the current escapers. For example, 
does it make sense for our Java escaper to escape printable non-ASCII 
characters, as it currently does? At least inside Google, our .java files are 
UTF-8. Considerations: If it *does* make sense to escape them, then the escaper 
should perhaps be named "javaAsciiCharEscaper." Also, is there any chance that 
the set of characters that we *would* need to escape would change over time? 
(For example, aren't there some other "newline-like" characters?) Or might it 
make sense to escape any confusable characters? Is there a standard enough set 
of confusable characters (maybe for domain names? though of course it might 
change), or would it be best to avoid non-ASCII altogether? Maybe this is 
reason to have both javaAsciiCharEscaper and javaCharEscaper 
("javaUnicodeCharEscaper?").

Original issue reported on code.google.com by cpov...@google.com on 19 Dec 2013 at 7:40

[GoogleCodeExporter]

This issue has been migrated to GitHub.

It can be found at https://github.com/google/guava/issues/<issue id>

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:10

• Added labels: MigratedToGitHub

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:17

• Changed state: Migrated

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 3 Nov 2014 at 9:08

• Added labels: Restrict-AddIssueComment-Commit