Template talk:Infobox organization

From JaxPlays
Jump to navigation Jump to search

Template:Talk header Template:Permprot Template:WikiProject Organizations Template:WikiProject Infoboxes Template:Old AfD multi User:MiszaBot/config Template:Archives

New "Members" parameter

I suggest adding a new parameter called "Members". This would list all other organisations / entities which are members of the organisation in question. This is would be entirely different to the "membership" parameter, which is a numerical value etc. For example Russell Group currently lists universities which are part of it under membership, which is not really correct.

Do others agree? Morris Schaffer (talk) 17:38, 1 September 2019 (UTC)

add full name parameter

Template:Edit template-protected Can a parameter be added that would allow for the full name of an organisation to display above the native name? This is useful for cases where an organisation has a long official name but is widely known by a shorter name. Free Lula movement is an example where ideally it would be possible to put International Committee of Solidarity in Defence of Lula under the Free Lula Movement text which appears at the top (instead of using professional name which is incorrect). As an example, the template {{infobox union}} allows this option using the {{{full_name}}} parameter. --Goldsztajn (talk) 15:57, 17 October 2019 (UTC)

Template:Ping I've used |above= from {{Infobox}} to display the content of the new |full_name= parameter. You can see an example at Template:Infobox_organization/testcases#Default_/_primary_names. Is this what you were thinking or did you want it displayed differently? It will also take |full_name_lang= to specify language. Wug·a·po·des​ 17:48, 17 October 2019 (UTC)
Template:Re Thank you! A small suggested revision; keep font size the same as native name and without italics or bold.--Goldsztajn (talk) 18:37, 17 October 2019 (UTC)
  •  Not done for now: Up and running in the sandbox, however I'm deferring implementation until consensus for the change is reached below. Wug·a·po·des​ 21:48, 17 October 2019 (UTC)

Native name parameter

Template:Edit template-protected Can the native_name parameter be italicised, please. Documentation seems to show it will italicise, but does not seem to be rendering. --Goldsztajn (talk) 16:06, 17 October 2019 (UTC)

Template:Re What in the documentation makes you think it will be italicized? Wug·a·po·des​ 17:49, 17 October 2019 (UTC)
Template:Re I had just looked at the template page in the "usage" section and the display on the right showed native name as italicised above the image....my mistake was not seeing below the image and seeing all items have been italicised as part of the formatting. Looking at the code of the template I see it is not italicised, however, I would still like to request the change, per MOS:FOREIGNITALIC.Goldsztajn (talk) 18:27, 17 October 2019 (UTC)
Template:Ping I see that you've edited the lang module and thought you might be able to help out here. Is the div element used in the template code here for |native_name= and |native_name_lang= redundant with the {{lang}} template? Could it be replaced with that template with something like <syntaxhighlight lang="text" class="" id="" style="" inline="1"> | subheader = {{#if:{{{native_name|{{{native name|}}}}}} |{{#if:{{{native_name_lang|}}} |{{lang |{{{native_name_lang}}} |{{{native_name|{{{native name}}} }} | }} | }}</syntaxhighlight> with warnings for not including the language name and such? Wug·a·po·des​ 18:48, 17 October 2019 (UTC)
I think that <div class="nickname">...</div> is required – it's part of the micro formats produced by this template. If you choose to use {{lang}} to render |native name= then I don't think that you need the lang= attribute in the <div> because that will be produced by {{lang}}. I think it is a good thing to use {{lang}} because editors will get error messages when they write |native_name_lang=Chinese (meaningless as a lang= attribute value) so such errors will eventually get fixed (or not).
Perhaps what you want is this (Template:Lang: wholly untested):
<source lang="moin">| subheader = </source>
Trappist the monk (talk) 19:32, 17 October 2019 (UTC)
 Not done for now: I've made the changes in the sandbox, however this may significantly change how existing transclusions display, and there's the potential that some will break. I believe that by using the {{ISO 639 code-3}}, whether existing transclusions use an ISO code or a language name, there should be no breakage, but there may be non-standard uses that would get an error message. We'll need to establish wider consensus for this change, so I've started an RfC below. Wug·a·po·des​ 21:55, 17 October 2019 (UTC)
It occurred to me that mixing data from Module:ISO 639 (via {{ISO 639 code-3}} with data from Module:Lang is not best practice. The lang= attribute should use the codes and language names defined in the IANA language-subtag-registry file. That registry file contains language codes from ISO 639-1, -2, and -3. When a language name is defined in more than one of those standards (typically -1, and -3) IANA uses the -1 code. For example the language name 'German' in the ISO 639 standards has code:
-1: Script error: No such module "ISO 639 name".
-2: Script error: No such module "ISO 639 name".
-3: Script error: No such module "ISO 639 name".
cf: IANA: Script error: No such module "Lang/sandbox".
Until now there hasn't been a need for Module:Lang to do reverse look up (language-name to language-code). Further, lang= attributes support IETF language tags which are not ISO 639 codes. So, I have hacked Module:lang/sandbox and added a reverse lookup function to use language names that {{lang}} would recognize:
{{#invoke:Lang/sandbox|tag_from_name|German}}Script error: No such module "Lang/sandbox".
the function is indifferent to casing:
{{#invoke:Lang/sandbox|tag_from_name|sPaNiSh}}Script error: No such module "Lang/sandbox".
returns IETF tags when appropriate:
{{#invoke:Lang/sandbox|tag_from_name|Serbian Cyrillic}}Script error: No such module "Lang/sandbox".
{{#invoke:Lang/sandbox|tag_from_name|Proto-Celtic}}Script error: No such module "Lang/sandbox".
{{#invoke:Lang/sandbox|tag_from_name|Celtic languages}}Script error: No such module "Lang/sandbox". (an ISO 639-2 / IANA code)
when there are errors, can identify the template where the error occurred:
{{#invoke:Lang/sandbox|tag_from_name|Friday|template=Infobox organization}}Script error: No such module "Lang/sandbox".
{{#invoke:Lang/sandbox|tag_from_name||template=Infobox organization}}Script error: No such module "Lang/sandbox".
Trappist the monk (talk) 18:16, 18 October 2019 (UTC)
Oh wow, this is great! One of the benefits of Module:ISO 639 is that it is able to handle input that is either a language name or code. So the use cases we need to account for are those where |native_name_lang=Agob and |native_name_lang=kit. Currently the Lang/sandbox seems to choke if you give it a language code (e.g. Script error: No such module "Lang/sandbox".). I'm not nearly as familiar with the module as you are, but I assume there's some form of dictionary that associates language names and codes? Could it check to see if the input is a code and return that (or whatever the ideal code for lang= is) so that the infobox is indifferent to whether it receives a language name or a language code. Wug·a·po·des​ 21:31, 18 October 2019 (UTC)
That is not the purpose of this function and I don't want to start heaping functionality changes into it. There is is_ietf_tag() which returns true when the argument is a known IETF language tag. Combining that function with tag_from_name(), perhaps in Module:Lang/utilities, should do what you want. The equivalent is something like this (also an option):
<source lang="moin">Template:Lang</source>
Trappist the monk (talk) 23:28, 18 October 2019 (UTC)
I have hacked Module:Lang/utilities/sandbox to have a function that, for lack of a better one, is currently named native_name_lang(). The function returns an ietf language tag when given an ietf language tag:
{{#invoke:Lang/utilities/sandbox|native_name_lang|sr-cyrl}}Script error: No such module "Lang/utilities/sandbox".
or it returns an appropriate ietf language tag when given a language name that Module:Lang recognizes:
{{#invoke:Lang/utilities/sandbox|native_name_lang|Serbian Cyrillic}}Script error: No such module "Lang/utilities/sandbox".
or it returns an error message (with template name if provided):
{{#invoke:Lang/utilities/sandbox|native_name_lang|Friday}}Script error: No such module "Lang/utilities/sandbox".
{{#invoke:Lang/utilities/sandbox|native_name_lang|aaj|template=Infobox organization}}Script error: No such module "Lang/utilities/sandbox".
It occurs to me to wonder if this function should be further enhanced. It could, for example:
  • call lang() to render the native name
  • wrap the return from lang() in the <dif class="nickname">...</dif> tag
  • support some sort of mechanism for multiple native names
This insource search suggests that there are about pages in template space that include the string native_name_lang. It might be beneficial to see if there is something that might be applied to all or most of these templates.
Trappist the monk (talk) 14:55, 19 October 2019 (UTC)

RfC on native name and full name parameters

Template:Quote box
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Per the edit requests by Template:U, I've updated the sandbox version of this template to have two new parameters: |full name= and |full name lang=. Additionally, I have updated |native name= and |native name lang= to use {{lang}} so that metadata on non-English scripts can be added. In most cases these changes should be non-breaking, but if existing transclusions use a non-ISO language code or use a language name not supported by {{ISO 639 code-3}}, the template produces an error message. I believe the benefit of the metadata outweighs the harm of a few errors, but want to establish consensus before these changes are made. Wug·a·po·des​ 21:55, 17 October 2019 (UTC)

  • Support, provided there's a mechanism to track the errors down.  — AReaderOutThatawayt/c 05:23, 22 October 2019 (UTC)
  • Support nom's proposal and Template:Ping's added rationale. Seems reasonable. --Doug Mehus (talk) 02:22, 28 October 2019 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Is this still a parameter? I've tried to use this and an unknown parameter error gets thrown. Kartano (talk) 13:34, 29 November 2019 (UTC)

I have found no evidence that |publications= was ever supported. |publication= appears to work. – Jonesey95 (talk) 01:06, 11 December 2019 (UTC)

More parameters

I suggest adding a new parameter called "flag(s)", "prayer(s)" and '"ideology" ( ideologies). Italawar (talk) 13:45, 20 December 2019 (UTC)

Template:Ping Can you provide an examples of where these would be useful? Ergo Sum 05:29, 4 January 2020 (UTC)
Template:Replyto I think the feature would be handy in regard to pages such as Rashtriya Swayamsevak Sangh, Vishva Hindu Parishad and Momentum (organisation) etc. Italawar (talk) 08:19, 4 January 2020 (UTC)
Ideology seems to already be covered by purpose. The other two seem to marginal to be included in the infobox. Ergo Sum 15:47, 4 January 2020 (UTC)
Flag would seem to be covered by logo or image. Prayers will only be relevant for a tiny number of religious organizations (certainly not Momentum!) and is not important enough even to be mentioned in the text of the other two examples you mention, so I don't see how they could be justified for an infobox – unless you mean something different from what I think you mean. Hairy Dude (talk) 01:08, 6 January 2020 (UTC)
Template:Replyto Consider the difference between Ideology and Purpose, Flag and Logo and Flag and Image. Italawar (talk) 08:14, 6 January 2020 (UTC)

Template-protected edit request on 3 January 2020

Template:Edit template-protected I suggest adding a new parameter called "flag(s)", "prayer(s)" and '"ideology" ( ideologies). Italawar (talk) 10:28, 3 January 2020 (UTC)

 Not done for now: please establish a consensus for this alteration before using the {{edit template-protected}} template. You'll need to announce your discussion to the interested projects, WT:WikiProject Organizations and WT:WikiProject Infoboxes. Cabayi (talk) 11:54, 3 January 2020 (UTC)

Horizontal images

May somebody please edit the template so that the images are displayed horizontally next to each other, like country infoboxes do with their flags and coats of arms? Would make it easier to read on wide displays and save some space. – Illegitimate Barrister (talkcontribs), 12:43, 23 December 2019 (UTC)