Support

From translatewiki.net
Jump to: navigation, search

Note Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries to track requests which need attention/action and help the developers find them.

All messages and requests can be placed here. After a few days at most, all the threads belonging to one of the supported projects (whether resolved or not) will be moved to their talk pages by the maintainers of this page, so that the developers and projects' managers can see them. In addition to that, and if possible before moving, the above-mentioned template should be added and updated as soon as possible to avoid forgetting threads.

First page
First page
Previous page
Previous page
Last page
Last page

new project: Huggle

Hello, on new project instruction I was sent to #mediawiki-i18n, in that channel I was sent here. I would like to request a set up of new project (huggle) so that we can manage translations through this wiki and make it easier for translators to translate interface. We are using

key:       value

format which is very easy to parse even by humans or machines and is very suitable for any translations. However I was told that this wiki is unable to parse this simple format. Parser for this format is a matter of 3 lines of code, but if you want I will write it. Thank you Petrb (talk) 15:17, 10 January 2014 (UTC)

Petrb (talk)15:17, 10 January 2014

Yep, please write it: as you chose an unsupported format, TWN has no resources to implement it (I tell you for your good :) ). As Nikerabbit mentioned, your format is similar to .properties files like:

# Messages for French (français)
# Exported from translatewiki.net
# Author: Nisard

index.quote=Que l'Amour s'introduise auprès d'elle sous le voile de l'amitié

so you can probably adapt https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FTranslate/HEAD/ffs%2FJavaFFS.php Even better if you can also commit a configuration patch after that (or after you pick a supported format); the format is documented but you can see e.g. [1] and [2] for the needed set of files/configs.

Whatever happens, please remember to keep this thread (and/or its summary above) up to date as regards the status of things and what the next steps are, so that it doesn't get stuck.

Nemo (talk)15:32, 10 January 2014
 
Edited by author.
Last edit: 15:35, 10 January 2014

here is the code, I have no idea what coding style you require, so feel free to reformat, it's obviously longer than 3 lines, because I add some comments and error checks too :-)

/*!
 * \brief Parses a line of translation text
 * \param line Line in ^key:\s*value$ syntax
 * \return array with 2 elements key and value or NULL in case that line can't be parsed
 */
function ParseLine($line)
{
    $colon_position = strpos($line,':');
    // check if there is colon in line
    if ($colon_position === false)
    {
        return NULL;
    }
    $key = substr( $line, 0, $colon_position );
    $value = substr ( $line, $colon_position + 1 );
    while ( strpos($value, " ") === 0 )
    {
        $value = substr ( $value, 1 );
    }
    return [ $key => $value ];
}
Petrb (talk)15:33, 10 January 2014

This doesn't look like a FFS to me, anyway please commit patches on gerrit.

Nemo (talk)15:34, 10 January 2014

no this is php.

anyway, where can I find documentation for that FFS format you talk about? this piece of french text isn't very self-describing. Thanks!

Petrb (talk)15:36, 10 January 2014

Petrb, are you still interested in working on this? Were the links above to other FFS not useful? Let us know if you get stuck at some point with the gerrit patches in Translate/translatewiki repos.

Nemo (talk)11:46, 21 February 2014

it seems easier if we just change the format to something what is sane and easy to parse, so from current list of formats supported by this extension, only properly supported format I found was XML, so I would probably go for that. What is next step, you can assume all our language files are XML now.

Petrb (talk)15:09, 24 April 2014
 
 
 
 
 

Hello!

Shouldn't these two messages rather be "Autopatrolled users" resp. "autopatrolled user"? The active form makes no sense to me as you cannot actively patrol with that right. Such a change would also be needed to stay in consistency with other "passive" rights like e. g. MediaWiki:Group-confirmed/en/MediaWiki:Group-confirmed-member/en and MediaWiki:Group-autoconfirmed/en/MediaWiki:Group-autoconfirmed-member/en resp. MediaWiki:Group-autoreview/en/MediaWiki:Group-autoreview/en.

Vogone (talk)15:01, 24 April 2014

Shouldn't this be in English?

Amir E. Aharoni (talk)20:00, 18 April 2014

No, as there is a source page on German Wikipedia. If there is a local version on a wiki language, you can point there.

Siebrand12:06, 24 April 2014
 

luri lrc translatewiki test adminship

Hello
please help me to be a luri lrc translate wiki adminship!!!!!

Mogoeilor (talk)10:41, 7 April 2014

Why would you need this?

Siebrand12:43, 8 April 2014

Hello MR siebrand
so thanks for your helps I want this point for delete superfluity edites or another interpolation
could you help me?

Mogoeilor (talk)11:19, 13 April 2014

What is it you need to get done?

Siebrand13:41, 14 April 2014

Hello
so thanks I need this for delete unasked edites and other superfluity edites if it possible
best wishes

Mogoeilor (talk)04:39, 15 April 2014

Which page(s) would you like to see deleted?

Siebrand14:40, 15 April 2014
 
 
 
 
 

Encoding format

Translatewiki and our project seem to have gotten into an unintentional tit-for-tat war over encoding formats. Which of these formats does Translatewiki prefer for qqq.json?

Quotes:

 " or " or \u0026quot; or \u0022

Angle brackets:

 > or > or \u0026gt; or \u003e

Looking at our logs, we see each of the above arriving from Translatewiki at one time or another.

NeilFraser (talk)00:26, 22 April 2014

We've recently (a few weeks ago) changed our code to do all UTF-8. So there's no longer \u-encoding.

Siebrand08:57, 23 April 2014
 

Function name should be in code tags.

Siebrand16:49, 14 April 2014

This message probably needs punctuation.

Siebrand17:27, 14 April 2014

Needs correct notation of CC license.

Siebrand17:39, 14 April 2014

Needs correct notation of CC license.

Siebrand17:39, 14 April 2014

Put LocalSettings.php in code tags.

Siebrand14:53, 14 April 2014

This should not have punctuation.

Siebrand13:54, 12 March 2014

Could this be rephrased? It is a little patchy…

Jeblad (talk)16:20, 20 April 2014

Would it be correct to translate this as the title? Or does this apply to all titles. Unlike content (see below) "title" by itself sounds wrong.

See also: Visualeditor-dialog-meta-settings-nocontentconvert-label ("<Visualeditor-dialog-meta-settings-nocontentconvert-label>")

Lokal_Profil (talk)13:54, 22 April 2014

Why getting the messages twice when searching?

Hi, I've noticed that I get the same messages twice when I search translations within Message group. For example at https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-flow&language=fi&filter=&action=translate when you search "suppressing" you get two different messages, but both of those twice. This is frustrating because of this sometimes I'm trying to translate the same message many times.

Stryn (talk)18:31, 20 April 2014

Help for namespace

Hello. I'm contributor (since 2011) and administrator (recently) in Mongolian Wikipedia. In Mongolian Wikipedia should change some Namespace name in headline bar. Especially "Category". But i can't discover editing source. How can suit this.

In my opinion〈Category:〉 namespace — should not 〈Ангилал:〉, but should 〈Анги:〉. Example: 〈Ангилал:Франц〉 → 〈Анги:Франц〉

MongolWiki (talk)00:20, 13 April 2014

See Translating:MediaWiki#Translating_namespace_names: [1]. You should have a local discussion to confirm this though, e.g. at portal talk:mn with a link where other mn.wiki editors will see it.

Nemo (talk)05:06, 13 April 2014

Thank you. Here discussion begin.

MongolWiki (talk)05:29, 14 April 2014
 

I used "Extended MediaWiki translation". But it doesn't work in our Wikipedia headline. What problem, pls?

MongolWiki (talk)01:58, 19 April 2014
 
 

The message documentation refers to non-existent messages "Jsonconfig-bool", etc.

Shirayuki (talk)08:36, 12 April 2014

I fixed the docs.

Siebrand18:05, 16 April 2014

Thanks.

Shirayuki (talk)00:40, 19 April 2014
 
 

This message needs GENDER support, with the current username.

Amir E. Aharoni (talk)10:10, 14 March 2014

Please report this in bugzilla.

Siebrand16:50, 8 April 2014
 

Can we avoid markup in the message?

Nike (talk)16:52, 16 April 2014

I don't know if the break was added to keep a rectangle more square or something like that. You'd better check with Santhosh...

Siebrand18:03, 16 April 2014
 
First page
First page
Previous page
Previous page
Last page
Last page