View source for Thread:Support/I can't find a field...

From translatewiki.net
Jump to navigation Jump to 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, see also documentation.


First page
First page
Last page
Last page

Translations export

Hi, I wish to export made by me last transfers to the Tatar Wikipedia (tt or tt-cyrl), but the program rejects export: "This language code should remain unused. Localise in tt-cyrl please".

Derslek (talk)04:09, 21 March 2015

Your contributions were indeed in the tt-cyrl subpages, so that's the language code you have to select. Out of curiosity, what are you using the exported file for? Note your translations to MediaWiki will be live on the Tatar Wikipedia this evening (in about 18 hours from now, to be precise).

Nemo (talk)07:29, 21 March 2015
 

I can't find a field...

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.


You can view and copy the source of this page.

 

Return to Thread:Support/I can't find a field....

MediaWiki doesn't have a link in that position. Is that a link to a user subpage/sandbox? It's probably a local JavaScript.

Nemo (talk)20:48, 30 January 2015

Than What to do to change this ? Please guide me.. Thank you....

NehalDaveND (talk)06:51, 13 March 2015

You have to search that string in w:sa:Special:Search I think, and ask a local administrator to add your translation.

Nemo (talk)06:59, 13 March 2015
 
 
 

Klicking the "next page" button https://translatewiki.net/w/extensions/LiquidThreads/images/arrow_right_25.png on [Support]] I do not get to the next chunk of messages but opens an edit window that lets me add another subject. Nice to be able to enter this error report but prohibitive when wanting to read the page.

Purodha Blissenbach (talk)12:50, 19 March 2015

Header message on this very page (Support) broken

I am currently being enchanted with the ksh version of what used to be an text in English. Somehow this language switching needs to be improved.

[[kgh]] (talk)21:38, 14 March 2015

Similarly, on pages transcluding {{ {{Localized|ProcessNavigation}} }}, there are times during which I see the transcluded stuff in another language for a while.

There has to be a caching problem somewhere.

Purodha Blissenbach (talk)00:46, 15 March 2015
 

Slow transfer of translated MediaWiki core

There used to be a delay of only 2 days, now it's weeks. Why? The block log entries translated into Finnish haven't reached the Finnish projects in ten days and it's annoying. Why is this and why has the delay expanded so massively?

Pxos (talk)16:47, 14 March 2015

Can we keep translator entered !!FUZZY!!s in place?

Edited by author.
Last edit: 12:22, 14 March 2015

I know that this may be controversial, and there are other possible solutions to the problem, depending on message handling, such as using HTML comments where they do not harm.

I use !!FUZZY!! so as to mark problematic or untranslated words that need further work. So, marked messages show up in the future and I know that they need treatment, which often takes a long time until it is possible to complete.

translatewiki.net usually removes the !!FUZZY!! markers and either deletes them, probably keeping them in a database field, or moves them to the beginnings of messages, depending on circumstances. That makes it harder for us translators to focus the marked word(s) or phrase(s) when quickly skipping through messages.

Only when using the AJAX editor and not reloading anything are !!FUZZY!! markers left in place. That helps, but only during the current session.

Purodha Blissenbach (talk)12:11, 14 March 2015

As a side note, if !!FUZZY!!s were kept in place, it might be worth thinking of machine generated !!FUZZY!! markers to be inserted next to the place where errors were detected in cases when that is easily possible.

Purodha Blissenbach (talk)12:15, 14 March 2015
 

How about GENDER support on the various user names?

Purodha Blissenbach (talk)22:15, 13 March 2015

I'm not seeing this message show up in Telugu on the TE Wikipedia:

https://te.wikipedia.org/wiki/%E0%B0%B5%E0%B0%BF%E0%B0%95%E0%B1%80%E0%B0%AA%E0%B1%80%E0%B0%A1%E0%B0%BF%E0%B0%AF%E0%B0%BE_%E0%B0%9A%E0%B0%B0%E0%B1%8D%E0%B0%9A:%E0%B0%AB%E0%B1%8D%E0%B0%B2%E0%B1%8B

How long does it usually take for the translation to show up? Is there a way to see when the translation was posted?

Sorry for posting newbie questions. Thanks for your help!

DannyH (WMF) (talk)18:56, 13 March 2015

I asked in the #wikimedia-i18n IRC channel, and Nemo_bis replied:

FAQ#How is the work done on translatewiki.net connected to other wikis?
But https://phabricator.wikimedia.org/T85790

So I'm not exactly sure what that equates to, at the moment...

I suspect the translations will show up, within 24 hours, given that T85790 is marked as recently resolved? Can anyone confirm/correct that, please? :)

Quiddity (talk)19:30, 13 March 2015
 

There are two parameters documented but not used in the message, which bodes somewhat stale without them.

Purodha Blissenbach (talk)08:41, 13 March 2015

GENDER support for 'user' here please. Thanks

Macofe (talk)23:07, 12 March 2015

Please delete it.

-- By LNDDYL. (Talk)04:05, 5 March 2015

Header duplicated in support form

Screen shot shownig duplicate head tool box in support form.

There are two headers in the support form, see screen shot. Click actions performed in either of them always affect both of them.

Purodha Blissenbach (talk)07:54, 4 March 2015

What is/are "tag/tags" in "NFC tags"? NFC stands for "Near field communication" - a set of ideas and technology that enables smartphones and other devices to establish radio communication with each other.

Purodha Blissenbach (talk)18:30, 3 March 2015

Group statistic figures appear to be inconsistent

Screenshot of statistics page, group closed.
Screenshot of statistics page, group opened.

Group statistic figures still appear to be inconsistent. See Screeen shots.

Purodha Blissenbach (talk)12:34, 3 March 2015

Color codes shown with user names on Special:SupportedLanguages are grossly incorrect, off by dozens of months, even half-dozens of years.

Example: Tilla contributed the latest to Ripuarian in 2008 but is shown with a green underline in Special:SupportedLanguages/ksh.

Btw. it is not clear and should be mentioned whether colors meant for contributions to the particular language or contributions in general, but neither would be accurate.

Purodha Blissenbach (talk)23:33, 28 February 2015

Intro lines on Special:SupportedLanguages talk about user names etc. even if there are no users shown.

Purodha Blissenbach (talk)23:28, 28 February 2015

Babel boxes where no native translation has been provided

If you take a look at my Nynorsk user page, you will see that the last babel box reads "This user has basic knowledge of Old Norse." in English, even though the relevant Nynorsk messages all appear to have been translated several years ago.

Njardarlogar (talk)10:38, 16 September 2012

Ok, messages are available locally and there are no local overrides, so this is not a translatewiki.net issue. What's wrong exactly? non is not even enabled here and there's no translation, isn't it the normal behaviour for the extension to look for non strings and fallback to English? (I don't remember.)

Nemo (talk)11:12, 16 September 2012

It shouldn't fallback to English, there is no reason why other languages should be presented in English rather than the local wiki language.

Njardarlogar (talk)12:27, 16 September 2012

Well, the user language information are in the language they refer to because they're supposed to be useful to people speaking that language (so French proficiency information is always in French, and so on); the local wiki language doesn't matter at all. This is only my uneducated opinion, though.

Nemo (talk)13:13, 16 September 2012

The box should be using Old Norse (non) texts, which is only possible, if the language is available. In translatewiki.net. However, we cannot even translate to Old Norse, so there is no chance to have those texts.

For all languages that are not enabled as target languages to be translated to, we have he problem that Extension:Babel cannot be fed the needed texts. We can use the traditional template way, though, on each wiki individually.

We can also add translations to the source code directly. This does not help, since MediaWiki does not load messages for languages missing from Names.php. Nevertheless, this may prove useful, since having additional translations is certainly an improvement, and maybe a way will be found someday to make them available as well.

Purodha Blissenbach (talk)17:15, 16 September 2012

We could perhaps add an empty "non" locale just to specify the fallback to nn, so that they get loaded in such cases (basically only Babel). Opinions?

Nemo (talk)23:02, 13 July 2014
 
 
 
 
 

Translatewiki handout material

Hi,

I will be present this weekend at the Hungarian Free Software Conference as a member of Wikimedia Hungary (which will have a stand there). I would like to use the oppurtunity to popularize Translatewiki amongst contributors of open source projects. Do you know have any leaflets or other handout materials which I could use?

Tgr (talk)01:37, 8 November 2011

We don't currently have any.

Nike (talk)16:00, 12 November 2011
 

Any volunteers (preferably designers) for this? I'll add this to the sitenotice.

Siebrand23:11, 5 August 2012

Isn't it a bit too late for making handout material now?

// WikiPhoenix (Talk)15:41, 14 August 2012

What do you mean? It will always be late if we don't prepare them in advance for the occasions when they're needed.

Nemo (talk)15:43, 14 August 2012

Tgr was asking for material that he needed 10 months ago and I thought it was too late to announce that now. That's why I wrote that.

// WikiPhoenix (Talk)16:44, 14 August 2012

It's pretty obvious that it's too late for that event. However, generic handout materials can always be used (and updated). As long as we don't have anything, this thread can perfectly well serve as a discussion forum for missed opportunities, so I call on everyone with design skills to please help out.

Siebrand19:56, 14 August 2012
 
 
 
 
 
First page
First page
Last page
Last page