Template talk:Infobox Tibetan Buddhist monastery
This is the talk page for discussing improvements to the Infobox Tibetan Buddhist monastery template. |
|
untitled
[edit]Hi again! It all looks good but I would suggest that the Infobox should have a place to indicate what order or sect the monastery is connected with: Gelug, Nyingma, etc. Also, is it worth indicating that the number of monks is approximate as we get the information from various sources of different dates and also, of course, the numbers change regularly. However. they are of use in gross terms - a monastery with 50 monks is clearly of a different order than one with 500. Cheers, John Hill (talk) 22:01, 8 October 2009 (UTC)
Oh - I have just noticed you already have a place for sect - missed it at first glance - you think of just about everything! John Hill (talk) 22:03, 8 October 2009 (UTC)
region code
[edit]Like {{Infobox building}}, this template relies on {{CountryAbbr}} to determine the region code for {{Coord}}. As a result, it sometimes generates coordinates with an invalid region code. I think the simplest way to resolve this issue would be to add an optional iso_region=
parameter as was done recently in {{Infobox building}}. Would anyone object to this addition? --Stepheng3 (talk) 07:17, 15 March 2010 (UTC)
- Hi. Add whatever you think is appropriate. If there are any problems with your addition we'll let you know. ‡ Himalayan ‡ ΨMonastery 09:43, 15 March 2010 (UTC)
- Done. --Stepheng3 (talk) 21:27, 15 March 2010 (UTC)
Suggest merge
[edit]Just thought this might be able to merged into Template:Infobox religious building like the previous Template:Infobox Buddhist temple any thoughts?--Cs california (talk) 06:58, 18 March 2017 (UTC)
- For the record: The discussion concluded with a result of merge, convert to wrapper. – Jonesey95 (talk) 01:59, 7 January 2019 (UTC)
Errors
[edit]@Jonesey95: The recent edit has put half a dozen articles in Category:Pages with script errors. For example, Khardo Hermitage is displaying "Lua error in Module:Location_map at line 419: No value was provided for longitude." in the infobox. Possibly that is an error in the article which should be fixed, but I haven't got time to investigate at the moment. Please check. Johnuniq (talk) 10:11, 3 January 2019 (UTC)
- Johnuniq: Strange. I'll take a look. I thought I was reverting to the last working version, but there must be some other forces at work. – Jonesey95 (talk) 13:15, 3 January 2019 (UTC)
Fixed. It looks like an editor started to merge this template with Infobox religious building but did not complete the merge, leaving many articles in a half-merged state. I have restored the template to an earlier version and then added a few tweaks to prepare it for a merge. Thanks for the note and the ping. – Jonesey95 (talk) 13:36, 3 January 2019 (UTC)
Working on a wrapper template
[edit]Per this merge discussion, I've been working on implementing the merger of this template with {{Infobox religious building}}, creating a wrapper template in the sandbox, per the TFD. You can see preliminary results at Template:Infobox Tibetan Buddhist monastery/testcases.
So far, I've hacked a way to support other-language transcriptions using the |native_name=
parameter. It needs formatting improvement.
The following parameters appear to be unsupported by Infobox religious building:
- lineage
- dedicated_to (use deity=?)
- head_lama
- colleges
- no._of_monks
Any ideas about what to do with them? I think they can be added to Infobox religious building if they are necessary. – Jonesey95 (talk) 02:03, 4 January 2019 (UTC)
- Would be worth looking into seeing how the merged Template:Infobox Shinto shrine using User:AnomieBOT. That was done really smooth. I agree with the changes of dedicated_to to deity. As for some of the other fields like no._of monks and head_lama I think these are very variable and so it should be checked if they are even used widely. If not we should just add them in the article. --Cs california (talk) 21:54, 5 January 2019 (UTC)
- Thanks for the tip. I found a way to format
|native_name=
better, mapped|head_lama=
to|leadership=
, and mapped|dedicated_to=
to|deity=
. I have implemented this template as a wrapper, completing the merge.
- Thanks for the tip. I found a way to format
-
- I have removed support for
|colleges=
,|lineage=
, and|no._of_monks=
, but I left them in the list of parameters that are valid in the unknown parameter check so that people would not remove them unnecessarily. If people think that there is a good reason to support them, Template talk:Infobox religious building is the best venue. – Jonesey95 (talk) 01:57, 7 January 2019 (UTC)- Other big issue was there was a large pool of stuff in different languages for the name that needed to go somewhere maybe have a bot consolidate them. Then I think it should be good to go --Cs california (talk) 07:19, 8 January 2019 (UTC)
- I do not understand what changes you would like to see. The template as it is currently written supports display of the name of the monastery in other languages and scripts. You can see how it currently works at Template:Infobox Tibetan Buddhist monastery/testcases. If you have a concern about how this text is displayed, perhaps you could link to a specific article and suggest a specific change. – Jonesey95 (talk) 14:02, 8 January 2019 (UTC)
- I already like the way you have it. If you can condense it on just the native_name that would be fine but if not that is cool too. I just don't like stuff using that chinese template to put the item name in all kinds of languages with their pronounciation like in Grass jelly under the infobox. --Cs california (talk) 08:54, 9 January 2019 (UTC)
- I do not understand what changes you would like to see. The template as it is currently written supports display of the name of the monastery in other languages and scripts. You can see how it currently works at Template:Infobox Tibetan Buddhist monastery/testcases. If you have a concern about how this text is displayed, perhaps you could link to a specific article and suggest a specific change. – Jonesey95 (talk) 14:02, 8 January 2019 (UTC)
- Other big issue was there was a large pool of stuff in different languages for the name that needed to go somewhere maybe have a bot consolidate them. Then I think it should be good to go --Cs california (talk) 07:19, 8 January 2019 (UTC)
- I have removed support for