Template talk:Docinfo

Relation to Template:Docu
Some pieces of information, such as the language of a page, are already set in the Template:Docu. It would be better to have only one place for each piece of information. Maybe it would be good to move the additional features of Docinfo into Docu (since docu already is widely used and since docu is necessary to create the language/version navigation box. --Markus Krötzsch 16:27, 2 August 2011 (CEST)


 * Yeah, this would be good to have it all in one template. So far I am the only one using Docinfo, but I has proven to be a very useful tool to keep track of updated pages and thus helps a lot with translations. However, I think I am not smart enough to do it or in other words: It might take me weeks whilst somebody else will only need an hour or so to figure out what to change. Cheers --&#91;&#91;kgh&#93;&#93; 16:42, 2 August 2011 (CEST)


 * I will be bold and merge them. No worries, I hope. Cheers --&#91;&#91;kgh&#93;&#93; 00:46, 10 August 2011 (CEST)


 * I just merged the templates. Considering the complexity from docinfo in comparison with docu I merged the other way around. Since the two templates are there the transition may take place step after step as time passes and I progress with translations. Cheers --&#91;&#91;kgh&#93;&#93; 00:50, 12 August 2011 (CEST)

Values of progress
It would like to suggest to add recommended values into the documentation of docinfo to allow a consistent usage, e. g. 80 %, 60 %, etc for completeness. --&#91;&#91;kgh&#93;&#93; 21:13, 9 April 2011 (CEST)


 * I changed the datatype of Property:Docinfo progress from String to Number with allowed values 0, 25, 50, 75, 95 and 100. Users may specify arbitrary number but it will be quantized with these values appropriately.  The default value is 95, means almost done or assumed that it is completed, since the null value is not allowed in SMW annotations and it also make a problem in their sorting.  Currently suffixed % is not available, since the installed version of Extension:ParserFunctions on semantic-mediawiki.org is old and does not contains string parser functions.  Once it will be upgraded (and $wgPFEnableStringFunctions will be specified as true), I'll add this feature soon.  How do you think about this implementation?  Once this quantization is accepted, I'll prepare their category and change progress property again to point to them. --K. Kawaguchi 03:29, 9 April 2011 (CEST)


 * Actually a null value would be an empty or non-existent page. Thus it is not a problem at all not to have it. Your suggestion for the other values is good since it conforms with the status of progress an Wikimedia wikis and translatewiki. :) --&#91;&#91;kgh&#93;&#93; 21:17, 9 April 2011 (CEST)

Values of priority
It would like to suggest to add recommended values into the documentation of docinfo to allow a consistent usage, e. g. top, normal and low for priority. --&#91;&#91;kgh&#93;&#93; 21:14, 9 April 2011 (CEST)


 * I splitted your suggestion into two tickets. I changed the datatype of Property:Docinfo priority from String to Number with allowed values 1 to 4, which means top, high, normal and low for each.  Users may specify this value not only with one of these priority level numbers but also one of priority names, such as top (and urgent as an alternative,) high, normal and low.  Local priority names are also available in German, French, Spanish, Dutch, Russien and Japanese at the moment.  Would you please check these names again in Docinfo code if you can?  As same as progress property, I'll prepare their category and make a change in the property to point them too, after this implementation will be accepted.  Your comment is appreciated. --K. Kawaguchi 04:06, 9 April 2011 (CEST)


 * I agree. Cool. --&#91;&#91;kgh&#93;&#93; 21:19, 9 April 2011 (CEST) PS I just saw that you made available five priority levels. I think only four, urgent=top, high, normal and low are needed to make the choice easier. I personally would not like to choose between top and urgent because both words basically convey the same. Thus a merge of 0 and 1 seems to be acceptable. What do you think? Cheers --&#91;&#91;kgh&#93;&#93; 21:25, 9 April 2011 (CEST)

desc parameter
I think that the language of description parameter (desc) should be local depending on a lang parameter. Is my intuition correct? --Yury Katkov 08:49, 7 October 2011 (CEST)

Please remove the space following the version range for the language zh-hans
zh-hans = 本文档页面适用于SMW从版到 的所有版本. | _________________________________________________________________________________^
 * Current version:

zh-hans = 本文档页面适用于SMW从版到的所有版本. | Sorry about that unnecessary space. Please revise it. Many Thanks. --Linforest 05:39, 16 February 2012 (CET)
 * Expected version:
 * No problem. Did this change fix the issue? Cheers --&#91;&#91;kgh&#93;&#93; 12:53, 16 February 2012 (CET)
 * I checked it. It should work. Thanks. Regards  --Linforest 13:00, 16 February 2012 (CET)
 * Yes, it did the trick. Thanks:) --Linforest 13:14, 16 February 2012 (CET)
 * Good to here! You are welcome. Cheers --&#91;&#91;kgh&#93;&#93; 13:25, 16 February 2012 (CET)