Template talk:Graphic novel list

Latest comment: 4 months ago by Jonesey95 in topic Dark mode

Error message and tracking category for invalid ISBNs

edit

I have added an error message and tracking category for invalid ISBNs. – Jonesey95 (talk) 04:03, 11 March 2016 (UTC)Reply

@Jonesey95: problem with that is, it also registers an error when the field is left blank, such as when the English release date/ISBN for a manga volume has yet to be announced; see List of Yamada-kun and the Seven Witches volumes for example. Can you do something to fix that? Because it looks really ugly as it is. G S Palmer (talkcontribs) 21:39, 14 March 2016 (UTC)Reply
I noticed this also, and then I noticed that the template appears to automatically insert a dash for an empty ISBN. I adjusted the documentation accordingly. It currently reads: "If both LicensedRelDate and LicensedISBN are empty, the template will yield output appropriate for one-language view. Manually insert an em-dash (—) in LicensedRelDate (but leave LicensedISBN empty) to overcome this, if a two-language view is desired." I have fixed the article in question and a few like it. – Jonesey95 (talk) 21:45, 14 March 2016 (UTC)Reply
Many thanks. I didn't notice that someone had put dashes in the LicensedISBN parameters. My bad.  :) G S Palmer (talkcontribs) 13:19, 17 March 2016 (UTC)Reply

ISBN magic word

edit

This template uses ISBN magic words (e.g. ISBN 0123456789). It should be updated to use isbn templates (e.g. {{ISBN|0123456789}}. Headbomb {talk / contribs / physics / books} 17:48, 24 March 2017 (UTC)Reply

Pinging @Jonesey95 and G S Palmer: on this. Headbomb {talk / contribs / physics / books} 17:50, 24 March 2017 (UTC)Reply
Updated. Ping me if there are errors. I found and fixed one article already. – Jonesey95 (talk) 18:37, 25 March 2017 (UTC)Reply

Template change

edit

There seems to be a change in format that is making the width and columns of the template compact to the text. Using the width parameter seems to fix the former, but the columns remain off-center. Here's how it looks without the width parameter:

No. Original release date Original ISBN North American release date North American ISBN
1 20182018
  1. The First Chapter
  1. The Second Chapter
2 20182018
  1. The Slightly Longer Titled Third Chapter
  1. The Even Longer and, Depending on Your Taste, Unnecessarily Detailed Titled Fourth Chapter

User:SubZeroSilver (talk) 15:55, 21 August 2018 (UTC)Reply

The table above looks fine to me. What are you expecting? Do you have examples in actual articles? – Jonesey95 (talk) 18:30, 21 August 2018 (UTC)Reply
From where I'm looking, the break in the columns are no longer split down the middle of the box; instead, the breaks depend on the length of the displayed text, and the box should automatically fit to 100% size without the width parameter filled. And when bullet points are used, the text in the left column overlaps with the bullets on the right, which are black in color. Examples: List of One Piece chapters (1–186), List of The Seven Deadly Sins chapters. User:SubZeroSilver (talk) 19:39, 21 August 2018 (UTC)Reply
For good measure, here's another template that omits the width parameter:
No. Original release date Original ISBN North American release date North American ISBN
3 20182018
  1. The Fifth Chapter
  1. The Sixth Chapter

User:SubZeroSilver (talk) 21:09, 21 August 2018 (UTC)Reply

The header template was changed to remove the width parameter. I have reverted that change just now. That should fix it. – Jonesey95 (talk) 04:31, 22 August 2018 (UTC)Reply
If you want the columns to have similar widths, just make them relatively the same instead of the entire thing 100%. There's no reason for it to extend across the entire screen. ―Justin (koavf)TCM 04:35, 22 August 2018 (UTC)Reply
@Jonesey95: This edit would also have to be reverted, as it's causing a conflict with bulleted chapters overlapping in the table. See List of The Seven Deadly Sins chapters.-- 05:21, 22 August 2018 (UTC)Reply
You are correct. I have reverted that edit as well. Thanks for figuring it out. List of The Seven Deadly Sins chapters looks much better now. – Jonesey95 (talk) 08:04, 22 August 2018 (UTC)Reply

Thank you for the fix. User:SubZeroSilver (talk) 14:52, 22 August 2018 (UTC)Reply

ChapterList

edit

It's the age of responsive web design. So I think "ChapterListCol1" and "ChapterListCol2" should be abolished in favour of one "ChapterList" parameter, and instead, there should be a new parameter that defines minimum width of each column. Just look at how {{Div col}} does it with the "colwidth" parameter. JSH-alive/talk/cont/mail 14:12, 26 November 2018 (UTC)Reply

Interesting idea. We could probably just use {{Div col}} to put chapters in a single multi-column list. It would be useful for someone to add TemplateData to this template in order to get the monthly report that shows which articles use each parameter. That way, we would know how much work it would take to merge the ChapterList parameters together. – Jonesey95 (talk) 17:22, 26 November 2018 (UTC)Reply
On a related issue, are you aware that the bullet format and spacing for "ChapterList" and "ChapterListCol2" is different? eg Master_Keaton#Volumes How hard would this be to fix? Ozflashman (talk) 02:47, 31 January 2019 (UTC)Reply
I think I have fixed the formatting of the bullets so that it is consistent across both columns. Does it look better to you? – Jonesey95 (talk) 07:43, 31 January 2019 (UTC)Reply
Excellent, thanks very much for the prompt response, it also improves the legibility. Ozflashman (talk)

This report, which is generated each month, shows the parameters that are used in this template, and how many articles use each of the parameters. – Jonesey95 (talk) 18:25, 9 September 2019 (UTC)Reply

Template-protected edit request on 21 April 2019

edit

Please remove

{{Template sandbox notice}}

since the template is not a sandbox and shows nothing. Furthermore, if this was left over from copying the /sandbox over, the notice can just be added to the /doc page, but it need not be hardcoded into the template itself. Thanks, --DannyS712 (talk) 03:22, 21 April 2019 (UTC)Reply

  Done - FlightTime (open channel) 03:24, 21 April 2019 (UTC)Reply

TemplateData

edit

Jonesey95, per your request, I've started adding TemplateData to the template using the tutorial. I plan to add all parameters, as my bandwidth permits. Cheers. —⁠andrybak (talk) 07:38, 31 May 2019 (UTC)Reply

Thanks, I appreciate your work. – Jonesey95 (talk) 12:22, 31 May 2019 (UTC)Reply
  Done. Jonesey95, please check out the result and let me know if there are any issues. —⁠andrybak (talk) 07:47, 3 June 2019 (UTC)Reply
Thanks! I set up a reminder to myself to check the Template Data monthly report, which usually appears about eight or ten days after the first of the month. – Jonesey95 (talk) 08:45, 3 June 2019 (UTC)Reply

Error in adding information

edit

On this edit, I tried listing the ISBN and release dates for an omnibus version that was only released in English, but after saving it, the information appears on the original Japanese release columns as well. lullabying (talk) 18:57, 3 October 2019 (UTC)Reply

It looks like you added an |ISBN_note= parameter, which applies to the original-language ISBN cell. If you want a note in the Licensed (in this case English) ISBN cell, you need to use |LicensedISBN_note=. – Jonesey95 (talk) 21:08, 3 October 2019 (UTC)Reply

Could ISBN parameter be disabled ?

edit

Some releases do not have isbn, like Sao sidestories and American digital-only releases.

Proposed change to Graphic novel list/header

edit

I am proposing that the </table> tag found in {{Graphic novel list/footer}} be added to the {{Graphic novel list/header}} template as shown in these testcases using the sandbox I have made so that the list of {{Graphic novel list}} will go inside the {{Graphic novel list/header}} template making it simpler to add this template and its functionality would be more inline with {{Episode table}}. A change I also made was to add <abbr> tags to the No. header cell to display Number when a cursor is over it. I appreciate any input, thanks. Terasail[Talk] 20:55, 11 October 2020 (UTC)Reply

Template edit request 20 October 2020

edit

Consensus: I have assumed a consensus due to WP:SILENT, I listed the proposal on this talk page, at Wikipedia talk:WikiProject Anime and manga#Graphic novel list template update & Wikipedia talk:WikiProject Comics#Proposed change to Graphic novel list/header. With no response after over 7 days.

Change explanation: The changes here are

— Preceding unsigned comment added by Terasail (talkcontribs)

I have a couple of comments, neither of which relates to the code you have changed.
  1. I don't like the mixture of wikitable syntax and HTML syntax for the table, although it doesn't seem to be causing problems currently.
  2. I can't figure out why the </tr> is repeated in line 17, or why the </th> is repeated in line 10. Can you explain? (May be related to point 1.)
I have also adjusted the whitespace to improve readability — Martin (MSGJ · talk) 12:58, 21 October 2020 (UTC)Reply
@MSGJ: I don't really know much about this template, I just noticed some things in the template I didn't aggree with and decided to change them. I guess I could have a go at changing it to remove the html table tags if you think that would make the template better? Terasail[Talk] 19:43, 22 October 2020 (UTC)Reply
@MSGJ: The current sandbox is in the wikitext table style. I think it is the same but I am not certain... The way this template is currently, it is a bit hard to read with all the html tags.. Terasail[Talk] 20:42, 22 October 2020 (UTC)Reply
I didn't mean you had to do that! It wasn't your job. Anyway everything looks good.   Done — Martin (MSGJ · talk) 21:01, 22 October 2020 (UTC)Reply
@MSGJ: Ah well, if it helps, I don't mind doing it. And it will make it easier if anyone wants to propose a change in the future I guess... Terasail[Talk] 21:03, 22 October 2020 (UTC)Reply
  • @Terasail and MSGJ: It appears that the changes to the code broke the display of the table across an unknown number of articles. Here are some examples that I have come across: [1][2][3]. The issue seems to be specifically related to the "WithTitle" parameter (as removing the parameter seems to fix the problem). — Goszei (talk) 21:53, 24 October 2020 (UTC)Reply
@Goszei: Ah yes, I see the issue, I have just fixed it in the sandbox. Thanks for the notification. Terasail[Talk] 22:31, 24 October 2020 (UTC)Reply

Template error fix

edit

Hello, I have just fixed the error noted by Goszei above with the |WithTitle= activating if set to no.
Changes: Changed all the if statements for |WithTitle= to ifeq:...|yes in the sandbox Terasail[Talk] 22:33, 24 October 2020 (UTC)Reply

To editor Terasail:   done, and thank you very much! P.I. Ellsworth  ed. put'r there 07:50, 25 October 2020 (UTC)Reply

ISBN errors

edit

I'm working on Crimson Spell and the LicensedISBN parameter does not allow me to include more than one ISBN at the same time, whereas OriginalISBN allows me to do so using ISBN note.

On another note, is there a way to implement parameters like OriginalRelDate2, OriginalISBN2, LicensedRelDate2, etc. in the future? There are some series that have been reprinted under a different ISBN, such as volume 1 of Don't Be Cruel and The Cornered Mouse Dreams of Cheese, or have several different versions such as A Polar Bear in Love, Ao Haru Ride, etc. Moreover, just like in the issue mentioned above with Crimson Spell and Finder Series, there may be more than one English translation by different companies. lullabying (talk) 11:17, 15 December 2020 (UTC)Reply

I just realized I ran into the same issue before and had asked the same question here; apologies for asking again. However, I'll still leave my suggestion out here.lullabying (talk) 11:18, 15 December 2020 (UTC)Reply

Global Width change request

edit

Given the change of the page width in the new layout, is it possible for someone to change all Width=75% and 72% to 70% on all pages automatically, so the lists dont conflict with the infobox position? Smeagol 17 (talk) 20:30, 23 November 2022 (UTC)Reply

Can you please link to a page that demonstrates the problem that you are describing? How would changing the width by a few percentage points fix the layout, and would it affect readers using other skins? – Jonesey95 (talk) 21:35, 23 November 2022 (UTC)Reply
See for example: A Galaxy Next Door on the new (Vector 2022) skin. Try changing 72% to 70% and you will see. And no, it will not appreciably affect the old skin. Smeagol 17 (talk) 09:37, 24 November 2022 (UTC)Reply
Thanks. On my screen, I had to go below 70% in that article to get the table to display alongside the infobox in the Vector 2022 skin, with its foolish obsession with narrowing the part of the window that displays the actual content of an article. It still looks fine in Vector. I don't know that it is a good idea to manually adjust our content to accommodate stubborn WMF developers' insistence on degrading the readers' experience. One challenge is that infoboxes typically have a fixed width in pixels, which is not directly compatible with the use of width percentages in block content placed alongside the infobox. Ideally, infobox widths would be set to a maximum width of maybe 23% (for example) to allow other content to be set up to 75%. This could be a massive change to Wikipedia layout "standards", however, and would have many consequences for other content. – Jonesey95 (talk) 15:07, 24 November 2022 (UTC)Reply
Yes, but the things I want changed are already adjusted to the old skin with the similar problem. And the information in them mostly wont degrade in readability with this width reduction (given the nature of most articles with this problem). I just wanted to know if there is a method to do the change automatically. Given thet I don't want the readers with the newest layout (like myself, as I took upon myself to test it) to see broken articles. (It is not the only problem of it, of course. For example, different chapter title lengths in ChapterList result in the use of ChapterListCol2 in some cases making the right column higher in the new skin, which was not intended.) Smeagol 17 (talk) 16:13, 24 November 2022 (UTC)Reply
Descriptions of what is happening in specific cases are simply not useful without links to examples. – Jonesey95 (talk) 16:41, 24 November 2022 (UTC)Reply
See for example. [[4]] (volumes 18 and 19 on the new skin) But that is a much more minor problem then this.
So. Is there an option for an automathic width change or shall I continiue to fix this manually? Smeagol 17 (talk) 16:49, 24 November 2022 (UTC)Reply
I do not see anything unusual with volumes 18 and 19 in that table. I see that the right column is four lines longer than the left column when it seems like there is room for them to be the same length, but that the opposite effect is visible in chapter 17, where the left column is three lines longer than the right one. It looks better when I hide the table of contents and let the content use more of the window's width. This column-length difference appears to happen because someone has manually separated the list items into columns, preventing the Wikipedia renderer from choosing the right balance for the columns. If the template were programmed to automatically generate two columns, the rendering would probably look better in all skins. If you manually move one or more items from one column to the other, you will fix the problem in your preferred skin but make it look worse in other skins. – Jonesey95 (talk) 17:06, 24 November 2022 (UTC)Reply
This template can create and balance columns automatically? How? (And also, you have not answered my question.) Smeagol 17 (talk) 17:12, 24 November 2022 (UTC)Reply
Here is an example of how to distribute content automatically between two columns. As for your question about automatic width change, the optimal outcome (with possible negative side effects) would be to prevent the Vector 2022 skin from narrowing content. Another option would be to change {{Infobox animanga/Header}} to use a percentage width instead of the current fixed width: 22em. Barring that, I think that adjusting the width manually in each article is your only choice for now. If you figure out how wide the Vector 2022 screen is in em units, that might work best. – Jonesey95 (talk) 18:22, 24 November 2022 (UTC)Reply
Thanks. Smeagol 17 (talk) 22:57, 24 November 2022 (UTC)Reply

Getting ISBNs and release dates for two different English versions?

edit

At Yo-kai Watch (manga) I found that the United States English ISBNs and release dates were already there. I wanted to add such dates for the Singapore English version, which has separate ISBNs and release dates. However the template seems to allow for only one English version to be listed. How may I deal with this?

Thank you, WhisperToMe (talk) 21:38, 24 April 2023 (UTC)Reply

Add Translator Field

edit

Sorry if this is utterly in the wrong place, but could we get a parameter for the translator? I'd like to put translator information in for light novels/manga, but they sometimes change per volume so it might make sense to put it in the table. Erynamrod (talk) 20:07, 19 December 2023 (UTC)Reply

Edit request: remove extra table row

edit

As reported at Wikipedia:Village pump (technical)#REST API returning HTML that doesn't exist in standard page, this template generates an extra empty table row below the heading when using the new Parsoid parser.

To remedy that, please apply this change from the sandbox: [5]. Matma Rex talk 16:03, 15 February 2024 (UTC)Reply

  Done Nardog (talk) 16:07, 15 February 2024 (UTC)Reply

Suggestion

edit

While updating the pt:Predefinição:Volume de mangá/Cabeçalho template, I came across something I'd like to suggest for implementation here. At the moment, parameters like |OneLanguage= and |WithTitle= are case-sensitive. It can be easily fixed if we replace, for example, {{#ifeq:{{{WithTitle|}}}|yes|24|48}} with {{#if:{{yesno|{{{WithTitle|}}}}}|24|48}}.

This way, even values like y and true would be accepted. Vinickw 16:52, 17 April 2024 (UTC)Reply

Dark mode

edit

Some text in the template appears black in The new dark mode. أحمد الناصر (talk) 16:34, 11 July 2024 (UTC)Reply

I think I have fixed it. If not, please link to an affected article and say which text is the wrong color. – Jonesey95 (talk) 17:08, 11 July 2024 (UTC)Reply