Last active
August 29, 2015 14:23
TranslatableStrings aims to enable Roslyn to again be at peace with resources or any other translation mechanism when using string interpolation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| var person="David"; | |
| Console.WriteLine($_"Hello {person}"); | |
| // Prints "Alô David" in pt-BR | |
| Console.WriteLine($"Hello {person}"); | |
| // Prints "Hello David" in pt-BR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The compiler would have a command line option similar to that of xml documentation to extract all translatable strings either to a resx file (maybe using sha256 to generate identifiers), or to gettext-like string tables to be used with some other tooling.
My experimental implementatiion will use Managed.Commons.Core Translation interfaces/proxy to abstract the specific translation engine.