Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 114 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  68762   Thu Mar 15 09:39:20 2018 Reply Matej Sedejmatej.sedej@gmail.comBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

To conclude this topic, we sadly can't use the characters č and Č propperly in the application. I have marked the problems in the screenshots below:

red square - the user name is changed immediately after saving. It is also written into the log file in the attribute "Lovec" preset as $long_name. This cannot be displayed correctly even when using HTML and the text tag.

orange sqare - This appears in translated menus and in the attribute "Preža" where the options are listed. The character is written correctly in the translation and the log file, but is displayed incorrectly as È and è.

pink square - After using the script on this attribute "Opis" to insert the html text tag the field correctly displays the characters. The minor problem remains when exporting this to a csv file where the html text tag remains.

I have no idea what effort it would take to change the ANSI background of the application to UNICODE and I can't really expect you to do this. On the other hand most modern applications go through this step eventually, mostly because of the Chinese and the Russian markets.

Thanks again for the otherwise great product, I guess we'll have to start using letters c and C instead. Best reagards,
Matej

Attachment 1: elog.png
elog.png
Attachment 2: logfile.png
logfile.png
  68763   Fri Mar 16 12:46:09 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

Matej Sedej wrote:

To conclude this topic, we sadly can't use the characters č and Č propperly in the application. I have marked the problems in the screenshots below:

red square - the user name is changed immediately after saving. It is also written into the log file in the attribute "Lovec" preset as $long_name. This cannot be displayed correctly even when using HTML and the text tag.

orange sqare - This appears in translated menus and in the attribute "Preža" where the options are listed. The character is written correctly in the translation and the log file, but is displayed incorrectly as È and è.

pink square - After using the script on this attribute "Opis" to insert the html text tag the field correctly displays the characters. The minor problem remains when exporting this to a csv file where the html text tag remains.

I have no idea what effort it would take to change the ANSI background of the application to UNICODE and I can't really expect you to do this. On the other hand most modern applications go through this step eventually, mostly because of the Chinese and the Russian markets.

Thanks again for the otherwise great product, I guess we'll have to start using letters c and C instead. Best reagards,
Matej

 

Attachment 1: Screen_Shot_2018-03-16_at_13.00.25_.png
Screen_Shot_2018-03-16_at_13.00.25_.png
  68764   Fri Mar 16 14:12:04 2018 Reply Matej Sedejmatej.sedej@gmail.comBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides. blush 

Stefan Ritt wrote:

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

  68765   Fri Mar 16 14:35:05 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

Easiest is to install the Cywgin environment (www.cygwin.com) and there select the C compiler package which installs also "make".

Matej Sedej wrote:

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides. blush 

Stefan Ritt wrote:

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

 

  68766   Fri Mar 16 15:39:17 2018 Reply Matej Sedejmatej.sedej@gmail.comBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

Phew, made it, sort of. Had to copy the contents of the mxml folder from an older version, the folder was empty in this git. I also had to change the SSL to 0 and then it compiled without errors plus I had to copy the cygwin1.dll to the folder to make the service run.

So yes, I can confirm that manually inputting the Č in the attribute field now works correctly. Excellent! This solves the pink problem then. Any similar solutions for the red and orange ones?

Thanks,
Matej

Stefan Ritt wrote:

Easiest is to install the Cywgin environment (www.cygwin.com) and there select the C compiler package which installs also "make".

Matej Sedej wrote:

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides. blush 

Stefan Ritt wrote:

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

 

 

  68767   Fri Mar 16 17:51:30 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

Pink problem: Yes the CSV export preserves the html tags, but what to do. CSV files are plain text with 8 bit characters. Unicode characgers have to be represented with more than one byte. So either HTML encoding or some special escape sequence encoding. If you like the second better than the first, I'm sure you find some conversion program on the internet.

Orange problem: No clue how C is converted to E. Maybe depends on the encoding of your browser? There is a elog option "charset = xxx" with which you can play.

Matej Sedej wrote:

Phew, made it, sort of. Had to copy the contents of the mxml folder from an older version, the folder was empty in this git. I also had to change the SSL to 0 and then it compiled without errors plus I had to copy the cygwin1.dll to the folder to make the service run.

So yes, I can confirm that manually inputting the Č in the attribute field now works correctly. Excellent! This solves the pink problem then. Any similar solutions for the red and orange ones?

Thanks,
Matej

Stefan Ritt wrote:

Easiest is to install the Cywgin environment (www.cygwin.com) and there select the C compiler package which installs also "make".

Matej Sedej wrote:

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides. blush 

Stefan Ritt wrote:

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

 

 

 

  68768   Fri Mar 16 18:08:10 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

Special characters in use names should now work in the current version.

Stefan Ritt wrote:

Pink problem: Yes the CSV export preserves the html tags, but what to do. CSV files are plain text with 8 bit characters. Unicode characgers have to be represented with more than one byte. So either HTML encoding or some special escape sequence encoding. If you like the second better than the first, I'm sure you find some conversion program on the internet.

Orange problem: No clue how C is converted to E. Maybe depends on the encoding of your browser? There is a elog option "charset = xxx" with which you can play.

Matej Sedej wrote:

Phew, made it, sort of. Had to copy the contents of the mxml folder from an older version, the folder was empty in this git. I also had to change the SSL to 0 and then it compiled without errors plus I had to copy the cygwin1.dll to the folder to make the service run.

So yes, I can confirm that manually inputting the Č in the attribute field now works correctly. Excellent! This solves the pink problem then. Any similar solutions for the red and orange ones?

Thanks,
Matej

Stefan Ritt wrote:

Easiest is to install the Cywgin environment (www.cygwin.com) and there select the C compiler package which installs also "make".

Matej Sedej wrote:

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides. blush 

Stefan Ritt wrote:

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

 

 

 

 

  68769   Fri Mar 16 20:54:40 2018 Reply Matej Sedejmatej.sedej@gmail.comBug reportWindowsELOG V3.1.3-fd7Re: Problem with special character "č"

That's great, Stefan, it works indeed. I tried fiddling around a bit with different charsets but haven't been succesful yet. I'll play around some more.

Stefan Ritt wrote:

Special characters in use names should now work in the current version.

Stefan Ritt wrote:

Pink problem: Yes the CSV export preserves the html tags, but what to do. CSV files are plain text with 8 bit characters. Unicode characgers have to be represented with more than one byte. So either HTML encoding or some special escape sequence encoding. If you like the second better than the first, I'm sure you find some conversion program on the internet.

Orange problem: No clue how C is converted to E. Maybe depends on the encoding of your browser? There is a elog option "charset = xxx" with which you can play.

ELOG V3.1.5-3fb85fa6