| Hi Geert, Hope your very well. Many thanks for your post. I think your our first user to create a language pack for InstantKB.NET  I believe i know what could be causing this problem. As our language files are XML based certain characters are not allowed and you need to provide the XML representation of that character. Also if you such certain characters with accents etc you will need to change the encoding type of the XML document. You can read more about the encoding types in the link below. One common problem that catches many customers is the ampersand (& character. This character is not allowed in XML. For example the following string would throw an exception... <<item name="KeyName">Preview & Print</item> The correct way to represent this within XML would be... <<item name="KeyName">Preview & Print</item> You can find a complete list of special characters within our forum documentation. As InstantKB.NET uses our localization code within the InstantASP.Common framework similar to the forum this information does apply to both. You can read more on this under the "XML Encoding & Special Characters" section at the link below... http://docs.instantasp.co.uk/instantforum/creatingalanguagepack.html For your problem i would suggest you first look at the encoding type of the XML document. XML documents may contain foreign characters, like Norwegian æ ø å , or French ê è é. To ensure the XML parser understands these characters, you should save your XML resource files as Unicode. In XML, the character encoding is optional and can be given in the XML declaration in the first line of the document, like this: <?xml version="1.0" encoding="iso-8859-1"?> For most standard character sets we would suggest utf-8. The XML processor can recognize the following character set names: UTF-8
UTF-16
ISO-10646-UCS-2
ISO-10646-UCS-4
ISO-8859-1 to -9
ISO-8859-11
TIS-620
ISO-2022-JP
Shift-JIS
EUC-JP Examples of encoding declarations: <?xml version="1.0" encoding="UTF-16"?> <?xml version="1.0" encoding="EUC-JP"?> (for Japanese character) <?xml version="1.0" encoding="iso-8859-11"?> (for Thai character ) If no encoding is given XML defaults to UTF-8. If you try to load an XML based resource file into Internet Explorer, you may one of the following error messages indicating encoding problems: If you attach your resources.xml file here i'll happily take a quick look to see what could be causing the problem.
Kindest Regards,
Ryan Healey
Director / Developer
 Explore our products...
http://demos.instantasp.co.uk/
|