How can I have a Terminal with Multi language Support?

jokar.mohsen · 12-02-2014, 10:17 AM

Quote:

Originally Posted by unSpawn

You could have saved time by stating that problem in your first post. For example this post explains some methods and with Syslog-NG one possible solution could look like this:

Code:

source src_win {
        udp(
                ip("192.168.1.1")
                port(514)
                encoding("ISO-8859"));
};

You could try that, and if that doesn't work for you, research the other methods mentioned in that thread.

Thank you so much but now, I understand that my main problem is my Syslog agent on Windows. I use Snare log agent on windows and I guess it can't support Persian name. Can you introduce me any agent that support Persian name?

TB0ne · 12-02-2014, 01:26 PM

Quote:

Originally Posted by jokar.mohsen

Thank you so much but now, I understand that my main problem is my Syslog agent on Windows. I use Snare log agent on windows and I guess it can't support Persian name. Can you introduce me any agent that support Persian name?

Is your syslog server running on Windows or Linux?? And which snare agent are you using, the free version or the commercial? The free version for Windows hasn't been updated in over a year now, but it looks as if it doesn't have ANYTHING where you can set an output language. It picks that information up from the Windows registry. Are your local Windows events getting logged in the right language/format?

And there IS a syslog-ng native agent for Windows, which could use unSpawn's solution:
http://www.balabit.com/sites/default...gle/index.html

..and MANY other solutions you can find with a quick search:
https://code.google.com/p/eventlog-t...downloads/list

jokar.mohsen · 12-04-2014, 11:29 PM

Quote:

Originally Posted by TB0ne

Is your syslog server running on Windows or Linux?? And which snare agent are you using, the free version or the commercial? The free version for Windows hasn't been updated in over a year now, but it looks as if it doesn't have ANYTHING where you can set an output language. It picks that information up from the Windows registry. Are your local Windows events getting logged in the right language/format?

And there IS a syslog-ng native agent for Windows, which could use unSpawn's solution:
http://www.balabit.com/sites/default...gle/index.html

..and MANY other solutions you can find with a quick search:
https://code.google.com/p/eventlog-t...downloads/list

on linux. No, I use Free version of it

. My Local Windows events are in correct format.

TB0ne · 12-05-2014, 09:04 AM

Quote:

Originally Posted by jokar.mohsen

on linux. No, I use Free version of it

. My Local Windows events are in correct format.

Ok, and we will AGAIN point out that you don't acknowledge things that are told to you. Did you read/understand the previous post????

Did you not see/read/understand the part where you could use the native syslog-ng client for Windows, and apply the fix that unSpawn suggested?
Did you not see/read/understand the part where it was suggested to try a DIFFERENT Windows logging agent?
Did you not see/read/understand the part where you were pointed to one of those different agents??

Again, unless you ACKNOWLEDGE getting advice, and TRY what is suggested, there is little point in just rehashing your original question. It's taken numerous posts to pull this much information out of you, yet you come here for advice. As you've been told before, people don't like having to play 20 questions to try to help you. Post details up front, and participate in getting the solution by acknowledging what you've been told, and maybe even TRYING it.