| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
990
|
Thu Mar 17 23:06:54 2005 |
 | Pieter Edelman | elog@pde.slimblondje.nl | Question | Linux | 2.5.7 | Re: Can't use the command-line client | Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client? |
|
991
|
Fri Mar 18 08:02:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Can't use the command-line client | > Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client?
I did modify it already, see http://midas.psi.ch/elog/userguide.html at the bottom. |
|
1070
|
Sun Apr 10 07:35:09 2005 |
 | Gregory M. Caughey | caugheygm@aol.com | Question | Linux | 2.5.7 | Howto Set Default Fonts in Editor Window? | Hello,
I have been running Elog for a long time on a variety of RedHat releases,
(this is a terrific project by the way). Currently running Elog v2.5.7 on
RedHat (Fedora Core-II) and most is working great excepting being able to
modify the default fonts being used by Elog when trying to write and save
in text mode while in Elog's main editing screen.
On my setup the font size is way too small and to work around this problem
I write and save everything in HTML mode. I've browsed the Elog css file
but don't yet see where or how to properly set the default font style or
size for the main screen in the editor. Can you shed some light on this for
me?
--
Regards, Greg |
|
1071
|
Sun Apr 10 09:36:07 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Howto Set Default Fonts in Editor Window? | > Hello,
> I have been running Elog for a long time on a variety of RedHat releases,
> (this is a terrific project by the way). Currently running Elog v2.5.7 on
> RedHat (Fedora Core-II) and most is working great excepting being able to
> modify the default fonts being used by Elog when trying to write and save
> in text mode while in Elog's main editing screen.
>
> On my setup the font size is way too small and to work around this problem
> I write and save everything in HTML mode. I've browsed the Elog css file
> but don't yet see where or how to properly set the default font style or
> size for the main screen in the editor. Can you shed some light on this for
> me?
The text style of the main message text is defined in the following lines in the
CSS field:
.messagepre {
font-family:'lucida console',courier,monospace;
font-size:10pt;
}
Locate these lines and change 10pt to 12pt or even 14pt. |
|
1393
|
Sun Aug 7 17:16:42 2005 |
 | cunnilinux | cunnilinux@bigmir.net | Info | Linux | 2.5.7 | charset specified in elog.conf has no effect [updated] | well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default)
when i specified charset in the global section, the problem's gone away.
2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset
elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc |
|
1405
|
Mon Sep 5 20:16:50 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.5.7 | Re: charset specified in elog.conf has no effect [updated] |
| cunnilinux wrote: | well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default) when i specified charset in the global section, the problem's gone away.
2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset
elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc
|
The documentation clearly states that the "charset" option is under the [global] section. I put it there since it does not make much sense to have separate charsets for separate logbooks. Or do you have one Russian, one Japanese and one Swedish logbook on the same server? Maybe for an international language school 
I can easily put it into the individual logbook's config, but only if more than one person requests this. |
|
1423
|
Tue Oct 4 19:40:27 2005 |
| David Spindler | dsspindler@earthlink.net | Question | Windows | 2.5.7 | Re: Can't use the command-line client | I have a similar problem. I am using Windows version, and whenever I use the elog client to send entry, it will not take with MOptions set. I usually have 2 attributes required (both MOptions), and I get the message that it is missing a required attribute. When I use ROptions, or Options, it works fine. Is there a problem with MOptions, or am I perhaps using a badly formatted commandline?
Commandline as follows: C:\elog>elog -h IP_ADR -p 80 -l gbld -u username password -a Type=Other -a Operator=SCADA -a Category=Controls -a Subject=Alarm "Please ignore."
Type and Category are required and MOptions.
Below is the pertinent part of the config file:
;***** Attribute Section
Attributes = Log Date, Operator, Type, Category, Engine, Work Order #, EPN, Fuel Tank 1 (A&B), Fuel Tank 2 (C&D), Engine Hours Stop, Engine Hours Start, Email To, Subject
Comment EPN = (Equipment Piece Number)
Comment Fuel Tank 1 (A&B) = (West)
Comment Fuel Tank 2 (C&D) = (East)
MOptions Type = Alarm, Trouble, ESP, Haz. Wx.,Problem, PM, Routine, Load Test, Other
MOptions Category = Engine, Generator, Controls, Fuel, Oil, HV Switchgear, MLG&W, Other
Options Engine = All, 1A, 2A, 3A, 4A, 5A, 1B, 2B, 3B, 4B, 5B, 1C, 2C, 3C, 4C, 5C, 1D, 2D, 3D, 4D, 5D, A Bus, B Bus, C Bus, D Bus, A&B Busses, C&D Busses, West Gen (001), East Gen (002)
Required Attributes = Type, Category, Subject
If time permits, I would appreciate any help possible.
BTW, I like the additional elcode. |
|
1424
|
Tue Oct 4 20:24:26 2005 |
| David Spindler | dsspindler@earthlink.net | Question | Windows | 2.5.7 | Re: Can't use the command-line client | | I just noticed in the changelog that my apparent problem with MOptions may have been fixed. I will try a newer version and see if it works. |
|