wrap "pre" tag in a "div" with fixed width, posted by Andrey Pashnin on Wed Jan 4 11:39:39 2023 
|
I'm sorry for being annoying...
but I have tried to wrap the <pre> tag in a <div> and it seems to do the trick
(the text is a single line with repeating aaa-b-cc sequence)
In the READ mode, the width is limited by the div's width
(see the first attachment)
In the EDIT mode, the width is only limited by the textarea width
(see the second attachment)
All this is with "wrap=hard" removed. |
wrap "pre" tag in a "div" with fixed width, posted by Stefan Ritt on Wed Jan 4 12:17:46 2023
|
Didn't work for me. The text is just truncated after the width and no extra lines are added. |
wrap "pre" tag in a "div" with fixed width, posted by Andrey Pashnin on Wed Jan 4 14:05:25 2023
|
Sorry, I forgot to mention that I also added some styles to the <pre> tag:
style="white-space: normal"
(see the screenshot on my previous post) |
wrap "pre" tag in a "div" with fixed width, posted by Stefan Ritt on Wed Jan 4 14:23:12 2023
|
> Sorry, I forgot to mention that I also added some styles to the <pre> tag:
> style="white-space: normal"
> (see the screenshot on my previous post)
Actually the
style="white-space: normal"
makes the difference, the <div> is not necessary at all!
But I'm not sure that "white-space: normal" is what we want. All manual line breaks in an entry are collapsed and you get just one text block without any new line. See here
https://developer.mozilla.org/en-US/docs/Web/CSS/white-space
I guess we want "white-space: pre-wrap" which keeps the old line breaks.
You can try that out by changing elog.css:
--- a/themes/default/elog.css
+++ b/themes/default/elog.css
@@ -475,6 +475,7 @@ td {
.messagepre {
font-family:'lucida console',courier,monospace;
+ white-space:pre-wrap;
}
and see the effect. If you like it, just keep it. No need to recompile elogd.cxx.
Stefan |
width of the textarea is too large (after reply), posted by Heiko Scheit on Mon Aug 4 14:02:52 2003
|
The width of the textarea after pressing reply is too large.
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
number of characters in the text to be the width of the longest line.
To search for '\n' instead should solve the problem. Please find the
diff output below.
$ diff -c elogd.c elogd.c~
*** elogd.c Mon Aug 4 13:57:35 2003
--- elogd.c~ Fri Aug 1 13:13:09 2003
***************
*** 6028,6035 ****
p = text;
do
{
! /* pend = strchr(p, '\r'); */
! pend = strchr(p, '\n');
if (pend == NULL)
pend = p+strlen(p);
--- 6028,6034 ----
p = text;
do
{
! pend = strchr(p, '\r');
if (pend == NULL)
pend = p+strlen(p);
|
width of the Text column in the summary list view, posted by Fabio Rossi on Fri Nov 6 12:49:22 2009
|
I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.
Which is the way to set the number of character displayed? |
white-space: pre-wrap", posted by Andrey Pashnin on Wed Jan 4 14:38:54 2023
|
> I guess we want "white-space: pre-wrap" which keeps the old line breaks.
Yep. You're right. Thanks! |
whishlist direct shortcut to select a files or folder (not http), posted by Etienne Van Caillie on Wed Dec 3 06:32:09 2003
|
whishlist
an entry like
file:///E:/Dossier\!!shorcut
will open IE with these current adresse
Stef could you add a logbook
'wishlist'
'subgroup' contribution/icons |