Jump to content

Extension Upload Wizard

Extension Upload Wizard

Edited by another user.
Last edit: 21:30, 25 June 2010

Hi, the following three messages do not seem to be ok:

  1. Mwe-upwiz-error-too-long
  2. Mwe-upwiz-error-too-short
  3. Mwe-upwiz-error-bad-chars

They relate to fields as being to short, to long, etc. Shouldn't it be entries being to short, to long, etc. ?

Cheers --kgh 18:47, 25 June 2010 (UTC)

kgh18:47, 25 June 2010

I don't understand the comment.

  • "too" is the correct word in English to imply an excess of something, not "to".
  • It talks about fields because the interface uses standard form fields. The data from these are later used to create wikitext entries.
NeilK20:53, 25 June 2010

Hi NeilK, usually an editor is not able to change the length of a field in a form, but the length of the entry put into a field. In contrast this message is asking to do the opposite: If the entry is too (thanks!) long for the field, please change the length of the field. To me this sounds very strange and this is why I posted my question. Cheers --kgh 22:31, 25 June 2010 (UTC)

kgh22:31, 25 June 2010

I apologize for not following up with you. I was not aware that you had sent additional messages. Maybe I don't have the right settings to get email from this.

The error message is trying to say that "the value you have typed contains too many characters", or "the value you have typed contains too few characters".

In English, we usually say "long" or "short" and the meaning is understood. There seems to be some confusion here between length as in centimeters or inches, and length in the sense of number of characters. Is that what was bothering you?

Should I rename these messages to something like "over-maximum-chars" / "under-minimum-chars" ?

NeilK17:55, 9 August 2010

No problem. I should have left a message on your talk page earlier.

However, your answer confirmed to me that I have localised correctly. Shouldn't the messages say "This entry is too long/short" instead of "This field is too long/short" or "This entry contains symbols that are not allowed." instead of "This field contains symbols that are not allowed." My question never related to short or long. I am sorry that I may have phrased my question incorrectly.

Cheers

kgh18:08, 9 August 2010
Edited by another user.
Last edit: 22:58, 9 August 2010

How about this?

       'mwe-upwiz-error-blank' => 'This field is required.',
       'mwe-upwiz-error-too-long' => 'Please make this shorter than $1 {{PLURAL:$1|character|characters}}.',
       'mwe-upwiz-error-too-short' => 'Please make this longer than $1 {{PLURAL:$1|character|characters}}.',
       'mwe-upwiz-error-bad-chars' => 'This entry contains symbols that are not allowed. Please do not use wikitext or HTML here.',
NeilK22:05, 9 August 2010

Yeah, cool. Perhaps

      'mwe-upwiz-error-too-long' => 'Please make this entry shorter than $1 characters.',
      'mwe-upwiz-error-too-short' => 'Please make this entry longer than $1 characters.',

Cheers and thank you for your help

kgh22:19, 9 August 2010

Incomplete. "characters" needs PLURAL support.

Siebrand22:27, 9 August 2010

Definitely. Plural support is already availabe in the current version and it is unlikely that NeilK will downgrade this. Cheers

kgh22:31, 9 August 2010
 

That's what I posted, but the system ate the PLURAL tag.

NeilK22:51, 9 August 2010

Nowiki the bitch :)

Siebrand22:58, 9 August 2010
 
 

Nothing seems to have happened here since "clarification". At least the internationalisation into German is up to date. I am sorry for wasting your time. Next time I would appreciate that somebody says that I should back off if there is no intention to work on this anyway. Thank you.

kgh12:09, 22 September 2010

For a while I was developing without committing to the central repository, because I'm refactoring a lot of things. As a newcomer to the MW community I was not sure how to proceed when I knew that things were going to be broken for a long time; the strongest community value seems to be "only commit things that are working".

Anyway I just gave up and went to a branch (uploadwizard). Sorry if this seemed to you like I was not addressing your concerns.

NeilK15:03, 23 September 2010

Hi NeilK, the easiest way is always to provide a brief information. In most cases it is totally acceptable if there are reasons. If there is no information at all, it is not possible to evaluate a situation. This leads to a misunderstanding like in our case. I am sorry in case I was a bit too brisk. Cheers

kgh21:15, 23 September 2010