Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/xleon/I18N-Portable
Simple and cross platform internationalization/translations for Xamarin and .NET
https://github.com/xleon/I18N-Portable
dotnet i18n internationalization localization translations xamarin
Last synced: 3 months ago
JSON representation
Simple and cross platform internationalization/translations for Xamarin and .NET
- Host: GitHub
- URL: https://github.com/xleon/I18N-Portable
- Owner: xleon
- License: mit
- Archived: true
- Created: 2016-03-01T23:30:03.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2023-11-12T23:49:43.000Z (12 months ago)
- Last Synced: 2024-07-15T23:34:58.914Z (4 months ago)
- Topics: dotnet, i18n, internationalization, localization, translations, xamarin
- Language: C#
- Homepage:
- Size: 763 KB
- Stars: 106
- Watchers: 6
- Forks: 16
- Open Issues: 16
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-xamarin - I18NPortable ★49 - Simple and cross platform internationalization/translations for Xamarin and .NET. (Internationalization)
README
> This project is now archived as there are no plans to update it.
> Please consider it before using it.
# I18N-Portable
Simple and cross platform internationalization/translations for Xamarin and .NET
[](https://www.nuget.org/packages/I18NPortable/)
[](https://www.nuget.org/packages/I18NPortable/)
[](https://ci.appveyor.com/project/xleon/i18n-portable)
[](https://codecov.io/gh/xleon/I18N-Portable)
- Cross platform
- Simple to use: `"key".Translate()`.
- Simple and fluent initialization setup.
- Readable locale files (.txt with key/value pairs).
- Support for custom file formats (json, xml, etc)
- Light weight
- No dependencies.
- Well tested
### Install
Install it on your PCL and platform projects.
From nuget package manager console:
`PM> Install-Package I18NPortable`
### Setup locales
- In your PCL/Core project, create a directory called "Locales".
- Create a `{languageCode}.txt` file for each language you want to support. `languageCode` can be a two letter ISO code or a culture name like "en-US". See [full list here](https://msdn.microsoft.com/en-us/library/ee825488%28v=cs.20%29.aspx).
- Set "Build Action" to "Embedded Resource" on the properties of each file
**Locale content sample**
# key = value (the key will be the same across locales)
one = uno
two = dos
three = tres
four = cuatro
five = cinco
# Enums are supported
Animals.Dog = Perro
Animals.Cat = Gato
Animals.Rat = Rata
Animals.Tiger = Tigre
Animals.Monkey = Mono
# Support for string.Format()
stars.count = Tienes {0} estrellas
TextWithLineBreakCharacters = Line One\nLine Two\r\nLine Three
Multiline = Line One
Line Two
Line Three
[Other file formats (including custom) supported](https://github.com/xleon/I18N-Portable#custom-formats)
### Fluent initialization
```csharp
I18N.Current
.SetNotFoundSymbol("$") // Optional: when a key is not found, it will appear as $key$ (defaults to "$")
.SetFallbackLocale("en") // Optional but recommended: locale to load in case the system locale is not supported
.SetThrowWhenKeyNotFound(true) // Optional: Throw an exception when keys are not found (recommended only for debugging)
.SetLogger(text => Debug.WriteLine(text)) // action to output traces
.SetResourcesFolder("OtherLocales") // Optional: The directory containing the resource files (defaults to "Locales")
.Init(GetType().GetTypeInfo().Assembly); // assembly where locales live
```
### Usage
```csharp
string one = "one".Translate();
string notification = "Mailbox.Notification".Translate("Diego", 3); // same as string.Format(params). Output: Hello Diego, you've got 3 emails
string missingKey = "missing".Translate(); // if the key is not found the output will be $key$. Output: $missing$
string giveMeNull = "missing".TranslateOrNull(); // Output: null
string dog = Animals.Dog.Translate(); // translate enum value (Animals is an Enum backed up in the locale file with "Animals.Dog = Perro")
List animals = I18N.Current.TranslateEnumToList();
List> animals = I18N.Current.TranslateEnumToTupleList();
string dog = animals[0].Item2; // Perro
Dictionary animals = I18N.Current.TranslateEnumToDictionary();
string dog = animals[Animals.Dog]; // Perro
// List of supported languages (present in the "Locales" folder) in case you need to show a picker list
List languages = I18N.Current.Languages; // Each `PortableLanguage` has 2 strings: Locale and DisplayName
// change language on runtime
I18N.Current.Language = language; // instance of PortableLanguage
// change language on runtime (option 2)
I18N.Current.Locale = "fr";
```
### Data binding
`I18N` implements `INotifyPropertyChanged` and it has an indexer to translate keys. For instance, you could translate a key like:
string three = I18N.Current["three"];
With that said, the easiest way to bind your views to `I18N` translations is to use the built-in indexer
by creating a proxy object in your ViewModel:
```csharp
public abstract class BaseViewModel
{
public II18N Strings => I18N.Current;
}
```
**Xaml sample**
```xaml
```
**Xamarin.Forms sample**
```xaml
`
```
**Android/MvvmCross sample**
```xml
```
**iOS/MvvmCross sample**
```csharp
var set = this.CreateBindingSet();
set.Bind(anyUIText).To("Strings[key]");
```
### Supported formats
The library ships with a single format reader/parser that is [TextKvpReader](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable/Readers/TextKvpReader.cs). Any other reader will be isolated in a different nuget/plugin to keep the library as simple as possible.
| Reader | Format | Source |
| ------------- |:-------------:| :-----:|
| [TextKvpReader](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable/Readers/TextKvpReader.cs) | [See sample](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable.UnitTests/Locales/es.txt) | I18NPortable |
| [JsonKvpReader](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable.JsonReader/JsonKvpReader.cs) | [See sample](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable.UnitTests/JsonKvpLocales/es.json) | I18NPortable.JsonReader [](https://www.nuget.org/packages/I18NPortable.JsonReader/) |
| [JsonListReader](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable.JsonReader/JsonListReader.cs) | [See sample](https://github.com/xleon/I18N-Portable/blob/master/I18NPortable.UnitTests/JsonListLocales/es.json) | I18NPortable.JsonReader [](https://www.nuget.org/packages/I18NPortable.JsonReader/) |
To use any non-default format, it needs to be added on initialization:
```csharp
I18N.Current
.AddLocaleReader(new JsonKvpReader(), ".json") // ILocaleReader, file extension
// add more readers here if you need to
.Init(GetType().Assembly);
```
### Creating a custom reader for another file format:
It's very easy to create custom readers/parsers for any file format you wish.
For instance, lets take a loot at the above mentioned `JsonKvpReader`:
Given this __en.json__ file
```json
{
"one": "uno",
"two": "dos",
"three": "tres"
}
```
Creating a custom reader is as simple as implementing `ILocaleReader`:
```csharp
public interface ILocaleReader
{
Dictionary Read(Stream stream);
}
```
```csharp
public class JsonKvpReader : ILocaleReader
{
public Dictionary Read(Stream stream)
{
using (var streamReader = new StreamReader(stream))
{
var json = streamReader.ReadToEnd();
return JsonConvert
.DeserializeObject>(json)
.ToDictionary(x => x.Key.Trim(), x => x.Value.Trim().UnescapeLineBreaks());
}
}
}
```
### Contributing new readers
If you implemented a new reader for another file format and you want to contribute, feel free to make a pull request. Any new reader will live in their own project in the solution and will produce a different nuget as a plugin to I18NPortable.