What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

How can I fix the corrupt display of certain strings in non-Western-European charsets?

Votes:

0

Some strings as e.g. the timezone selection in the user account show only scrambled content in charsets that are different from the Western European codepage ISO-8859-1. What can be done to prevent this?

codepage prtg translation

Created on Jan 25, 2010 10:00:21 PM by  Dirk Paessler [Founder Paessler AG] (11,025) 3 6



1 Reply

Accepted Answer

Votes:

0

PRTG comes with a set of languages that feature their according code page settings. If you use a Windows with a different system code page you have to adapt the language file you are using to your needs. This can be done as follows:

  • Locate the language file (usually English.lng) in the language folder of your PRTG installation.
  • Copy and rename it to English(mylanguage).lng
  • Open the new file in your text editor
  • At the top of the file, change the following entries to:

<Language id="en" name="English(mylanguage)"> <codepage>mycharset</codepage>

where mycharset has to be replaced with an entry from this list: http://www.w3.org/International/O-charset-list.html, e.g. shift_jis for Japanese or iso-8859-5 for Russian(Cyrillic). You might want to experiment with the alternatives if it still doesn't work.

If your charset uses multibytes as Japanese, Chinese, Korean etc. you also have to change the chartfont entry in the lng file:

<chartfont> msgothic.ttc </chartfont>

This font should work with most multibyte charsets.

Save the changes, open the PRTG Server Administrator, select English(mylanguage) from the list, click OK and restart the PRTG service.

Now PRTG should display the strings correctly.

Created on Jan 25, 2010 10:02:01 PM by  Dirk Paessler [Founder Paessler AG] (11,025) 3 6




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.