Long lines in printout, posted by Bertram Metz on Wed Aug 10 10:50:55 2005
|
Hi,
long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer. Does anybody know a solution for this?
Thanks,
Bertram |
Re: Long lines in printout, posted by Stefan Ritt on Mon Sep 5 20:39:15 2005
|
> long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> Does anybody know a solution for this?
Can you post an example here? If I try a
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
long line, it's shown correctly. You just have to scroll right in your browser. |
Re: Long lines in printout, posted by Bertram Metz on Mon Sep 12 10:44:51 2005 
|
> > long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> > text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> > Does anybody know a solution for this?
>
> Can you post an example here? If I try a
>
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
> long line, it's shown correctly. You just have to scroll right in your browser.
the lines are displayed as expected on the screen, but they are cut off when the browser window is printed via
the browsers print function.
This did not occur in a previous version (V2.5.6).
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Tue Sep 13 13:33:59 2005
|
Your problem is related with the fact that I changed the formatting from fixed font to proportional font ("ELCode"). This gives you three options:
- Enter your elog entries in "plain" text, which brings you back to the old mode
- Change the page setup of your browser. Mozilla Firefox has File/Page Setup/Shrink to fit page and left and right margin
- Reduce the entry window via the config setting "Message width"
|
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 10:56:29 2005
|
Hi Stefan,
I tried your suggestions with 'page shrinking' and 'message width', but they didn't help. What I do not understand is why this problem occurs only if the message text is formatted as plain text. The lines are printed correctly, if the text is formatted as EL code or as HTML.
It is of course possible to format new entries in EL code or HTML, but we have a lot of existing entries, which are formatted as plain text.
Kind regards,
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 11:19:09 2005
|
Ok, I found the problem. In the default.css file, you will find a section
.messagepre {
font-family:'lucida console',courier,monospace;
font-size:10pt;
}
Just go and delete the line with the font-size, this should fix your problem. If the font-size is fixed, the browser cannot resize the text to fit into your printing page. I still have problems with IE, but with Firefox it works fine if you select Shrink to fit page width on the page setup. |
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 13:27:02 2005
|
The lines are still cut, if printed on paper.
I played again with the 'message width' parameter, which actually the key parameter in my problem. I saw in the source, that the default value is now 112, but it was 76 in the elog version we'd used previously (V2.5.2). If I set 'message width' to 76 again, it works fine for new entries!
I wrote in the previous reply, that changing 'message width' didn't help. That seems to be the case for entries, which are re-submitted. For new entries it works.
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 13:51:55 2005
|
| Bertram Metz wrote: | | The lines are still cut, if printed on paper. |
Are you sure? After you change the CSS file, you have to reload the page. I just tried with the very long entry from this thread and got in the Firefox preview window the picture which I attached. The font size of the text body is shrunk such that all lines (except the one very long line) fit on the paper. |
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 17:45:58 2005
|
You're right. I don't know what I've tested this afternoon 
Without the fixed font the text might get very small, if the line is too long.
I think we'll set 'message width' = 76.
Thanks a lot Stefan! |
|
Trying to remove "mailto:" from the email address, posted by Matt Kimball on Wed Oct 12 23:59:13 2005
|
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.
Thanks
Matt |
|
Re: Trying to remove "mailto:" from the email address, posted by Stefan Ritt on Thu Oct 13 08:32:20 2005
|
| Matt Kimball wrote: | | We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file. |
The "mailto:" is there for good reason. After you submit the entry, elogd converts the "mailto:" into
<a href="mailto:user@domain.com">user@domain.com</a>
so the browser shows the email address as a link. If you click it, the browser automatically opens your email client with the email address already in the "To:" field. The same works in the main text body. So if I put "mailto:stefan.ritt@psi.ch", it gets converted automatially to "stefan.ritt@psi.ch", a feature many people rely on.
Now from your request it looks to me like you want email notifications, so you put
Email System CareWare = ..., $user_email
In that case the "mailto:" gets automatically stripped during the email notification, so the user_email gets entered and will be used correctly for the notification. |
|
elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Fri Sep 23 17:27:40 2005
|
| I can't seem to connect using elog: elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt it run fine through the web interface on http://<myhost>:8080/Servers I have URL = http://<myhost>:8080 in my elogd.cfg Any clues what I'm doing wrong? Thanks for any help. ScottK |
|
Re: elog fails to connect with "cannot get host name: Success" message, posted by Stefan Ritt on Wed Oct 5 13:24:52 2005
|
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
Re: elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Tue Oct 11 15:09:42 2005
|
| Stefan Ritt wrote: |
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
Oops - amazing when I read the syntax correctly -- it works! Thanks for taking the time to reply to a "dumb, RTFD" question, Stefan. Thank you for making a great program!
ScottK |
Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Sun Oct 9 20:43:31 2005
|
| As the title. |
|
Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Mon Oct 10 14:01:14 2005
|
| Exaos Lee wrote: | | As the title. |
There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page. |
|
Re: Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Mon Oct 10 19:33:05 2005
|
| Stefan Ritt wrote: |
| Exaos Lee wrote: | | As the title. |
There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page. |
Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly. |
|
Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Tue Oct 11 09:24:12 2005
|
| Exaos Lee wrote: | | Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly. |
A way around that problem would be to use user level access (via the Password file = ... and Admin user = ... settings). Can you try if that works under a Chinese logbook? |
Some spell mistakes, posted by Exaos Lee on Sun Oct 9 20:49:41 2005
|
I find some new strings from the warnings like this:
| Quote: | | Language error: string "HelpELCode" not found for language "chinese" |
I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink". |
|
Re: Some spell mistakes, posted by Stefan Ritt on Mon Oct 10 14:09:49 2005
|
| Exaos Lee wrote: | I find some new strings from the warnings like this:
| Quote: | | Language error: string "HelpELCode" not found for language "chinese" |
I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink". |
Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much. |
|
Re: Some spell mistakes, posted by Exaos Lee on Mon Oct 10 19:26:35 2005
|
| Quote: | | Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much. |
Sorry. I will mail you first next time. |
Install error on MacOS X, posted by Exaos Lee on Mon Oct 10 19:22:51 2005
|
Executing "make" on MacOS X is OK, but "make install" failed due to the following error:
/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
/usr/bin/install -m 0755 -o bin -g bin elog elconv /usr/local/bin
install: bin: Invalid argument
make: *** [install] Error 67
The reason is that the account "bin" and group "bin" are missing on MacOS X. I also found that the following lines in "Makefile" doesn't work:
ifeq ($(OSTYPE),darwin)
CC = cc
endif
I have fixed this problem. The diff of Makefile as following:
diff Makefile.darwin Makefile.origin
====================================
24,25d23
< BINOWNER = bin
< BINGROUP = bin
30,31d27
< OSTYPE = $(shell uname)
<
40,43d35
< ifeq ($(OSTYPE),Darwin)
< OSTYPE=darwin
< endif
<
46,47d37
< BINOWNER = root
< BINGROUP = admin
89,90c79,80
< $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elog elconv $(DESTDIR)
< $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elogd $(SDESTDIR)
---
> $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
> $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)
The modified Makefiles have been attached. |
|
Display Attribute no longer works in Beta 5?, posted by Ulrich Trüssel on Fri Oct 7 08:53:00 2005
|
Just changed from Beta 2 to Beta 5:
I'm using Display Attribut = [elog:$logbook/$message id] as a reference link for other entries (ex.: Display Referenz = [elog:$logbook/$message id]). also see the attached elogd.cfg file.
With Beta 2 (not testet with Beta 3 or 4!) this worked very well -> see attached Display Attribute with 260-b2.jpg file.
With Beta 5 is seems no longer to work -> see attached Display Attribute with 260-b5.jpg file.
ANy ideee what's wrong in my elogd.cfg??? Thanks! |
|
Re: Display Attribute no longer works in Beta 5?, posted by Stefan Ritt on Mon Oct 10 13:57:20 2005
|
This option has been changed on July 25th from "Display <attribute>" to "Change <attribute>" which is a more appropriate expression. The documentation has also been updated. |
The Chinese Language,Demo Configuration and Help Files, posted by Exaos Lee on Sun Oct 9 20:18:23 2005
|
Hi, Stefan,
The days from Oct.1~7 are our Nation Day's vacation, so I delayed the translation to Chinese. I just finished these files today:
- eloglang.zh_CN-GB2312 : This is for simplified Chinese using GB2312 encoding.
- eloglang.zh_CN-UTF-8 : This is for simplified Chinese using UTF-8 encoding.
- eloghelp.zh-CN.html : Help file for elog in simplified Chinese.
- elcode_zh-CN.html : The help file for ELCode in simplified Chinese.
- elogd-zh_CN-GB2312.cfg : Demo configuration file for simplified Chinese with GB2312 encoding.
- elogd-zh_CN-UTF-8.cfg : Demo configuration file for simplified Chinese with UTF-8 encoding.
I have to provide the language files in different encodings because the elogd cannot creat new logbook file named in Chinese with GB2312 encoding under MacOS X. The default charset under MacOS X is UTF-16, and elogd works with UTF-8 while processing Chinese contents and logbooks named in Chinese.
I want to make elogd display the date in Chinese format. Please tell me howto.
Thanks. |
|
Re: The Chinese Language,Demo Configuration and Help Files, posted by Stefan Ritt on Mon Oct 10 12:53:46 2005
|
| Exaos Lee wrote: | | I want to make elogd display the date in Chinese format. Please tell me howto. |
Thank you for the files.
If you specify
Language = zh_CN
Then elogd looks for a file "eloglang.zh_CN" for the translation, for a file "eloghelp_zh.html"
for the help, and does a
setlocale("zh_CN");
to switch to Chinese date format. To retrieve the date, elogd calls strftime("%x"); |