[opensuse-buildservice] Fwd: Re: [yast-devel] Displaying Package Descriptions
The Web interface does not honor the "traditional" markup-less
formatting of the package descriptions. Simply replacing every
\n with <br /> leads to strange results.
Instead, please replace \n\n with </p><p> (paragraph end and start,
iff a paragraph follows). Another rule is, lines starting with *
are unordered list items.
Maybe, there are more rules. Please, coordinate with the yast
developers.
I'm sorry about these ambiguities, but it is often hard to convince
developers to use a proper markup language...
----- Forwarded message from ke@suse.de -----
Date: Thu, 09 Sep 2010 13:43:33 +0200
From: Karl Eichwalder
Johannes Meixner
writes: On Sep 8 04:42 Tim Serong wrote (shortened):
# rpm -q --qf '%{DESCRIPTION}' $PACKAGE | sed \ -e 's/\&/\&/g' \ -e 's/\</g' \ -e 's/>/\>/g' | awk \ 'BEGIN { print "<pre>" } { print } END { print "</pre>" }'
Thanks, but <pre> is a no-op. These days, various PDAs with small displays are in use, and then, there is this ncurses yast interface...
BTW, the BS is also one of these "players" and it keeps line-breaks, but uses a proportional font... For example, see https://build.opensuse.org/package/binary?arch=i586&filename=opensuse-manuals_en-11.3-31.1.noarch.rpm&package=opensuse-manuals_en&project=Documentation&repository=openSUSE_11.3 This is why formatted text without self-explaining markup sucks. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org ----- End forwarded message ----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 10. September 2010, 07:49:28 schrieb Karl Eichwalder:
The Web interface does not honor the "traditional" markup-less formatting of the package descriptions. Simply replacing every \n with <br /> leads to strange results.
Instead, please replace \n\n with </p><p> (paragraph end and start, iff a paragraph follows). Another rule is, lines starting with * are unordered list items.
Maybe, there are more rules. Please, coordinate with the yast developers.
I'm sorry about these ambiguities, but it is often hard to convince developers to use a proper markup language...
Where do you want to get this replacement exactly ? The descriptions in project and package view do not end in the spec file. You can of course edit the spec file with the webui file editor like any other file, but we can't do the replacement there easily, because you can edit also other sections of the spec file. So what I am saying is that we don't have any special interface for package descriptions only atm. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Fri 10 Sep 2010 08:01:21 AM CEST schrieb Adrian Schröter
The descriptions in project and package view do not end in the spec file. You can of course edit the spec file with the webui file editor like any other file, but we can't do the replacement there easily, because you can edit also other sections of the spec file.
Ok, thanks, I see. I probably must discuss it on the packagers' list first. We must figure out whether they want to stay with the traditional formatting. ATM, package descriptions are rather bewildered and in yast they often look bad ;-( -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter
-
Karl Eichwalder