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 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 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 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! |
Attachments in duplicated entries, posted by Bertram Metz on Thu Dec 8 10:32:37 2005
|
Hi,
the duplicate command duplicates the entry text itself, but it does not duplicate attachments.
If attachments in a duplicated entry are deleted, the original attachment files are deleted as well and cannot be accessed anymore within the original entry.
My suggestion is to copy the attached files too and to use file names of the copies in the duplicated entry.
Kind regards,
Bertram |
Re: Attachments in duplicated entries, posted by Bertram Metz on Tue Jan 24 14:39:21 2006
|
| Stefan Ritt wrote: |
| Bertram Metz wrote: | The duplicate command duplicates the entry text itself, but it does not duplicate attachments. If attachments in a duplicated entry are deleted, the original attachment files are deleted as well and cannot be accessed anymore within the original entry.
My suggestion is to copy the attached files too and to use file names of the copies in the duplicated entry. |
I chaned it such that attachments are removed from the duplicated entry, which was easier to implement. I hope this is ok as well. The change is in SVN revision 1584. |
Yes, that's ok for me.
Thank you very much Stefan.
Best Regards,
Bertram |
Email notification (bug tracking system), posted by Bertram Metz on Fri May 5 14:49:19 2006
|
Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
Re: Email notification (bug tracking system), posted by Bertram Metz on Thu Nov 30 16:07:54 2006
|
| Stefan Ritt wrote: |
| Bertram Metz wrote: | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo
You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754. |
Thank you very much Stefan,
that works fine for me!
Bertram |
|