Bot request

Fragment of a discussion from User talk:CodeCat
Jump to: navigation, search

The long list means: select for each line with character "x" the page "x" and insert there "{{commonsrad|#}}", the number # from the same line. There are pages 丿, and all with number 4.
The short list means: select for each line with character "x" the page "Index:Chinese radical/x" and insert there "{{commonsrad|#}}", again # from the line with the character. Only page Index:Chinese radical/丿 exists for number 4, the other two and 乁are redirects to 丿.
This will be the procedure when you work from the list. Since no parent category exists of the affected pages yet (the template could easily do the categorizing for such a category e.g. "Han character radicals" or so), I do not know another possibility. May be you prefer to do both in one run from the "long list", either with the bot remembering when one number is done not to try the index page for further occurencies, or you check for existence anyway; then you will not need the "short list".

13:05, 16 April 2012

I've done the short list now. One of the pages could not be updated, because it was a redirect: Index:Chinese radical/廿.

For the long list, do you think it would be better if the template is placed inside the ==Translingual== section? I think it would be.

14:04, 16 April 2012

from my view, I do not think it better. There is lot of place to the right above the Transligual section - no matter whether the "contents" are hidden or shown; but it is often rather stressy below, there are pictures an longt text parts. And the uppermost right corner is the place where the other links from&to Commons for radicals are placed. So I prefer to place it above, before any other text as {{also}}, that means without any checking.

Index:Chinese radical/廿 was my fault, there was an error in the index list which is now corrected to 廾. Thank you!

15:55, 16 April 2012

That may be true but I have tabbed languages enabled, and it looks a bit strange then: File:Radical one tabbed.png

16:36, 16 April 2012

May give a problem. I'll try to find a solution.

17:03, 16 April 2012

How about now? Too dirty trick???

17:23, 16 April 2012

Uh... yeah, kinda...

18:29, 16 April 2012

I think things should be placed inside the translingual section, just because we don't usually place things outside of some language section.

18:32, 16 April 2012

OK, I tried. ‎一 after the translingual L2, and at the sections end. Both doesn't look any good, no matter TOC is hidden or not, and Language Tab is on or off. It gets only worse! I keep my opinion that above is best. See yourself; and decide how to handle these problems.

19:54, 16 April 2012

Can we make it 'float right' to the same extent as the stroke order templates? That is, can we make its right side line up with the right side of the stroke order template? That would improve its appearance.

20:00, 16 April 2012

Not any problem, I just undo the shift to the left. within an instant

20:02, 16 April 2012

The "see also" is above the language section and anything else. I would treat the link alike.

19:59, 16 April 2012

Last night I saw that MewCat was a bit furious and partially out of control, editing approx. 20 articles a 2nd time devastively. I undid three of the 2nd edits and can continue healing all quickly, but I am not sure whether you agree to my action. So I am waiting for your OK to continue. Sorry that this all consumes more of your time than expected.

06:03, 17 April 2012

- Another recognition happened to me: your mew-task inserting the template string is a fine thing, and I think it is a benefit for wikipedia/wiktionary/commons. This about the "short list".
For the questioned "long list"-insertions I see now a better possibility: the affected articles are those where {{Han char}} has the parameter value 00 for "as" (additional strokes). If I can persuade the guards of that protected (21 461 transclusions) template to accept a small expansion it will be no need for an insertion of an extra template, as mine.
So I draw back my bot request.
Thank you for your useful work. For sure a long discussion will go on now, whether the communinity allows the expansion of {{Han char}}.

12:48, 17 April 2012