Help talk:Convert

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Wikipedia Help Project (Rated NA-class, Mid-importance)
WikiProject icon This page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.
 NA  This page does not require a rating on the project's quality scale.
 Mid  This page has been rated as Mid-importance on the project's importance scale.


Why do this page and Help:Convert units refer to "convert/sandboxlua"? -- John of Reading (talk) 06:29, 2 October 2013 (UTC)

I have been working on a complex module to replace the series of complex existing templates that currently implement {{convert}}. Testing is performed using {{convert/sandboxlua}} to invoke the module. When the module is deployed, the "/sandboxlua" will be removed from these doc pages. The proposal is here. Johnuniq (talk) 08:05, 2 October 2013 (UTC)

Lua Convert in Slovenian Wikipedia[edit]

The problem is that that our input and output parameters contain decimal comma system. Example : 2300,12 or 2.300,12: 1234567,89 or 1.234.567,89. I've just stared to work in our sandbox sl:Template:Convert/peskovnik. Is there an easy solution? --Pinky sl (talk) 06:26, 15 January 2014 (UTC)

Please see my response at Module talk:Convert#Lua Convert in Slovenian Wikipedia. Johnuniq (talk) 10:53, 15 January 2014 (UTC)

Range indicators added[edit]

I've added range indicators (separators) ndash and plus-minus:

They are accepted by {convert} for the obvious, but I have not check that this is to be documented (=guaranteed). Check me. -DePiep (talk) 11:48, 11 March 2014 (UTC)
Fine, but there are lots of things that convert can do which are not necessarily a good idea. As you know I am a long way behind getting the docs to a good state, and I have no particular problem with the above addition. But the rule I was following was to document what was "desirable", rather than what is possible. I think editors should be encouraged to be reasonably uniform in how converts are entered, and should use C rather than °C for Celsius, and just a hyphen rather than an en dash for the range. There probably is a need to document what works for people such as yourself who are trying to use convert via infoboxes and so need to know more details—I'm not sure how best to handle that as well as provide guidance for the general editor. The ultimate documentation for ranges is at range_types and range_aliases in Module:Convert/text. Johnuniq (talk) 02:03, 12 March 2014 (UTC)
Documentation first serves as a legal statement: what is documented is promised. If promised in a doc, it should be maintained etc. The alternative is undocumented feature, i.e. no promises are made about (future) workings and so. Since I did not know whether these two were guaranteed this way, I wrote this post. If the options were undocumented for some reason, this is an invitation to delete my edits. No problem.
As you describe it, it is about preferred and demoted usage. How to convey preferred usage is less simple. I don't know if omitting things this way would help. OTOH I wanted to have a (more) complete list of options available. And I'd say the en dash as a range indicator is MOS, and also entering a the desired outcome as input (both – and ±) unsymbolised/uncodes should be mentioned to keep the searching editor sane. -DePiep (talk) 06:49, 12 March 2014 (UTC)