Template talk:Bo-textonly

Text size sometimes too large

The sizing on this template appears to have been adjusted to work with the Microsoft Himalaya font (default Tibetan font on MS Windows) which renders Tibetan text at a small size. This template fixes that - but results in Tibetan text when displayed on other operating systems, or with other Tibetan fonts, being rendered too large and this can mess up line spacing. There is no "standard" size for Tibetan fonts - so one scaling size does not fit all - in fact some Tibetan fonts don't need any enlargement at all. Is there a way of fixing this so the re-sizing is based on the default Tibetan font being used on the client system? Meanwhile I'm going to put the scaling size back to 130% where it was before Great Brightstar changed it. This is not ideal for all systems - it will be a little big on some and a little small on others but it seems to be the best compromise based on all the different systems I've tried it on. Chris Fynn (talk) 22:56, 9 August 2014 (UTC)

@CFynn: This might be something worth bringing up at WP:VPT; not a lot of people watch this talk page, meaning that few people may respond. --benlisquare_T•C•E 05:54, 10 August 2014 (UTC)

Thanks benlisquare. I've now opened a discussion at Wikipedia:Village_pump_(technical)#Bo-textonly template renders Tibetan text too large (except on MS Windows) Chris Fynn (talk) 10:33, 10 August 2014 (UTC)

More Tibetan fonts

This template should add more fonts as Yalasoo website provided. The Digital Tibetan website has an article mentioned them. --Great Brightstar (talk) 04:39, 21 June 2016 (UTC)

 Done. Only Uchen styled fonts available. --Great Brightstar (talk) 05:43, 8 July 2016 (UTC)

 Done again. Umê styled fonts are also available, they can be activated via |ume=1. Additionaly, I also added more fonts from SonamDawa.com, also found at the Digital Tibetan website. --Great Brightstar (talk) 10:58, 7 September 2016 (UTC)

Order of Fonts

The order of the Tibetan fonts in this template probably needs changing. If a user has a number of Tibetan fonts installed the template currently (Sept. 2018) seems to prioritize some fonts with very poor or non-standard glyph shapes. Those fonts should preferably be moved nearer the end of the list.
Chris Fynn (talk) 11:03, 22 September 2018 (UTC)

 Done Chris Fynn (talk) 11:15, 22 September 2018 (UTC)

Semi-protected edit request on 4 May 2020

Add line-height: 1 to element with class uchen to avoid lines with tibetan being rendered as taller than other lines. 84.214.109.174 (talk) 17:34, 4 May 2020 (UTC)

Not done for now. Can you provide an example where this is causing a problem and how this will improve it? My reading of the docs for line-height seems to indicate that it should be used for divs, not spans, although I'm certainly not an expert with this stuff and I could easily be mistaken. –Deacon Vorbis (carbon • videos) 18:03, 4 May 2020 (UTC)

{{Script}}?

Is there any reason this is not a part of {{Script}}? Should it stay separate? Or is it just cuz no one got around to adding it? Eievie (talk) 05:04, 27 January 2024 (UTC)

{{Script}} uses {{Script/Tibetan}}, but that lacks the parameters this template has. {{Script/Tibetan}} cannot be used to set the language for lang= to use in its <span> tags, uses a more limited set of fonts than Template:Bo-textonly/fonts.css, and has some minor differences in style=, specifically it doesn't include vertical-align:middle; word-wrap:break-word. I'm not sure why it differs regarding style=, that could just be because no-one synchronised them, however there's no easy way to implement the parameters into {{Script/Tibetan}}. Though {{Script/Tibetan}} could be made to use a .css file for its fonts, as it does for other scripts, it wouldn't be able to utilise the same fonts.css this template uses due to lacking parameters. Even if you added the needed parameters to {{Script/Tibetan}}, they would also have to be added to {{Script}} to be useful, and adding Tibetan-specific parameters to that template doesn't seem appropriate. – Scyrme (talk) 03:27, 6 March 2026 (UTC)