search

robert-j-engdahl / ngettext-wpf

Proper internationalization support for WPF (via NGettext)
GNU Lesser General Public License v3.0
9 stars 12 forks source link

Support for XML character entities in XAML markup extension(s) #27

Open D-Bullock opened 5 years ago

D-Bullock commented 5 years ago

If one uses a html entity (say " for a " sign) then the translation doesn't work - it can't find the string in the po file.

What happens is that the gettext extension receives the content with the " converted into a ", ie if we were to use {wpf:Gettext "example"} the gettext extension would see "example"

I think the correct way to solve the problem is to change the C# MO parser to convert html entities, in the same way that the XAML parser is doing. The other solution would be to change the extractor to convert the HTML entities.

To get around the issue, I'm currently doing a manual find/replace in the generated PO files

robert-j-engdahl commented 5 years ago

Yes, this should be fixed in the XAML internationalization process, i.e. XGetText-Xaml.ps1.

I think XAML is supposed to support all XML character entities.

Here is an example of something we might be able to use in solving this:

https://stackoverflow.com/a/10082285/2154774

Pull requests are welcome