It would be great to have either two radio-buttons "uppercase initial" (default) and "lowercase initial" or checkbox "change initial to lowercase" on Special:Import page to make transwiki import yet easier.
(There's usually need of page move to lowercase initial name on wikt: after import and this feature could remove that additional step.)
Thanks.
Version: unspecified
Severity: enhancement
Well, aren't you needing to move it out of transwiki namespace anyway? I'm not sure I see this as saving any steps...
(In reply to comment #1)
Well, aren't you needing to move it out of transwiki namespace anyway? I'm not
sure I see this as saving any steps...
I don't have any idea what you mean by "transwiki namespace". :-/
Here's the procedure I've done:
2 and 3 can be omitted if option described in comment #0 was existing.
robchur wrote:
This could have similar problems to bug 6808, in that there's the assumption of a single page being imported.
(In reply to comment #3)
This could have similar problems to bug 6808, in that there's the assumption of
a single page being imported.
So far I know, I can transwiki only one page at moment, not more. This feature is intended exactly only for transwiki, not for XML import.
robchur wrote:
(In reply to comment #4)
So far I know, I can transwiki only one page at moment, not more. This feature
is intended exactly only for transwiki, not for XML import.
And as with bug 6806, we anticipate that this might change in the future.
That would be *very* useful: e.g. on it.wiktionary importers have to move hundreds of imported pages and then ask for deletion of the redirects (since they don't have suppressredirect right), hence triple work is needed.
From a user perspective, sensible thing may be to use the locally-normalized title form that was typed in locally for the local name.
That is, if you're on a case-sensitive wiki and you put in for import:
"foo"
it'll send off to en.wikipedia.org and say "give me 'foo'", which returns the page "Foo"... and we then go "ok well we typed in "foo", so we name it that way.
The tricky thing of course is that this doesn't fit nicely into the current code model. :) Would basically need some kind of name map in theory. :P
Relatively easy to do for a single-name current special case though.