ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65690
|
Thu Jan 10 15:24:53 2008 |
| Kristján Jónsson | kj@raunvis.hi.is | Bug report | Linux | 2.7.0-1954 | "Default encoding" default is not as documented |
Hi,
"Default encoding" appears to have the default value of 2 (HTML) instead of 0 (ELCode) as documented in http://midas.psi.ch/elog/config.html
ELOG V2.7.0-1954 : elog.c line 8952
Kristján |
65691
|
Thu Jan 10 15:30:35 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.0-1954 | Re: "Default encoding" default is not as documented |
Quote: | "Default encoding" appears to have the default value of 2 (HTML) instead of 0 (ELCode) as documented in http://midas.psi.ch/elog/config.html
ELOG V2.7.0-1954 : elog.c line 8952
Kristján |
I changed the documentation 
The reason for this is to give beginners the FCKeditor by default instead of the ELCode encoding. |
65694
|
Thu Jan 10 18:30:26 2008 |
| Kristján Jónsson | kj@raunvis.hi.is | Question | Linux | 2.7.0-1954 | Configuration of HTML editor |
Do I have to do any extra configuration in elog to enable the FCKeditor.
What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).
ELCode works as expected. Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup. Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.
I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory. All are world readable.
Any hints about what could be the problem?
Thanks
Kristján
|
65695
|
Fri Jan 11 08:08:51 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.0-1954 | Re: Configuration of HTML editor |
Kristján Jónsson wrote: |
Do I have to do any extra configuration in elog to enable the FCKeditor.
What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).
ELCode works as expected. Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup. Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.
I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory. All are world readable.
Any hints about what could be the problem?
|
Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.
|
65696
|
Fri Jan 11 14:33:58 2008 |
| Kristján Jónsson | kj@raunvis.hi.is | Question | Linux | 2.7.0-1954 | Re: Configuration of HTML editor |
Stefan Ritt wrote: |
Kristján Jónsson wrote: |
Do I have to do any extra configuration in elog to enable the FCKeditor.
What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).
ELCode works as expected. Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup. Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.
I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory. All are world readable.
Any hints about what could be the problem?
|
Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.
|
Excellent, works as expected now, thanks.
Didn't realise how far behind the SVN version elog-latest.tar.gz is.
|
65699
|
Mon Jan 21 15:03:48 2008 |
| Carl Shirey | carl.shirey@pw.utc.com | Question | Linux | 2.7.0.1 | 80 column Message width. |
First thing we have been using the Elog for 2 yr for a shift carryover and it has works out great.
Now for the problem I have. I heave the message width set to 80. It works for plain Encoding but it does not work for HTML or ELCode. The text does not wrap around when viewing using Explorer or Fire Fox or printing out the Elog. Is this a problem or do I need to modify the Config file?
Thanks |
65700
|
Mon Jan 21 15:08:19 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.0.1 | Re: 80 column Message width. |
Carl Shirey wrote: |
First thing we have been using the Elog for 2 yr for a shift carryover and it has works out great.
Now for the problem I have. I heave the message width set to 80. It works for plain Encoding but it does not work for HTML or ELCode. The text does not wrap around when viewing using Explorer or Fire Fox or printing out the Elog. Is this a problem or do I need to modify the Config file?
Thanks
|
A limited message width does not make sense for HTML or ELCode encoding since the text is laid out by the browser dynamically when displaying messages. For example have a look at this very message in your browser, and resize your window. You will see that the text flows dynamically, so the line breaks move with the window size. Furthermore the text entry uses a variable width font, so a fixed line length would not result in line breaks at the same vertical position. Therefore the message entry size scales automatically with the browser window. If you need lines with fixed length, you can only do that in plain encoding. |
65701
|
Mon Jan 21 15:32:06 2008 |
| Carl Shirey | carl.shirey@pw.utc.com | Question | Linux | 2.7.0.1 | 80 column Message width. |
That is the the problem the text does not resize with the window or sending to the printer. |