Template talk:Infobox name module

This is the talk page for discussing improvements to the Infobox name module template.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Film: Chinese / Japanese / Korean / Southeast Asian

	Film portal This template is within the scope of WikiProject Film. If you would like to participate, please visit the project page, where you can join the discussion and see lists of open tasks and regional and topical task forces. To use this banner, please refer to the documentation. To improve this article, please refer to the guidelines.FilmWikipedia:WikiProject FilmTemplate:WikiProject Filmfilm articles
	This article is supported by the Chinese cinema task force.
	This article is supported by the Japanese cinema task force.
	This article is supported by the Korean cinema task force.
	This article is supported by the Southeast Asian cinema task force.

A lot of stuff

Would it be possible to display the Japanese a bit more simply? It is kind of horrible to have all the blue links to "Kanji" and "Hepburn" right at the top of an article about a film. Wistchars (talk) 23:31, 27 April 2013 (UTC)[reply]

As the creator of this template I certainly have no objections to aesthetic improvements, but the people you really need to talk to about this are the Wikipedia:WikiProject Film/Japanese cinema task force. Betty Logan (talk) 23:50, 27 April 2013 (UTC)[reply]

Thank you for your effort in creating the template. I sincerely appreciate your effort and do not wish to disparage it. I apologize if my comment above seems undiplomatic. However, my strong feeling is that when a general or average reader looks at an article on a film, it is extremely distracting to have highlighted the words "Kanji" and even more obscurely "Hepburn" at the very top of the infobox, above even the film's director. It overemphasizes the linguistic at the expense of the cinematic. Wistchars (talk) 00:00, 28 April 2013 (UTC)[reply]

No it's fine, I'm not offended. The foreign language infoboxes were recently merged into the main film infoboxes as per Wikipedia:Templates_for_discussion/Log/2013_March_29#Non-standard_film_infoboxes which used these linguistic titles. The Chinese films and Korean films also have these linguistic titles (see Crouching Tiger Hidden Dragon for instance). These parameters were installed by whoever created those infoboxes originally for whatever reason, but since the main film infobox doesn't include these parameters they were all collected into this template so the foreign language articles wouldn't lose them. So even though I created the template I'm not really in a position to help you since it is the Japanese cinema task force that created the parameters in the original Japanese film box, so that's why you need to talk to them. I can handle any technical changes, but it's up to them what is changed. Betty Logan (talk) 00:13, 28 April 2013 (UTC)[reply]

Thank you for your advice. I've added a note to the page. Wistchars (talk) 01:44, 28 April 2013 (UTC)[reply]

I find it useful to see the film name in the source language at the top of the infobox where the name of the film is. As I only know one Asian language I find the romanization very helpful to be able to pronounce the name properly as it is the official name of the film. I don't know about Japanese as much but I know Korean has two main forms of romanization and those affect pronouncation as well as the name in the source language is usually very different than it is in English. I hope the debate/discussion goes well in the Japanese cinema task force page. Take care. ₪RicknAsia₪ 02:27, 28 April 2013 (UTC)[reply]

I certainly agree that the native name and the romanized form of the name should be in the infobox. There is only one romanization used for Japanese on Wikipedia. I don't have any suggestions for changing the Korean format. Wistchars (talk) 02:44, 28 April 2013 (UTC)[reply]

Question

@Betty Logan: I added the template Infobox name module to a couple of film articles, and I'm confused, is it supposed to display the original-language title in the infobox? See for example [1] Godless (film); the Bulgarian version of the title is not showing up in the infobox. Or is the purpose of the template just to include metadata but not display anything in the article? Mathew5000 (talk) 20:23, 23 October 2016 (UTC)[reply]

The title parameters had been input incorrectly. I have fixed it for Godless (film), and you can see the original title is now displayed. You may find the template in this form more convenient to use though since it makes usage a little more compact. I will try to make the template instructions clearer with some examples. Betty Logan (talk) 20:31, 23 October 2016 (UTC)[reply]

Thank you! Mathew5000 (talk) 07:01, 24 October 2016 (UTC)[reply]

Language link

While this template has an option to delink the language, can anything be done to change the link? Because if I type {{Infobox name module|Hindi|हिंदी}}, the language link is [[Hindi language]] which redirects to [[Hindi]]. But I thought templates aren't supposed to redirect, but directly link. Can anything be done about this? --Kailash29792 (talk) 08:20, 20 March 2017 (UTC)[reply]

I am not aware of the rule that templates should not link through redirects, but it is easy enough to link directly if that is what you want to do. Basically you just need to disable automatic linking and wikilink manually:

{{Infobox name module | [[Hindi]] | हिंद ी | nolink=1}}

Betty Logan (talk) 16:22, 20 March 2017 (UTC)[reply]

Thank you for providing me with the answer. --Kailash29792 (talk) 16:31, 20 March 2017 (UTC)[reply]

English text (in non-English script) allowed?

In this field, are we allowed to write anything like {{Infobox name module|Tamil|மிஸ் மாலினி}}? Because while Malini is not an English name, "miss" is used in various languages (not just English) to refer to an unmarried woman. --Kailash29792 (talk) 04:40, 9 May 2017 (UTC)[reply]

The template should take it. Whether it is "allowed" or not depends on the relevant taskforce (listed at the top of this talk page) supporting the template. If a taskforce for the language you want to add doesn't support it then you can ask them to support it; if a taskforce doesn't exist then I would say it is down to individual article consensus. Betty Logan (talk) 06:40, 9 May 2017 (UTC)[reply]

Why no IPA?

Why is there no IPA or other pronunciation parameter like in standalone language infoboxes? – Finnusertop (talk ⋅ contribs) 01:26, 9 June 2018 (UTC)[reply]

This template was created with the sole purpose to "merge" parameters from the foreign language film infoboxes into the main film infobox to standardise usage. Rather than dropping a dozen extra parameters into {{Infobox film}} this intermediary template was created with two specific aims: i) to avoid clutter in the main infobox and ii) because "Infobox film" is a protected template it was difficult for the foreign language film task forces to edit, so having a non-protected name template facilitated maintenance of taskforce specific parameters. As such when this template was created we only merged the parameters that existed in those infoboxes at that time. If pronunication parameters had been present in the original infoboxes they would have been merged into this, but since they did not they do not exist in this template. That's not to say they should not exist, or will not exist, but rather it was beyond the scope of the template at the time. Betty Logan (talk) 11:25, 9 June 2018 (UTC)[reply]

Merging with Template:Infobox Chinese and Template:Infobox East Asian name

Is there a plan on how to merge Template:Infobox Chinese and Template:Infobox East Asian name into this? The amount of code in these templates make me think that maybe a true module would be better in handling this. Additionally, the parameter names should be sanitized. We can't have parameters as |c=, |t=, |s= and we should also separate multi word parameters by an underscore as is common. --Gonnym (talk) 16:24, 12 November 2018 (UTC)[reply]

There is no easy way to perform the merge IMO. The merge was put forward as a "nice" idea without any thought given to the practicality of it. These templates perform different functions and there is hardly any functional overlap. Betty Logan (talk) 16:37, 12 November 2018 (UTC)[reply]

Gonnym, you can use {{infobox Chinese}} as a module, e.g. here which is certainly better than having two infoboxes. Frietjes (talk) 16:57, 12 November 2018 (UTC)[reply]

Yes, I know Frietjes, that wasn't though what I was asking. A merge discussion over a year ago resulted in the decision to merge those 2 templates into this one. I was following up on this to see where it currently stands. --Gonnym (talk) 17:13, 12 November 2018 (UTC)[reply]

Betty Logan, what different functions to they perform? I haven't taken a deep dive into this yet, but on the surface it seems both represent the translated name and they just differ in style. --Gonnym (talk) 17:15, 12 November 2018 (UTC)[reply]

The problem is that some of the parameters share names but have different functionality from what I recall. I had a go at merging it last year but came to the conclusion it was more hassle than it was worth. On the other hand somebody else thought it was straightforward to carry out so maybe I am just too thick to do it! You can see the discussion at Template_talk:Infobox_Chinese/Archive_3#Merger_with_Template:Infobox_name_module. Betty Logan (talk) 17:55, 12 November 2018 (UTC)[reply]

I've looked at this a bit more. It doesn't seem hard. It would need parameter name changes as some are conflicting and some are just bad. I'll need to research a bit more how to create an infobox in lua as currently that is what is blocking me from moving forward. --Gonnym (talk) 13:55, 31 December 2018 (UTC)[reply]

Missing lang tags

It's considered good practice when using non-English text to specify its language in the HTML. This template does do it for Japanese, but doesn't seem to do it for Chinese. Lang tagging is especially important for CJK because it signals the OS to use a proper font and actually affects how the character itself will look. I'm aware that this template was meant to be merged but that seems to have stalled so best to fix it here for now. Opencooper (talk) 19:23, 22 July 2020 (UTC)[reply]

I just noticed this and definitely agree! Frankly it's just odd to see it say "simplified" or "traditional" but then not display the characters in the appropriate font. I also tested this template and found that it correctly formats Korean hanja, so all the more reason it should be changed to handle Chinese correctly as well. ChromeGames923 (talk · contribs) 07:57, 1 November 2020 (UTC)[reply]

@Gonnym: Pinging you on this since I notice you're a template editor and you've expressed some interest in this template a while back. I'm not sure what the usual process for requesting edits to templates is, so I apologise if this is unwarranted, it's just that it's been some time since the original comment without any activity. It seems like specifying Chinese and particularly traditional/simplified Chinese would be a relatively minor change, but I'm not at all familiar with templates. ChromeGames923 (talk · contribs) 08:24, 1 November 2020 (UTC)[reply]

Template-protected edit request on 27 July 2021

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

I want to change the template to properly tag Chinese text and the relevant script (Traditional/Simplified), as mentioned in the above section on this talk page, and at the village pump. This change would make the template follow Wikipedia guidelines regarding Chinese-language text and is thus non-controversial (likely being the original intention of this template anyways).

In particular, I propose to change the lines

  
| label2    = [[Traditional Chinese characters|Traditional]]
|  data2    = {{#if:{{{traditional|{{{fanti|}}}}}}|<big>{{{traditional|{{{fanti|}}}}}}</big>}}
| label3    = [[Simplified Chinese characters|Simplified]]
|  data3    = {{#if:{{{simplified|{{{jianti|}}}}}}|<big>{{{simplified|{{{jianti|}}}}}}</big>}}
| label4    = [[Chinese characters|Chinese]]
|  data4    = {{#if:{{{chinese|{{{Chinese|}}}}}}|<big>{{{chinese|{{{Chinese|}}}}}}</big>}}

to be:

  
| label2    = [[Traditional Chinese characters|Traditional]]
|  data2    = {{#if:{{{traditional|{{{fanti|}}}}}}|<big>{{lang|zh-Hant|{{{traditional|{{{fanti|}}}}}}}}</big>}}
| label3    = [[Simplified Chinese characters|Simplified]]
|  data3    = {{#if:{{{simplified|{{{jianti|}}}}}}|<big>{{lang|zh-Hans|{{{simplified|{{{jianti|}}}}}}}}</big>}}
| label4    = [[Chinese characters|Chinese]]
|  data4    = {{#if:{{{chinese|{{{Chinese|}}}}}}|<big>{{lang|zh|{{{chinese|{{{Chinese|}}}}}}}}</big>}}

Essentially, adding {{lang|zh-Hant|...}}, {{lang|zh-Hans|...}}, and {{lang|zh|...}} where appropriate. However, I am not familiar with editing templates, so it would be safe to make sure that my proposed change actually works and does not break anything. Thanks, ChromeGames923 (talk · contribs) 01:07, 27 July 2021 (UTC)[reply]

Done Looks fine to me. * Pppery * _{it has begun...} 14:25, 10 August 2021 (UTC)[reply]

Pinyin parameter

I know Pinyin is mainly used for Mandarin Chinese but I think the result of using Pinyin parameter should say Pinyin and not Mandarin, that's confusing. — Preceding unsigned comment added by Gyoren1 (talk • contribs) 18:06, 12 February 2022 (UTC)[reply]

I agree. —Mx. Granger (talk · contribs) 17:24, 8 January 2023 (UTC)[reply]

How can I put the Simplified parameter before the Traditional?

Is there no way to do this? Because I tried putting it before but it's the same. Megutim (talk) 20:31, 27 February 2022 (UTC)[reply]

The order of the parameters are hard coded in. Is this not the case for all infobox parameters? Betty Logan (talk) 09:38, 2 March 2022 (UTC)[reply]

I didn't know that, thank you. Megutim (talk) 18:01, 7 March 2022 (UTC)[reply]

Request to add |italics=no parameter for CJKV names

I know this template has been "replaced" by individual Chinese, Japanese, Korean, and Vietnamese templates, but this template is still commonly used for names in those languages (and frankly, it's easier to just use this template when the native name is all that's desired, and not all of the accompanying formatting and information). In these cases the text should not be italicized, and I think there should be the option for that. ChromeGames (talk · contribs) 09:34, 14 January 2024 (UTC)[reply]