Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Using translation tool without being married to Globalizer

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Globalizer Support
View previous topic :: View next topic  
Author Message
rigolo



Joined: 19 May 2012
Posts: 2

PostPosted: Sat May 19, 2012 12:45 am    Post subject: Using translation tool without being married to Globalizer Reply with quote

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
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Sat May 19, 2012 1:26 pm    Post subject: Reply with quote

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
View user's profile Send private message Visit poster's website
rigolo



Joined: 19 May 2012
Posts: 2

PostPosted: Thu May 31, 2012 3:59 am    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Globalizer Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group