Translating talk:MediaWiki

From translatewiki.net
Jump to navigation Jump to search

Contents

Thread titleRepliesLast modified
Lqt-older and Lqt-newer312:35, 11 January 2011
MediaWiki:Lqt hist comment edited117:01, 13 July 2012
Mwe-upwiz-desc514:58, 9 January 2011
Password-login-forbidden320:17, 6 January 2011
Extension:Sudo212:55, 3 January 2011
Revreview-reject-summary-old-short207:27, 21 August 2015
Revertpage-nouser215:32, 20 December 2010
Pdfbook-log217:03, 13 July 2012
Extension:Installer217:11, 13 July 2012
Uploadwizard-desc212:39, 14 November 2010
Extension:Installer / chg for kons311:11, 14 November 2010
ResourceLoader109:22, 14 November 2010
Extension:ArticleComments / chg322:44, 7 November 2010
Extension:Donation Interface - Payflow Pro Gateway / messages missing for translation423:02, 7 November 2010
There are some threads which still need some attention.122:32, 7 November 2010
Extension:Maps / chg - consistency213:25, 26 October 2010
Extension:ArticleComments / messages missing for translation422:09, 16 October 2010
Extension:Donation Interface - Payflow Pro Gateway / chg017:14, 13 July 2012
Extension:Installer / chg216:52, 10 October 2010
Extension:Installer / chg216:51, 10 October 2010
First page
First page
Last page
Last page

Lqt-older and Lqt-newer

Have looked and looked and can't find where these two messages appear - Lqt-older ("older") and Lqt-newer ("newer"). Can anyone tell me whether these messages refer to 1 older (or newer) something or more than 1 older (or newer) something? And what is the something referred to - is it an edit?

Lloffiwr16:49, 9 January 2011

Seem to be unused.

Nike17:11, 9 January 2011

Should we remove the messages, or consult the devs?

Siebrand10:46, 11 January 2011

Done Done I removed the messages in mwr:79996.

Siebrand12:35, 11 January 2011
 
 
 

MediaWiki:Lqt hist comment edited

Lqt hist comment edited ("Comment text [$2 edited]") Example: http://translatewiki.net/w/i.php?title=Support&lqt_method=talkpage_history Broken links in history page after thread was edited.

Тест19:19, 9 January 2011

Mwe-upwiz-desc

What is the context of Mwe-upwiz-desc ("Description")? What follows it?

Lloffiwr01:55, 10 November 2010

Apparently this is followed by a language name (or language selector)

Verdy p01:25, 21 November 2010

Oh dear. I guess there might be some languages which are going to struggle to fit a translation of this message with the language selector. Anyway, have documented.

Lloffiwr10:16, 21 November 2010

Best report this issue in bugzilla:.

Siebrand23:35, 2 December 2010

Bug report done on bugzilla:26231

Lloffiwr14:29, 4 December 2010

Thanks Lloffiwr, I have commented on bugzilla.

Dhaval (ધવલ)14:58, 9 January 2011
 
 
 
 
 

Password-login-forbidden

In Password-login-forbidden ("The use of this username and password has been forbidden.") 'these' should be 'this'.

Lloffiwr14:08, 27 December 2010

Can a native speaker please comment here? I am not sure what is the correct grammatical form.

Siebrand13:38, 29 December 2010

I have consulted with a friend of mine who is an English teacher and she confirms that it should be 'this' because username and password are both in the singular. The message is however a little ambiguous - should this really be 'or' instead of 'and'? If it is 'or' then it would be better style to write 'the use of this username or this password has been forbidden'.

Lloffiwr21:37, 1 January 2011
 

Done Done mwr:79751. Thanks for double checking.

Siebrand20:17, 6 January 2011
 

Extension:Sudo

Hi, I just tested this extension and realised that Sudo-unsudo ("Welcome $1, you are currently logged into the wiki as $2. Click on "⧼sudo-unsudo-submit⧽" to return to your own account.") should be rephrased because it is outdated.

Welcome $1, you are currently logged into the wiki as $2, just submit the form to return to your normal login.

Welcome $1, you are currently logged into the wiki as user $2. Click on "Return" to return to your own login.

I have already changed the translations for de and de-formal so these do not have to be fuzzied.

Thank you and cheers

kgh00:56, 8 December 2010

This has already been done, hasn't it?

Siebrand13:39, 29 December 2010

Cool, many thanks to the person solving this issue. Cheers

kgh12:55, 3 January 2011
 
 

Revreview-reject-summary-old-short

As non-native English speaker I am a bit unsure about Revreview-reject-summary-old-short ("Rejected the first $1 text changes that followed revision $2 by $3"). The message reads in Plural: Rejected the first $1 changes that followed revision $2 by $3. Is the word "first" correct? Shouldn't it be Rejected $1 changes that followed revision $2 by $3.?

Raymond09:20, 26 December 2010

It sounds weird, but it is correct English. "The first three changes" means "the first, second and third changes". If this doesn't work in other languages then perhaps the translation can use the word 'next' or 'following' instead of 'first'.

Lloffiwr12:51, 26 December 2010

Thanks for clarifying. I have updated the German translation already.

Raymond16:41, 26 December 2010
 
 

Revertpage-nouser

Is the message Revertpage-nouser ("Reverted edits by a hidden user to last revision by $1") a log entry? If so, should the first letter of the message be small, because the message follows the name of the person who did the action?

Lloffiwr17:27, 18 December 2010

No, it's a confirmation message a user sees after reverting.

Max Semenik18:19, 19 December 2010

Done Done - documented. Thanks for info.

Lloffiwr15:32, 20 December 2010
 
 

Pdfbook-log

In Pdfbook-log ("$1 exported as a PDF book") what is the variable $1?

Lloffiwr20:32, 18 November 2010

After reading the code $1 is the username of the user who exports as PDF.

Raymond16:31, 22 November 2010

Hurrah! I can move the variable $1 away from the front end of this log entry. Have documented.

However, it seems that some translators have been guessing that $1 is the book title. Perhaps it's worth marking all existing translations !!FUZZY!! for review?

Also, I have assumed that nothing follows at the end of this message. Is there more information added at the end of the log entry, after this message? If so, then my translations might be wrong.

Lloffiwr19:06, 22 November 2010
 
 

Extension:Installer

I am not sure if it is something for translatewiki.net or a bug to be reported at bugzilla. E. g. Config-upload-help ("File uploads potentially expose your server to security risks. For more information, read the security section in the manual.

To enable file uploads, change the mode on the images subdirectory under MediaWiki's root directory so that the web server can write to it. Then enable this option.") uses wikitext to generate a link [ ] and <code> </code> to emphasise parts of the text. This and other similar messages populate balloons to give the user hints and are currently not working. One solution would be to fix this, or if this is not possible, to change the message. Are there any thoughts on this?

kgh18:26, 15 November 2010

mwr:75832 that broke it is currently fixme'd, lets's wait for resolution.

Max Semenik18:56, 15 November 2010

Cool, thank you for for reply. Cheers

kgh11:56, 16 November 2010
 
 

Uploadwizard-desc

In Uploadwizard-desc ("Upload Wizard, a user-friendly tool for uploading multimedia") what does 'for' mean? Should this word be replaced by 'using' or 'by'?

Lloffiwr01:13, 10 November 2010

It refers to this event, i.e. it was paid with this 300,000 $.

The Evil IP address11:03, 14 November 2010

Done Done Thanks for info - documented.

Lloffiwr12:39, 14 November 2010
 
 

Extension:Installer / chg for kons

Config-brokenlibxml ("Your system has a combination of PHP and libxml2 versions that is buggy and can cause hidden data corruption in MediaWiki and other web applications. Upgrade to libxml2 2.7.3 or later (bug filed with PHP). Installation aborted.")

Your system has a combination of PHP and libxml2 versions which is buggy and can cause hidden data corruption in MediaWiki and other web apps. Upgrade to PHP 5.2.9 or later and libxml2 2.7.3 or later! ABORTING (bug filed with PHP).

Your system has a combination of PHP and libxml2 versions which is buggy and can cause hidden data corruption in MediaWiki and other web applications. Upgrade to PHP 5.2.9 or later and libxml2 2.7.3 or later to fix this. ABORTING (bug filed with PHP).

Reason: Consistency with Config-using531 ("MediaWiki cannot be used with PHP $1 due to a bug involving reference parameters to __call(). Upgrade to PHP 5.3.2 or higher, or downgrade to PHP 5.3.0 to resolve this. Installation aborted.")

Cheers

kgh21:57, 7 November 2010

I think it would be better if you'd just mention what you request to be changed, instead of copying the complete message. Feels like a puzzle this way, and is less inviting to give attention to putting it like above.

Siebrand22:34, 7 November 2010

The problem here is that this is a pretty long message. I think with short messages it will be still working to do it like that. I will shorten my requests to make them easier to grasp. Cheers

kgh22:54, 7 November 2010

You could, for easier readability, mark the changed parts bold or italic, which would immediately focus the eye on these parts.

The Evil IP address11:06, 14 November 2010
 
 

Done Done mwr:76276.

Siebrand22:49, 7 November 2010
 

ResourceLoader

Configure-section-resourceloader ("ResourceLoader") Resource loader → ResourceLoader, typo see ResourceLoader

kgh19:55, 13 November 2010

Fixed with mwr:76655.

Raymond09:22, 14 November 2010
 

Extension:ArticleComments / chg

Article-comments-talk-page-starter ("")

<noinclude>Comments on [[$1]] <comments /> ----- __NOEDITSECTION__</noinclude>

<noinclude>Comments on "[[$1]]" <comments /> ----- __NOEDITSECTION__</noinclude>

kgh21:25, 15 October 2010

And this needs to be changed why?

Siebrand11:13, 16 October 2010

For consistency reasons. All other messages of this extension use "$1" instead of just $1 as they refer to pages (see e. g. Article-comments-no-comments ("Sorry, the page "$1" is not accepting comments at this time."), Article-comments-submission-success ("You have submitted a comment for "$1""), etc. Cheers

kgh22:05, 7 November 2010

Done Done mwr:76273.

Siebrand22:44, 7 November 2010
 
 
 

Extension:Donation Interface - Payflow Pro Gateway / messages missing for translation

Below this Payflowpro gateway-donor-stateTemplate:Msg/wrong parameter there is a dropdown list for selection containing "Select a State", "Outside the U.S." and all the names of the different U.S. states. The first two messages should be translated. Cheers

kgh21:37, 12 October 2010

Done Done Even though they shouldn't be there, I moved those two messages to a different group in mwr:75716.

Siebrand14:14, 31 October 2010

Thank you! Thank you!

kgh22:01, 7 November 2010

There's no need to reply to a done if there's no new information. We know you appreciate it. Thanks.

Siebrand22:36, 7 November 2010

You can bet that it do appreciate it. :) It may sound strange to you, though it will most probably not be unexpected for you that it is: It is one kind of creating fun for me here. I know that it is not neccessary.

kgh23:02, 7 November 2010
 
 
 
 

There are some threads which still need some attention.

I just realised that they seem to be orphanded. Thank you and cheers

kgh22:09, 7 November 2010

I/we know. They're my/our wachlist(s).

Siebrand22:32, 7 November 2010
 

Extension:Maps / chg - consistency

The second part of these two messages seems to be identical: Maps-error-no-layertype ("You need to specify the layer type. These types are supported: $1") and Maps-error-invalid-layertype ("There are no layers of type "$1". Only these types are supported: $2"). Why not adjusting them, except for the parameters of course.

kgh16:47, 25 October 2010

JeroenDeDauw> Nikerabbit: One message is for when an user does not provide a layer type, the other is for when the user provides an invalid layer type.

Nike13:21, 26 October 2010

Hi Nike, thanks for addressing this to Jeroen. Cheers

kgh13:25, 26 October 2010
 
 

Extension:ArticleComments / messages missing for translation

At least the reasons for failure "Name field is required." and "Comment field is required." are not available for translation. Cheers

kgh21:46, 15 October 2010

And where in the code are these texts observed?

Siebrand12:04, 16 October 2010

Well I do not know. I tested this extension to be able to make a better translation. I you enter nothing and try to save the comment you get these hints. To me it makes sense to have them too. Cheers

kgh12:57, 16 October 2010

I think you didn't take the following message into account: Article-comments-required-field (""$1" field is required.").

Siebrand16:30, 16 October 2010

Oops, your are right! The version provided there must show an earlier phase of development. Actually I should have realised this on my own. :-|

kgh22:09, 16 October 2010
 
 
 
 

Extension:Donation Interface - Payflow Pro Gateway / chg

Payflowpro_gateway-donor-countryTemplate:Msg/wrong parameter "Country/Region" → "Country" Region is misleading and actually not asked for. If region is to be kept somehow it should be added to payflowpro_gateway-donor-stateTemplate:Msg/wrong parameter instead.

kgh21:14, 12 October 2010

Extension:Installer / chg

Config-no-fts3 ("Warning: SQLite is compiled without the FTS3 module, search features will be unavailable on this backend.") "Warning: SQLite is compiled without the FTS3 module, search features will be unavailable on this backend." → "Warning: SQLite is compiled without the FTS3 module, search features will be unavailable on this backend."

kgh19:26, 6 October 2010

Thanks, done in mwr:74589.

Max Semenik12:56, 10 October 2010

Thank you! Thank you!

kgh16:52, 10 October 2010
 
 

Extension:Installer / chg

Config-have-fts3 ("SQLite is compiled with the FTS3 module, search features will be available on this backend.") "SQLite is compiled with the FTS3 module, search features will be available on this backend." → "SQLite is compiled with the FTS3 module, search features will be available on this backend."

kgh19:28, 6 October 2010

Thanks, done in mwr:74589.

Max Semenik12:56, 10 October 2010

Thank you! Thank you!

kgh16:51, 10 October 2010
 
 
First page
First page
Last page
Last page