View previous topic :: View next topic |
Author |
Message |
rigolo
Joined: 19 May 2012 Posts: 2
|
Posted: Sat May 19, 2012 12:45 am Post subject: Using translation tool without being married to Globalizer |
|
|
Globalizer is nice and simple (and cheap).
But before recommending it to customers, I would like to know whether it is possible to use it to manage resx translation without being married to Infralution because the Markup Extension (Static Wrapper) refers to an Infrasolution extension (Wrapper)?
I suppose in practice the question comes down to how easily could people move to another tool after having started using Globalizer to localized their code. |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sat May 19, 2012 1:26 pm Post subject: |
|
|
The WPF code localization technique doesn't really tie you to Globalizer. In both the Resx Extension and the Resource Wrapper localization methods can be hand coded without any reliance on Globalizer. While Globalizer certainly makes coding these easier by automatically converting XAML properties to resources it doesn't tie you to using Globalizer.
The Resource Wrapper localization method doesn't use any external code - just the wrappers that Globalizer generates for you - but you could code these by hand if required. The ResxExtension does use the Infralution.Localization.WPF assembly - but this is an open source assembly. The full code is available on Code Project. Again you don't have to use Globalizer (and many of the Code Project users don't) - but it certainly makes it easier and provides great translation and previewing capabilities. _________________ Infralution Support |
|
Back to top |
|
|
rigolo
Joined: 19 May 2012 Posts: 2
|
Posted: Thu May 31, 2012 3:59 am Post subject: |
|
|
Infralution wrote: | The WPF code localization technique doesn't really tie you to Globalizer. In both the Resx Extension and the Resource Wrapper localization methods can be hand coded without any reliance on Globalizer. While Globalizer certainly makes coding these easier by automatically converting XAML properties to resources it doesn't tie you to using Globalizer.
The Resource Wrapper localization method doesn't use any external code - just the wrappers that Globalizer generates for you - but you could code these by hand if required. The ResxExtension does use the Infralution.Localization.WPF assembly - but this is an open source assembly. The full code is available on Code Project. Again you don't have to use Globalizer (and many of the Code Project users don't) - but it certainly makes it easier and provides great translation and previewing capabilities. |
Thank you for those explanations ! |
|
Back to top |
|
|
|