Template talk:Tt-Klingon

tt-alternative

I know that the tt-tag is obsolete, but the "code"-tag seems not be a good solution either: it produces a strange rectangle around the word which destroys the text: Using tt makes tlhIngan and using the code-tag makes this: tlhIngan. What else can we do? It would be nice if there was a tage like <tlh>tlhIngan</tlh> which then uses a serif-font, like verdana or tahoma etc. So I can write using tlhIngan Hol vocabulary. Do you think it may be possible? -- Lieven (talk) 14:48, 18 September 2014 (UTC)

@Lieven: tt was purely decorational mark-up--it was the equivalent of a monospace font in CSS. code demarcates some text as code, which is semantically meaningful. The simple solution is to just make this wrapper have a monospace font and also use the {{lang|tlh|...}} wrapper around the text to place it in a tracking category (Category:Articles containing Klingon-language text) and allow machines to understand that there are multiple languages in this document, etc. —Justin (koavf)❤T☮C☺M☯ 05:33, 27 September 2014 (UTC)

@Lieven and Koavf: It was not purely decorative, as the text in the template explains. Clarity requires the visual distinction between lowercase ell l and uppercase eye I, and wikicode integrity requires avoiding the ASCII straight apostrophe '. Simply specifying a monospace font does not guarantee the first, and certainly cannot control the second. I preferred the "tt" tag, but it is now deprecated in HTML. koavf, your solution would work if it could guarantee a monospace serif font, and preferably if the wrapper – which would need to be applied to every discrete piece of Klingon text in the document, e.g., Klingon grammar – were shorter than {{lang|tlh|...}}.

Now that I look at Klingon grammar, a CSS style such as the one used in some of the tables there, style="font-family:Courier New, Courier, monospace", would provide the font, and would be feasible if it were made into a template like {{tlh|...}} so we wouldn't have to type <span style="font-family:Courier New, Courier, monospace">...</span> around each morpheme in the table!

@68.148.186.93: The references you deleted are there to advise anyone editing the page of the reasons for using a serif font and avoiding the straight apostrophe - see above 2 paragraphs. The alternative would be to put that text into the note, which would be quite excessive for almost all users (those who are reading the page, not editing it). Please do not delete them again. --Thnidu (talk) 14:15, 25 July 2015 (UTC)

Selfref

This template, especially its reference to itself that ends up in articlespace, is a MOS:SELFREF and should be marked as such (via {{selfref}}).—Ketil Trout (^<><!) 23:16, 11 April 2016 (UTC)

@Ketiltrout: I've done so. But I haven't used that template before, and I'm not sure I've done it properly. Would you mind checking it now? Thanks. Please {{Ping}} me to discuss. --Thnidu (talk) 04:55, 12 April 2016 (UTC)

@Thnidu: Looks okay to me. (Though I'm no expert with it either.)—Ketil Trout (^<><!) 19:38, 12 April 2016 (UTC)

@Ketiltrout: Thanks. --Thnidu (talk) 06:55, 13 April 2016 (UTC)

Unicode point for the apostrophe

The shape of the curly-quote apostrophe is right, but per Unicode that code point is for a punctuation mark rather than a letter, and doesn't behave like a letter. I changed it to the letter apostrophe here and in all articles that transcluded this template. — kwami (talk) 05:55, 15 March 2019 (UTC)

@Kwamikagami: Thanks a lot! I was only dimly aware of that distinction in Unicode and wouldn't have known how to apply it. --Thnidu (talk) 14:15, 8 July 2019 (UTC)

link to Mozilla.org article on HTML

@Soumya-8974: In the documentation for {{Tt-Klingon}} you wrote

Note: A previous version of this template (20 May 2014‎) specified the <tt>...</tt> tag, which is obsolete.

That external link goes only to the developer.mozilla.org page Introduction to HTML, not to the intended subpage "Obsolete_things_to_avoid", which I cannot find in searching on that site. Such a broad reference link is useless. Please fix it. --Thnidu (talk) 14:53, 8 July 2019 (UTC)

"Typewriter" font

On 8 July 2019 Soumya-8974 changed the beginning of line 1 of {{Tt-Klingon}} from

{{Hatnote|On this page, Klingon text in the Latin alphabet is displayed in  <code>typewriter font</code>}}

which displayed as

On this page, Klingon text in the Latin alphabet is displayed in  typewriter font

to

{{Hatnote|On this page, Klingon text in the Latin alphabet is displayed in  {{font|font=Typewriter|text=typewriter font}}}}

which displays as

On this page, Klingon text in the Latin alphabet is displayed in  typewriter font

I do not know of any font named "Typewriter", and whatever Wikipedia considers it to be, this is not a typewriter font. It is a serif font but it is not monospaced, which is part of the purpose of the template, to set it off from regular text.

Lieven and Koavf have pointed out the undesirability of the "code" tag, which encloses the affected text in a box. I'd like to use
<span style="font:Courier New;Courier;serif">
but until I or someone else has time to work out a suitable template, I am changing the specification back to <code>...</code>. --Thnidu (talk) 05:20, 11 July 2019 (UTC)