Difference between revisions of "Help talk:Article naming guidelines"

From ArchWiki
Jump to: navigation, search
(recent edits about i18n title convention)
(article type suffix recommendation has been removed)
Line 1: Line 1:
==Article type suffix==
 
 
Should "Article type suffix..." really be recommended?  Working with the Gentoo Wiki I remember almost everybody began naming their articles "HOWTO Dnsmasq" or "Compiz HOWTO".  Because this is an instructional-wiki could we consider this implied?  Also since there are table of content tags available this seems to be repetative.  Possibly this would be better to call it Naming Suggestions for pages that aren't howtos?  For example, "AUR Guidelines" and "Virtual Machine FAQ".  --[[User:Gen2ly|Gen2ly]] 08:36, 19 June 2009 (EDT)
 
 
:Just about every article is a HOWTO. Why is the distinction between tutorial and HOWTO helpful? This is just as redundant as the HOWTO category, which I remember being criticized for the same reasons. The HOWTO suffix is completely unnecessary, annoying to read, and duplicates what categories are supposed to do.
 
:HOWTO, [[User:Lavandero|Lavandero]] 21:53, 16 November 2010 (EST)
 
 
::I concur; I am not a supporter of article type suffixes. Perhaps the other parts of this page could be merged with [[Writing Short Article Names]] and the result renamed to [[Writing Article Names]] or [[Naming Articles]]. -- [[User:Pointone|pointone]] 14:58, 17 November 2010 (EST)
 
 
----
 
 
I don't like and not recommend suffix, actually only a little articles in ArchWiki follow this principle. is it needed? already have a HOWTO category. many article only have a single name like [[Xorg]] [[Compiz]] etc and it's enough for a title. [[User:GD|GD]] 21:58, 19 June 2009 (EDT)
 
 
 
== Translated article title conventions: matching by arbitrary number ==
 
== Translated article title conventions: matching by arbitrary number ==
  
 
A [https://wiki.archlinux.org/index.php?title=Article_Naming_Guidelines&diff=131422&oldid=113184 unique ID] would offer the benefit of being able to match articles in different, possibly unknown languages without infringing on translated articles' usability. The current scheme requires the title to be in English, which is clearly awkward for ''translation'' efforts. [[User:Lavandero|Lavandero]] 20:06, 18 February 2011 (EST)
 
A [https://wiki.archlinux.org/index.php?title=Article_Naming_Guidelines&diff=131422&oldid=113184 unique ID] would offer the benefit of being able to match articles in different, possibly unknown languages without infringing on translated articles' usability. The current scheme requires the title to be in English, which is clearly awkward for ''translation'' efforts. [[User:Lavandero|Lavandero]] 20:06, 18 February 2011 (EST)

Revision as of 16:49, 24 February 2011

Translated article title conventions: matching by arbitrary number

A unique ID would offer the benefit of being able to match articles in different, possibly unknown languages without infringing on translated articles' usability. The current scheme requires the title to be in English, which is clearly awkward for translation efforts. Lavandero 20:06, 18 February 2011 (EST)