Last modified: 2014-07-23 04:59:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T8810, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 6810 - create <prose> tag
create <prose> tag
Status: REOPENED
Product: MediaWiki extensions
Classification: Unclassified
Extensions requests (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: Wikisource
  Show dependency treegraph
 
Reported: 2006-07-25 02:53 UTC by Ryan Dabler
Modified: 2014-07-23 04:59 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Quick and nasty hack of Poem extension (697 bytes, patch)
2006-07-25 03:32 UTC, Jude Brown
Details

Description Ryan Dabler 2006-07-25 02:53:40 UTC
There is currently a <poem> tag in use on MediaWiki, which allows for easy presentation of poem-
based texts.  This doesn't really help us when it comes to prose works, however, as (at least at 
Wikisource) the presentation is going to be very different.  If a <prose> tag could be added which 
would allow us to easily customize presentation of its text, that would be much appreciated.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-07-25 03:00:42 UTC
What's the intended difference between the prose text and ordinary untagged
text?  <poem> is somewhat different in its parser behavior from ordinary text,
in that it preserves certain types of spacing during parsing.
Comment 2 Ryan Dabler 2006-07-25 03:06:18 UTC
(In reply to comment #1)
> What's the intended difference between the prose text and ordinary untaggedtext? <poem> is somewhat 
different in its parser behavior from ordinary text,in that it preserves certain types of spacing during 
parsing.

A lot of CSS changes.  Paragraphs would be indented, the alignment would be justified, the width of the page 
would be drastically shortened so there would be fewer words per line.  There is an attachment for the 
proposal which will be added shortly.
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-07-25 03:11:05 UTC
So you're basically asking for <prose> to become an alias of <div
class="prose">?  Why not just use the latter?  It's only marginally longer to
type, and it doesn't require extensions to be padded on.  You could even just
restyle "#content p".
Comment 4 Ryan Dabler 2006-07-25 03:17:35 UTC
(In reply to comment #3)
> So you're basically asking for <prose> to become an alias of <divclass="prose">? Why not just use the latter? 
It's only marginally longer totype, and it doesn't require extensions to be padded on. You could even 
justrestyle "#content p".

Since this would be a site-wide style, it would be easier for newer/inexperienced users to not have to drudge 
through all the different classes that are available on Wikisource and know that one tag will present the text 
exactly as desired.  It's far more expedient to help get people into the flow of things.
Comment 5 Jude Brown 2006-07-25 03:32:43 UTC
Created attachment 2147 [details]
Quick and nasty hack of Poem extension

I have to agree with Ryan. Yes, it's not much shorter, but I think it's
inherently easier for new people to use something like <prose>...</prose> than
<div class="prose">...</div>. It also standardises all prose text into a single
class, which can then be altered in the style sheet, without having to go
through and find prose texts which use other classes or customised CSS tags.

Either way, here's an ugly hack that might do the trick.
Comment 6 Filip Maljkovic [Dungodung] 2006-07-26 18:09:49 UTC
And what about putting those div tags in templates?

{{prose start}}
Foo bar prose
{{prose end}}

This looks intuitive enough for me. No extension work! Alternatively, you could
use something like {{prose}} and {{prose.}} or something
Comment 7 Bryan Baron 2009-09-24 22:27:16 UTC
As stated above, it's better to use templates or a CSS class instead of an extension.
Comment 8 555 2014-02-10 16:17:56 UTC
The given solution isn't intuitive to newcomers.

Considering the current efforts to make editing *Wikipedia* a more intuitive expecience and the bug 52061, I'm boldly reopenning this bug.

Please also see https://bugzilla.wikimedia.org/show_bug.cgi?id=52061#c38
Comment 9 Andre Klapper 2014-02-10 16:43:41 UTC
lugosto: Why does this block bug 52061?
Comment 10 555 2014-02-10 17:03:20 UTC
Have you checked https://bugzilla.wikimedia.org/show_bug.cgi?id=52061#c38 ?
Comment 11 Andre Klapper 2014-02-11 09:43:49 UTC
This is not blocking fixing bug 52061 but it likely won't matter if this ticket is open or not, as long as nobody provides a patch.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links