This is an old revision of this page, as edited by Johnuniq (talk | contribs) at 00:41, 16 January 2014 (→Spell: good). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 00:41, 16 January 2014 by Johnuniq (talk | contribs) (→Spell: good)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
I'll reply to messages here, unless requested otherwise. |
Index of stuff
Module:Convert
- User:Johnuniq/Using the convert module – proposal to use Module:Convert
- Module talk:Convert – to discuss what needs to be done
- Template:Convert/sandboxlua – template to invoke Module:Convert
- Template:Convert/sandboxlua2 – same, with
warnings = on
- Template:Convert/sandbox – template to invoke the sandboxed convert modules
- Module:Convert – main convert module; same on all wikis
- Module:Convert/doc – overview of modules
- Module:Convert/data – unit definitions, for en.wiki
- Module:Convert/text – text messages and parameter names and values, for en.wiki
- Module:Convert/extra – extra (temporary) unit definitions
- Module:ConvertNumeric – spell an input value in words (only English is supported)
- Module:ConvertTestcase – implements following testcases
- Template:Convert/testcases – tests comparing output from Template:Convert with output from Template:Convert/sandboxlua
- Template:Convert/sandboxlua/parameter options – more tests
- Module:Convert/tester – module to perform tests with fixed expected results
- Module:Convert/sandbox/testcases – tests for the sandboxed convert modules
- Module talk:Convert/sandbox/testcases – results of running tests
- Module:Convert/documentation/conversion data/doc – master list of unit definitions
- Module:Convert/documentation/conversion data introduction/doc – explanations transcluded into above
- Module:Convert/makeunits – script to translate master list of units to Lua code
- Help:Convert – user documentation on template usage (being written)
- Help:Convert units – user documentation with simplified list of some units
- Help:Convert messages – user documentation with help on error messages
- User:Johnuniq/Convert documentation – now mostly at Help:Convert, but has a little more
- User:Johnuniq/Convert messages – examples of messages that can be displayed
- User:Johnuniq/Convert notes – problems encountered using old template
- My talk page at test2 with old notes
Archives (not related to convert)
- Comments re free speech
- Jagged: misuse of sources progress, more, genre articles
- Links to highbeam.com from dumps of external links ∙ earlier ∙ more Credo
- Gregorian serial date template
- Analysis of EL dump using Amazon S3 very interesting methods from GabrielF
- Module:Number at Hindi Misplaced Pages request from Siddhartha Ghai
Misplaced Pages Library, Metrics Coordinator
Hey John. You've been invaluable to demonstrating the imapct of our library donations. I want to ask you if you'd like to take on this role more fully, running metrics reports for all of our partnerships every 3 months. The key ones we have not done yet are Questia and JSTOR and Cochrane. Having data on these would help us greatly in making the case for extension and expansion of these parternships. Would you be interested in having the Metrics Coordinator position and doing this regularly? You've been great at it so far and it's really invaluable. Perhaps we should set up a time to chat and see what would work best for you. Hope you're well, Jake Ocaasi 15:05, 11 December 2013 (UTC)
- There will be a more clever way of doing what I have been doing. I have been wanting to investigate WP:Labs for a while, and something run there on a regular basis makes more sense than searching downloaded external links dumps. A problem for me is that a major project (Module:Convert) that I have worked on for a year has just gone live, and I won't feel like looking at anything else for a few weeks. But yes, I'm happy to do more link searching. Johnuniq (talk) 19:32, 11 December 2013 (UTC)
- Awesome! Yeah, there must be a way to automate this.
- I was wondering...if we could run the JSTOR numbers using the old method, from 1/2011 to 11/2013 searching for http://www.jstor.org*** or https://www.jstor.org/stable*** (I'm not sure which is more appropriate). This could be really useful in persuading JSTOR to extend the partnership and expand out of pilot phase to more accounts. Any chance we could have that by New Year's? Pretty please? ;)
- Oh yeah, you're informally now appointed the Metrics Coordinator, so congratulations!! We can talk more later about how to make that easy and rewarding on your end, but I want you involved, most definitely. Cheers, and thank you for your work, Ocaasi 14:33, 18 December 2013 (UTC)
- OK, I'll look at the JSTOR issue soonish. Poke me if I forget because there's a few things going on. Johnuniq (talk) 20:28, 18 December 2013 (UTC)
- Oh yeah, you're informally now appointed the Metrics Coordinator, so congratulations!! We can talk more later about how to make that easy and rewarding on your end, but I want you involved, most definitely. Cheers, and thank you for your work, Ocaasi 14:33, 18 December 2013 (UTC)
@Ocaasi: The JSTOR results are below. You wanted 1/2011 to 12/2013, but my earliest dump of external links is 6/2011 and my "history" method for estimating counts at earlier dates is unattractive because far too many pages (20,000 articles) would need analysis.
I started by looking at all the JSTOR links in articles in December 2013, and saw no reason to exclude some of them, so I ended up searching for all links of form "jstor.org/something" (not case sensitive, but virtually all occurrences are lowercase).
The following shows all external links of form "jstor.org/something" (not case sensitive) in articles, found by examining dumps like enwiki-20131202-externallinks.sql.gz downloadable from here. Links in pages other than articles are not included.
Date | Unique articles | Unique links | Total links |
---|---|---|---|
2011-06-20 | 19,953 | 27,727 | 33,001 |
2011-07-22 | 20,263 | 28,121 | 33,486 |
2011-09-01 | 20,696 | 28,825 | 34,359 |
2012-02-11 | 22,808 | 29,886 | 36,294 |
2012-03-07 | 23,471 | 30,600 | 37,115 |
2012-04-03 | 23,733 | 30,963 | 37,588 |
2012-05-02 | 24,318 | 31,619 | 38,400 |
2012-06-01 | 24,668 | 32,598 | 60,531 |
2012-07-02 | 25,698 | 33,290 | 40,313 |
2012-08-02 | 26,089 | 33,783 | 40,897 |
2012-09-02 | 26,412 | 34,164 | 41,431 |
2012-10-01 | 26,756 | 34,614 | 41,981 |
2012-11-01 | 27,070 | 35,103 | 42,578 |
2012-12-01 | 27,607 | 35,803 | 43,402 |
2013-01-02 | 28,055 | 36,460 | 44,187 |
2013-02-04 | 28,496 | 37,111 | 45,016 |
2013-03-04 | 82,983 | 91,903 | 100,024 |
2013-04-03 | 83,679 | 92,826 | 100,984 |
2013-05-03 | 84,666 | 94,049 | 102,352 |
2013-06-04 | 84,881 | 94,304 | 102,644 |
2013-07-08 | 86,430 | 96,285 | 104,920 |
2013-08-05 | 87,253 | 97,268 | 106,059 |
2013-09-04 | 88,258 | 98,458 | 107,415 |
2013-10-01 | 89,031 | 101,316 | 121,514 |
2013-11-04 | 90,125 | 101,643 | 137,188 |
2013-12-02 | 90,843 | 102,537 | 138,574 |
The number of pages and links dramatically rose during February 2013—the number of articles tripled, and the number of links more than doubled. I investigated to see if that was some bug in my scripts, but it appears to be correct. It looks as if a tremendous amount of wikignoming went on in that month, but the most significant factor is that the number of "doBasicSearch" links rose from 1300 to 55,300, and most of them appeared to have been placed in articles which had not previously had a JSTOR link. So, in February 2013, 54,000 JSTOR "doBasicSearch" links were added to articles! Looking at a couple of examples shows that doBasicSearch is coming from {{notability}} which generates "Find sources" with a JSTOR search. Confusingly, "Find sources" is not visible on some articles (example), apparently due to {{notability}} being embedded in {{multiple issues}}—however, the JSTOR link is present in the html source of the article, and it is counted as an external link. An example of an article where the JSTOR search is visible is here. All that suggests that I should run my scripts again, but adjust the search to eliminate doBasicSearch links. On the other hand, the fact that a search to JSTOR is visible at the top of thousands of articles could well be seen as a bonus for JSTOR, so for the moment I'll just report what I have found, despite the fact that a significant number of the links are not visible. While comparing the February and March 2013 results it was clear that hundreds of standard reference links were added, as well as the 54,000 doBasicSearch.
- Fantastic Johnuniq. I'm adding this to the JSTOR/metrics page and will let Steven (WMF) know about how much we have expanded out links to JSTOR. Hopefully that will be persuasive for increasing/expanding/continuing the pilot donation program. Thank you! Ocaasi 17:23, 27 December 2013 (UTC)
As a matter of interest, I noticed that the oldest article that currently contains JSTOR links is Anarchism, which was created in 2001.
I guess you are aware, but in case you missed it, I did some Credo results earlier this month, see here. I'm afraid I still have not got around to fixing the graphing software that I use, so I don't have a graph for the above. Please find someone at WP:VPT to plot it because the numbers look like they show a steady increase. Johnuniq (talk) 07:02, 27 December 2013 (UTC)
One week alive and no sleep lost for anyone: here it is
1 mi = 1.6093440 km | ] | |
p = {} global function expressBarnStar ( star, reasons, sign ) -- todo: function to handle the data; ask Juniq return ']' .. reasons .. /n .. sign end return p |
||
One week live already and wonderfully stable, consistent and very few faults appearing. A pleasure to work with. -DePiep 12:00, 18 December 2013 (UTC) |
- Thanks, that's stunning, and very much appreciated! Johnuniq (talk) 20:26, 18 December 2013 (UTC)
You might enjoy this
You might enjoy this. Maybe you could come up with a "kind description". Barleybannocks (talk) 08:58, 24 December 2013 (UTC)
- Thanks, but it will be a while before I get a moment to try that. Perhaps some seasonal goodwill (backed by some solid topic bans!) will bring an outbreak of peace soon. Johnuniq (talk) 11:00, 24 December 2013 (UTC)
- Perhaps, but if you keep banning everyone who knows what they're talking about, the chances seem rather slim. Better just to write a reasonably neutral article and be done with it. Even if that does mean telling some of the frightened children to grow up.Barleybannocks (talk) 11:07, 24 December 2013 (UTC)
Convert and use in val template
I've been trying to use convert module in the {{val}} template with the following code:
{{Val/unitsfromconvert|1|m|disp=unit}}
which works fine for when the unit is a recognised one but when the unit is not recognised, it is displaying a warning.
{{Val/unitsfromconvert|1|abcd|disp=unit}} - Template:Val/unitsfromconvert
I had thought that setting warnings=0 in Val/unitsfromconvert would have suppressed the message and just output the unit but it doesn't seem to. -- WOSlinker (talk) 10:21, 24 December 2013 (UTC)
- A warning can only be disabled if the problem does not prevent valid output. Because an unknown unit has no valid output, it's an error that cannot be disabled. What do you need? With some new option, disp=unit would display the unit if valid, or the input unit code if it is not known? Are other options involved like lk=on? Is anything else needed like also showing a value while suppressing an error message? If you have suggested syntax, let me know, or I'll think about it. Johnuniq (talk) 10:57, 24 December 2013 (UTC)
Here is a test of a very q&d modification I just made to Module:Convert/sandbox:
{{convert/sandbox|1|abcd|test=noerror}}
→ 1 abcd{{convert/sandbox|2|abcd|test=noerror|disp=unit}}
→ abcd{{convert/sandbox|2|abcd|test=noerror|lk=on|disp=unit}}
→ abcd
The option "test" is an exception that does not require translation in convert/text, so I used it. If a better name is devised ("error=ignore"?) that can be used, but it would have to be defined properly in convert/text. Using test=noerror means an unknown input unit is assigned a dummy unit of type length, with scale 1. Is this useful? Johnuniq (talk) 11:39, 24 December 2013 (UTC)
- Yes, that would work. -- WOSlinker (talk) 11:43, 24 December 2013 (UTC)
- Good, but are you ready to say exactly what should be done? Are any other tricks needed for {val}? I used input value 2 above to show that the dummy unit suppresses adding an "s" to make a plural name. I guess that is wanted, and/or you don't care because {val} will always use 1? The trick will only ignore an unknown-unit error when looking up the input, but other errors like specifying a nonexistent output unit would cause an error. I guess that's ok? Does any option spring to mind, or will I make something up? Johnuniq (talk) 11:51, 24 December 2013 (UTC)
- I'll look at it in a bit more detail & get back to you after christmas. -- WOSlinker (talk) 11:56, 24 December 2013 (UTC)
- Good, but are you ready to say exactly what should be done? Are any other tricks needed for {val}? I used input value 2 above to show that the dummy unit suppresses adding an "s" to make a plural name. I guess that is wanted, and/or you don't care because {val} will always use 1? The trick will only ignore an unknown-unit error when looking up the input, but other errors like specifying a nonexistent output unit would cause an error. I guess that's ok? Does any option spring to mind, or will I make something up? Johnuniq (talk) 11:51, 24 December 2013 (UTC)
test
should not be used in mainspace. Stay clean. -DePiep (talk) 13:37, 24 December 2013 (UTC)
@WOSlinker: What do you think of the following, which I have put in the module sandbox? If you can think of a better option name, let me know. Is anything else needed?
- Forget
|test=noerror
(I have removed that). - Use
|disp=unit or text
to display the input unit if known, or the input text. - Examples:
In {{val/units}}, I think you would replace the first of the following lines with the second.
|#default={{#ifexist:Template:Convert/{{{1}}}|{{convert/{{{1}}}|d=ScientificValue/LoffAonSoff}}|{{{1|}}}}} |#default={{convert/sandbox|1|{{{1}}}|disp=unit or text|abbr=on}}
For {{val/unitswithlink}}, do the same but add |lk=on
, although you would probably wait until the code is moved to the main convert module.
I replaced Template:Val/units/test with the text necessary to use Module:Convert/tester because it actually tests the results, and it is easy to add new tests. Johnuniq (talk) 10:57, 3 January 2014 (UTC)
- disp=unit or text looks good to me. Thanks. -- WOSlinker (talk) 22:18, 3 January 2014 (UTC)
- agree, 'disp=unit or text' will work. for now, I have simply expanded the list of units in the switch statements to cover all the actively used units, so it's not actively using any of the convert subtemplates. once we have 'disp=unit or text', we can trim the switch statement back to only the ones that are needed. Frietjes (talk) 00:44, 7 January 2014 (UTC)
I wonder what's in the box?
Season's greetings from Santa and her little helpers
Verily trembling, little J welcomes Bigzilla, and hopes to escape with perhaps only a pocketing. Many thanks for the greetings, and don't worry about leaving sulfur fumes ... they will dissipate, eventually. Johnuniq (talk) 20:12, 26 December 2013 (UTC)
Greetings
Hello, Johnuniq! How did the switch of the Convert template go? Smoothly enough to stick around, I see :) I must keep an eye on {{val}} and its subs to see what you guys come up with there. Once that's done, I'm probably going to delete the network of convert templates on simplewiki. Osiris (talk) 19:49, 2 January 2014 (UTC)
- HNY Osiris! I don't really understand why, but the transition to using the module seems to have passed largely unnoticed, other than by a handful of the regulars who monitor Template talk:Convert. I had anticipated that a few things would break, but the slow job queue meant that only a small number of pages were reformatted each day, and people seem to have fixed the few glitches that arose by following the error tracking categories. I can't seem to stop fiddling with the module, and there are some large changes in the sandbox which will go live in a week or two. I'm hoping WOSlinker will resume work on {val} in due course so that can be sorted out. I suggest looking back in about a month when you might consider updating the modules at Simple. Removing the old templates would involve some work, but I guess it would makes things cleaner. Let me know how you go. Johnuniq (talk) 23:08, 2 January 2014 (UTC)
- That's great! You all deserve a sincere congratulations for the hard work you've put in to make it work so well! It was no doubt a massive undertaking. No problem about the updates, I'll keep an eye on them and check back with you when they become stable (to check whether there will be anything to look out for). Happy New Year to you also :) and thank you so much for all you've done! Osiris (talk) 19:54, 3 January 2014 (UTC)
Pony!
Pony!
Congratulations! For all your hard work on the hands conversion issue, you have received a pony! Ponies are cute, intelligent, cuddly, friendly (most of the time, though with notable exceptions), promote good will, encourage patience, and enjoy carrots. Treat your pony with respect and he will be your faithful friend! Montanabw 21:50, 3 January 2014 (UTC)
To send a pony or a treat to other wonderful and responsible editors, click here.
- Hey that's great, thanks! I enjoy carrots as well—I hope we can reach an accommodation on sharing them. Johnuniq (talk) 00:35, 4 January 2014 (UTC)
- You and your pony will have to work that one out between you! LOL! Montanabw 19:32, 4 January 2014 (UTC)
Advice from an IP
This message is being sent to inform you that there is currently a discussion at Misplaced Pages:Administrators' noticeboard regarding an issue with which you may have been involved. Thank you. — Preceding unsigned comment added by 124.170.221.69 (talk) 03:23, 4 January 2014 (UTC)
- Thanks for the notice, but I think reading the previous comments might be more profitable. Johnuniq (talk) 03:59, 4 January 2014 (UTC)
Thank-you
Hi Johnuniq. Just a quick, but sincere, thanks for your edits in archiving threads and changing headings which were including my name in unfounded and extremely uncivil postings. I won't mention the pages as I would rather not draw any further attention to them, but my thanks.__DrChrissy (talk) 15:28, 5 January 2014 (UTC)
- Yes, that nonsense was way over the top. It will probably need more in a day or so when the IP comes off the range block, but at least it is clear that the matter will be readily handled now. Glad to help! Johnuniq (talk) 21:32, 5 January 2014 (UTC)
List of units
Hi, I was going to update the various "Convert/list of units" documentation subpages to use the convert module, and I nearly got everything working. the only issue is that the tables have the conversion factor as one of the entries, which is not as easy to extract. there are a few options here, (1) forget about the conversion factor column and just replace it with a sample conversion (2) rewrite the row generator in lua, and import the list of units, or (3) have a disp option added to the convert module which returns the conversion factor. what do you think? Frietjes (talk) 00:41, 7 January 2014 (UTC)
- I created a sample of option (1) here -> User:Frietjes/example (compare with Template:Convert/list of units/length/short list). Frietjes (talk) 00:51, 7 January 2014 (UTC)
- Wow, that's difficult. I'm hopeless at making up my mind about things like this because I see benefits and problems. Thanks for taking this on!
- My preference would be an automated system of some kind, and I would be happy to write some code to extract the required data in the wanted format—perhaps the output would be wikitext calling User:Frietjes/unitrow. The benefit is that we would know that the displayed table matches the data, and we would not need to spend a lot of time formatting the tables. The problem is that any automated system loses flexibility (or requires heaps of code to provide the flexibility), and I'm sure the table has many exceptional areas where you wouldn't want to just follow a fixed pattern.
- I guess you've seen my initial attempt at Help:Convert units#Units (click "edit" on that section to see that it is entirely automated). That displays core information for simple input units (it currently cannot show tricky things like ftin which outputs feet and inches). We can very easily add units to that—I just put a few to get started—search for "common_units" in Module:Convert/show.
- I think we should show the "recommended" unit code first, and only show the aliases when there is good reason to do so. I know the full list of units is intimidating, but if someone wants to see all the details, that's where they should go. For example, tell people to use "um" for micrometres so they don't think they need to fiddle with the micro symbol.
- Re extracting the scale: That would be difficult for convert to do, and in general cannot be done in a helpful way because Module:Convert/data only has the result of any expression entered as the scale in the unit definition. For example, a bu has scale "1/330" in the definitions, but all that convert knows is that the scale is 0.0030303030303030303. For
lightyearparsec, the scale is 3.0856775814671916e16 which would need tricky formatting, with no guarantee that the digits would be exactly as expected due to floating point precision limitations. However, the scale could be extracted from the unit definitions, using some variation on Module:Convert/makeunits. - What about the SI units? The old templates had to define each SI term, whereas the module allows all combinations. We need to choose which of those to show, and have a note explaining that all are possible.
- I'll be elsewhere for a while, but will return and think some more. Johnuniq (talk) 01:46, 7 January 2014 (UTC)
- After some thought, I don't think we can do any better than what you have done. While the scale could be extracted from the unit definitions, it's not terribly meaningful, and has some tricky cases (for example, Mm is not a defined unit—its scale is calculated using the mega prefix). Also, it's quite nice to show the sample conversion because that includes the default output unit.
- While rewriting the row generator as a module would have benefits, it would be quite difficult in practice because Module:Convert/data omits redundant fields in a complex manner—missing fields are constructed on demand if needed for a particular convert. Also, the link and default output can have exceptions—µm has a different link and default from the m base unit—and the rules for handling all that are buried in convert. I think calling convert is best.
- What do you think about the "full list" tables? They would be difficult to create and maintain, and I'm wondering if we should skip them, and instead link to the relevant section in the master list. We would then have the really simple list of units shown at Help:Convert units, and the more detailed overview in the lists you are preparing, and the master list.
- If you think there may be something I can help with, please get in touch. Johnuniq (talk) 09:34, 7 January 2014 (UTC)
- I updated all of the list of units pages as suggested. I agree that we can probably ditch the 'complete lists' and instead just link to an automatically generated complete list, otherwise these will be perpetually out of sync. for now, though, I did update everything to call convert directly. Frietjes (talk) 21:30, 14 January 2014 (UTC)
Spell
looking through the module code, it looks like there are some vestiges of support for 'spell=out' and 'spell=Out'. if we could add 'spell=on' and 'spell=On', I think we can completely replace 'convert/spell'. I created a wrapper in 'convert/spell/sandbox' which would work if we had 'spell=on' and 'spell=On', assuming that's the best choice for the parameter. thank you again. Frietjes (talk) 21:30, 14 January 2014 (UTC)
- I have put that in the sandbox. When pondering spelling months ago, I checked all usage of convert/spell in articles and found that spelling for the output is never used. Because there are some ugly corner cases, and because of the rounding issue, I decided to just implement enough to make disp=flip work. The rounding problem is that it is very unlikely that spelling the output from a conversion would be helpful—there are some cases like 8 km → 5 miles where the value would be reasonable, but usually it would be something silly like "five point one two miles". Anyway, now that frac=N works, spelling the output is more plausible ("five and a half miles").
- There may be some glitches with strange combinations. One known issue is that I did not bother implementing spelling of output values for the hand unit.
- Here are some artificial examples:
{{convert/sandbox|17+3/4|in|ftin|frac=4|spell=In}}
→ Seventeen and three-quarters inches (1 ft 5+3⁄4 in){{convert/sandbox|17+3/4|in|ftin|frac=4|spell=On|abbr=off}}
→ Seventeen and three-quarters inches (one foot five and three-quarters inches){{convert/sandbox|17+3/4|in|ftin|frac=4|spell=In|disp=flip}}
→ One foot five and three-quarters inches (17+3⁄4 in){{convert/sandbox|17+3/4|in|ftin|frac=4|spell=On|disp=flip}}
→ One foot five and three-quarters inches (seventeen and three-quarters inches){{convert/sandbox|53|in|ydftin|spell=On|disp=flip|abbr=off}}
→ One yard one foot five inches (fifty-three inches){{convert/sandbox|2|ft|3+1/2|in|cm mm|spell=On|-1}}
→ Two feet three and a half inches (seventy centimetres; seven hundred millimetres){{convert/sandbox|2|ft|3+1/2|in|cm mm|spell=On|disp=flip|-1}}
→ Seventy centimetres; seven hundred millimetres (two feet three and a half inches)
- The spelling of fractions is probably not always fully correct (perhaps it should be "three-quarter inches" above?), but I'm not going to worry about that. Johnuniq (talk) 11:18, 15 January 2014 (UTC)
- awesome, looks close enough for me. let me know when this is implemented, and we can update 'convert/spell'. thank you again. Frietjes (talk) 16:22, 15 January 2014 (UTC)
- @Frietjes: Hmmm. On actually thinking about this, we don't need to replace convert/spell because there are not all that many of them in use in articles, and one day I intend updating the wikitext in them to use convert with spell=in/In.
- already updated, and only found one use of words=out in the articles, so having spell=on and spell=On is not a high priority. I plan to update 'convert/spell' anyway to allow for old revisions to display properly, but we can certainly deprecate the frontend now. Frietjes (talk) 21:52, 15 January 2014 (UTC)
- Good point, I had forgotten about old revisions. Thanks. Johnuniq (talk) 00:41, 16 January 2014 (UTC)
- already updated, and only found one use of words=out in the articles, so having spell=on and spell=On is not a high priority. I plan to update 'convert/spell' anyway to allow for old revisions to display properly, but we can certainly deprecate the frontend now. Frietjes (talk) 21:52, 15 January 2014 (UTC)
- @Frietjes: Hmmm. On actually thinking about this, we don't need to replace convert/spell because there are not all that many of them in use in articles, and one day I intend updating the wikitext in them to use convert with spell=in/In.
- awesome, looks close enough for me. let me know when this is implemented, and we can update 'convert/spell'. thank you again. Frietjes (talk) 16:22, 15 January 2014 (UTC)