Hello,
the (column) width of the table is not set.
El Perú, con el tratado, buscaba que resguardar sus ricas salitreras de Tarapacá; pero no sólo ello, sino apuntaba también, a impedir la competencia del salitre boliviano que se encontraba en poder de los capitales chilenos y británicos. |
Peru, with the treaty, sought to protect its rich nitrate fields in Tarapaca, but not only that, it sought to impede the competition of the Bolivian saltpeter produced by Chilean and British investors. |
—Reyes Flores, Alejandro (1979). La Guerra del Pacífico (1979 ed.). Lima, Peru: Universidad Nacional Mayor de San Marcos. p. 97. | —translation attribution |
It could be better:
Peru, with the treaty, sought to protect its rich nitrate fields in Tarapaca, but not only that, it sought to impede the competition of the Bolivian saltpeter produced by Chilean and British investors. | (Orig. Spanish:) El Perú, con el tratado, buscaba que resguardar sus ricas salitreras de Tarapacá; pero no sólo ello, sino apuntaba también, a impedir la competencia del salitre boliviano que se encontraba en poder de los capitales chilenos y británicos. ... |
Alejandro Reyes Flores in "Relaciones Internaconales en el Pacífico Sur", page 110 |
--Keysanger (talk) 10:01, 18 September 2016 (UTC)
I have the same problem! Fixed width of 50% would be good! C-Kobold (talk) —Preceding undated comment added 19:35, 23 February 2019 (UTC)
I've written about this at length in an essay, but the colon should not be used to indent text. The syntax is strictly for definition lists, it pollutes the HTML which reduces accessibility, and is semantically incorrect. It is far more appropriate to use CSS in a template and the documentation here even notes an equivalent. Better yet, the template should instead be enclosed in the <blockquote>
tag instead as that is much more semantically appropriate and would automatically format the verse alike with other quotes. Opencooper (talk) 06:24, 12 February 2017 (UTC)
<poem>
tags, which translate colons into spaces. The wikitext looks like it has deflist definitions without corresponding deflist terms, but the resulting HTML does not. I agree that it ought to use <blockquote>
for semantic reasons. Hairy Dude (talk) 03:52, 22 January 2019 (UTC)Perhaps some line breaks should be added to the "Full example" so that the "Markup" does not overlap with the "Renders as", making them both illegible. Hyacinth (talk) 03:16, 10 September 2018 (UTC)
Would someone please look at Gevninge helmet fragment#Context and Beowulf and see if this template is displaying correctly? It used to for me, but as I see it now (in both Firefox and Chrome) the Old English text is lumped together into two paragraphs; the line breaks only appear for the English translation. The same template displays fine for me in such articles as Benty Grange helmet#Boar-crests in Beowulf and Sutton Hoo helmet#Beowulf. Thanks, --Usernameunique (talk) 16:21, 26 September 2018 (UTC)
The documentation states that "The indentation provided automatically in this template is approximately equal to <blockquote>
and <poem>
". There are three ways in which this sentence is misleading:
<blockquote>
;<blockquote>
is not merely indentation: there's a dark grey stripe on the left, and font size is increased, which makes them visually distinct.The template ought to remove the indentation so that a <blockquote>
can be added manually, or else add one automatically. Hairy Dude (talk) 03:57, 22 January 2019 (UTC)
The template ought to remove the indentationand that using table columns for the side-by-side presentation is sub-optimal. Instead,
style="float:left;"
should be added to each <poem>...</poem>
, with a terminating ((Clear|left))
, of course. -- Michael Bednarek (talk) 05:29, 8 February 2019 (UTC)
So I have run into a situation at Nestor's Cup (mythology) and could use some advice.
I want to quote part of the Iliad with a translation, and this template seemed like the correct way to do so. However, because the translation is in prose, the text of the translation squashes the original over to the side, which results in each line of the poem being shown over two lines (on my 1080p screen, full screen, as a logged-out user with default settings: different skins and window sizes change this). If the window is big enough, it would obviously be desirable that this not occur.
((verse translation))
?The two obvious work-arounds are to use a different translation which is in verse (possible in this case, but not necessarily always, and there is not always an equivalently good verse translation available), or to insert artificial line breaks into the translation (which, depending on where the line breaks are, leads to different effects at different window sizes, and seems generally undesirable...) Caeciliusinhorto (talk) 17:33, 5 September 2019 (UTC)
This is a very useful template! Is there an equivalent template that handles three or four columns, or is it possible to extend this one to do so? There are some articles with beastly (and error-laden) markup that could use such a thing. pauli133 (talk) 13:06, 23 December 2019 (UTC)
PERSIAN |
LITERAL TRANSLATION |
It would be nice if this template could use an HTML class for its content so that users could style it in their CSS or userscripts could target it, etc. Something like {| class="verse-translation"
maybe? Opencooper (talk) 15:39, 17 July 2020 (UTC)
When browsing Wikipedia on mobile, I have seen this template break the poem text into unreadable, narrow strips. Because of the wide usage of this template, and of mobile Wikipedia, I think this is a urgent issue. I was planning to fix it by making the poems stack vertically under a certain width, using media queries and template styles to restyle the td
elements as blocks. However, I realised this would not work for poems with attributions, because the cell for attr1
would end up in the wrong place, wedged between the translation and attr2
. Does anyone have any other ideas for how to deal with this? A temporary solution might be to implement this only for instances without poem attribution. --small jars tc
19:26, 27 June 2022 (UTC)
tc
09:27, 4 September 2022 (UTC)Block styling works! The only issue left is that it looks the same as surrounding text. Did a temporary fix by giving it a tiny bit of padding, but personally I would prefer something like a combination of <blockquote>...</blockquote>
and ((Flex columns))
. Artoria2e5 🌉 00:41, 25 November 2022 (UTC)
tc
10:46, 26 November 2022 (UTC)The verse in this is, unfortunately, somewhat broken in mobile browser view, as in: if the translated text is longer/has more lines than the original text then the original line and the corresponding translated line are "misaligned" in that they are not next to each other/not in the same row. Like this:
Original | Translation | ||
---|---|---|---|
Verse1 | Translation1 | ||
Verse2 | Translation2 which is long and | ||
Verse3 | "bleeds" into the next row and thus breaks the verse | ||
Translation3 |
Here's an example in an article: Straja Țării. Open the article via mobile browser to see the problem. Nakonana (talk) 14:24, 9 December 2023 (UTC)
tc
20:29, 13 April 2024 (UTC)
The majority of template parameters claimed by this template's documentation simply do not exist in the code at all, including the heading parameters, and all the ones for language, RTL, and related matters for the second (righthand-side) text.
Do we want these parameters implemented (I can do that), or do we want the claims that they exist to be removed from the documentation? I'm presuming the former, but can make it happen either way. — SMcCandlish ☏ ¢ 😼 02:34, 14 May 2024 (UTC)
|lang1=
alias had something to do with the issue was incorrect, and I've restored the alias. It's been sandboxed, and everything works fine. — SMcCandlish ☏ ¢ 😼 11:43, 19 May 2024 (UTC)