> But as I mentioned I don't want to use Resources.
> This is a really specific situation inside an application.
> So I am looking for something around what I described.
> Thank You,
> Miguel
I would use XML files with an DTD which enforces that a certain node has all required languages.
Xml files can be searched with Linq.
<translation name='username'>
<es>Usuario</es>
<en>User</en>
<es_EU>Basque username</es_EU>
</translation>
Notes: - Be carefull with Xml file encoding, so the file type does not restrict the languages charsets.
- Thats not and standar choice, I would use resources and globalization
> > But as I mentioned I don't want to use Resources.
> > This is a really specific situation inside an application.
> > So I am looking for something around what I described.
> > Thank You,
> > Miguel
> I would use XML files with an DTD which enforces that a certain node has all required languages.
> Xml files can be searched with Linq.
> <translation name='username'>
> <es>Usuario</es>
> <en>User</en>
> <es_EU>Basque username</es_EU>
> </translation>
> Notes:
> - Be carefull with Xml file encoding, so the file type does not restrict the languages charsets.
> - Thats not and standar choice, I would use resources and globalization
I am also trying to avoid XML.
This is something I really prefer to include on the application.
Again, I am using this to localize very specific parts of the application which possible changes always occurs with a new compilation.
To make things easier I am trying to concentrate all those translations in one place.
I came up with the following class:
public class Pair {
public String Content { get; set; }
public String Culture { get; set; }
public Pair(String content, String culture) {
Content = content;
Culture = culture;
}
}
Then I use List<List<Pair>> to hold the data:
List<List<Pair>> data = new List<List<Pair>>();
And I get it as follows:
data.Add(new List<Pair> { new Pair("Hello", "en"), new Pair("Olá", "pt"), new Pair("Bounjour", "fr") });
data.Add(new List<Pair> { new Pair("Bye", "en"), new Pair("Adeus", "pt"), new Pair("Adieu", "fr") });
> On Wednesday, November 14, 2012 5:20:50 PM UTC, bradbury9 wrote:
<snip>
> > I would use XML files with an DTD which enforces that a certain node has > > all required languages.
<snip>
> > - Thats not and standar choice, I would use resources and globalization
> I am also trying to avoid XML.
> This is something I really prefer to include on the application.
> Again, I am using this to localize very specific parts of the application > which possible changes always
> occurs with a new compilation.
> To make things easier I am trying to concentrate all those translations in > one place.
> I came up with the following class:
> public class Pair {
> public String Content { get; set; }
> public String Culture { get; set; }
> public Pair(String content, String culture) {
> Content = content;
> Culture = culture;
> }
> }
> Then I use List<List<Pair>> to hold the data:
> List<List<Pair>> data = new List<List<Pair>>();
> And I get it as follows:
> data.Add(new List<Pair> { new Pair("Hello", "en"), new Pair("Ol ", > "pt"), new Pair("Bounjour", "fr") });
> data.Add(new List<Pair> { new Pair("Bye", "en"), new Pair("Adeus", > "pt"), new Pair("Adieu", "fr") });
1. Consider what your reasons are for not using the globalization and localization resources provided for you. You may have good reason, but don't reject what is there out of hand.
2. Your class is the easy bit. What is yuck is the notion of hard coding these in your application, because you then need to go back to the code each time you need to add a new translation or a new language. Better to have an external resource from which you can load them. Whilst XML wouldn't be my first choice, it does provide one means. Possibly a better approach would be an external database.
3. If you are serious about languages then you will also need to consider reading order - although it might not make much difference for isolated words.
> Honest feedback: Yuck.
> 1. Consider what your reasons are for not using the globalization and > localization resources provided for you. You may have good reason, but don't > reject what is there out of hand.
I really did consider Resources for this case.
And I have been using it in many projects ...
But in this particular case it is to restricted.
I need something which functionality I can extend.
> 2. Your class is the easy bit. What is yuck is the notion of hard coding
> these in your application, because you then need to go back to the code each
> time you need to add a new translation or a new language. Better to have an
> external resource from which you can load them. Whilst XML wouldn't be my
> first choice, it does provide one means. Possibly a better approach would be
> an external database.
Brian, that is the point I tried to explain, maybe not well:
I am already using a SQL database which includes localization.
But there are parts of the application where I do not want to use it:
1 - Localize a Route;
2 - Localize a list originated by an enum;
3 - Localize a 404 error message ...
These parts of the application in fact will rarely change.
And when they change it will always be with a new application version.
By doing this way I can make it flexible enough to take a string, a list of strings or even an enum by adding an "adapter" in the pipeline.
Instead of having this localization done across the application my intention is to have it in a centralized place ...
NOTES:
- I will not have a huge list of strings / phrases to localize.
Maybe 200 at its maximum on the entire application ...
Usually defined in 4 classes (each one for a section of the application).
- Everything else will be localized on the SQL database (Content, so on).
Please, don't take me wrong. I am open to any advice.
But when I say I do not want to use Resources, SQL or XML is because I did really used these three options in the past.
And they were, for this kind of situation, or to rigid, or in case of the SQL problematic because the need of changing something in the code would always be dependent of changes in the database and also added database calls for no need.
> 3. If you are serious about languages then you will also need to consider
> reading order - although it might not make much difference for isolated
Sounds like you have done your homework. Sorry if I implied otherwise.
> > 3. If you are serious about languages then you will also need to > > consider
> > reading order - although it might not make much difference for isolated
> > words.
> Sorry, could you explain what do you mean?
Reading-order is simply whether the text is read from left to right or right to left. It also affects the layout of the page.
For example where I might write:
Error: 404
in Arabic the reading order is right to left so the above would be written - and you'll have to excluse me for using English words and numbers rather than Arabic "squiggles":
404 :Error
(and right aligned on the page)
Reading order is something you can probably ignore if you only expect to target European/Western countries - but I'm sure someone will let me know if I'm mistaken.
> El mi rcoles, 14 de noviembre de 2012 17:36:53 UTC+1, Shapper escribi :
>> I do know all about that ...
>> But as I mentioned I don't want to use Resources.
>> This is a really specific situation inside an application.
>> So I am looking for something around what I described.
> I would use XML files with an DTD which enforces that a certain node has all required languages.
> Xml files can be searched with Linq.
> <translation name='username'>
> <es>Usuario</es>
> <en>User</en>
> <es_EU>Basque username</es_EU>
> </translation>
XML is certainly an option for persisting of data.
(I would probably prefer a database in this case, but XML is
certainly an option)
But for in memory data structure I don't see it work.
Both XmlDocument and XDocument would perform horrible for
the required operations.
> El miércoles, 14 de noviembre de 2012 15:23:15 UTC+1, Shapper escribió:
>> Hello,
>> I need to store some strings in different languages as follows:
>> "Hello", "en" ; "Olá", "pt" ; "Bounjour", "fr"
>> "Goodbye", "en" ; "Adeus", "pt" ; "Adieu", "fr"
>> Then I would have two methods:
>> String Translate(String value, String fromLanguage, String toLanguage);
>> IEnumerable<String>Translate(IEnumerable<String>, String fromLanguage, String toLanguage);
> Globalization and localization.
> public class Pair {
> public String Content { get; set; }
> public String Culture { get; set; }
> public Pair(String content, String culture) {
> Content = content;
> Culture = culture;
> }
> }
> Then I use List<List<Pair>> to hold the data:
> List<List<Pair>> data = new List<List<Pair>>();
> And I get it as follows:
> data.Add(new List<Pair> { new Pair("Hello", "en"), new Pair("Olá", "pt"), new Pair("Bounjour", "fr") });
> data.Add(new List<Pair> { new Pair("Bye", "en"), new Pair("Adeus", "pt"), new Pair("Adieu", "fr") });
NOTE: If possible also have two methods that accepts a IEnumerable<String> Keys or a IEnumerable<String> Values ... These methods would be the same as the one before but to N values. The fromCulture and toCulture would be the same for all.
I am looking for the following:
1 - Translator must implement ITranslator
This is because I will inject ITranslator in parts of my application;
2 - I need a configuration class such as:
public static class TranslatorConfiguration {
public static IList<TranslatorProviderBase> Providers { get; set; }
public static String DefaultFromCulture { get; set; }
public static String DefaultToCulture { get; set; }
// ...
}
A) Providers are classes that contains the translations.
I could separate some translations in 2 or 3 files.
Translator would go into these providers for search.
It would be just a table partition ...
B) DefaultFromCulture would be for example "en".
Then I would have a methods such as:
TranslateValue(String value, String toCulture);
C) DefaultToCulture would be set for example as follows:
I would set this culture maybe as follows:
Now I could would have methods such as: TranslateValue(String value, String toCulture)
And I can add a few more like "AllowedCultures", etc.
In App_Start I would set the configuration with all these values.
Then I would inject ITranslator and use those methods.
I hope I gave an idea on how I am trying this to "work".
I read your answers but when you suggest something like:
public class Translation
{
private Dictionary<string, Dictionary<int, string>> forward;
private Dictionary<string, Dictionary<string, int>> backward;
...
}
I am completely lost on how to integrate this in what I am trying to do.
I can post the code I have at the moment:
(NOTE: I am using List<Dictionary<String, String>> because at the moment I didn't add the Keys yet. I was trying to make it work only with Values. But my intention is to use Dictionary<string, Dictionary<string, int>> to Keys to.)
> On Sunday, November 18, 2012 3:03:43 AM UTC, Arne Vajhøj wrote:
>> On 11/14/2012 7:13 PM, Shapper wrote:
>>> I think I found the best option for this:
>>> List<Dictionary<String, String>>
>> Containing what?
> Yes, I know you did helped me on a similar question.
> At that moment I had a different approach ... Maybe wrong.
> To be honest I didn't completely understand your suggestions.
> Let me explain what would be the ideal in my head:
> NOTE: If possible also have two methods that accepts a
> IEnumerable<String> Keys or a IEnumerable<String> Values ... These
> methods would be the same as the one before but to N values. The
> fromCulture and toCulture would be the same for all.
That part is trivial.
> I read your answers but when you suggest something like:
