search

jirentabu / crashrpt

Automatically exported from code.google.com/p/crashrpt
0 stars 0 forks source link

Have you consider that the output messages' language can also be custom? #57

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 

Have you considered that some fixed keywords(such as: copying file, Dumping 
registry keys..., Connecting to server and so on) of the output messages can 
also be loaded from the INI file to customize language as UI current use?

Original issue reported on code.google.com by dreamexcel@gmail.com on 19 Sep 2010 at 3:55

Attachments:

GoogleCodeExporter commented 9 years ago 
UI used Chinese Language
the TextEdit(Or RichTextEdit) control always used English language

Original comment by dreamexcel@gmail.com on 19 Sep 2010 at 3:57

GoogleCodeExporter commented 9 years ago 
Actually I thinked about using localized strings. But I didn't implement this 
because of the following reasons:

1. There are too many strings to localize in the log. If I have about 100 
strings to localize, no one will contribute a language file for CrashRpt ;)

2. I localized only the strings that are needed for user to understand what's 
happen at the current moment. The log is intended for the developer (not for 
user) to understand what's wrong. User doesn't need to read the log, he just 
copies it and sends to the developer.

Finally, I'm not a fan of translating those strings and adding them to the INI 
file.

Original comment by zexspect...@gmail.com on 19 Sep 2010 at 10:01

GoogleCodeExporter commented 9 years ago 
I decided not to fix this, because language file may become very large.

Original comment by zexspect...@gmail.com on 25 Sep 2010 at 2:48