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, see also documentation.

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

Please support "Traditional Mongolian Script"

"Traditional Mongolian Script" ([w:https://en.wikipedia.org/wiki/Mongolian_script] ) are used in mongolia and Inner Mongolia of China to this day to write Mongolian , which based on this classical vertical script. In Mongolia, the Cyrillic script writing system is used. Until 1990, only elders used to read and write the Mongolian script. But in the 1990s, secondary schools began to intensify the teaching of the Mongolian script.In China, the ethnic Mongol population was nearly 6 million according to a 2010 census. Many of them still receive nine-year compulsory education in Mongolian using the traditional Mongolian script.Mongolians living in Inner Mongolia are not familiar with the Cyrillic script and use the Mongolian script writing system only. They are unable to read Mongolian Wikipedia in Cyrillic. Data: A valid ISO 639-1 or 639-3 language code:mon [1] Unicode range: [2] The language name in English and in its own language: mongolian -ᠮᠤᠨᠭᠭᠤᠯ ᠬᠡᠯᠡ writing-mode: vertical-lr. Now, Internet Explorer, Safari, and Chrome support CSS writing-mode: vertical-lr. Default should still be "mon" in Latin alphabet. Please support "Traditional Mongolian Script".

00:50, 5 January 2014

I would exclusively oppose mn-Mong, as currently the Traditional Mongolian language is having a test-Wikipedia against at incubator:Wp/mvf.

13:15, 27 May 2017
 

Requeat addition for Portal:Dag

I wish to

  • Request addition of a new language for translation: Portal:Dag
  • Request translator privileges for the same language.
10:34, 27 May 2017

Apertium MT not working for Asturian language

Edited by another user.
Last edit: 11:25, 25 May 2017

Hi. Some months ago Apertium machine translation stopped working for Asturian language.

Is there something I need to do to have it again? It was really useful to speed up our translations.

Regards.

11:10, 25 May 2017

I reported a few days ago that Apertium is broken for everyone: phabricator:T165949. The issue may already be fixed in the code, but translatewiki.net was not upgraded yet, I think.

11:27, 25 May 2017

Thank you!

I missed your report in phabricator, I hope it all will be fixed soon.

Regards

12:45, 25 May 2017

Apertium works now. If you were seeing empty suggestions, this was the reason. If it is not appearing it could be

  1. Apertium service temporarily unavailable
  2. Missing Spanish translation (if I remember correctly Apertium only does Spanish to Asturian)
13:05, 26 May 2017
 
 
 

random list of texts to translate/reread

Is it possible to have the list of items to translate or to review, presented in a random order ? It appears that the order is always the same. May be there is a reason. But presenting the texts in a random order improves the covering of the operations and brings surprises in the translated subjects making them atractive.

07:15, 26 May 2017

I can imagine some people would like to do it in random order, especially for review. For myself it helps to do it in order, so I don't need check context for every message. For example two different software could use different wording for some term, and inconsistent translations would be hard(er) to notice if related messages did not appear together.

13:01, 26 May 2017
 

Include phabricator in translatewiki.net

Hello, following this phabricator entry, I would like to know what action are now required to make advance the project of adding phabricator translation on translatewiki.net.

16:04, 25 May 2017

Thanks for your interest. Let's keep the discussion on the Phabricator thread. I'm not sure you saw my reply on #mediawiki-i18n:

17.45 < Nemo_bis> psychoslave: did translatewiki.net staff get push access to the upstream repository?
16:28, 25 May 2017
 

In the message MediaWiki:Action-newsletter-restore/en: 'retore a newsletter' should most probabély be 'restore a newsletter'

Please fix this typing mistake

21:59, 24 May 2017

Reviewed messages to watchlist

Wouldn't be nice to have the option to add the messages one _reviews_ to his watchlist? Probably in [Special:Preferences#mw-prefsection-watchlist|Advanced options]]. Where could I request this feature?

02:44, 21 May 2016
15:41, 20 May 2017

Yes to this "Translators should be able to stay on top of new translation work easily". But the example given in the tracking task T159642 (duplicate of T62904) talks about watchlisting entire message groups. It might help for some messages groups that I care of. But I sometimes translate or review random messages. I may not have a big interest in some projects, but I do in the messages I translate/review.

I was asking for the reviewing part.

Thanks Nemo.

04:22, 24 May 2017

We should probably automatically watchlist all the messages reviewed by the user who has selected "Add pages and files I edit to my watchlist" in the preferences.

06:58, 24 May 2017
 
 
 

Time out in some translatewiki pages

I often find while visiting Special:Watchlist or Special:ContributionScores the message "504 Gateway Time-out" from nginx. I refresh the page and the problem is gone. It doesn't happend with other pages. Certainly, not a big problem. Does anybody see this too?

22:18, 13 March 2015

Are you seeing less 504 errors, recently? I think I see less errors in the logs.

15:07, 18 June 2016

Yes, less errors since I reported back in March 2015. Anyway, I just tried both links and only Special:Watchlist gave me 504.

14:06, 19 June 2016

Did it get better recently?

10:47, 21 May 2017

Yes. Can´t remember dates though. Thank you.

04:26, 24 May 2017
 
 
 
 

Use MobileFrontend

Now that Special:Translate is available on mobile, MobileFrontend could be enabled on translatewiki.net. Translation is a not very complicated action, which can be done on the go.

15:10, 13 May 2017

Special:MainPage doesn't work at all with MobileFrontend, though.

09:39, 19 May 2017

What’s the problem with it? Maybe that should be fixed—Special:Translate is much more used. Also I don’t think it’s hard to be fixed as Special:MainPage seems to have an absolutely responsive design.

12:21, 19 May 2017

Some of the styles are not getting loaded I think.

11:48, 20 May 2017

Is there any way to make MobileFrontend opt-in through the preferences (for testing)? Or can I get the source code of Special:MainPage to test on my own wiki? (Currently there’s no link on Special:Version, please link to its Git repo there if possible.)

11:57, 20 May 2017
 
 
 
 

www subdomain not working

Please amend When using Firefox at computers other than my own, I will type in "translatewiki + Shift + Enter" which the browser then redirects to http://www.translatewiki.net/ but that URI can't be found. Although the days of a "www" subdomain are long ago, it's still worth maintaining these to redirect to the proper https://translatewiki.net/

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)

20:56, 16 October 2016

What version of Firefox is this? I've never seen such a behaviour.

06:43, 17 October 2016

Every version since at least 2.x has had this. Have you tried it?

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)

06:51, 17 October 2016

Ah, I see now. I had missed the shift.

19:52, 19 October 2016

Is this the best place to post bugs? I don't see a Village Pump here, so I figure this is the most centralized discussion space.

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)

21:52, 19 October 2016
 
 
 

DNS/Apache config needed? Who has the ops access to twn server?

03:09, 29 November 2016

I am not convinced this is worth the hurdles of adding DNS records and redirects and making sure HTTPS is not broken.

10:06, 21 May 2017

If you think that adding an HTTP redirect is too difficult then that is definitely a problem. I'm 100% certain that there are incoming links which include a www subdomain so if you want incoming viewers to think the site is still functional, I would recommend adding it.

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)

17:47, 21 May 2017

Redirects are hard nowadays, yes. See for instance phabricator:T133548. Closed.

22:31, 22 May 2017

Well, several dozen of them certainly are. Much harder than one to be sure. I don't see how no response--not even a 404 page--is preferable but that's where that incoming traffic will go: nowhere http://isup.me/www.translatewiki.net

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)

00:49, 23 May 2017
 
 
 
 
 

Machine translations of User:Irus

This user massively uploads terrible machine translations, including to Russian language (which is stated as his "native language" on his userpage), see User talk:Irus and (for Russian-speaking users) [1]. All his edits must be rollbacked, his new pages (Wikimedia:Wikiedudashboard-articles.none/ru) must be deleted. His messages already displayed on Russian Wikipedia special pages, it's a clear vandalism. (If this page is not administrator's noticeboard of this project, please, move this thread to that page).

13:07, 11 November 2016

User:Nemo bis, what about reverting and deleting? I can do first, but I don't have rollbacker rights, can you grant it to me?

13:29, 11 November 2016

Deleting doesn't have any effect, you'd better retranslate any newly translated message which you think it worse than nothing. As for rollbacks, are you sure everything needs to be rolled back? How many messages did you check? I can make you sysop temporarily, but tell me how much time you need.

13:45, 11 November 2016

Until all his new messages are re-translated, English versions are much better then Irus's versions. I sure that many of his edits need to be rolled back, maybe all /ru-edits. I check many of his /ru-edits and almost all of this is nightmare horror. I think this weekend will be sufficient.

14:01, 11 November 2016

Ok. If you can't check every single translation before rolling back, try at least to sample them. Sometimes, or in some message groups, there might have been some logic.

Deletions don't have any effect because FuzzyBot will reimport the exported translations on the very next day. One would need to first remove the translations with a patch to the MediaWiki extension or other project. It's vastly faster to retranslate.

14:07, 11 November 2016

Is it possible to filter from his contribs only /ru-pages?

15:25, 11 November 2016
 
 
 
 
 

Activate support for webm

Could webm be added as a file format to be displayed? I linked a file used on Wikimedia Commons on the page Translating:Proofreading the messages but it does not display as a video, only as a link. And even on the file page no preview of the file is available. I guess this is just a configuration issue, and adding webm in the right place is enough.

16:58, 29 May 2015

Could you send a patch against the gerrit translatewiki repo?

13:16, 30 May 2015

Unfortubately not, since I do not know exactly which parameter need to be changed.

14:09, 30 May 2015

The README highlights a number of prerequisites, but hopefully easy with Ubuntu packages and puppet: https://phabricator.wikimedia.org/r/p/mediawiki/extensions/TimedMediaHandler;browse/master/README

08:22, 22 May 2017
 
 
 

Using alternative date/time params $2, $3 leads to warning

In cases where a date/time parameter $1 is used, alternative date $2 and time $3 parameters may be given in message documentation suggesting that these two parameters can be used instead of the combined one, in languages that need to split date and time, such as Greek.

But editor doesn't seem to recognise that $2 and $3 together are legitimate substitutes of $1, leading to an edit warning and a fuzzybot edit.

See example message MediaWiki:Userrights-expiry-current/el screenshot:

Screenshot of date params edit warning in translatewiki.net.png

09:50, 7 February 2017

I begin to wonder whether the checkers should look in qqq instead/in addition to the source.

06:23, 22 May 2017
 

Lost edit summaries

The popup thing that is supposed to warn you about the importance of edit summaries actually eats them if you submit the edit form via keyboard.

18:38, 30 June 2015

Or the "publish" bottom at the top of the edit form (which is what a keyboard submit falls back to as the first submit element), instead of the "save" at the bottom.

18:40, 30 June 2015

Thanks for reporting. What do you suggest/plan to do? Did you report this on phabricator with more details in the meanwhile?

21:08, 31 August 2015

T111670. I suggest removing $wgDefaultUserOptions['wikieditor-publish'] = 1; from the TranslateWiki configuration; it seems to be a thoroughly useless feature.

07:05, 7 September 2015

Thanks, now I understand. I never use WikiEditor so I had no idea those buttons existed.

07:33, 7 September 2015
 

I don't find such a setting in the current or past configuration for twn. Hmm.

13:06, 21 May 2017
 
 
 
 

Wikimedia:Wikipedia-android-strings-app name/sr

Delete this page, translation already in sr-ec. Also delete messages made by MileK messages are already in sr-ec.

09:31, 27 June 2014

There's only 20 of them, all in the Wikipedia android app, right? [1]

10:52, 21 May 2017
 

Improvements for Serbian language

I have a few questions.

  1. Bot for "sr-el": Is it possible that someone creates bot that will copy all pages suffixed "/sr-ec" to "/sr-el" (only if "/sr-el" does not already exist or exists but is different from Cyrillic counterpart when transliterated to Latin) so that newly created pages are same as "/sr-ec" ones but transliterated to Latin script? This tool, http://free-zg.t-com.hr/halama/lc/, is good and might be useful for taking script or some sort of mediate usage. This would improve largely percent statistics as main translation tool creates pages suffixed "/sr-ec" i.e. only for Cyrillic script.
  2. Change "sr" to "sr-ec" in interface so link lead to proper places: Where to change "sr" into "sr-ec" that makes on the left menu link titled "Translation" ("Превођење"), right below logo, because now it gives no result because localization is being done in "sr-ec" and not "sr" ("Language code" field)?
  3. Main Page of Translate Wiki: This is also problem on Main Page, where statistics are 0 for some reason — maybe because "sr" is used instead of "sr-ec". Also, how convert "9.6k" into "9,6k" (comma is for Serbian) and make "поруке за превођење" displays in two lines (I tried with br but it does not expand into newline but displays as such; right now [2017/5/10 18:33] it is with newline in message, but it might not work either). Bottom "Powered by" should be made translatable.
  4. Mobile sr.wikipedia logo: Someone should implement translated image commons:File:Wikipedia wordmark sr.svg to m.sr.wikipedia.org.

Also, is it possible to remove two "српски" messages in menus and elsewhere and leave only one i.e. make them different (for example, "српски / srpski" for "sr", "српски" for "sr-ec" and "srpski" for "sr-el"). It is very confusing to have two same "српски" messages... This problem is also present when choosing language on Wikimedia Commons etc. --Obsuser (talk) 16:46, 10 May 2017 (UTC)

11:32, 6 May 2017
Edited by another user.
Last edit: 13:54, 20 May 2017

1) Yes it is possible, but I don't have time for it.

4) This should be reported to phabricator.wikimedia.org. We do not handle logo changes here.

For 2 and 3 I need to investigate more.

12:05, 20 May 2017

OK, can you also change dot to comma as default separator for Serbian (especially on TW Main Page; here it is comma for Croatian and Bosnian, should be for Serbian too; maybe MediaWiki:Twnmp-stats-number-k/sr-ec and sr-el should be deleted, as those two languages have not created these pages).

Also, why there are two toolbars shown when editing this thread (at least for me)?

17:03, 20 May 2017

I reported https://phabricator.wikimedia.org/T165958 for the first issue.

The two toolbars has started happening recently. https://phabricator.wikimedia.org/T165959

09:51, 21 May 2017
 
 
 

Questionable translations

A thread, Thread:Support/Questionable translations, was moved from here to Portal talk:Ro. This move was made by Liuxinyu970226 (talk | contribs) on 20 May 2017 at 21:50.

Language coordinator

I talked with a friend who is a member of KDE Serbian translation team about what should be done if two or more users do not agree about translation, terminology or other language issues. He told me the following, and I quote:

"As people are aware that in practice the translation is a very subjective thing, then it is determined who is in charge of that language (the person is often called "coordinator"), and what the coordinator says, that's final. It is very important that the coordinator has technical means in order to be his last. If there is someone new and do not agree about some issues, and do not convince the coordinator what they want, they can leave; if they just start to work beside the warnings, then the chief will prevent that using his/her technical means.

As to who is in charge of a translation unit, in voluntary undertakings it's the one who first came on the project *AND* work on a regular basis. The coordinator can be changed only if he leaves the project or stops to work regularly. There is no other way — for example, referring to any writings, even if they are from God itself, do not pass."

This method is used in many open source projects, including Gnome, KDE, Debian, Fedora, Mandriva etc. Something similar could be applied here. What do you think?

12:16, 17 August 2012

I'm fine if some language communities want to have a benevolent dictator who is be able to have the final say, if that reduces conflicts. I would limit it to that, however. What I don't want is any kind of gate keeper role like the coordinators usually are in above mentioned projects.

10:45, 19 August 2012
 

I think it would be much better to strive for a consensus model, if possible. Precisely because translation is subjective, I don't think it is a good idea to give one person the absolute power to impose his/her personal preferences -- especially if this power is not based on translation quality but simply given to whomever got there first and/or produces the most. That way, one person could easily ruin an entire project language.

11:45, 19 August 2012

I have the exact opposite problem. A user came into the project, ignoring the translation practice in Serbian language, and started fuzzing around with the translations. This message is a response to his use of noun forms for button messages, which is totally wrong. Of course, he didn't consider my suggestions, and he kept reverting my edits, stating that "It is inappropriate to revert my edit or initial translation without a discussion". For such a basic thing a discussion or consensus is not necessary at all.

23:04, 5 September 2012

Well, this is a discussion. Niklas gave his suggestion, is it impossible to follow it? If that's a basic thing perhaps it won't be too hard to get it added to your language's guidelines with a brief discussion on portal talk.

07:24, 6 September 2012

I already posted the guidelines on the portal page of Serbian language, but it seems nobody care for it. Though, I am the only active Serbian translator on this site. Other users periodically come here to translate a few messages (often on translation rallies, like the already mentioned user I had problems with, which proves an obvious thing).

15:45, 8 September 2012
 
 
 

We try to cover some of these desires (from our own point of view) at mw:Internationalisation_wishlist_2017#Motivation_and_understanding. Some reasonable pieces are still missing.

17:11, 20 May 2017
 

Talysh Wikipedia Project's Name

A thread, Thread:Support/Talysh Wikipedia Project's Name, was moved from here to Portal talk:Tly. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 17:04.

Talysh language

A thread, Thread:Support/Talysh language, was moved from here to Portal talk:Tly. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 17:02.
First page
First page
Previous page
Previous page
Last page
Last page