A personal welcome and thank-you, for the contributions you've made in Indo-European language entries & discussions! --Frigoris (talk) 19:29, 21 September 2021 (UTC)
Caoimhin ceallach, please search to see if a reference template already exists before creating one. I've had to delete three of your duplicates. Thanks. -- Skiulinamo (talk) 06:56, 14 September 2022 (UTC)
Thanks for improving the Etymology at beocere. But I wonder if *cere meant "vessel-maker, keeper" rather than "basket, vessel". There are two Middle Low German related terms, immekar (“beehive”) and immeker (“beekeeper”) (where imme (< Proto-West Germanic *imbī) substitutes for "bee"). Here we see that kar "basket" (from *kaʀ) is distinct from ker "keeper" (from *kaʀi), which is of course derived from the former. Mind if I update it to point this out ? I may also go ahead and create *kaʀi (“vessel-maker”) as well. Leasnam (talk) 04:25, 22 March 2023 (UTC)
On the project here, we reconstruct all PIE terms with a leading vowel with a laryngeal before it. So, for example, **én would be an invaid reconstruction, demanding instead *h₁én. – Sokkjō 01:07, 25 March 2023 (UTC)
{{R:ine:LIPP}} is considered by most academics as crackpottery. Use with a grain of salt. – Sokkjō 10:08, 25 March 2023 (UTC)
In case you haven't already figured this out by now: the whole point of these is to be transcluded in the template page; Because this is always done with <noinclude>{{documentation}}</noinclude> in the template page, there's simply no way anything on the documentation subpage will ever end up in the entry.
When adding categories with {{refcat}} or the like, always surround them with <includeonly></includeonly> so the template will be categorized rather than the documentation subpage (after all, it's Category:Proto-Germanic reference templates, etc., not Category:Proto-Germanic reference template documentation pages). Thanks! Chuck Entz (talk) 23:21, 15 September 2024 (UTC)
<includeonly></includeonly> to include things on the template page. On the template page itself you use <noinclude>{{documentation}}</noinclude> to keep the documentation from being transcluded in the entry. The {{documentation}} is what does the transcluding, not the <noinclude></noinclude> tags. so:
{{refcat|gem-pro}} on the documentation page transcludes the categories.<includeonly>{{refcat|gem-pro}}</includeonly> on the documentation page keeps {{refcat}} from adding the categories to the documentation page itself.{{documentation}} on the template page transcludes the documentation page on the template page<noinclude>{{documentation}}</noinclude> on the template page transcludes the documentation page on the template page but the tags prevent the documentation page from being transcluded in the entry.{{RQ:gem-pro:abcxyz}} in the entry transcludes the template in the entry{{refcat}} should be on the documentation page and as opposed to on the template page between <noinclude> tags, i.e. the way it is on template pages that lack documentation, like Template:R:Schrijver:1997? —Caoimhin ceallach (talk) 20:13, 20 October 2024 (UTC)@Chuck Entz, did you intentially remove the gem-pro and ine-pro tags from Template:R:non:AnEW/documentation and Template:R:gem:EDPG/documentation respectively? I was following what I perceived as a convention to add templates for etymological dictionaries of daughter languages to the mother language category. See for instance the other references included in Category:Proto-Germanic reference templates. Also aren't the non and gem tags respectively superfluous, as {{refcat}} adds them by default? —Caoimhin ceallach (talk) 22:13, 16 September 2024 (UTC)
Hello,
Is this how your username is pronounced?
Thank you. Flame, not lame (Don't talk to me.) 02:41, 14 January 2025 (UTC)