Help talk:Citation Style 1
Add topicTemplate:BotsTemplate:Skip to bottomTemplate:Talk header Template:Central Template:WikiProject banner shell User:ClueBot III/ArchiveThis Template:FAQ
Support for trans-series and trans-publisher
{{cite book |last1=Hiriart-Urruty |first1=Jean-Baptiste |last2=Lemaréchal |first2=Claude |author-link2=Claude Lemaréchal |year=1993 |chapter=XII Abstract duality for practitioners |title=Convex analysis and minimization algorithms, Volume II: Advanced theory and bundle methods |series=Grundlehren der Mathematischen Wissenschaften |trans-series=Fundamental Principles of Mathematical Sciences |volume=306 |publisher=Springer-Verlag |location=Berlin |pages=136–193 (and bibliographical comments on pp. 334–335) |isbn=3-540-56852-2 |mr=1295240}}{{cite journal | last1 = Hallgrímsson | first1 = Helgi | last2 = Eyjólfsdóttir | first2 = Guðríður Gyða | date = 2004 | language = Icelandic | title = Íslenskt sveppatal I - smásveppir | trans-title = Checklist of Icelandic Fungi I - Microfungi | journal = Fjölrit Náttúrufræðistofnunar |trans-journal=Polygraph of the Institute of Natural Sciences | publisher = Náttúrufræðistofnun Íslands |trans-publisher=Natural History Institute of Iceland | location = Reykjavík}}
Gives
- Lua error in package.lua at line 80: module 'Module:Citation/CS1/Suggestions' not found.
- Template:Cite journal
Headbomb {t · c · p · b} 16:38, 14 September 2025 (UTC)
- A "trans-series" parameter would be helpful. I just came to this page for the same reason—it would be helpful for Rex Raab's 1993 biography cited in the article on Edith Maryon, where "trans-title" works but "trans-series" does not. The former is obviously more important, but the latter would be a bonus. --Usernameunique (talk) 03:52, 30 September 2025 (UTC)
- What about
|script-publisher=and|script-series=? -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 12:51, 30 September 2025 (UTC)
i18n: Translatable texts from Module:Citation/CS1
- 'character' is translatable.
err_msg = char_name .. ' ' .. 'character';
- 'Wikidata', 'Wikisource' and 'Wikipedia' are translatable.
local proj_name = ({['d'] = 'Wikidata', ['s'] = 'Wikisource', ['w'] = 'Wikipedia'})[proj]; -- :w (wikipedia) for linking from a non-wikipedia project
- '-name-list parameters' is translatable.
utilities.set_message ('err_redundant_parameters', err_name .. '-name-list parameters'); -- add error message
- A single space between
Minutesandcfg.messages['minutes']should be optional, since some languages do not require a space between them. For example, in Korean, "23 minutes in" is translated as "23분부터", not "23 분부터". (The same goes for Japanese, where they created separate module for i18n. See ja:Module:Citation/CS-ja and ja:Module:Citation/CS-ja/Configuration)
Position = " " .. Minutes .. " " .. cfg.messages['minutes'];
- 'citation' (the second one) and 'cite ' are translatable. In addition, in Korean, the 'cite *' series is translated as '* 인용', such as 웹 인용 or 서적 인용. (Same for tr:Şablon:Web kaynağı, etc.) So there should be an option for swtiching the order of 'cite ' and
config.CitationClass.
local template_name = ('citation' == config.CitationClass) and 'citation' or 'cite ' .. (cfg.citation_class_map_t[config.CitationClass] or config.CitationClass);
So, it would be much better if these literal strings were moved to the /configuration and given a slight adjustment to improve i18n. Thanks.--Namoroka (talk) 02:36, 20 September 2025 (UTC)
- Thanks for finding those. Fixed in the sandbox, I think. Examples in the same order:
- for invisible characters:
- for interproject wikilink annotations:
- For redundant author/editor parameters:
- for 'minutes in' in-source location:
- for error message, maint message, and preview message annotation (Template:Tld same as
{{cite book}}annotations above):
- for error message, maint message, and preview message annotation (Template:Tld same as
- —Trappist the monk (talk) 19:12, 21 September 2025 (UTC)
- Please move also "(empty string)". And
cfg.messages['archived-unfit']should have place-holder. FlatLanguage (talk) 05:10, 26 September 2025 (UTC)- And
cfg.messages['inactive']. --FlatLanguage (talk) 06:19, 26 September 2025 (UTC) - 'empty string' done:
{{cite book/new |title=Title|=}}
- I don't know what you mean by Template:Tq.
- —Trappist the monk (talk) 18:20, 4 October 2025 (UTC)
- And
- Please move also "(empty string)". And
What's the point of "Script title" parameter?
And while it might have been answered here before - pretty please, add that explanation to the documentation of templates that use this paramter (like Template:Cite web). It should be obvious from readng the doc (and it very much isn't now; as in - why use this field if the Chinese etc. scripts display perfectly fine in regular title field?). Piotr Konieczny aka Prokonsul Piotrus| reply here 02:40, 30 September 2025 (UTC)
- Ctrl + F finds the following (eventually) in the cited template documentation:
script-title: Original title for languages that do not use a Latin-based script (Arabic, Chinese, Cyrillic, Greek, Hebrew, Japanese, Korean, etc); follows Romanization defined in title (if present). Must be prefixed with one of the supported language codes to help browsers properly display the script:
... |title=Tōkyō tawā |script-title=ja:東京タワー |trans-title=Tokyo Tower ...- I suppose we might adjust this to say that script-title is only needed when italics would otherwise be output (which may be a general adjustment), as CS1 might for the name of a book or website. Izno (talk) 03:05, 1 October 2025 (UTC)
- One thing I hate about the |script parameters is that they strip things like quotation marks from article titles. Snowman304|talk 00:32, 4 October 2025 (UTC)
- In addition to avoiding italics for Chinese characters etc in book titles, this allows one to also give the romanized title in
|title=. Kanguole 07:30, 1 October 2025 (UTC) - Template:Cite web#csdoc_script-title. --Redrose64 🌹 (talk) 20:16, 1 October 2025 (UTC)
- @Izno @Redrose64 I did see that, but I did not realize italics would be a problem - this needs to be clearly explained in the text. Should title field be empty for Chinese and similar languages? This is very much still uncledar to me (and there is even an error prompt when saving the template about title field being empty). Piotr Konieczny aka Prokonsul Piotrus| reply here 02:49, 2 October 2025 (UTC)
- PS. I noticed this problem when c/e a ref here. In the past I've always seen and included Chinese / Korean titles in the title field, and I can't recall I've ever seen this parameter used until today. Piotr Konieczny aka Prokonsul Piotrus| reply here 02:50, 2 October 2025 (UTC)
- @Izno @Redrose64 I did see that, but I did not realize italics would be a problem - this needs to be clearly explained in the text. Should title field be empty for Chinese and similar languages? This is very much still uncledar to me (and there is even an error prompt when saving the template about title field being empty). Piotr Konieczny aka Prokonsul Piotrus| reply here 02:49, 2 October 2025 (UTC)
- A week later and I still don't know when to use this. A lot of my students are adding Chinese and Korean sources, and I am telling them to use the title, not script, field, and nothing in our rules tells me I am giving them bad advice (since the title field does not say not to use non-latin scripts in it). Piotr Konieczny aka Prokonsul Piotrus| reply here 07:29, 9 October 2025 (UTC)
- In order to be most helpful to readers not familiar with the script, I suggest that the documentation should recommend that titles in non-Latin scripts should be placed in
|script-title=, with a romanization in|title=. Kanguole 08:18, 9 October 2025 (UTC)- Indeed; but we also should have a way to dynamically fix it - a pop up or such when saving a template with non-Latin characters in the title parameter. Otherwise next to nobody will be doing this, as it is counter-intuitive not to have a title in the, well, title parameter. Plus we have the "trans-title" parameter, for translating the, well, title, not the "trans-script-title"... Frankly, I don't undestand the technical problem of not being able to handle non-Latin stuff in title field. I've never seen any problem with the non-Latin stuff in that field. Piotr Konieczny aka Prokonsul Piotrus| reply here 10:02, 9 October 2025 (UTC)
- I'll second this; I've used plenty of Cyrillic in the title field w/o any issues. Or is the idea non-Latin script in the script field, transliterated title in the title field and translated title in trans-title? If so then that should be made much clearer.--Sturmvogel 66 (talk) 11:29, 9 October 2025 (UTC)
- @Sturmvogel 66 "Bah, editors should figure that out by using wiki telepathy. The person who designed that field had a good idea how to use it - why can't everyone else?" :P Piotr Konieczny aka Prokonsul Piotrus| reply here 12:36, 9 October 2025 (UTC)
- Something like
<ref>{{cite book | title = Luach Ha-pe'alim Ha-shalem | script-title = he:לוח הפעלים השלם | trans-title = The complete verb table | author = Dr. Shaul Barkali | publisher = Levine/Millenniu }} </ref>
- Rendering as this[1] and creating metadata for the Hebrew title. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 12:54, 9 October 2025 (UTC)
- Do that ↑; don't do this:
{{cite book |title=he:לוח הפעלים השלם |author=Shaul Barkali |publisher=Levine/Millenniu}}- Shaul Barkali. לוח הפעלים השלם. Levine/Millenniu.
- —Trappist the monk (talk) 14:03, 9 October 2025 (UTC)
- Do you mean that title is for rendering the title in latin characters (romanization), and non-latin go in the script? That makes sense, but rendering titles in latin is often hard. It also requires extra steps. When pasting a random Korean ref into Citoid etc. I am pretty sure it ignores script-title, and uses Hangul for title. I see no problem with this (of course, best practice is to provide translation and romanization, but this is not what most editors do in 99% of cases...). Frankly, this is something we should have an AI tool run by a bot handle :P Piotr Konieczny aka Prokonsul Piotrus| reply here 14:55, 9 October 2025 (UTC)
|script-title=was created because non-latin text, especially cjk text, should not be italicized and because right-to-left text (Arabic, Hebrew, Persian, etc) must be isolated from left-to-right text.|script-title=also marks-up the non-latin text so that browsers and screen readers can render and pronounce the text using appropriate fonts and pronunciation.- If you have issues with citoid, this place is not the correct venue; a discussion at Help talk:Citation Style 1 has no power to change citoid. Try Phabricator.
- —Trappist the monk (talk) 15:30, 9 October 2025 (UTC)
- @Trappist the monk I don't have issues with citoid - much. I am trying to figure out when script-title should be used, and get some folks who know the answer to this to update the relevant documentation at Template:Cite web and wherever else this paramater is used. Piotr Konieczny aka Prokonsul Piotrus| reply here 15:36, 9 October 2025 (UTC)
- Template:Tq (link) and Template:Tq (link) read like complaints about citoid (and ve) to me. We can't fix those things here.
- I am known to suck at writing documentation – my style is too technical. If you (or anyone) knows how to make the documentation more complete and understandable, the template docs are not protected, so please do. See:
- That abomination that is TemplateData must be edited at each of the 29 cs1|2 templates.
- —Trappist the monk (talk) 15:56, 9 October 2025 (UTC)
- @Trappist the monk I don't have issues with citoid - much. I am trying to figure out when script-title should be used, and get some folks who know the answer to this to update the relevant documentation at Template:Cite web and wherever else this paramater is used. Piotr Konieczny aka Prokonsul Piotrus| reply here 15:36, 9 October 2025 (UTC)
- Do you mean that title is for rendering the title in latin characters (romanization), and non-latin go in the script? That makes sense, but rendering titles in latin is often hard. It also requires extra steps. When pasting a random Korean ref into Citoid etc. I am pretty sure it ignores script-title, and uses Hangul for title. I see no problem with this (of course, best practice is to provide translation and romanization, but this is not what most editors do in 99% of cases...). Frankly, this is something we should have an AI tool run by a bot handle :P Piotr Konieczny aka Prokonsul Piotrus| reply here 14:55, 9 October 2025 (UTC)
- Do that ↑; don't do this:
- I'll second this; I've used plenty of Cyrillic in the title field w/o any issues. Or is the idea non-Latin script in the script field, transliterated title in the title field and translated title in trans-title? If so then that should be made much clearer.--Sturmvogel 66 (talk) 11:29, 9 October 2025 (UTC)
- Indeed; but we also should have a way to dynamically fix it - a pop up or such when saving a template with non-Latin characters in the title parameter. Otherwise next to nobody will be doing this, as it is counter-intuitive not to have a title in the, well, title parameter. Plus we have the "trans-title" parameter, for translating the, well, title, not the "trans-script-title"... Frankly, I don't undestand the technical problem of not being able to handle non-Latin stuff in title field. I've never seen any problem with the non-Latin stuff in that field. Piotr Konieczny aka Prokonsul Piotrus| reply here 10:02, 9 October 2025 (UTC)
- In order to be most helpful to readers not familiar with the script, I suggest that the documentation should recommend that titles in non-Latin scripts should be placed in
- The discussions attendant on implementing
|script-title=: - —Trappist the monk (talk) 14:03, 9 October 2025 (UTC)
Discussion at Wikipedia:Bots/Noticeboard § Is Monkbot 21 removing url-status=dead desirable?
You are invited to join the discussion at Wikipedia:Bots/Noticeboard § Is Monkbot 21 removing url-status=dead desirable?. Dan Leonard (talk • contribs) 19:46, 8 October 2025 (UTC)
PMC limit too low
Trace Gas Orbiter has Template:PMC, which is correct. It looks like there's currently an unreleased article with Template:PMC, if that helps determine the upper limit of this increment. Snowman304|talk 01:14, 11 October 2025 (UTC)
SSRN value
Needs update per Template:SSRN. DrKay (talk) 17:00, 14 October 2025 (UTC)
Cite journal
I don’t know if this applies to the other journals but you have to enter [month in words] [year] but in journals it is often written as [year] [month number] which messes up the automatic citation maker. Houcaris (talk) 20:44, 20 October 2025 (UTC)
- For example January 1988 and 1988-1. Houcaris (talk) 20:45, 20 October 2025 (UTC)
- Yes. "1988-1" or "1988-01" are not valid date formats on the English Wikipedia. See MOS:DATESNO for more information. You may need to edit the automatic output of citation tools. – Jonesey95 (talk) 21:00, 20 October 2025 (UTC)
- We write dates according to the documentation for {{Cite journal}}. How the publication being cited chooses to write dates doesn't matter. Jc3s5h (talk) 21:02, 20 October 2025 (UTC)
- ↑ Dr. Shaul Barkali. Luach Ha-pe'alim Ha-shalem לוח הפעלים השלם [The complete verb table]. Levine/Millenniu.