User talk:Daniel Carrero/2010

Here. Portuguese speaker needed. Thanks. Mglovesfun (talk) 11:12, 5 January 2010 (UTC)Reply

I don't speak French, so I won't participate directly in that discussion. Nevertheless, música para acompanhar is indeed a Portuguese term; a very common phrase. See entry . --Daniel. 11:37, 5 January 2010 (UTC)Reply

Why does this link to "*" (at the top) instead of to "0"? SemperBlotto 18:16, 9 January 2010 (UTC)Reply

Thanks for pointing me to this error. It probably ocurred when I was programming the support for ], which unlike most similar categories, doesn't have upper case and lower case variations, therefore it needed a slightly different description. The links are working properly now. --Daniel. 18:25, 9 January 2010 (UTC)Reply

Hi. You moved Appendix:Hebrew declension to Appendix:Hebrew parts of speech a while back, and I was wondering if it's really necessary. The appendix really does deal specifically with declension, but only with some parts of speech (not verbs; this is why I just put a note atop it directing the reader to another appendix for verbs). Is there something wrong, or wronger than "Hebrew parts of speech", with "Hebrew declension"?​—msh210℠ 17:44, 11 January 2010 (UTC)Reply

Hi, msh210. Based on the current contents of the appendix, I can safely say the title Appendix:Hebrew declension would also be correct. Although, I'm inclined to choose the current title Appendix:Hebrew parts of speech. One reason for my choice is simply coherence with other similarly-named appendices, for instance, Appendix:English parts of speech. If all these related appendices share the same naming scheme, they are easier to find. Another reason is the fact that the Hebrew appendix is not absolutely informative either way: it could be improved with more details about declensions or about parts of speech in general; or both. --Daniel. 17:59, 12 January 2010 (UTC)Reply

Fair enough. I was thinking each Hebrew appendix (main ones, not subpages) should include a boxed link to the others à la w:template:content policy list (see it in use at w:WP:NPOV) or w:template:style (in use at w:WP:MOS). What do you think?​—msh210℠ 18:05, 12 January 2010 (UTC)Reply

A box containing links to related Hebrew appendices is indeed a good idea. I may express more accurate opinions and contributions after I see it. --Daniel. 18:38, 12 January 2010 (UTC)Reply

Template:he-appendices?​—msh210℠ 19:13, 12 January 2010 (UTC)Reply

The appendix Hebrew patterns and its subpages are unclear to me. They seem to explain how particular groups of letters are found in words, so their contents may be moved to Appendix:Hebrew spellings. --Daniel. 19:47, 12 January 2010 (UTC)Reply

You may find Wiktionary_talk:About_Hebrew#Patterns. interesting and informative. I don't think it should move to Appendix:Hebrew spellings.​—msh210℠ 19:51, 12 January 2010 (UTC)Reply

Wiktionary_talk:About_Hebrew#Patterns. was interesting and informative indeed. Although, while the existence of patterns became clearer to me, I still think that Appendix:Hebrew spellings would be a good new name for Appendix:Hebrew patterns, while Patterns may be a L2 section inside it; this proposal would also be consistent with similar appendices such as Old French spellings and Portuguese spellings. In addition, would you consider adding Appendix:Hebrew given names to Template:he-appendices? --Daniel. 15:10, 14 January 2010 (UTC)Reply

The Old French and Portuguese appendices are really abou thow to spell words; the Hebrew one is a list of patterns used to form words (irrespective of their spelling, though of course each pattern is spelled a certain way), or perhaps can be a discussion of such patterns. it's really not about spelling at all. By all means bring this to Wiktionary talk:About Hebrew for more input if you disagree. I'll add given names.​—msh210℠ 22:32, 14 January 2010 (UTC)Reply

Alright. Aside from the current naming scheme that includes patterns, I have no more objections. The {{he-appendices}} looks useful and suitable. Nice work. --Daniel. 22:43, 14 January 2010 (UTC)Reply

Hey again. What do you think of adding support for alternative forms to this? In case you don't know, from what I gather, the difference between alt sp.'s and alt forms is that alt forms is generally used for alt forms of words that have a different pronunciation and of course it'd surely be appropriate for stuff like o.O. :) So: Is plausible? What do you think of it? 50 Xylophone Players talk 20:34, 14 January 2010 (UTC)Reply

I know; in Wiktionary, alternative forms is basically synonym of synonyms. Although, some cleaning up could be done, as various members of English alternative forms might belong to English alternative spellings instead. The English spellings, its subcategories and similar categories for other languages were designed to contain words differentiated by groups of characters, such as English color/colour and perhaps Japanese コンピュータ/コンピューター. So, in my opinion, alternative forms should be avoided in it. For the sake of organization and coherence with the current categories, the name spellings simply doesn't fit variations of words, for example and reality TV and reality television; or head south and go south. --Daniel. 21:13, 14 January 2010 (UTC)Reply

Well then, is there any catboiler template which you think would suit these forms? (sorry for late reply but I've been busy on Wiktionary and (deprecated template usage) IRL.) 50 Xylophone Players talk 20:50, 10 February 2010 (UTC)Reply

I prefer to create and maintain catboiler templates for more well-defined categories. I've started a discussion at WT:BP#English synonyms on this issue. --Daniel. 20:02, 12 February 2010 (UTC)Reply

Na'vi does not pass our CFI. Would you like to make an Appendix instead? --Bequw → ¢ • τ 15:07, 23 January 2010 (UTC)Reply

Appendix:Na'vi already exists. Conrad.Irwin 15:11, 23 January 2010 (UTC)Reply

(Edit conflict) Yes, I just saw that. I'm more concerned about his recent conlang additions that aren't appendices: {{art-nav}}, Category:Na'vi language, {{qya}}, Category:Quenya language, {{sjn}} and Category:Sindarin language. The constructed languages are restricted to Appendices, so these should be deleted, especially the language-code templates since we don't want people using them for entries and translations. --Bequw → ¢ • τ 15:18, 23 January 2010 (UTC)Reply

How the fact that fictional constructed languages does not meet our criteria for inclusion influences the existence of templates and categories for these languages? I did not found anything at WT:CFI (or at WT:LANGCODE, by the way) that supports your view on this issue, Bequw. --Daniel. 15:38, 23 January 2010 (UTC)Reply

(another edit conflict) See the recent BP discussions of constructed languages in 2008 and 2007 where "restrict to Appendix" was used synonymously with "disallowed from the main namespace". The issue of categories has not been explicitly brought up, but I don't think they're desirable. Why have a category that by policy will be basically empty? If it's just to get better visibility of the Na'vi appendix a better bet would be to add it to Wiktionary:List of languages (where Sindarin and Quenya already are). Who would even be looking in the category space for them?

Normal language code templates for these conlangs should not be allowed because we want to have only normal language code templates for possible entry L2's. This is why Template:tlh was deleted. This is why we partition off etymology-only codes to the etyl:*. (Find these discussions by searching for {{etyl}}, the old dot-style etymology templates, fr-ca/CA, etc.) --Bequw → ¢ • τ 16:16, 23 January 2010 (UTC)Reply

To answer your question, I, as a Wiktionary editor who is interested in organization, appearance, consistency and user-friendliness of category trees, would certainly look for languages by searching in related categories. There is a Category:All languages and there is another called Category:Constructed languages, and, as you pointed out, there are even other lists of languages in the Wiktionary: namespace, so Quenya, Klingon, Na'vi and other fictional languages must be findable in all these options, as long as they are up-to-date and accurate. Certainly, I'm not the only person who has been using, editing and improving the current system. If you don't feel comfortable by using language categories, constructive ideas are welcome, including the idea of deleting categories of fictional languages. However, this specific proposal breaks the scheme. If I have the knowledge and want to edit Quenya in Wiktionary, I would respect the place to do it. Not in entries, but in appendices - it seems very reasonable. But I would want to find the place easily.

That said, the etyl: system seems very good. Perhaps, similarly, {{ficl:sjn}} ("fictional language: Sindarin") could be the code for Sindarin, specifically programmed to not work in entries. --Daniel. 01:51, 24 January 2010 (UTC)Reply

Very good idea about a new language code prefix. Maybe we can make the prefix conl: so that it can handle other reasons that a language is not allowed by the CFI (constructed languages independent of fictional worlds & reconstructed languages). That is assuming we'll use codes for these languages. Currently they are only used in {{langcatboiler}}, right? Not sure. Maybe it's good to have codes for them anyways.

I would say that including a link to Category:Fictional languages appendices in the header of Category:All languages and Category:Constructed languages would be much better than having actual categories for nonCFI languages. As for breaking the structure of , the consistency is nice when it makes sense, but here I don't think so.

How do these changes sound? --Bequw → ¢ • τ 23:26, 24 January 2010 (UTC)Reply

I agree, conl: is a good idea for the new language code prefix.

Currently, the discussed language codes are used in {{langcatboiler}} and {{tempcatboiler}} (to create the automatic text at ]). Possibly, the existing Na'vi templates could be renamed to reflect the current scheme. That is, if pt-verb, en-verb and many more similar templates exist, I'd expect sjn-verb and art-nav-verb as well.

The idea of categorizing ] together do makes sense, as much as categorizing ] together. A link at ] specifically for constructed languages, as I imagine, would draw too much unnecessary attention for them. --Daniel. 14:22, 25 January 2010 (UTC)Reply

(unindent) I'll let you move the language codes to the new prefix as you'll have to retool {{langcatboiler}}. I link in the category header probably is too much. I think we could have a category for languages not allowed by the CFI Fictional languages wasn't general enough so I moved the appendices to Constructed languages appendices. But now that seems overly broad as a similarly named category Constructed languages includes both allowed and disallowed languages. What if instead we had a category such as Disallowed languages, Non-CFI languages, or Appendix-only languages? Do any of those work? --Bequw → ¢ • τ 14:17, 26 January 2010 (UTC)Reply

Oh, I see you posted a similar idea in the BP. --Bequw → ¢ • τ 19:02, 26 January 2010 (UTC)Reply

{{langcatboiler}} is now ready for the prefix conl:. From these three naming possibilites, I prefer Appendix-only languages, because, even if Wiktionary editors are used to say Disallowed languages or Non-CFI languages to point to the languages which should appear only in appendices, this meaning is not ineherently obvious. That said, as reconstructed languages are also appendix-only (or "disallowed", or "non-CFI"), I've created a more detailed category: Appendix-only constructed languages. I've also updated WT:LANGCODE. --Daniel. 08:26, 27 January 2010 (UTC)Reply

OK, I reverted that change. I'll leave Category:Fictional languages appendices, but delete it if you think it's now redundant to the categories you just made. Thanks. --Bequw → ¢ • τ 15:29, 27 January 2010 (UTC)Reply

More accurately, "to pass CFI" is a subjective expression. Na'vi definitely passes CFI, as meriting definitions in the appendix namespace. Surely, templates and categories would be welcome for them if presumably they help to improve Wiktionary. There is a small quantity of Na'vi templates, which naturally are categorized together, in a subcategory of Na'vi language. --Daniel. 16:04, 23 January 2010 (UTC)Reply

I'm pretty sure everyone who says "passes CFI" means for the normal namespace. I did not argue with Category:Na'vi templates only with the language category. A better parent cat would be at Category:Fictional language templates to match Category:Fictional languages appendices. --Bequw → ¢ • τ 16:19, 23 January 2010 (UTC)Reply

You didn't argue with Category:Na'vi templates, I did. As you can see at my message above, I wouldn't want to break the current system, in which a Category:(language) templates is expected to be one subcategory of Category:(language) language. --Daniel. 01:51, 24 January 2010 (UTC)Reply

Olá Daniel! Que bom achar um administrador lusófono aqui. Você sabe o que faz funcionar o {{#section:Index:Portuguese/w|toc}} em Index:Portuguese/w? É que lá no Wikcionário, eu botei a mesma função ({{#section:Vocabulário:Português/w|toc}}) na página Vocabulário:Português/w e não funcionou? Cumprs. Luan (discussão) 05:05, 26 January 2010 (UTC)Reply

Olá. Nas páginas Special:Version e pt:Especial:Versão, você pode ver as extensões que estão instaladas no Wikcionário em inglês e português, respectivamente. Para ativar o comando {{#section:Vocabulário:Português/w|toc}}, primeiro a extensão Extension:Labeled Section Transclusion deve ser instalada no Wikcionário em português. --Daniel. 06:53, 26 January 2010 (UTC)Reply

My bad! Foi um lapso de memória, tinha me esquecido dessas palavras. Obrigado por me corrigir. Jesielt (user talk) 15:43, 27 January 2010 (UTC)Reply

Hello Daniel.. I have tried using Template:poscatboiler in Category:German acronyms, but it seems not to function properly. What am I doing wrong? --Volants 13:51, 28 January 2010 (UTC)Reply

Also, in Category:Polish imperfective verbs and Category:Polish perfective verbs. Maybe more. --Volants 13:54, 28 January 2010 (UTC)Reply

Not all parts of speech are supported by {{poscatboiler}} yet, specially in-depth ones such as imperfective verbs, which require distinct descriptions. At the template's talk page, there's a list of supported commands; please see it. I've now programmed the two options {{poscatboiler|(language)|perfective verb}} and {{poscatboiler|(language)|imperfective verb}}, so you may use them. Although, perhaps ] isn't suitable as a subcategory of ], so I left it alone until further discussion. --Daniel. 14:22, 28 January 2010 (UTC)Reply

Hi Daniel, would you add the <language> citations category to this template? For example, as a result, the Category:Hungarian citations will be listed in Category:Hungarian language page, and the same for other languages. Thank you. --Panda10 00:48, 31 January 2010 (UTC)Reply

Done. --Daniel. 22:48, 1 February 2010 (UTC)Reply

You deleted this but it is still used on 2 pages. Is there something to replace it with? Nadando 19:56, 2 February 2010 (UTC)Reply

Carolina wren deleted ] before I deleted {{zhx-sha}}. As I remember, I was simply following her lead on considering Shanghainese to be a dialect, not a language. To substitute that template and still treat Shanghainese as a dialect, I've now created {{etyl:Sha.}} --Daniel. 14:28, 3 February 2010 (UTC)Reply

Looking at Wanted Categories, I think you may or may not want to consider adding support to this for (deprecated template usage) ambitransitive and (deprecated template usage) ditransitive verbs. 50 Xylophone Players talk 14:05, 15 February 2010 (UTC)Reply

Two current Icelandic categories. I see. Support added. --Daniel. 15:10, 15 February 2010 (UTC)Reply

What's this "Dass" stuck on the end? Did you test your changes? SemperBlotto 15:46, 15 February 2010 (UTC)Reply

The "}Dass" was one effect of a single bracket out of place. It's fixed now, as expected of whatever error that could happen by editing a relatively messy code for the sole purpose of making it cleanier. Yes, I did technically test my changes, by having a few entries ready to be checked promptly. --Daniel. 16:01, 15 February 2010 (UTC)Reply

Yes, these wiki templates are a dreadful mass of brackets. I always generate a temporary template and test it privately, then implement it after testing. Cheers. SemperBlotto 16:04, 15 February 2010 (UTC)Reply

Creating a separate temporary template is a nice idea, which I may use for my next complex template edits (as I've already done, several times). This was just one time I didn't think a error would happen, especially after reading the code in a long and careful way, but unfortunately not error-proof. Cheers. --Daniel. 16:15, 15 February 2010 (UTC)Reply

Regarding {{apphead}}, prefixing appendix templates with "app" is problematic because "app" is the ISO code of the Apma language, which is why I prefixed the appendix templates that I made with "apdx". Also, wouldn't it make sense to have it based on the same kind of patterns as the regular templates (- for uncountable/uncomparable, verb forms set like {{en-verb}}, forms set by X=, etc.)? And one more thing: what are the advantages of using {{apphead|title}} over '''title'''? --Yair rand 19:52, 15 February 2010 (UTC)Reply

Strictly speaking, templates for individual languages are named as language code followed by hyphen, so I don't consider the name "Template:apphead" particularly problematic as having potential to be confused with something directly related to the Apma language. Similarly, {{trans-top}} begins with "tr" and "tra" (codes for Turkish and Tirahi), {{temp}} begins with "te" and "tem" (codes for Telugu and Timne) and {{also}} begins with "als" (code for Tosk Albanian). Even apdx begins with apd. Furthermore, head was chosen on purpose, as an uncommon ending which is not used by other templates (there is no "Template:pt-head" or "Template:pthead") and very understandable as dealing with headwords.

Yes, new ideas for {{apphead}} are welcome. Though, proposing "the same kind of patterns as the regular templates" is subjective and prone to various interpretations.. Here are some schemes that would fit this description, regardless of which template name ("apphead" or "apdx") is used, to define the hypothetical fictional term incredibabble, an uncomparable adjective:

• {{apphead|incredibabble|adj|-}}
• {{apphead|incredibabble|comp=-}}
• {{apphead|incredibabble|nocomp}}
• {{apphead-adj|incredibabble|nocomp}}
• {{apphead-adj|incredibabble|-}}
• {{en-apphead-adj|incredibabble|-}}

The following version is simpler as having to type less characters and remember less concepts.

• {{apphead|incredibabble|comp}}

If there is no predictable need to label one term simultaneously as both comparable and countable, I don't see how logically parameters like comp= and count= would be useful. You might want to explain this point with more examples.

The value es serves different functions in {{en-noun|buzz|es}} and {{en-verb|buzz|es}}, therefore some distinction has to be made in appendice headword coding, instead of merely copying these two possible parameters.

The main advantage of using {{apphead|title}} over '''title''' is: don't worry, both work fine so they are interchangeable. The other advantages are cohesion and conveniency, because if all headwords tend to use the same template, the overall result is cleanier and more understandable; and, at least for me, it became easy to copy or automatically type templates where needed. By the way, there is potential to use styles on appendice headwords, so not all users might want to see exactly a main bold text. --Daniel. 04:08, 16 February 2010 (UTC)Reply

Should this be supported by {{poscatboiler}}? Mglovesfun (talk) 10:27, 16 February 2010 (UTC)Reply

Wouldn't Old French masculine singular past participles, Old French masculine plural past participles, Old French feminine singular past participles and Old French feminine plural past participles be better than Old French past participle forms? --Daniel. 10:38, 16 February 2010 (UTC)Reply

Do you intend to duplicate w:HTML element in the Appendix space? --Bequw → τ 14:25, 16 February 2010 (UTC)Reply

I wonder if describing usage details of various deprecated tags at w:HTML element violates the rule Wikipedia is not an indiscriminate collection of information. Anyway, I would expect Wikipedia to explain notable and in-depth information about HTML tags, such as comparison of web browsers by tag behavior, hystory of Web 1.0 and how character coding may be harmed by sites that use <font face= instead of <style="font-family:. In Wikibooks and Wikiversity, people may learn HTML through different didactical approaches. In Wiktionary, we deal with words. Probably, Wiktionary is the best Wikimedia project to explain, for instance, that "title" and "type" have more than one individual definition. Well, HTML is a constructed (and well-known) language, therefore it merits being defined in the Appendix namespace. If, by chance, Wikipedia has a list of HTML terms purely containing lexical information, it should probably be transwikified. --Daniel. 15:06, 16 February 2010 (UTC)Reply

	Hello, Daniel Carrero. You have new messages at WT:RFM#Appendix:English letters.
	You can remove this notice at any time by removing the {{talkback}} template.

Hi, can you give an example sentence for vc? --Rising Sun talk? contributions 21:56, 8 March 2010 (UTC)Reply

Yes, done. --Daniel. 05:41, 9 March 2010 (UTC)Reply

Do you think it would make more sense for {{list}} to interface with a category (Category:Blues) and take the list of blues from there, rather than creating a completely new list for something that already exists (but in category form)? Nadando 22:09, 8 March 2010 (UTC)Reply

No, I don't think that taking the terms out of a category to the list template would make more sense than the opposite. Compare these two alternatives:

===See also===
* {{list|en|blues}}

===See also===
* {{list|en|blues}}

]

In short, if the {{list}} took terms from the category, we would have to put terms in the category first. However, the opposite is currently done: When you add {{list|en|blues}} to an entry, that entry becomes a member of ]. --Daniel. 22:19, 8 March 2010 (UTC)Reply

Isn't the point of categories that we don't `need` to list everything on the same page? :p (Also, what's the benefit of splitting the documentation to a different page, it just means i have to watchlits more). Conrad.Irwin 22:58, 8 March 2010 (UTC)Reply

• (20 is on the big side of ok) one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten
• (30 is a good limit to me) one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten
• (40 is a few too many) one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten
• (60 is little excessive) one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten, one, two, three, four, five, six, seven, eight, nine, ten

How would you organize the various tones of blue on the basis that lists shouldn't reach sixty items? --Daniel. 23:14, 8 March 2010 (UTC)Reply

I would only include the common/useful ones (as defined by editorial discretion). I've never heard of eggshell blue or genitian blue, blue green is arguably not a blue, it doesn't need both cornflower and cornflower blue. My gut feeling would probably be to exclude most of the ones that are "X blue" just on principal, which leaves a meagre 13. That said, the current list isn't too bad either. Afterall, a huge list of items is likely to deter people, which is presumably why the category pages and index pages are not formatted as large in-line lists. Conrad.Irwin 23:45, 8 March 2010 (UTC)Reply

As I think, if any user see a list of English blues without cerulean (or any other blue tone, regardless of rarity, that he or she happen to know), the most likely conclusion would be that Wiktionary does not have this entry yet. This reasoning is also true for anagrams, verb conjugations, alternative spellings, etc. If a set is recognized as incomplete, the most likely constructive action would be to fulfill it. You might want to try something similar to {{list|en|TOP10 blues}} or {{list|en|most common blues}} (from my reasoning, these would be clearly sets of colors chosen by editors) but I would be against a deliberately incomplete {{list|en|blues}} because the deliberate incompleteness would be unclear then liable to misunderstanding. --Daniel. 00:13, 9 March 2010 (UTC)Reply

Urm... That is totally untenable :p. http://en.wikipedia.orghttps://dictious.com/en/Category:Shades_of_blue also lists 53 blues, not all of which we have categorised... The problem will be much worse for things like "breeds of dog". I don't think providing incomplete lists is a problem, particularly given that we also link to the category on the same line. It would even be possible to change it so that the category could be included as a more... link at the end of the list. Conrad.Irwin 00:37, 9 March 2010 (UTC)Reply

There are lists whose items decidedly share the same level of importance, commonness and usefulness, such as {{list|en|Latin letter names}} (twenty-six terms if we ignore alternative spellings such as zee and zed, possible ligature names and names of letters with diacritics) and {{list|ja|days of the month}} (at least thirty or fourty different names, if I remember correctly and ignore hiragana and romanizations). The set of dogs is not the case: instead of {{list|en|dog breeds}}, we may use {{list|en|hunting dogs}} and so on.

If we use the ^(more...) system, perhaps category names could fit into it, like ^{(more blues and colors)}. However, I still think that incomplete lists at entries are not the better course of action.

Complete lists are more informative, as I'd like to list the proprioception along with sight, smell, etc. through a {{list|en|senses}}. I can roughly predict that this list would totalize approximately ten items, along with sense of pain and sense of temperature.

If possible, please provide more details on how (approximately) 10 shades of blue would improve Wiktionary entries more than (approximately) 50 shades of blue would improve them. You said that the more extense version would deter people, but I don't think so: According to my idea of including all blues, if a user is interested on searching through them (say, if the user is looking for a particular shade), they are easily readable at each blue shade. They are even conveniently navigable because each link is at each related page. If more complex organization schemes are desirable (for instance, to list whether some words are more well-known), they may be listed at Appendix:Blues or Appendix:Colors if my previous proposal similar to {{list|en|basic blues}} is not utilized.

I'm sorry for the long message; in short, I'd like complete lists at entries and any more complex organizations at appendices. Additionally, if you'd like, {{list}} could be reformatted completely to generate collapsible boxes rather than horizontal lines of text. --Daniel. 04:17, 9 March 2010 (UTC)Reply

Hi, what's with the mass lists of entries? There's already a category link at the bottom of the page for this.

There is no lexicographical basis for linking to the term shocking pink in the entry for the term Indian red, along with a couple dozen other unrelated terms. This represents a thematic relationship between things, which Wikipedia covers. This stuff doesn't belong in the dictionary, which only deals with terms and their relationships, as in synonyms, derived terms, hyponyms, etc. —Michael Z. 2010-03-10 14:56 z

Hi, Michael. I've noticed some logical fallacies in your complaint, such as claiming that the relationship between shocking pink and Indian red doesn't belong to Wiktionary while still suggesting that they should be together in categories. Nonetheless, I think I can properly answer your question: Linked terms at See also sections have commonly existed at Wiktionary for years; my project is merely to standardize these links. (Few) entries of shades of red were already linking to other entries of shades of red before I've added that extense list, supposed to be complete. Therefore, three or thirty reds share a common set of definitions which makes them suitable to link to each other. If you don't like links based solely on definitions, I strongly suggest you to discuss your opinions at WT:BP. If you don't like the way I am standardizing them, you may also propose different approaches, such as lists with less items, for instance "(Pinks) hot pink, shocking pink" or lists with only "common", "useful" terms as defined by Conrad who probably would agree with you. Until the community reaches a consensus to modify or delete these lists, note that they are presumably easy to remove all together due to my efforts on organizing them; then, please don't revert anymore my contributions related to lists on the basis that they are contributions related to lists. --Daniel. 15:56, 10 March 2010 (UTC)Reply

I didn't say there should be encyclopedic category listings, just that there already are. I'll discuss this further at the BP. —Michael Z. 2010-03-10 17:47 z

{{poscatboiler}} seems to provide a link to Appendix:Greek adjectives - is this insertion under user control - and how? —Saltmarsh^{απάντηση} 06:50, 10 March 2010 (UTC)Reply

A link to Appendix:Greek adjectives is provided to Category:Greek adjectives and its subcategories (for instance, possibly Category:Greek adjectives, Category:Greek uncomparable adjectives, Category:Greek adjective superlative forms, Category:Greek adjective feminine forms, etc. if they exist). If the appendix exist, it is linked. It is not possible to choose to hide that link, but you might propose this function. --Daniel. 06:57, 10 March 2010 (UTC)Reply

OK - thanks —Saltmarsh^{απάντηση} 07:31, 10 March 2010 (UTC)Reply

You're welcome. --Daniel. 07:33, 10 March 2010 (UTC)Reply

Is there any reason for creating this vote? You archived the related discussion (which implies you thought it is over). Please note the top of WT:VOTE "Votes should not be called for on this page." - if you thought the issue needed voting on, it is more correct procedure to first ensure that people agree that a vote is needed, (and secondly, in this case, that there is more than one person who might support it). Conrad.Irwin 14:03, 15 March 2010 (UTC)Reply

If there isn't anyone that will openly support this, just delete it. I won't support it. Mglovesfun (talk) 14:10, 15 March 2010 (UTC)Reply

Exactly, Conrad: Some people were already accepting that change; I accept too. Although it is so big that I don't see how it wouldn't need a vote. Then I created that vote to gather people's opinions. As said by the yellow box: "It has been created to solicit advice on wording and fitness to purpose."

Most BP discussions I archived were technically over, but the RFD vs RFV was not one of them. One of my next steps planned for this voting procedure is starting a new BP discussion related to the previous discussion and the vote, rather than making people re-read arguments. Mglovesfun, I didn't see a reason to delete the vote; if people somehow dislike the very existence of this vote rather than its purpose or context, I could simply move it to my userspace and continue my work. --Daniel. 14:29, 15 March 2010 (UTC)Reply

Shouldn't this be adding top name categories (like Category:English names) to Category:Names by language? --Yair rand 00:30, 18 March 2010 (UTC)Reply

Actually, it seems like none of the categories done by this template are being added to the "by language" categories. Is it supposed to be working like this? --Yair rand 00:35, 18 March 2010 (UTC)Reply

I prefer to populate ] and related categories through {{namecatboiler}} as you suggested. I've introduced this function now. --Daniel. 02:00, 18 March 2010 (UTC)Reply

When using something like {{en-phrase|truly yours}}, there's no need to link the individual words in the etymology as well. This is why template have sg and head parameters. Mglovesfun (talk) 16:20, 20 March 2010 (UTC)Reply

I prefer to not follow this advice. A reason is the fact that I roughly remember one or two BP discussions about duplication of individual words between etymology and inflection line: their result (as I remember) was to not avoid such duplication, due to lack of consensus of where to place these links and how useful they theoretically would be. Personally, I would choose to remove links from all inflection lines, not etymologies, if duplication is not desirable but consistency is. Etymology sections with links to individual words are decidedly desirable for various entries, including foreign language ones such as the current toda brincadeira tem um fundo de verdade. --Daniel. 17:06, 20 March 2010 (UTC)Reply

Unless I am wrong, you have added gmq-osw as the code for Old Swedish. I have a question; view Category talk: Old Swedish language, please. Smiddle 08:32, 21 March 2010 (UTC)Reply

Hello Daniel.. I've retrained User:Dawnraybot to add Portuguese verb forms. Please can you check his recent entries, because I've been working from templates, and from an alpha version of a bot I sent to User:Volants, who doesn't want to continue his bot. --Rising Sun talk? contributions 04:07, 27 March 2010 (UTC)Reply

I did spot few issues on the current verb forms of agasalhar: the past participles have repeated definitions, agasalhara and other forms were not created yet and the contributions are all labelled as "French". The rest looks fine. --Daniel. 04:28, 27 March 2010 (UTC)Reply

please can you tell me which particular past participles have repeated definitions. --Rising Sun talk? contributions 05:10, 27 March 2010 (UTC)Reply

I've done another trial with abandonar. There's improvements --Rising Sun talk? contributions 12:57, 27 March 2010 (UTC)Reply

Apparently, you've fixed the past participles of agasalhar manually. I didn't see many improvements in abandonar. There are some entries with double definitions, such as abandonando, abandonámos and abandonaríeis. --Daniel. 06:22, 29 March 2010 (UTC)Reply

Hey could you please try to fix this so that when invoked in the English category there is no "en" prefix in the link to Category:Typography? 50 Xylophone Players talk 15:17, 28 March 2010 (UTC)Reply

Done. --Daniel. 06:08, 29 March 2010 (UTC)Reply

Hi, I created the {{list:days of the week/hu}} template and I was wondering if these type of templates should be listed in the Template category for the appropriate language. It would be easier to find. Your thoughts, please? --Panda10 10:45, 29 March 2010 (UTC)Reply

In my opinion, this is a very good idea. Done. --Daniel. 10:59, 29 March 2010 (UTC)Reply

I hope you're ready to fix all these now. — opiaterein — 13:48, 29 March 2010 (UTC)Reply

Of course I am. --Daniel. 13:52, 29 March 2010 (UTC)Reply

? I would have thought it better to open with a simple single-word translation, which is then clarified with a fuller explanation, rather than the other way round. --EncycloPetey 22:10, 29 March 2010 (UTC)Reply

In my opinion, any of these two arrangements would be fine, but I see no particular improvement on this proposed emphatization of "thick" as the definition of "grosso". Both the English word and the Portuguese word have too many meanings. Anyway, I usually create definitions comprised of two to four different simple wordings such as the more recent "Offensive to morality; obscene; distasteful; vulgar." so the roles of the "single-word translation" and the "fuller explanation" are, as I see, quite interchangeable. --Daniel. 22:42, 29 March 2010 (UTC)Reply

Hi, please can you provide more information. Why does tc mean type? Maybe another example sentence? --Rising Sun talk? contributions 18:57, 30 March 2010 (UTC)Reply

Yes, I can. Done. --Daniel. 04:40, 31 March 2010 (UTC)Reply

There was a move to support cap= and dot= instead of nocap= and nodot=, they are more pleasant for editors, you can see arrangments and rottweillers for how they were (ab)used. Conrad.Irwin 10:20, 31 March 2010 (UTC)Reply

Hrm, dot= is tricky, there are several hundred pages using |dot=}}, but of course that's hard to pass through meta-templates. Not sure the best thing to do, perhaps pass a sentinal value of NONE through from the templates when it is not set on the page? The cap= is also tricky to do in a meta-template, but I'll fix the few pages in which it has been used to include the article, or a bracket as well as the initial letter. Conrad.Irwin 11:06, 31 March 2010 (UTC)Reply

Good. The {{deftempboiler}} seems to be fully functional now, including its parameters cap= and dot=. Thank you for fixing those pages and for your suggestions. --Daniel. 11:58, 31 March 2010 (UTC)Reply

No problem, thanks for fixing "everything"! Conrad.Irwin 13:23, 31 March 2010 (UTC)Reply

You broke it...Please fix it. 50 Xylophone Players talk 11:33, 31 March 2010 (UTC)Reply

I've broken the template indeed. I'm sorry for that. However, that situation was temporary. I've fixed the template before I received your message. It should be working properly now. --Daniel. 11:38, 31 March 2010 (UTC)Reply

Yep, it's okay now. 50 Xylophone Players talk 13:15, 31 March 2010 (UTC)Reply

Hi Daniel.. I've added 2 new rules to the competition - the first allows me to create new rules ;p and the second demands a translation of the quote into English. --Rising Sun talk? contributions 19:34, 1 April 2010 (UTC)--Rising Sun talk? contributions 19:34, 1 April 2010 (UTC)Reply

Understood. In that case, I'll translate the translations myself. :) As opposed to "stealing" the English words directly from J. K. Rowling; I have the official Harry Potter books in Portuguese but can't reach the English versions so soon to aim for fan-friendly perfection. --Daniel. 19:47, 1 April 2010 (UTC)Reply

This needs a sortkey, but I'm not quite sure how to do it. See Category:Languages by script. --EncycloPetey 21:57, 5 April 2010 (UTC)Reply

Done. --Daniel. 22:07, 5 April 2010 (UTC)Reply

Gracias. --EncycloPetey 22:15, 5 April 2010 (UTC)Reply

De nada. --Daniel. 22:24, 5 April 2010 (UTC)Reply

Related question: Why does Category:Greek script languages contain Category:Ancient Greek language, but not Category:Greek language? --EncycloPetey 22:18, 5 April 2010 (UTC)Reply

Because the information |el=Grek was not present at {{langscript}} when you asked this question. Prince Kassad added it seconds ago. --Daniel. 22:24, 5 April 2010 (UTC)Reply

This generates the wrong category name. I suspect en-prefix will as well. --EncycloPetey 06:16, 8 April 2010 (UTC)Reply

Fixed. --Daniel. 06:46, 8 April 2010 (UTC)Reply

Thanks. These are templates we should have had a long time ago. --EncycloPetey 06:49, 8 April 2010 (UTC)Reply

Agreed; we should. Eventually, similar templates may be easily created by adapting their codes, like I done with {{pt-prefix}} and {{la-prefix}}. Enjoy. --Daniel. 08:26, 8 April 2010 (UTC)Reply

Thanks again, although Latin doesn't have very many true prefixes. Does the general template permit the specification of gender? Some suffixes in Romance languages have a particular gender, like Spanish (deprecated template usage) -ción or (deprecated template usage) -idad.

Trying to expand that template to cover Latin suffixes might be too much, though. Latin suffixes sometimes inflect (with a specific declension pattern), sometimes have macrons, and sometimes have gender, which has led to the several templates I've created for them that mimic the noun, adjective, and adverb templates. I spent a lot of time thinking about the problem before starting to work on Latin suffixes and creating the templates. The huge differences in number and kind of parameters needed, and keeping it all straight for editors, suggested that having several templates for Latin suffixes was preferable to an attempt to do it in one. --EncycloPetey 14:48, 8 April 2010 (UTC)Reply

All right. Since the Latin suffixes are apparently well covered, I think we don't need to use {{headtempboiler}} for them. --Daniel. 01:21, 9 April 2010 (UTC)Reply

Please do let me know when you're happy with {{pt-suffix}}. I've modeled {{es-suffix}} on it, but don't want to start implementing it until all major changes are finished. --EncycloPetey 21:11, 8 April 2010 (UTC)Reply

I am happy with {{pt-suffix}}. All Portuguese suffixes that I could quickly find are templatized; so I believe you may implement {{es-suffix}} too. --Daniel. 01:21, 9 April 2010 (UTC)Reply

Noun instead of initialism? Why? Equinox ◑ 11:07, 10 April 2010 (UTC)Reply

Initialism isn't really a part of speech like noun is. Consider DVD, DVDs. Ideally wherever possible they should be in both categories (IMO) with noun as a header in this case. Mglovesfun (talk) 11:11, 10 April 2010 (UTC)Reply

Hear, hear! --Daniel. 17:22, 10 April 2010 (UTC)Reply

Hi Daniel.,

Just so you know, Rising Sun has requested verification of your entry ]. If you could add durably archived quotations demonstrating its use in Portuguese, I'd appreciate it.

Thanks in advance!
—Ruakh_TALK 15:40, 10 April 2010 (UTC)Reply

Hello, Ruakh. Yes, I noticed two interesting Portuguese entries which came from English and are currently undergoing RFV: I love you and the other you mentioned. I plan to attest both soon. --Daniel. 03:11, 11 April 2010 (UTC)Reply

Please do not create hard redirects. Wiktionary aims to define every term, including variants. If you think these are SoP, then simply don't add entries for them. ---> Tooironic 05:32, 11 April 2010 (UTC)Reply

I didn't find a consensus written anywhere, including Wiktionary:Redirections, to endorse your statement; so I suppose we are merely talking about your judgement against mine. In this case, I'm planning to continue doing what I've always done: creating hard redirects when I want and think they could be useful, a decision which results in approximately 1.4 new entry redirects per year as I remember. --Daniel. 10:02, 11 April 2010 (UTC)Reply

FWIW, to my knowledge, Tooironic is right on this point. Our conventions frequently go uncodified in policy, so it's no surprise that you don't find his statement backed-up. IIRC, one of the few cases where hard redirects are permitted are for conjugated and declined forms of multi-word idioms, but some even object to their use in that case.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 13:13, 11 April 2010 (UTC)Reply

Let's see if we can empty this, and Category:English words spelled with nonstandard characters. I'll need yours (or someone else's) help, as there are some characters I don't recognize. Mglovesfun (talk) 20:58, 13 April 2010 (UTC)Reply

OK. A fairly considerable quantity of my help was already provided, since many members of Category:English spellings by character were moved by me. Thanks for working on this project too; you can count on me to help to empty that category from now. --Daniel. 21:29, 13 April 2010 (UTC)Reply

Yeah, I need help with the ones with very rare characters, especially since all of them have to be in uppercase, which prevents copy-and-paste. I can do almost all of them by bot. I've done 300 already, but it's not all that quick. Mglovesfun (talk) 10:59, 16 April 2010 (UTC)Reply

(Pardon me for butting in.)

Can we give some thought to tweaking the terminology and categorization in the long run? The naming of, e.g., Category:English spellings by character and Category:English terms spelled with É is not technically correct. In the computer-encoding sense, É, é, E, and e are all different characters. But in terms of language and writing, which are the direct concern of the dictionary, they are all the same letter e (from both letter cases, with or without diacritic). This kind of lax naming leads to people saying that expose and exposé are “spelled differently”, that é is a “foreign letter,” and attributing lexical significance to every Unicode code point (e.g., creating dictionary entries referring to оу and ѹ, different encodings of the exact same letter, as “alternate spellings”). —Michael Z. 2010-04-16 16:06 z

Would Category:English spellings by glyph improve things?  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 16:14, 16 April 2010 (UTC)Reply

Not really, I think. In computer terms, glyph is still further removed from the concept, referring to the “artwork” displayed (e.g. Times Roman has a different glyph for é than Times Italic, or Helvetica Semibold). In writing/language terms, I think e is a drawn or printed glyph, and the accent is a separate mark placed over it. I believe we need to give some thought to rearranging the categories, not just picking a better name. —Michael Z. 2010-04-16 16:25 z

Maybe glyph isn't incorrect, but in non-computer contexts it doesn't usually mean an English/Latin letter. —Michael Z. 2010-04-16 16:54 z

In my opinion, the current categorization scheme is more useful than other approaches that I could think, like possibly a category with English terms spelled with "É", exactly as upper case letter with acute accent. Or, perhaps, a category of English terms with acute accent. --Daniel. 16:33, 16 April 2010 (UTC)Reply

I don't know if it be worth it, but I kind of want to see parallel “by character” and “by diacritic” categories at the same level, since diacritics get applied to characters. There may be other considerations for other languages (I think in some European languages, e.g., å is considered a single digraph letter, not a letter a with diacritic). I'm not asking anyone to do a bunch of work rearranging everything right now, but let's think about this. I'd be glad to help out. —Michael Z. 2010-04-16 16:54 z

So, Michael, please inform your opinion (or clarify it) on this possible categorization scheme: The current categories English terms spelled with Á, English terms spelled with É and English terms spelled with Ó all together in a supercategory of the acute accent. --Daniel. 17:34, 16 April 2010 (UTC)Reply

Okay, here's a proposal. Going down this road would have various repercussions on the way we handle other languages, but it would make our categories more in touch with the dictionary's content.

• Category:English spellings
  • Category:English spellings by character
    • Category:English terms spelled with 0 ... 9
    • Category:English terms spelled with !, &, ', *, etc. (including @ and $)
    • Category:English terms spelled with æ, þ, ð, œ ... (dated or foreign-derived English)
    • Category:English terms spelled with α, β, γ, δ ... (Greeks)
  • Category:English terms with diacritics
    • Category:English terms with acute accent
      • Category:English terms with á
      • Category:English terms with é
      • Category:English terms with ó
    • Category:English terms with cedilla
      • Category:English terms with ç
    • Category:English terms with circumflex
      • as above
    • Category:English terms with diaeresis
    • Category:English terms with grave accent
    • Category:English terms with háček
    • Category:English terms with macron
    • etc.

For each language, we'd have to determine which are considered letters (e.g., Swedish w: å, maybe Dutch w: ij) and which are considered letters with diacritics. This would be a bit of work, but then the results would better reflect the real meaning of the written symbols we are presenting.

(By the way, I don't think we should have Category:English terms spelled with ſ at all: the long s is a typographical stylistic form, used in every word containing a non-terminal S. There is no difference in the spelling of perſons and persons.) —Michael Z. 2010-04-16 19:07 z

In re (deprecated template usage) ſ, see Wiktionary:Beer parlour archive/2010/January#ſ (long s) typographic variants &c.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 19:15, 16 April 2010 (UTC)Reply

From scanning over that talk, sounds like we might include it for German, but omit it for English. This would support a language-specific categorization of letters, digraphs, diacritics, etc. Does it get complicated where German ö = oe, etc? —Michael Z. 2010-04-16 19:21 z

IIRC, the conclusion was to autoredirect all occurrences of (deprecated template usage) ſ to (deprecated template usage) s, but to have that redirection bring up a noticeable banner explaining the redirection and with a link to a page that would explain the history of use of the long ess, with special import given to such rarities as the German (deprecated template usage) Wachſtube.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 20:22, 16 April 2010 (UTC)Reply

So its repercussion on this topic is that there is no need for Category:English terms spelled with ſ, because its contents would consist only of autoredirect addresses, right? All I see in the category's entries are a couple of citations that should be moved to the respective modern-spelling entries. —Michael Z. 2010-04-16 21:13 z

In theory, yes. Once the banner and link to an explanatory appendix is sorted, that category should be regarded as a clean-up category.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 03:57, 17 April 2010 (UTC)Reply

Hm. Looking at my proposal above, I see categories named “English terms spelled” and “English spellings.” But this branch is different than the majority in Category:English spellings, because it doesn't group alternate, archaic, etc, spellings of terms. It's really “English terms by character” and “diacritic.” —Michael Z. 2010-04-16 21:51 z

“English terms by character” does indeed seem a much better name. Mglovesfun (talk) 21:57, 16 April 2010 (UTC)Reply

Re: Kırklareli, when you capitalize the dotless I, it just turns into a Latin capital I, so that can't appear in any categories. Mglovesfun (talk) 22:05, 16 April 2010 (UTC)Reply

Ah, you mean it can't appear in category names? Do both Turkish i's become the same letter in caps? Could name the category Category:English terms spelled with ı or Category:English terms with dotless I. Do we need a Turkish-language category for it? I thought we were only doing this for unusual characters, not for every letter A–Z. —Michael Z. 2010-04-17 00:29 z

The Turkish lower-case (deprecated template usage) ı becomes the upper-case (deprecated template usage) I, whereas the Turkish lower-case (deprecated template usage) i becomes the upper-case (deprecated template usage) İ. Consistency would require us to categorise every Turkish derivation containing (deprecated template usage) I or (deprecated template usage) i into their respective special-character categories because of their complimentary forms in the other case.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 03:57, 17 April 2010 (UTC)Reply

So imam bayildi belongs in both Category:English terms spelled with I and Category:English terms spelled with İ? I guess we could try to put a prominent warning on the former category that only Turkish derivations belong in it, but I could see a thousand other words creeping into it. It could be named Category:Turkish derivations spelled with I. —Michael Z. 2010-04-17 14:37 z

Well, no, that page doesn't belong in the categories (except maybe Category:English terms spelled with İ, though it looks to me as if that spelling has just been "normalised" with ordinary Latin 'i's, although there isn't really any way of knowing). If it's also spelt (deprecated template usage) imambayıldı in English (with or without a space as (deprecated template usage) imam bayıldı), then that page would belong in both those categories. As you've already noted, the fact that the nomenclature uses upper-case letters as standard may be problematic; we may simply need to make an exception for ı–İ. Alternatively, the substitute category name you propose would be, IMO, the way to go.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 15:18, 17 April 2010 (UTC)Reply

Would Category:English terms with é include the term Étaín? --Daniel. 05:26, 18 April 2010 (UTC)Reply

Yes. (I tried out lower-case letters in the category names above, because I think they are often easier to read on screen.) —Michael Z. 2010-04-18 21:51 z

In my opinion, upper case letters would be easier to read on screen as some groups of lower case letters are too similar: i/j/l, c/o/q and probably others. In addition, I think that upper case is the more common version used in dictionaries, keyboards, etc. to refer to each letter. I'd also like to make another suggestion: The wording Category:English terms spelled with É is better than Category:English terms with É as consistent with other current naming system: Category:English words suffixed with -ness. --Daniel. 14:04, 20 April 2010 (UTC)Reply

I find that diacritics on capitals can be harder to distinguish at normal screen resolutions, especially É, È, Ë, Ě, Ĕ, Ẽ, Ē, vs é, è, ë, ě, ĕ, ẽ, ē (and by some French conventions for example, diacritics are omitted from caps, even in print). Several Greeks are identical to Latin capitals, and no text resizing will change this (Α, Β, Ε, Γ, Ζ, Η, Ι, Κ, Μ, Ν, Ρ, Τ, Υ, Χ, vs. α, β, ε, γ, ζ, η, ι, κ, μ, ν, ρ, τ, υ, χ).

Did you even notice that your argument for consistency uses an example of a category name containing English words and another with English terms? Consistency is good, but these minor inconsistencies are not a hindrance to the reader, if they're even noticeable at all. in contrast, an index intended to sort out letters and diacritics is quite broken if those letters and diacritics aren't distinguishable.

(If you have difficulty with i j l and c o q then you might have more fundamental readability problems. Maybe you should increase your browser's font size or change the font in your user style sheet.) —Michael Z. 2010-04-22 16:05 z

I personally am currently stuck with a hateful 13'' screen with slightly poor focus that is probably blinding me as I write. :| Anyway, I agree with your arguments: lowercase is better than uppercase if we choose only one case to represent each "character". Although I still want the wording "spelled with" rather than simply "with" since I intuitively think that Category:Portuguese terms with à would contain "ir à Roma e não ver o papa" but wouldn't contain "àquele". --Daniel. 16:21, 22 April 2010 (UTC)Reply

I admire your dedication to this project. —Michael Z. 2010-04-22 17:36 z

Well, thanks. --Daniel. 19:20, 22 April 2010 (UTC)Reply

I agree with the use of lower-case characters as standard* (with redirects from the upper-case forms, if possible) and with the wording "spelled with" per Daniel.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 16:54, 22 April 2010 (UTC)Reply
* Except that the Turkish ı–İ problem still exists with that nomenclature…

I don't object strongly to “spelled with.” We could use uppercase plain letters (A B C D E F) and lowercase to emphasize the contrast with diacritics and Greeks (á β ç δ ē γ, not Á Β Ç Δ Ē Γ). This has a consistent visual logic for English, and another language may call for a different variation. —Michael Z. 2010-04-22 17:36 z

Aah, that could work! So, do you mean something like Category:English terms spelled with Æ, æ, Category:English terms spelled with I, ı, and Category:English terms spelled with İ, i?  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 18:06, 22 April 2010 (UTC)Reply

That's another option, but, since we don't have plain-letter categories like Category:English terms spelled with A, I was still thinking of converting all the names in Category:English spellings by character to lowercase. Advantages: resolves the problems of Greek α, β, resolves the Turkish un-dotted ı, slightly improves the readability of ē, &c. Consequence: sort headings either remain in a contrasting case, or get changed to to match those common in category listings for terms. There's no reason for the Greek sort heading to be a question mark, when α clearly stands for the Greek alphabet. —Michael Z. 2010-04-22 19:07 z

Converting to lower case may resolve the problem of the Turkish (deprecated template usage) ı, but it creates the problem of the Turkish (deprecated template usage) İ (as in (deprecated template usage) İzmir). Other than a gloss (like "dotted i" or "undotted i"), giving both cases of the characters is the only way I can see to resolve the problems of both those Turkish letters whilst maintaining consistency.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 19:23, 22 April 2010 (UTC)Reply

This is a problem no matter what. Because the upper and lowercase forms correspond to different English letters, we either have to make an exception in case or include a gloss. Neither Turkish letter really corresponds to a single English one, so I would use two categories with “Turkish i” and “Turkish ı” (or Turkish İ and Turkish I). Or will these be coming from other languages too?

Or can we consider Turkish i to be the same letter as English/Latin i, with an alternate uppercase form? —Michael Z. 2010-04-22 21:17 z

This affects (deprecated template usage) Afyonkarahisar, (deprecated template usage) bektashi, (deprecated template usage) beylic, (deprecated template usage) binbashi, (deprecated template usage) comitadji, (deprecated template usage) dervish, (deprecated template usage) Dervish, (deprecated template usage) devshirme, (deprecated template usage) divan, (deprecated template usage) haremlik, (deprecated template usage) ibrik, (deprecated template usage) ichoglan, (deprecated template usage) imam bayildi, (deprecated template usage) imbat, (deprecated template usage) irade, (deprecated template usage) İzmir, (deprecated template usage) janissary, (deprecated template usage) kilim, (deprecated template usage) leblebi, (deprecated template usage) mahaila (?), (deprecated template usage) millet, (deprecated template usage) minaret, (deprecated template usage) muezzin, (deprecated template usage) narghile, (deprecated template usage) pilaf, (deprecated template usage) rakija (?), (deprecated template usage) shish, (deprecated template usage) shish kebab, (deprecated template usage) shisha, (deprecated template usage) shishkabob, (deprecated template usage) spahi, (deprecated template usage) vilayet, (deprecated template usage) vizier, (deprecated template usage) ziamet, and (deprecated template usage) zill. In theory, anyway; that list is all our Turkish derivations in English for which it isn't absolutely impossible for the Turkish (deprecated template usage) i to have been preserved in English. For the vast majority of them, I am of the opinion that they are just written with normal letters (deprecated template usage) i.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 21:54, 22 April 2010 (UTC)Reply

Nota bene w:Dotted and dotless I#Usage in other languages.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 22:02, 22 April 2010 (UTC)Reply

Are the above languages' alphabets derived from the Turkish? Could we still call it a Turkish(-alphabet) i/ı if it's in a word from one of those languages? It appears that the Gaelic dotless I is a stylistic variation, and not a different letter, so it should be handled by specifying an appropriate font rather than by entering a different code point (anyone know?). —Michael Z. 2010-04-22 23:55 z

I would be inclined to say not, but I just wanted to make the list as comprehensive as possible. IMO, we can omit from those categories any word which does not preserve the other spelling features of its Turkish etymon (which should remove the vast majority of them). Moreover, restricting membership in the categories to direct derivations from Turkish may be a sensible regulation. Regaring the Gaelic (deprecated template usage) i, in technical terms, the tittle is not graphemic; see also the last two paragraphs of w:Irish orthography#Diacritics.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 00:14, 23 April 2010 (UTC)Reply

As an active Portuguese language contributor, I strongly support the addition of categories for the following plain-letter characters of that language: K, W, Y and their lowercase counterparts (that is, possibly Category:Portuguese terms spelled with K and so on). They are incredibly rare; to the point of being usually substituted by other letters when a word comes from other language. For instance, caratê means karate, quilo means kilo and Válter means Walter. --Daniel. 19:20, 22 April 2010 (UTC)Reply

Doremítzwr and Michael, would you object if I remove the pieces of text "a rare character in this language" or "a obsolete character in this language", which are currently present at the discussed categories? I'm not a big fan of this type of statement at that place; one reason is: Perhaps it could serve as criteria for inclusion (since A is not rare, we don't want a English terms spelled with A, but Ü is rare, so we have English terms spelled with Ü) But this criteria doesn't reflect flawlessly the current categories, because ' and * are not rare characters. --Daniel. 22:00, 23 April 2010 (UTC)Reply

Far from it; I'd consider the removal of those pieces of text an improvement. I've objected to "a rare character in this language" in the past. Also, when it's done with (deprecated template usage) archaic, IIRC it yields "a archaic character in this language".  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 22:28, 23 April 2010 (UTC)Reply

The erroneous wording "a archaic" is not a serious problem; because, if we actually wanted to inform such contexts at the category descriptions, it could be easily and automatically changed to "an archaic". But, since we don't want the contexts, I removed them all. --Daniel. 19:17, 24 April 2010 (UTC)Reply

Hi Daniel. Please ensure that when you create entries requested in that list that they satisfy the criteria for inclusion. Many of your recently-created entries are now at RFV or RFD. You're only wasting your own time and creating unnecessary work for others by making entries that are either RFD fodder or which would fail to pass a request for verification.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 20:48, 15 April 2010 (UTC)Reply

Of course I will aim to satisfy CFI when contributing to Wiktionary. Although I don't consider my edits particularly unsatisfying, be them from that list or not, because the entries created by me are usually kept, even after a healthy RFV or RFD discussion when necessary. --Daniel. 23:54, 15 April 2010 (UTC)Reply

That doesn't seem to be the case with, for example, (deprecated template usage) kawaiify, (deprecated template usage) so do I, and (deprecated template usage) neither do I. I thought it best I'd mention it, since I've noticed a pattern with the requests from Wiktionary:Wanted entries and, well, prevention is better than cure, and all that…  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 00:25, 16 April 2010 (UTC)Reply

The three entries you mentioned seem to be the most recent ones that were created by me and are discussed at RFV or RFD, so a consensus was not reached for them yet. When I create an entry, I suppose it will be kept, as opposed to deliberately waste time of any editors. I also check for their related discussions regularly; so, for instance, I recently formally discovered that the entry Tetris-like should not exist due to consensus, then I'll refrain from defining more English nouns ending in "-like" like that one. On the other hand, kawaiily, unownable, who are you and what have you done with someone, absent-minded professor, response time and many other entries that were created by me seem acceptable. For these reasons, I think I don't need to change my pattern of contributions based on your comments. Nonetheless, feel free to comment on my contributions anytime. --Daniel. 02:22, 16 April 2010 (UTC)Reply

Don't get me wrong — I'm not saying that all your contributions are bad or that you're deliberately wasting anyone's time; most of your contributions are good. I ask, however, that you do two things: 1) Use {{b.g.c.}} and/or {{google|type=groups}} (&c.) to ensure that the terms you're adding occur with sufficient frequency in durably archived media to satisfy one or more of the CFI's attestation criteria. & 2) Think carefully as to whether your multi-word contributions are idiomatic (i.e., not SOP); for example, (deprecated template usage) absent-minded professor would not be includible if it just meant "a professor who is absent-minded", but since it is a term that can be applied more broadly to any oblivious academic (or, broader still, to any person oblivious of reality), it is therefore idiomatic. Is it reasonable that I request that you take those small steps?  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 02:39, 16 April 2010 (UTC)Reply

Yes, frequency checking and SOP avoidance are reasonable steps to be taken by me. Although, as you certainly know, both attestability and idiomacity are not absolute references: Some terms may be considerably confusing like security through obscurity, that as Conrad pointed out at RFD, is rather considered lack of security than a SOP of "security + through + obscurity". Others are rare enough to be controversial, like kawaiiness whose meaning is supposedly not known by people without interest in Japanese culture; presumably all others at RFV and RFD are initially controversial too, so kudos to people who are creating and solving such discussions, including you. In an effort to improve my entries, I could also attest more of them by adding quotations, since I don't do this very much. --Daniel. 05:28, 16 April 2010 (UTC)Reply

That would be great; thanks for your coöperation. I agree that idiomaticity is a difficult one to judge sometimes, though attestability is pretty easy, thanks to our more-or-less objective criteria for it (well, that much applies to the fourth criterion at least, and that is the most commonly invoked one). The meanings of all the terms derived from (deprecated template usage) kawaii ((deprecated template usage) kawaiify, (deprecated template usage) kawaiily, and (deprecated template usage) kawaiiness) are obvious as long as one is aware what (deprecated template usage) kawaii means; however, that isn't the salient point. (deprecated template usage) Kawaiily was only attestable via Google Groups; although google books:"kawaiiness" yields only two hits, there are 640 Google Groups Search hits to choose from; conversely, google books:"kawaiify" OR "kawaiifies" OR "kawaiifying" OR "kawaiified" yields nothing, whereas none of the nine Google Groups hits are valid (you must ensure that "Google Groups" is selected, not "all groups"). I hope that makes sense. Thanks again.  — Raifʻhār Doremítzwr ~ (U · T · C) ~ 18:08, 16 April 2010 (UTC)Reply

We seem to lack an entry for the Portuguese verb! I'm going to do what I can, but please clean up after me, if you would. --EncycloPetey 21:35, 17 April 2010 (UTC)Reply

You did a good job when contributing to the entry agir. After a quick research I unsurprisingly couldn't find more than one or two definitions per dictionary (including the Portuguese Wiktionary) and you covered them all. I then splitted that definition into two, added the language-specific templates and links to other Portuguese words. So, done. --Daniel. 05:22, 18 April 2010 (UTC)Reply

Come how {{poscatboiler}} doesn't allow it? Mglovesfun (talk) 13:50, 20 April 2010 (UTC)Reply

Interlingua plurals differs from the naming system present in all {{poscatboiler}} categories. Specifically, I think a category Interlingua plural forms would be more acceptable, since the word "forms" appears in all POS categories that should inherently contain non-lemma terms. Additionally, each language has plurals for different parts of speech, so the main purposes of poscatboiler would be defeated by a standardized text and place in a category tree. In my opinion, Category:Interlingua noun plural forms and Category:Interlingua adjective plural forms would be examples of categories flawlessly supported by that template. --Daniel. 14:12, 20 April 2010 (UTC)Reply

So why does it accept Category:English plurals? BTW I do agree. Mglovesfun (talk) 14:14, 20 April 2010 (UTC)Reply

The category "English plurals" is not supported by poscatboiler. --Daniel. 14:28, 20 April 2010 (UTC)Reply

Hi,

I followed your example and created Template:list:Cyrillic script letter names/ru. Other Cyrillic based languages can be added. --Anatoli 05:00, 22 April 2010 (UTC)Reply

Very good. Feel free to contribute on my Wiktionary projects anytime. --Daniel. 05:15, 22 April 2010 (UTC)Reply

Hey do you think you could support for duals to this? Thanks. Breton, for one, is a language that needs such a category. — This unsigned comment was added by PalkiaX50 (talk • contribs).

Yes, I can add support for dual forms. Firstly, please inform which dualized parts of speech do you need. For instance, do you expect to create categories for dual nouns, dual adjectives, dual verbs? --Daniel. 13:36, 22 April 2010 (UTC)Reply

Well, dual nouns at least. That's what Breton has (though it may have dual adjectives too, (deprecated template usage) idk). I asked because I saw the Category "Breton duals" on WantedCategories. 50 Xylophone Players talk 15:21, 22 April 2010 (UTC)Reply

As I see, the category name Breton duals, like English plurals, is not likely to enlighten a reader nor provide a suitable workspace for editors; in addition, it is named differently from other {{poscatboiler}} categories and is probably not standardizable due to the various possible descriptions and category trees of duals of each language. You may want to see the related and recent discussion Interlingua plurals at my talk page. If you want to create and/or edit the category Breton duals, please don't use poscatboiler for it. On the other hand, it is advisable to create the newly-supported categories Breton noun dual forms and Breton adjective dual forms. --Daniel. 15:50, 22 April 2010 (UTC)Reply

Gothic verbs conjugate to dual forms. So we definitely need support for dual verb forms. -- Prince Kassad 09:29, 24 April 2010 (UTC)Reply

OK. You may use {{poscatboiler|got|verb dual form}} in Category:Gothic verb dual forms now if you want. --Daniel. 19:42, 24 April 2010 (UTC)Reply

The heading for the list has been formatted to look like a restricted-usage label (a context label). But the heading is not a context label, so this will cause confusion. (And why put the whole list into a one-item unordered list? Why does this list include “week,” which is not a day of the week?)

Instead of this:

• (days of the week) week; Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

Why not format it more simply, like this?

Days of the week: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

Or with the structure of a definition list?

Days of the week

Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

(You could even add semantic structure by making the whole list a DL definition list, with the heading in a DT and each item in a DD.) —Michael Z. 2010-04-24 20:27 z

I know what DL, DT and DD are, but I have not fully understood what you mean by "semantic structure"; so please explain further, if you would.

The list includes the term "week" because it explains well how the items are connected. If a person does not know what is a week, he or she might learn by clicking on the link. Similarly, and more likely to be unclear, if a person sees a list of types of random access memory "(random access memory) random access memory; single data rate, double data rate, static random access memory, dynamic random access memory", he or she might learn about that hypernym easily that way.

In my opinion, the current italicized explanatory text between parentheses is not particularly confusing, neither it lacks simplicity. Specifically, I like how that text is clearly separated from the items. Let me quote your first suggestion:

Days of the week: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

I think its overall effect is undesirable because I have to search for where the title ends and the list starts. The blue links may help, but please note that an appendix can be linked to the explanatory text (as an option of {{list}}), so another possible effect is:

Days of the week: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

Mentally separating the text from the items is not a difficult task, but it might be avoided by some basic formatting. For that reason, I like your second suggestion:

Days of the week

Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

--Daniel. 03:55, 26 April 2010 (UTC)Reply

This template, and all others like it, will need to be revised to correctly make use of the /doc subpages. --EncycloPetey 21:37, 24 April 2010 (UTC)Reply

OK. The letter templates were revised as you asked. --Daniel. 03:17, 26 April 2010 (UTC)Reply

Don't know which ones, or what the cause is, but {{de-phrase/doc}} and {{pt-suffix/doc}} were the ones I noticed. Conrad.Irwin 01:15, 26 April 2010 (UTC)Reply

In case you are talking about the template loops, and are interested in the cause, it is: There were little pieces of code whose purpose was automatically getting each template name to create examples of usage of such templates. These "pieces of code" were not programmed for a sudden move from talk pages to /doc pages, so documentations were naturally doomed to be adapted sooner or later. I believe they are fixed now. --Daniel. 03:15, 26 April 2010 (UTC)Reply

Can you think of a good way to display the list of duplicate language names on both WT:LANGNAME and on the documentation of the language templates (eg {{fa/doc}})? It would be nice if the information could be shown in both places and even at the entries (eg Farsi, Persian) without too much manual updating to keep them synced. Would we want something like Template:fa/names for language templates? --Bequw → τ 01:10, 30 April 2010 (UTC)Reply

Yes, I think I could do the "think of a good way to display the list of duplicate language names on both WT:LANGNAME and on the documentation of the language templates" since I received your message. Then I created a new set of parameters from scratch. See Template:si. --Daniel. 10:30, 30 April 2010 (UTC)Reply

I like it. Thanks. Maybe pass it by the GP before using widely? --Bequw → τ 21:26, 30 April 2010 (UTC)Reply

Yes, a GP discussion would be good. Then I've started one. --Daniel. 21:42, 30 April 2010 (UTC)Reply

Hi, I suggest you don't try to spend any more time on {langtempboiler}, as I've tried to explain, it is not possible to add another layer and expansion to these templates without blowing out the page expand limit in the parser. Whatever it is you are trying to do can not be done in the templates.

I moved "testingtest" to a user subpage, it was breaking tools. Should not be in cat. Robert Ullmann 17:56, 4 May 2010 (UTC)Reply

Ah, I forgot the tools; sorry for placing "Template:testingtest" in that dangerous category and thanks for removing it from there. Thanks for your suggestions too; although I'm still planning to spend some more time on langtempboiler, at least for self-instructive reasons. I'm generally curious about the limits and possibilities of MediaWiki templates; such knowledge would help me to find and solve technical problems better, even if, as you imply, the current language templates don't have problems to be solved. --Daniel. 07:29, 5 May 2010 (UTC)Reply

How did I fuck up Category:Walloon cardinal numbers? You make templates too complicated for ordinary users like me --Soleil levant 08:08, 30 April 2010 (UTC)Reply

Well, you may adapt the code of Category:Portuguese cardinal numerals into a Category:Walloon cardinal numerals if you want to use {{poscatboiler}}. A convenient reason is: poscatboiler relies on consistency between many languages. Currently, due to the lack of consensus, the members of a category called " numbers" could possibly be either numerical symbols or words of that language. That template can't know that you want to keep words in Category:Walloon cardinal numbers, so I mercifully removed poscatboiler from that category. --Daniel. 08:33, 30 April 2010 (UTC)Reply

You know damn well that if it goes to a vote that "cardinal numbers" would win out, because we speak English here. It's bad faith to continue with a policy that's against the consensus and can't possibly win out. Mglovesfun (talk) 10:32, 30 April 2010 (UTC)Reply

You've got to get it out of your head that you own these templates. If you want to use them as "toys" use user subpages, or create your own wiki for fun and games. If your aim is to improve the Wiktionary, and I sincerely believe it is, you'll have to listen to other editors. I think you have a conflict at this level, the need to improve the Wiktionary and the need to play. Mglovesfun (talk) 10:45, 30 April 2010 (UTC)Reply

I don't recollect saying that I own any Wiktionary template, neither playing games that involve deliberately ignoring people here. In fact, my behaviour seems quite contrary to those concepts, since I'm inclined to help people and discuss with them. Rising Sun did not ask for Walloon cardinal numbers to be supported by {{poscatboiler}}, he just informed about "fucking up" that category, so I didn't ignore him (her?) by fixing the category without that template. I see you removed "numerals" from poscatboiler and added "numbers" to it, hence effectively removing the distinction between a symbol and a word; this fact would probably be brought up in the vote whose result you foresaw, and was pointed out by me in this very conversation. --Daniel. 11:42, 30 April 2010 (UTC)Reply

The fact is there already is a consensus, negating the need for a vote. You didn't answer my question, do you feel a need to create templates to "play" and use them as "toys"? Mglovesfun (talk) 16:18, 1 May 2010 (UTC)Reply

Come on Gloves, lay off him. He's a great help when it comes to templates. The best templatist known to the world of Wiktionary, in fact. --Rising Sun talk? contributions 16:30, 1 May 2010 (UTC)Reply

MG, we had a vote on this, and the result was no consensus. Please do not push one view over the other with a claim that there is consensus, beacuse there isn't. Your accusations and insults do not reflect well on you; it may be time to take a wiki-break, as you do seem to be leading the entire community in number of Talk page edits. --EncycloPetey 16:52, 1 May 2010 (UTC)Reply

Hi Daniel. I wanted to use the postcatboiler template in Category:Hungarian future participles and Category:Hungarian adverbial participles, but it does not recognize them. Can you please add them? Thanks. --Panda10 17:25, 2 May 2010 (UTC)Reply

Done. --Daniel. 06:52, 5 May 2010 (UTC)Reply

Thank you. --Panda10 21:34, 8 May 2010 (UTC)Reply

Enjoy. --Daniel. 17:17, 10 May 2010 (UTC)Reply

Hi Daniel.. For getting the highest score with a single entry in my Easter Competition, you're entitled to a prize. What would you like? It can be anything you want that'll take less than two hours of my time --Rising Sun talk? contributions 07:20, 3 May 2010 (UTC)Reply

OK, thanks for the offer; then yes, I agree to command such a generous Wiktionary editor. Before choosing how I'll take (less than) two hours from your time, please say if you're good at IPA. :) --Daniel. 12:49, 5 May 2010 (UTC)Reply

My IPA knowledge for French and British English is perfect. Anything else could be a bit more complicated. --Rising Sun talk? contributions 11:41, 6 May 2010 (UTC)Reply

Please, can it be adding pronunciation to the entries in Category:Vulgarities? Or something that involves dirty words? --Rising Sun talk? contributions 11:44, 6 May 2010 (UTC)Reply

According to a new rule I'm about to add, the deadline for claiming your prize is tonight --Rising Sun talk? contributions 10:57, 17 May 2010 (UTC)Reply

OK, then. Your idea of editing vulgarities is a good one for my purposes, which include improving my own IPA knowledge. You shall make sure that the following terms have proper IPA pronunciations, in this order, if you have time:

1. The terms fuck, fucked, fucking, fucks, fuck up, fucked up, fucking up, fucks up, fuck ups, shit, shitted, shitting, shits, worry, worried, worrying, worries, speak, spoke, speaking, speaks, dirty word, dirty words, magic word and magic words.
2. And, I don't speak English, do you speak English, I don't speak Portuguese, how old are you, I am twenty years old, I am hungry, I am thirsty, I am tired, leave me alone, what's your name and where can I pee.
3. The "synonyms" listed at WS:promiscuous woman.
4. The "derivations" of the noun, adjective and verb shit.
5. The "members" of the category English swear words.

--Daniel. 22:35, 17 May 2010 (UTC)Reply

Super. I'll work on it --Rising Sun talk? contributions 06:08, 18 May 2010 (UTC)Reply

{{langcatboiler}} has started listing the scripts of languages as if there were four of them in every case ("Latin, , and scripts"). Could you take a look at it? --Yair rand 04:49, 6 May 2010 (UTC)Reply

Fixed. --Daniel. 05:06, 6 May 2010 (UTC)Reply

For {{symbcatboiler|iso|letter}}, the template should really read the script used from the {{langscript}} template. That's what it's there for, after all. -- Prince Kassad 11:15, 6 May 2010 (UTC)Reply

Granted. --Daniel. 11:32, 6 May 2010 (UTC)Reply

Please don't create these. They can't be edited or tailored for individual entries, and contain no useful information about the specific templates on which they appear. Boilerplate documentation doesn't work because the templates are all different. --EncycloPetey 17:57, 6 May 2010 (UTC)Reply

What he said. Mglovesfun (talk) 17:57, 6 May 2010 (UTC)Reply

I suppose you are talking about the generic examples like "word1 word2" and examples with erroneous scripts, as you pointed out at RFC. Then, perhaps these documentations should be subst:'ed with headtempdocboiler and further edited, rather than not created at all. --Daniel. 18:25, 6 May 2010 (UTC)Reply

No, I'm talking about the whole thing. Latin prefixes need additional explanation about usage that I can't add to the boilerplate. Most people mistakenly create prefix entries for prepended prepositions, and a cautionary note needs to be added. There are similar issues on most other templates. And I disagree about creating them with "subst:" All that does is fool people into thinking the template has real documentation, when all it has is mindless substed boilerplate that may not apply to the template at all. They have the same problem on the Russian Wiktionary, but there they have boilerplated whole entries for many languages and so they have lots of pages with no content whatsoever except for the empty boilerplate. --EncycloPetey 18:51, 6 May 2010 (UTC)Reply

Could the hypernym parameter be modified so that items can be partially unlinked? For example, in {{list:chess pieces/es}} I would want to show pieza de ajedrez but not pieza de ajedrez. Nadando 02:36, 11 May 2010 (UTC)Reply

{{wlink}} looks like it would do what I am suggesting. Nadando 02:44, 11 May 2010 (UTC)Reply

Hmm, this differs considerably from the original plan, but I like your suggestion, then implemented it. --Daniel. 02:53, 11 May 2010 (UTC)Reply

Hi. It's not clear to me what {{langscript}} does that {{lang2sc}} isn't meant to. (Of course, langscript has many more languages in it than lang2sc.) Can you clarify, please?​—msh210℠ 19:21, 11 May 2010 (UTC)Reply

AFAIK, the main difference between these two templates is that lang2sc is currently a mess while langscript isn't. Also, I'm not inclined to type some possible values for lang2sc like {{lang2sc|Japanese (alias for Han + Hiragana + Katakana)}} to get a simple "Jpan"; it would be impractical. --Daniel. 19:40, 11 May 2010 (UTC)Reply

I think that those were meant as comments. The #switch will ignore them if it doesn't encounter them, so no harm done. Anyway, can lang2sc simply be converted to a hard-redirect to langscript, then?​—msh210℠ 20:03, 11 May 2010 (UTC)Reply

The hard-redirect seems a good idea. Although, apparently, the only page that uses lang2sc is User:Conrad.Irwin/creation.js/!sc, so I asked Conrad about this subject. --Daniel. 20:32, 11 May 2010 (UTC)Reply

There are two differences - lang2sc is subst'able, and it defaults to Latn, langscript isn't and defaults to Xyzy. The purpose of !sc is to include the script template wherever it is not Latn - so I'm not sure that langscript can do that (though if I'm wrong, that's fine too) . If you want to move lang2sc into my userspace to stop other people using it that's great too. (In short, I don't care as long as nothing breaks :p). Conrad.Irwin 21:11, 11 May 2010 (UTC)Reply

So what do you think about changing !sc from {{#ifeq:{{lang2sc|{{{1|en}}}}}|Latn||{{!}}sc={{lang2sc|{{{1}}}}}}} to {{#ifeq:{{langscript|{{{1|en}}}}}|Latn||{{!}}sc={{langscript|{{{1}}}}}}}? (Both of those are simplified here for legibility. Of course I'm not suggesting getting rid of the substs.) That would add (if I understand it correctly) an explicit call to Xyzy that currently is lacking — but only in the highly unusual case that a language has no script listed in langscript — and would default languages to their primary script (e.g. sh to Cyrl) where lang2sc defaults them to Latn. AFAICT there would be no other change (besides better coverage of languages natch).​—msh210℠ 21:30, 11 May 2010 (UTC)Reply

Sounds alright - making langscript subst'able isn't hard now either. I imagine that Hebrew is one of the languages that is using this, so you'll be in a good position to test how it works :p. Conrad.Irwin 22:02, 11 May 2010 (UTC)Reply

Having this template list just planets and not the myriad other objects in the solar system is ridiculous. Thanks for that. — opiaterein — 12:13, 12 May 2010 (UTC)Reply

This is a problem I have with some of the list templates that have been created. I feel like the template should only be used when there is a definite bounded set of objects in the list. For instance, I'm sure that I could find more terms fitting in {{list:sexual orientations/en}}, and there are thousands of objects in the solar system- what criteria are we using to include only some of them? Compare that to the list of planets, which can be said to be complete. Nadando 12:48, 12 May 2010 (UTC)Reply

Most of the objects in the Solar System are either large and identifiable, like the Planets and Pluto and Eris, or they're part of large sub-systems, like the asteroid belt, Oort cloud and Kuiper belt.

On the sexual orientations lists, the main ones are homo-, hetero-, and bi-. pan-/omni- are the same thing, a- is sorta marginal. I'm not going to include paraphilias, just the basic terms. Like the "basic colors" lists. — opiaterein — 12:55, 12 May 2010 (UTC)Reply

I used the "Criteria for inclusion" from Template:list/doc, that I wrote myself and of course may be discussed and changed if necessary; I think {{list|en|sexual orientations}} is good enough, as long as I think of it as somewhat separate from a possible {{list|en|paraphilias}}.

I consider the deletion of the former Template:solar system an improvement; to begin with, its title was apparently so inclusive that the template would never be fulfilled. Specifically, it contained only "Moon" but not other satellites, neither did it contain all dwarf planets and asteroids. And, it didn't contain me; I'm an inhabitant of the solar system and my full name would probably be shown in a {{list|en|solar system}} or {{list|en|people of the solar system}}.

In addition, the myriad of celestial bodies may all be included, but please keep them subdivided into smaller lists, like {{list|en|planets of the solar system}}, {{list|en|dwarf planets of the solar system}}, {{list|en|satellites of the solar system}}, etc. Note that all these subdivided lists would appear together in the entry solar system, so incompleteness isn't an issue. --Daniel. 15:19, 12 May 2010 (UTC)Reply

Hi,

Could you help me fix this appendix, please? I tried to use the same structure as in Appendix:I don't speak but failed miserably :). --Anatoli 00:21, 13 May 2010 (UTC)Reply

As you can see, I have fixed it now using your new tags, thanks!, please have a look, you can add more languages, if you wish. If someone doesn't do it - next thing I need an interpreter in many languages. --Anatoli 01:58, 13 May 2010 (UTC)Reply

Good; I'm glad you could use the new tags after I made them a little easier and more intuitive. In addition, I placed some suggestions for improvement of Appendix:I am at its talk page. --Daniel. 05:03, 15 May 2010 (UTC)Reply

Thanks, I replied there. It may work for "I am" + nationality/ethnicity but will not work for other suggestions you made. The idea is good, though. I'd like to have I need an interpreter to be easily converted into I need a doctor by replacing the key word interpreter -> doctor. So far, all the translations would need a simple replacement of FL words for interpreter to doctor, except for English, article "an" needs to be changed for "a". --Anatoli 05:19, 15 May 2010 (UTC)Reply

Hey, if you're able can you please make appropriate topic cat subtemplates for this? It's just that I'm not sure really what to say for the topic cat description (since North Germanic seems to be a group of languages not one language). 50 Xylophone Players talk 00:25, 13 May 2010 (UTC)Reply

Also, could you make {{topic cat description/English derivations}} please? :) For the English category I'd like it to say that like, it contains categories for the derivations (as obviously we do not say that English word X is "from English Y") and just have the normal derivations description for other languages. 50 Xylophone Players talk 19:55, 14 May 2010 (UTC)Reply

Oops, *facepalm*...I had made a typo while making a category...Perhaps though you should still consider adding that functionality to the category. 50 Xylophone Players talk 19:59, 14 May 2010 (UTC)Reply

Everything done, or so I think. Since the standard description for Category:X derivations is the so generic "This category comprises words whose etymologies involve X roots.", I believe it can be used language families as well. The "English derivations" switch and the "North Germanic derivations" templates are done; and, I didn't find any category with typos to fix. --Daniel. 08:36, 17 May 2010 (UTC)Reply

Surely you don't advocate using {{list}} for lists with one item? All it will do is link an entry to itself. Mglovesfun (talk) 22:40, 16 May 2010 (UTC)Reply

I suppose you are talking about the list of "moons" of Earth, because this is currently the only list with only one item. I wouldn't advocate any list merely because it contains one item, but I support the existence of {{list|en|moons of Earth}}. That template links to seven entries, including few synonyms of "satellite" and the name of our planet. Furthermore, please see the "See also" section of satellite. It would be seriously deficient if lacking Luna and Dysnomia. --Daniel. 22:53, 16 May 2010 (UTC)Reply

Oh, and of course there is also the current list of moons of Eris. I support its existence too. --Daniel. 23:19, 16 May 2010 (UTC)Reply

I made a mess of the unblock the second time. Conrad.Irwin 23:08, 16 May 2010 (UTC)Reply

No worries. --Daniel. 23:13, 16 May 2010 (UTC)Reply

Sigh. It seems MG has finally snapped, and feels he owns my talk page too. What should the community do? --EncycloPetey 23:14, 16 May 2010 (UTC)Reply

Whatever you did, it broke the section editing in the BP. --EncycloPetey 23:31, 16 May 2010 (UTC)Reply

The problem is that the server is still catching up with the edit. Should be resolved shortly. I almost wonder if he did it on purpose, as I think the project benefited from having that page disabled for a few minutes. If so, very shrewdly done sir. :-) -Atelaes λάλει ἐμοί 23:37, 16 May 2010 (UTC)Reply

Petey, you probably tried to click in a section link soon after I've archived the BP. When I removed some sections to place in the archive, naturally all section links have changed. Specifically, there are now thirty sections in the BP. To edit them normally, try reloading the page first: simply click here. --Daniel. 23:45, 16 May 2010 (UTC)Reply

Yes, I've tried that several times. The month of April still shows up, even though it's now archived. Guess whatever connection I've got isn't as up-to-date as everyone else's. --EncycloPetey 23:49, 16 May 2010 (UTC)Reply

It takes a little while. I tried refreshing, and cache emptying and refreshing, and it still took a few minutes for the new version to get loaded. But, if it's still not loading properly for you, you can always press the edit section link, then manually change the section number in url bar (subtract about 55 or so) and it'll work. -Atelaes λάλει ἐμοί 23:51, 16 May 2010 (UTC)Reply

Kazakhstan is in central Asia. --EncycloPetey 05:02, 17 May 2010 (UTC)Reply

Correct. And also in Europe. --Daniel. 05:40, 17 May 2010 (UTC)Reply

Huh... Wonder why I never knew that before. --EncycloPetey 05:43, 17 May 2010 (UTC)Reply

Effectively because Wiktionary had not taught this to you yet. (: Well, I also never knew the exact relation between Kazakhstan, Asia and Europe before doing some quick research for the lists. --Daniel. 06:00, 17 May 2010 (UTC)Reply

Armenia is not in Europe. Some say it's culturally part of Europe, but I'm not sure what that means. Nor are Georgia and Azeristan in Europe. PS Add Nagorno-Karabakh Republic to the list of countries or I'll kick your ass :D --Vahagn Petrosyan 14:28, 17 May 2010 (UTC)Reply

The maps say that both Armenia and Georgia are located physically in both Europa and Asia. I don't know what Azeristan means. I'm not quite sure about the Nagorno-Karabakh Republic; to quote Wikipedia again, "The country remains unrecognized by any international organization or country, including Armenia."; I added it to the list of countries of Europe anyway. --Daniel. 20:40, 17 May 2010 (UTC)Reply

Do you have a moment to clean this up from the following pages. Thanks. Conrad.Irwin 17:39, 17 May 2010 (UTC)Reply

• fishes out of water 29832430: == {{langtempboiler|code ==
• hunter greens 29832467: == {{langtempboiler|code ==
• midnight blues 29832484: == {{langtempboiler|code ==
• butterscotches 29832564: == {{langtempboiler|code ==
• dilacerates 29832667: == {{langtempboiler|code ==
• dilacerating 29832686: == {{langtempboiler|code ==
• dilacerated 29832705: == {{langtempboiler|code ==
• dilacerations 29832744: == {{langtempboiler|code ==
• dikinases 29832773: == {{langtempboiler|code ==
• mannitols 29832792: == {{langtempboiler|code ==
• ebonites 29833013: == {{langtempboiler|code ==
• buttfaces 29833317: == {{langtempboiler|code ==
• topdresses 29833768: == {{langtempboiler|code ==
• topdressing 29833797: == {{langtempboiler|code ==
• topdressed 29833816: == {{langtempboiler|code ==
• topees 29833835: == {{langtempboiler|code ==
• Andeans 29834232: == {{langtempboiler|code ==
• Oceanians 29834555: == {{langtempboiler|code ==
• metasubstitutions 29834617: == {{langtempboiler|code ==
• comfreys 29834750: == {{langtempboiler|code ==
• metarules 29834966: == {{langtempboiler|code ==
• merogonies 29835213: == {{langtempboiler|code ==
• fire bricks 29835805: == {{langtempboiler|code ==
• deionising 29835901: == {{langtempboiler|code ==
• deionisations 29835975: == {{langtempboiler|code ==
• deionizations 29835994: == {{langtempboiler|code ==

Yair already did it. --Daniel. 07:58, 18 May 2010 (UTC)Reply

I urge you to vote. (I don't know which way you'll vote, but I want more voices, especially English Wiktionarians' voices, heard in this vote.) If you've voted already, or stated that you won't, and I missed it, I apologize.​—msh210℠ 17:00, 21 May 2010 (UTC)Reply

Hi. Could you please put Chinese or Mandarin translation requests under "Chinese:" or "Chinese: ... Mandarin:" in the future? It makes it a little easier. Thanks. ---> Tooironic 13:05, 23 May 2010 (UTC)Reply

I have not noticed those little formatting issues of "Chinese:" translations when I made requests for entries of that language. Yes, I'll remember to put new requests under the proper headers in the future. --Daniel. 14:49, 1 June 2010 (UTC)Reply

FYI, I've posted a response here: Wiktionary talk:Votes/pl-2010-05/Names of specific entities. --Dan Polansky 09:53, 1 June 2010 (UTC)Reply

OK you deserve a shot to reply. I've accused you of acting almost entirely in your own interests rather than in the interests of Wiktionary. I'm not saying everything you do is bad - far from it, {{poscatboiler}} and {{topic cat}} are genius, on the other hand you edit without any discussion {{past of}} of {{present participle of}} and {{third-person singular of}} and break literally tens of thousands of entries. My point is this: if your main aim is to test your own abilities at making templates, why Wiktionary? Couldn't you do that on Wikia or something? Mglovesfun (talk) 09:32, 5 June 2010 (UTC)Reply

I was going to send you a message now asking whether there was a reason for you to revert my edits in these three templates minutes ago. Thanks for the overall praise, but for your information I have not created or actively participated in the existence of the {{topic cat}}. I do apologize for forgetting about a little piece of code which recognizes English as a language that does not need to be specified with a parameter like |lang=en; I think this is the reason for you to edit those templates, although this issue was already fixed when you did that. Aside from my mistake, which was indeed not planned in discussions, the edits done by me on these three templates were already discussed beforehand. I am certainly inclined to continuously improve my own abilities as a programmer, but I don't see how my personal behavior overlaps with your accusation and suggestions. --Daniel. 10:21, 5 June 2010 (UTC)Reply

Funny as that was the bit I wanted a reply to. Why Wiktionary? Why not any othe wiki? Mglovesfun (talk) 10:30, 5 June 2010 (UTC)Reply

I have responded that I don't see how my behavior has something to do with your suggestions to date; that is, you haven't gave me reasons to change my patterns of edits. In fact, the "Why Wiktionary?" is probably the least important sentence in your text, since it apparently relies on the unproven assumption that I do something here that belongs somewhere else. In short, I edit Wiktionary because when I feel like contributing to a dictionary, I choose this one. --Daniel. 11:00, 5 June 2010 (UTC)Reply

Did you break en-noun? See cryptex. Equinox ◑ 23:16, 5 June 2010 (UTC)Reply

en-noun is fine. I've edited a subtemplate to fix cryptex as well. --Daniel. 23:24, 5 June 2010 (UTC)Reply

Hi,

Please add at least one translation along with your translation requests. into your phrasebook entries, e.g. Portuguese. They would qualify as real phrasebook entries then. --Anatoli 02:39, 7 June 2010 (UTC)Reply

Hello. I disagree with this particular criterion of qualification of "real phrasebook entries". Nonetheless, I'll certainly add Portuguese translations to them eventually. --Daniel. 02:56, 7 June 2010 (UTC)Reply

It's not a criterion as CFI (not at the moment), don't get me wrong, just a courtesy - a phrasebook is supposed to be multilingual or at least bilingual. We can end up having too many phrases without translations, if they grow too fast. The value of a phrase increases straight away with a translation. Besides, it must be easy for you, if you're fluent in Portuguese. Thanks for understanding. --Anatoli 03:06, 7 June 2010 (UTC)Reply

I think you really should stop adding uncommon phrasebook entries. google:"I need petrol" has mere 137,000 hits, while google books:"I need petrol" has mere 48 hits. Phrasebook entries should be not only attestable but also common. The only requirement they are exempt from is the one of idiomacity AKA non-sum-of-partness. --Dan Polansky 10:19, 8 June 2010 (UTC)Reply

I suggest that both entries I need petrol and I need gasoline be either kept or deleted; since the latter existed and is restricted by regional labels, it seemed to me only natural that the other existed too, then I created it.

On the subject of commonness, the unfortunate lack of fuel for one's vehicle occurs very often. If Google hits are indeed a reliable criterion for which 48 or 137.000 results are not sufficient for a phrasebook entry to merit inclusion, perhaps different wordings but similar in effect would fill that gap: some possibilites would be "I need gas" (375.000 raw hits), "where is the gas station" (503.000) and "I ran out of gas" (516.000). --Daniel. 10:48, 8 June 2010 (UTC)Reply

I indeed do not deny the use case of needing petrol but rather the particular phrases. I think that both "I need petrol" and "I need gasoline" should be deleted. google books:"I ran out of gas" shows 640 hits, so this would pass the tentative criterion that I have been proposing. google:"where is the gas station" with its 510,000 hits also seems to perform acceptably well, although google books:"where is the gas station" with its 30 hits is rather unconvincing. Checking against real phrasebooks would be better in the early phase of building the phrasebook, in the phase in which the criteria of inclusion are unclear and in the making. google books:"I ran out of gas" intitle:phrasebook gives four hits, already a first indicator that the phrase is not an utter tosh as a phrasebook one.

Google hits are a mere proxy criterion, yet a better one than no criterion of commonness at all. --Dan Polansky 11:09, 8 June 2010 (UTC)Reply

In BrE I'd expect "I'm out of petrol" or "I've run out of petrol". Equinox ◑ 11:38, 8 June 2010 (UTC)Reply

Perhaps usefulness would be other possible criterion; I, personally, and hopefully other English-speaking people would help someone whose only intelligible words are "I need gasoline" in that language, so it's useful. The alternative "where is the gas station?" seems equally useful, except that I remember something about places where gas is sold at markets in gallons.

Notably, Wikitravel (for example, its Japanese phrasebook ) has I need a toothbrush and I need a Japanese-English dictionary among other "I need X" variations.

Equinox, similarly to our current both I need gasoline and I need petrol, both I've run out of gasoline and I've run out of petrol would naturally be kept or deleted together. --Daniel. 11:50, 8 June 2010 (UTC)Reply

Usefulness alone is a poor filtering criterion. Usefulness should be a condition necessary, not sufficient, for inclusion of a phrasebook entry. It is rather subjective, and prone to lead to disputes. It fails to capture the fact that some phrases, although useful in principle, are not the primary way of how an idea is expressed in English.

Wikitravel is a project I know almost nothing about, but, from its being a wiki, it is hard to tell how well it is executed.

By sheer numbers of hits, "I'm out of petrol" performs poorly, while google books:"I've run out of petrol" gives decent 418 hits, and performs really well in google books:"I've run out of petrol" intitle:phrasebook with 54 hits. These 54 hits may be misleading, though, in that many of the various hits are from the same publisher, Lonely Planet, who probably uses the same underlying database of phrases as a basis for phrasebooks in various languages. --Dan Polansky 12:24, 8 June 2010 (UTC)Reply

Usefulness is completely subjective. Some of us would use I have a big penis 17,809 times and use I need a diaper...never.

Wikitravel kinda sucks. They're kinda like a "real phrasebook"'s retarded cousin who wears a football helmet everywhere. — opiaterein — 12:47, 8 June 2010 (UTC)Reply

Elder people and parents of babies (and actors who play babies, and sellers of diapers, etc.) need diapers; so, like I said above about petrol, I think we should have either I need a diaper or something similar with different words.

Both that wiki and Lonely Planet apparently fall under the staple rule of "if lemmings have that particular phrase, we may consider having it too" merely because they are phrasebooks, so they'll probably appear in further discussions.

Wikitravel does seem to have some basic thus useful terms like "hello" and "excuse me", but I have to agree with Opiaterein on its apparent retardness after reading that from the Portuguese phrasebook : "I swear I didn't do it, Mr. Officer.", which sound funnily weird even when translated. --Daniel. 14:32, 8 June 2010 (UTC)Reply

I had this idea to templatize organization of phrasebook stuff. I figured since you've worked so much on the list stuff and the category boilers that it'd be right up your alley. — opiaterein — 16:52, 8 June 2010 (UTC)Reply

I was thinking, for the phrasebook entries in the main namespace a template format like... {{phrasebook/en/<situation>}} would work, with the usage on the page itself like the list templates. — opiaterein — 16:53, 8 June 2010 (UTC)Reply

Have you ever considered changing your username to one without a period at the end? When I write your user name in the middle of a sentence in full, the period appears to end the sentence. I can simply write "Daniel" instead of "Daniel.", admittedly, but that does not match the user name perfectly. --Dan Polansky 09:41, 10 June 2010 (UTC)Reply

Well, apparently I'm the only "Daniel" here as long as the other Daniel keeps unproductive and linking to me. I think you may simply type Daniel, without the period, if you prefer. --Daniel. 10:09, 10 June 2010 (UTC)Reply

He could also say Daniel Dot, that should make sense. — opiaterein — 13:10, 10 June 2010 (UTC)Reply

Please do not turn instances to hyponyms in Wikisaurus. These are different things. --Dan Polansky 12:20, 16 June 2010 (UTC)Reply

Please explain how you differentiate "Instances" from "Hyponyms" and "Meronyms". If possible, provide examples and mention specific mistakes that I have done, since I prefer not to simply follow an instruction to blindly "never rename from that title to that other title."

I noticed that you tend to occasionally "fix" my Wikisaurus edits, then leave a note mentioning how you're returning the page to the "correct" state. Apparently, your comments are the first signal that I've done something wrong, since consensus is unspoken or nonexistent; and rules are unwritten.

I've not found the word "Instances" either in Wiktionary:Wikisaurus or in Wiktionary:Wikisaurus/Format; I've only found it naming sets of hyponyms and meronyms, so it's only natural that I fix them, unless I'm ignoring a distinction. --Daniel. 14:14, 16 June 2010 (UTC)Reply

On a broader note, can you please leave things that I have done in Wikisaurus alone unless you are very sure you know what you are doing? I do not get why you have removed meronyms from "Wikisaurus:computer", to take another instance. There is a lot of things you can do in Wikisaurus without turning things upside down. --Dan Polansky 12:28, 16 June 2010 (UTC)Reply

I noticed that you said that "software' is not a meronym of "computer"; I believe your statement is incorrect. Without software, there is no instruction on how to compute effectively (at least in modern computers which don't require to be rewired). I can fathom that there is a lot of things to be done in Wikisaurus, but most of them are not listed in the 8,788 bytes of Wiktionary:Wikisaurus/Requested entries, which leaves me with either (1) adding new pages or (2) improving old pages as I see fit. I've been doing both.

Since a computer has large sets of hardware and software as meronyms, I've added them to both respective lists: WS:hardware and WS:software. They help to understand the distinction and may have additional hypernyms, hyponyms and meronyms. --Daniel. 14:14, 16 June 2010 (UTC)Reply

It seems you should first get a clear idea of hyponymy and meronymy. You have entered "chess" as hypernym of "chess piece" into Wikisaurus, an obviously wrong thing to do. A computer is equiped with software, right, but it does not consist of software. An apartment does not consist of furniture either, although it is of not much use without it. A taxi does not consist of a taxi driver, although without a taxi driver no taxi can go anywhere. And a car does not consist of gasoline.

By example, "Mars" is an instance of "planet", while "planet" is a hyponym of "celestial body"; each planet is a celestial body, while "each Mars" is meaningless unless you read Mars as a common noun. "Each chess" is meaningless, while "chess is a game" is meaningful. If you want to see a set-theoretic characterization of the distinction, see User:Dan Polansky/Wikisaurus#Semantic_relations.

Before you start renaming the heading "Instances", intentionally entered by the only long-term contributor to Wikisaurus, I would think it proper to first ask the contributor what the intention was. Anyway. --Dan Polansky 15:09, 16 June 2010 (UTC)Reply

Would it be possible to have it so we don't have to make an addition to list every time we add a new topic? Check out Appendix:English phrasebook/Love — opiaterein — 12:46, 16 June 2010 (UTC)Reply

I've added love to the list. Your request of not having to make additions to it can be easily fulfilled, but why? Apparently, the PB will not have more than ten sections. When these sections are created, either (1) we are happy with them and definitely would not want additions such as Appendix:English phrasebook/How to ask for woman-on-top sexual positions; or (2) we do want such new sections, but they would be subsections, which would require specific and reasonably complex codes in the list. --Daniel. 14:24, 16 June 2010 (UTC)Reply

I'm not sure 10 would be quite enough... but since I'm having trouble thinking of more... heh. — opiaterein — 14:38, 16 June 2010 (UTC)Reply

Was it one of your recent edits that caused ] to have its plural not a link? If so, can you fix it? Thanks.​—msh210℠ 17:30, 17 June 2010 (UTC)Reply

Yes. When I reverted my edits, the link was restored, thus I discovered that the lack of it was my fault. Thanks for pointing me to that bug. I'll have to analyze the template later to restore the other functions that I have added to it while keeping "Reader's Digest version" intact. --Daniel. 17:44, 17 June 2010 (UTC)Reply

Hi, what do you think about the possibility of adding an button (or similar) to topic cat, and maybe also to poscatboiler when/if you get around to converting poscatboiler/theList like you mentioned in the GP a while ago? --Yair rand (talk) 07:45, 12 July 2010 (UTC)Reply

Yes, I think a button like you described is a good idea, which I'll remember to make appear in categories handled by poscatboiler and topic cat.

As an initial plan, perhaps simply (one word, in superscript text) fits poscatboiler better, because I intend to make one template per POS. For instance, one template for nouns that handles Category:English nouns, Category:Portuguese nouns, Category:Japanese nouns, etc.

On the other hand, the right buttons for topic cat would be , because there are two templates per subject. In my opinion, both links are necessary, but the final text is too undesirably long, so it may require further pondering. --Daniel. 07:38, 19 August 2010 (UTC)Reply

The description for Category:Cities says "At this time the category includes cities, towns and villages of all sizes. It is anticipated that it will be divided at some later time". So I figure maybe it's time. I think you could probably make a boiler template that would be used in categories like Category:Cities in Brazil, Category:Cities in Sudan and stuff like that. Come back soon, man. Sometimes I want to punch you, but I know you do a lot :D — opiaterein — 20:49, 12 July 2010 (UTC)Reply

Agreed; that category is indeed asking for some clean up.

Do you have any ideas for the standardized definition line? Perhaps, for instance, the entry Osasco would contain the following, at least:

1. A city in Brazil.

Or, more detailedly:

1. A city in Greater São Paulo, Brazil and whose boundaries are Barueri, Carapicuíba, Cotia, Santana de Parnaíba and São Paulo city.

--Daniel. 08:04, 19 August 2010 (UTC)Reply

I usually just say "A (large/small city/town/whatever) in the X region of the Y country". In Bengali cities, I've also been including categories of the specific areas. — opiaterein — 23:57, 19 August 2010 (UTC)Reply

Well, my second definition line fits your description by providing the "(large/small city/town/whatever)" part and listing some regions. I've created Osasco as a testcase. It notably displays overcategorization, which may or may not be a good thing, given that some standardized categories should exist and I ignored wider distinctions such as "Greater São Paulo, São Paulo, Southeastern Brazil, Brazil, South America, Earth"

And I don't know if approximately one month is "soon" enough, but I'm happy to come back here. Thanks for the praise and go punch something else when you need to. --Daniel. 06:58, 20 August 2010 (UTC)Reply

I actually had templates for categories like {{topic cat}} and {{poscatboiler}} in mind, but actually {{place}} is really excellent, too :D I would take out the Category:Greater São Paulo, Category:São Paulo, and Category:Brazil, but the Cities in and Municipalities in parts are good. How would we do something like Chalan Beel? It'd be slightly odd at first thought to have a template that categorizes "Marshlands in Rajshahi District". It might be easier to have one template for cities and towns, and another for geographic features or something? But I can also see how one might be curious to find mountains or rivers in specific areas... I dunno, I'm rambling at this point :D — opiaterein — 13:32, 20 August 2010 (UTC)Reply

If {{place}} can create refined and standardardized definition lines and category links, the work of the future catboiler will likely be much easier.

Chalan Beel is a little tricky. I had to make a new parameter for it.

As for the categories Marshlands in Pakistan, Mountains in Russia, Rivers in Egypt, etc., I think they should exist. Leaving city names categorized but hundreds of river names uncategorized seems a bad idea. (Alternatively, rivers, mountains, marshlands could be categorized by country but not by smaller regions.)

My answer to your "one template for cities and towns, and another for geographic features or something?" would be no, because these two hypothetical templates have very similar functions, therefore they would probably resemble each other and be a little easier for users to remember if such functions existed in only one template. (And, technically, it is not difficult to alter details, such as categorization, for individual types of places: {{place}} already knows that the plural of town is towns and the plural of city is cities.)

I've removed from {{place}} the categories whose name don't contain "in" as you asked. --Daniel. 17:20, 20 August 2010 (UTC)Reply

Hi,

Please add a Portuguese translation to your entry. --Anatoli 04:48, 23 July 2010 (UTC)Reply

Done. --Daniel. 08:06, 19 August 2010 (UTC)Reply

--Yair rand (talk) 07:04, 19 August 2010 (UTC)Reply

Thanks. --Daniel. 08:06, 19 August 2010 (UTC)Reply

In the entry linierna, I use {{obsolete spelling of|linjerna|lang=sv}} and the result is a link to linjerna#English instead of the expected linjerna#Swedish. I guess this is related to how the lang parameter is passed from {{deftempboiler}} to {{makelink}}. Should makelink use parameter 1 rather than lang, or should deftempboiler pass the language value as lang= in addition to parameter 1? --LA2 14:22, 19 August 2010 (UTC)Reply

Your code {{obsolete spelling of|linjerna|lang=sv}} indeed was pointing to the English section of linjerna; it is pointing to the intuitively correct Swedish section now.

Specifically, I have fixed the link, not by editing the entry, but by making the correct value be passed from one template to another: Template:makelink is now using the parameter 1 to recognize the parameter lang from Template:obsolete spelling of. --Daniel. 23:09, 19 August 2010 (UTC)Reply

Hi Daniel,

On discussion pages, something like this:

{{abbreviation of|foo}}

now generates this:

Abbreviation of (example).

. This is because you changed {{abbreviation of}} to use {{deftempboiler}}, and changed {{deftempboiler}} to use {{makelink}}, and designed {{makelink}} not to work on discussion pages.

Needless to say, it is not the only template affected.

Please fix it.

Thanks,
—Ruakh_TALK 20:02, 23 August 2010 (UTC)Reply

Also, in future, could you please start discussions before changing very widely used templates in very drastic ways? For example, the {{deftempboiler}} stuff broke various templates' support for things like lang=French. —Ruakh_TALK 22:35, 23 August 2010 (UTC)Reply

Hi, Ruakh. I've changed {{makelink}} to display the results without the automatic "(example)" in discussion pages as you asked. The "lang" parameter whose value is any language name like lang=French is also functional now; specifically, I had to edit Template:wlink2 to accomplish this. The community seems to feel it is increasingly necessary to have the chance to discuss my major edits — especially since I engaged in handling template functions which are complex, thus prone to errors. This phenomenon is in conflict with my previous reasoning related to {{deftempboiler}}: that this template would not change anything per se, because it is only supposed to standardize various similar templates, namely by them having the same code and the same functions (e.g., if I remember correctly, {{obsolete spelling of}} hadn't any sc parameter until recently, which is a shame). With that in mind, I've already decided to become more inclined to directly report my actions. As a result, I have been directing my attention to GP, documentation and other pages more often, as you certainly saw and occasionally replied. --Daniel. 02:07, 24 August 2010 (UTC)Reply

Thanks, on all counts! —Ruakh_TALK 02:24, 24 August 2010 (UTC)Reply

This template doesn't work properly anymore. See, as an example, nuclear reaction. The two words of the headword are no longer wikified. SemperBlotto 08:04, 15 September 2010 (UTC)Reply

• See also reproductivity for strange apostrophes. SemperBlotto 08:10, 15 September 2010 (UTC)Reply

  How interesting. Thank you for pointing me to nuclear reaction and reproductivity. The template seems to be working properly now. --Daniel. 08:19, 15 September 2010 (UTC)Reply

This needs to be able to accept language names instead of language codes. This has lead to thousands of entries being uncategorized. NB I'm not saying it's your fault, just that you are best placed to fix it. I haven't even looked at its history. Mglovesfun (talk) 16:30, 16 September 2010 (UTC)Reply

I think this preference for language codes over names is a result of this recent GP discussion. Apparently other users would prefer to fix (by bot) these thousands of uncategorized entries instead of changing back the related templates. --Daniel. 16:38, 16 September 2010 (UTC)Reply

With regret. You have to be a bit more responsible and take on board others' comments. If you're not interest in improving Wiktionary, please do not edit it. Mglovesfun (talk) 16:58, 16 September 2010 (UTC)Reply

The template {{rfc-header||lang=ru}} + lang=ru is supposed to drop the pagename into Category:Russian words needing attention, but now it is not happening. You have changed something in some template that should not have been changed. —Stephen (Talk) 01:45, 17 September 2010 (UTC)Reply

That was Bequw moving the category . --Yair rand (talk) 01:53, 17 September 2010 (UTC)Reply

Changing "words" to "terms" in {{attention}} broke {{rfc-header}}? I can’t comprehend the logic behind it. Be that as it may, can we change it back so that {{rfc-header}} works again? —Stephen (Talk) 03:00, 17 September 2010 (UTC)Reply

Sorry, I thought you were assuming that it wasn't working because the words weren't showing up in Category:Russian words needing attention. As far as I can see, the template is correctly categorizing the entries into Category:Russian terms needing attention. Can you point out an entry in which it isn't working? --Yair rand (talk) 03:16, 17 September 2010 (UTC)Reply

I’ve never seen Category:Russian terms needing attention before. I’ve been checking Category:Russian words needing attention all day and could not understand why it was suddenly empty. —Stephen (Talk) 03:51, 17 September 2010 (UTC)Reply

All the attention categories now use "terms" instead of "words". Sorry that caught you off-guard. Let me know if there any problems with the new categories. --Bequw → τ 04:43, 17 September 2010 (UTC)Reply

Your contract of etyl:prv broke all the links. You have to check them before you shorten them. For example, Ruakh's example edit worked because w:North Germanic redirects to w:North Germanic languages. This was not the case at Provencal as the shortened version is a disambiguation page. Spot checking your other edits shows similar problems. Can you check and fix your previous edits?

More generally, I must ask you check your edits. While I don't believe this reoccurring issue is worthy of de-sysopping, it is harmful both in terms of wiktionary as a website and in terms of other editors time. --Bequw → τ 02:29, 24 September 2010 (UTC)Reply

Sorry for the trouble. I've re-checked the templates and edited them where necessary, by using the older system with #switch. --Daniel. 03:11, 24 September 2010 (UTC)Reply

Thanks. Good use of the wiki redirects! --Bequw → τ 18:53, 24 September 2010 (UTC)Reply

These look like Dawnraybot errors, before it got a lifetime block. Care to delete them (if that is the case, of course). Mglovesfun (talk) 23:07, 26 September 2010 (UTC)Reply

Special:WhatLinksHere/gesticulatar is empty. Anyway, there is no Portuguese verb "gesticulatar"; that would probably be "gesticular". --Daniel. 16:30, 27 September 2010 (UTC)Reply

This template takes a pos= parameter- could you edit it so that other POS categories also show up if they exist? For example, Category:English words derived from: load (noun) would also show Category:English words derived from: load (verb) (similar to how {{poscatboiler}} works). Nadando 19:31, 2 October 2010 (UTC)Reply

Sure. Done, for adverbs, nouns and verbs. --Daniel. 03:47, 3 October 2010 (UTC)Reply

One appendix per one markup keyword that you are creating seems a really poor idea. More in my answer in Beer parlour, "colspan, etc.". --Dan Polansky 14:24, 7 October 2010 (UTC)Reply

This can probably be cited outside Star Trek. Shouldn't this go through RFV before being moved to the appendix namespace? --Yair rand (talk) 04:03, 10 October 2010 (UTC)Reply

If it can be cited without context of Star Trek, then it can indeed be defined at beam up. In this case, the additional page Appendix:Star Trek/beam up probably should still exist, because (1) the term was firstly used in this context and (2) perhaps there are additional information unique to the series, such as possibly "To teleport by using a transporter." --Daniel. 04:11, 10 October 2010 (UTC)Reply

Klingon is from a fictional universe, but since it has an ISO 639-3 code, I'd suggest that this is in wide enough use to be considered cited outside of the fictional universe. Therefore I'll move it back, but the appendix entry would also be valid, just not really necessary. Mglovesfun (talk) 11:41, 10 October 2010 (UTC)Reply

I didn't know that there are ISO 639-3 codes for fictional races... I was genuinely believing it was only for languages. --Daniel. 11:46, 10 October 2010 (UTC)Reply

Hmm, klingono is also the language right? Double hmm. Mglovesfun (talk) 11:48, 10 October 2010 (UTC)Reply

klingono, or Appendix:Star Trek/klingono, is defined as a race. (and the language would be klingona lingvo; w:eo:Klingona lingvo). --Daniel. 11:54, 10 October 2010 (UTC)Reply

klingono might be attestable for the language as well, see anglo for example. Mglovesfun (talk) 11:56, 10 October 2010 (UTC)Reply

Then see how Klingon and Appendix:Star Trek/Klingon are neatly organized. I don't think that attesting one word is enough to bring all the fictional homonymous words together in the entry namespace, namely the language and the race. --Daniel. 12:02, 10 October 2010 (UTC)Reply

I'm going to revert your reversion, effectively transforming klingono into an appendix-only entry again. If you want to create an attestable definition of klingono as a language, in the main namespace, go ahead. If you want to define klingono, in the main namespace, but describing it as a race only existing in context of Star Trek, please don't. Thank you. (: --Daniel. 16:18, 10 October 2010 (UTC)Reply

I think this should be renamed Category:The Simpsons derivations. --Felonia 12:42, 10 October 2010 (UTC)Reply

And I agree. --Daniel. 12:44, 10 October 2010 (UTC)Reply

And I think you should do (and probably want to do) all the work necessary to have this renamed. --Felonia 12:50, 10 October 2010 (UTC)Reply

Sure. I hereby accept this duty. --Daniel. 12:53, 10 October 2010 (UTC)Reply

Another thing, can you give me a translation of Azorean, please? --Felonia 08:48, 11 October 2010 (UTC)Reply

Yes, I can. Done. (from English to Portuguese) --Daniel. 09:51, 11 October 2010 (UTC)Reply

I request that you stop creating one-page-per-term appendices for terms from fictional universes until you demonstrate that this is widely supported by Wiktionary editors. --Dan Polansky 08:11, 14 October 2010 (UTC)Reply

Sorry, but I don't intend to cease this particular work. These are some relevant pages:

Wiktionary:Votes/pl-2008-01/Appendices for fictional terms for the vote that specifically allows fictional terms.

Wiktionary:Entry layout explained for the policy on how to format entries. --Daniel. 12:37, 14 October 2010 (UTC)Reply

You ought to stop. The vote does not explicitly enable that there should be one-term-per-page appendices. ELE does not regulate appendixes but main namespace, as you have guessed. You know that what you are doing has raised disagreement, and that other people interpret the vote quite differently. So there is no consensus for this one-term-per-page practice. Either demonstrate consensus (neither ELE nor the vote demonstrate the consensus), or stop.--Dan Polansky 13:41, 14 October 2010 (UTC)Reply

I have already participated in discussions, most notably WT:BP#English appendix-only nouns where my reasons have been stated. What other format do you suggest for appendix-only entries? Or don't you support their existence at all, preferring that, for example, "image inducer" be never defined on Wiktionary? --Daniel. 13:47, 14 October 2010 (UTC)Reply

It does not matter that you have stated reasons that you have find convincing. What does matter is that people disagree with what you are doing. Understood? Your reasons matter when you are deciding alone, but this is a wiki, a colloborative project in which you are not acting and deciding alone. If your reasons do not convince other people, then they do not matter. The page Appendix:Glossary of Farscape terms is an example how an appendix of terms from fictional universe should look like. --Dan Polansky 13:55, 14 October 2010 (UTC)Reply

I do not see a place for etymologies, pronunciations and translations at Appendix:Glossary of Farscape terms. Should them be shoehorned into the list? --Daniel. 13:59, 14 October 2010 (UTC)Reply

(unindent) There should be no etymologies, pronunciations and translations of terms originating in fictional universes. Or else those terms might equally well be placed in the main namespace. --Dan Polansky 14:03, 14 October 2010 (UTC)Reply

Why should we neglect the connection between アーボック and Arbok? --Daniel. 14:07, 14 October 2010 (UTC)Reply

(<-) Because we do not want to document Pokémon in the first place. If we wanted to, we would have included Pokémon in the main namespace. After you convince other editors that Pokémon should be documented in as much detail as mainspace entries, with pronunciations, translations, etymologies, whatnot, then you can start creating such appendixes. --Dan Polansky 14:11, 14 October 2010 (UTC)Reply

I believe you should gather consensus yourself on how to limit the coverage of fictional words. --Daniel. 14:18, 14 October 2010 (UTC)Reply

(<-) I see. You, one who has introduced in stealth mode a new practice, do not feel obliged to do the political work for what you propose, even after your proposal has raised fierce opposition in Beer parlour. You seem to think that clear opposition in Beer parlour is not enough. I do not share this view of wiki collaboration. At some point, I will possibly need to start a vote on forbidding what you are doing. The vote may end up in no consensus, say 60% against your proposal. Then you will continue with 40% support. Well I think that what you are doing is wrong, and that it is you who should start a vote and lose the vote unless you garner consensus, if you plan to continue your practice. --Dan Polansky 14:23, 14 October 2010 (UTC)Reply

I have created and participated in relevant discussions, including this one. Except for you and other editor, there's virtually no "clear opposition in Beer parlour" regarding the concept of formatting fictional words as other entries. You apparently are trying to push your opinion on how to format them, while sliding the burden of proof onto my shoulders. It's not really difficult to create a new BP discussion if you think there's something wrong and unspoken, or participate in the current discussions, like you are doing now. So, be my guest and share your disagreements, if you would, and feel free to participate in discussions and votes as you see fit, which I think is the better way to garner and acknowledge consensus. --Daniel. 14:41, 14 October 2010 (UTC)Reply