User talk:Purodha

Archives: 1, 2.

Hi!

I found a few html strings in the ksh app translations. No big deal, I removed the html, but just wanted to let you know :)

You can see the strings I modified here:

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-no-email-account-alert/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-main-menu-heading-zero/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-main-menu-zero-faq/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-search-field-placeholder-text-zero/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-zero-settings-devmode/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-zero-warn-when-leaving/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-zero-wikipedia-zero-heading/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-zero-interstitial-title/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-zero-charged-verbiage/ksh

Thanks again for your translations!

Since strings of varying provenances are mingled in the "recently changed/added" message group which I very often use for translating, and there is no link to the appropriate message group per message in it, I shall likely continue to add HTML where it should not be. Is there a chance to add a per message check against HTML for Wikipedia-ios added to translatewiki.net?

Totally understandable. And having a check is a good idea - I will see if this can be done :)

Hi,

Could you please review my Myanmar translations for Google Blockly Games?

[[1]]

Many Thanks, Yoon

Sorry, no. As you can see on my user page, I do not read the language, nor do I unerstand anything of it.

Sorry for this. The editor simply showed that there was a double space, not that there was an on purpose added FUZZY tag in the middle.

I know the problem of unshown FUZZies :-) no problem. The intentional FUZZY is there because I still have to find out, what an entity is in the message context and how to translate it properly. Maybe you can help?

I just happened to stumble over https://translatewiki.net/w/i.php?title=Special:Translate&group=int-dcatap&language=ksh&filter=&action=translate where i learned that the terminology of wikidata https://www.wikidata.org/wiki/Wikidata:Glossary applies. So, now I know how to proceed. Thank you anyways ;-)

Hey thanks for all your translations of app ksh strings! Very cool!

(https://translatewiki.net/w/i.php?title=Special:Translate&group=out-wikimedia-mobile-wikipedia-ios&filter=translated&language=ksh&action=translate)

I just wanted to give you a head's-up on a couple small issues:

The native app isn't presenting these strings in a web browser, so HTML can't be embedded in the strings.

Also the app doesn't yet support "{{...}}" substitutions for things like plurals or gender at the moment, though we hope to add this support soon.

It's actually a good thing that you tried these though because we caught it and have now added tests to automatically catch this in the future when the app tries to bundle an incoming set of translations :)

Okay, no HTML. I shall try to fix this but if you stumble over something, your assistance is welcome :-) or send me a list - whatever.

If there are "{{...}}"'s now, should I remove them, or better keep them for the future? Are they only caught or actually filtered when bundling? If you happen to haven an estimate, how numerous are they?

Thank you for making me aware!

I think it's just the following strings which have HTML and / or braces:

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-article-languages-downloading/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-account-creation-captcha-required/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-account-creation-captcha-obtaining/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-account-creation-email-placeholder-text/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-wikitext-upload-captcha-error/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-wikitext-upload-captcha-needed/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-wikitext-upload-save-anonymously-warning/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-main-menu-language-title/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-main-menu-more/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-page-history-downloading/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-credits-gerrit-repo/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-credits-github-mirror/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-about-repositories-app-source-license-mit/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-lastmodified-by-anon/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-abuse-filter-warning-blanking/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-migration-prompt-message/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-page-read-in-other-languages/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-captcha-prompt/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-welcome-explore-tell-me-more-related/ksh

https://translatewiki.net/wiki/Wikimedia:Wikipedia-ios-explore-most-read-heading/ksh

Oh and yes it would be awesome if you could remove the "{{...}}" bits for now :)

Done. Found two minor typos, btw. :-) Thank you for the list that made it really easy for me.

Hello. Can you please elaborate on the edit summaries of Special:Diff/6706249 and Special:Diff/6712370? I allways thought that we should not modify markup in translations. Thanks in advence. Best regards.

Both $parameters are quotes, so they need to be included in quotation marks. With that done, <em> markup becomes superflous. It had been culturally wrong anyways, because it renders italics, and there is no justification to italicize quotations unless they are in a foreign language.

Hi Purodha,

Your feedback has helped us to add new features in Search Translations. Please read about it here. It would be really helpful if you could give us some feedback about the new features in Search Translations.

Thank you and we shall be waiting for your feedback.

Sorry that it took a while for me to read the abovmentioned "here!" page.

I am using the search in translatewiki.net quite often and it is a constant source of frustration for me.<ref>Although it bacame less.</ref> Maybe, the search page does not make obvious to the layman how to obtain the desired results, at least I do not get what I direly need. Here is a list:

• Search translations in the source language and find corresponding translations in your language.

  Neither can I select a/the source language(s) (looking for checkboxes) nor can I tell my wanted target language(s) nor which message group(s) I want to search. Having connected "languages" such as nl and nl-informeel, a common search was good to have, but that also holds for less obvious cases, e.g. when searching for accidental amendments across several languages.

• Search translations also supports search in the source language and find non existing and outdated translations in your language.

  No. Or: How? Btw: a/the source languge(s) and a/the target languge(s) would be what is generally needed, defaulting to what you write.

• Allows exact message title match.

  Again: how? The is no "search message title" checkbox in Special:SearchTranslations anywhere?

• Allows case (in)sensitive search.

  Yes, that checkbox was added.

• Set language and group prior to search with language and group operators.

  There is nothing the like on the search page.

• Refine your search with subgroup filter.

  I do not even understand what that means leaving alone detecting it on the search page anywhere. Group and subgroup is imho both synonymous for message group. Yes, languages and message groups are listed once a search has been performed. But that is after the fact, and clicking them does not seem to have any real effect.

• Provide an option to search for any, all and exact string match.

  Again, no buttons to be seen.

Btw. there is a "help" link that does not help searching, but may help when you want to install the translate extension, which is obviously already insalled when you see the link. ;-) --Purodha Blissenbach (talk) 07:35, 19 December 2015 (UTC) <references />

Hi. Do not destroy en-gb translations.

It seems to me that I got the en and en-GB versions swapped when editing. I am sorry. I do not understand how that could happen. I shall investigate how to avoid that in the future. Thank you for fixing the messages.

Hi!

I noticed your contributions here during the Translation Rally, well done! I wanted to let you know about another contest that Wikimedia Sverige is organizing on Wikidata.org. In this contest the aim is to translate words related to food so that we can create multilingual menus that we will use at a food fare in a week. You can read all about it here. We would really appreciate having the menus in your language. Also, there are some handy instruction videos available if you haven't worked on Wikidata before.

Kind regards,

I am sorry, I am not going to join the challenge.

1. It is almost over, I have no chance to earn an even decent position of honor.
2. The time to get a page where I could find out what to enter is in the 2-minutes range - much, much too slow to do effective work.
3. There is usually no way for me to find out what a page is even about.
   Startig from "apple", I followed the arrows to the next page several times (having to guess how to continue every now and then when the next page was deleted - why does the link then go it anyways?). The resulting pages, if they existed, did almost always not reveal anything that I could read or understand.
4. I was expecting that I am presented with a list of food items lacking a translated label. How would I find then given no such list?
5. Having to add each item I edited to a list with additional info that I have to learn how to find them out - looking cmplicated at my first glance - is not what I am interested to invest my time in.

I can be much more effective doing something else.

Thank you kindly for considering it anyway!

I checked your patches the other day and I see you are doing well. Code review is a bit slower these days because Siebrand is less active, but I'll make sure all your patches are eventually merged. Can I "assign" your reports to you, when you have already identified the solution in the report? Then you can assign them to me (by editing the support template in the thread summary) when you're unable to handle them, but I'll know which requests I need to get the developers' attention for.

Yes.

Ok, I'm proceeding. I'm fixing most of the things myself, but those assigned to you are still multiple. Most of them don't take much time and I left some hints. The most tedious ones are PLURAL and GENDER support, I suggest to file reports in phabricator when you see that a patch would take too long.

1. Reporting in phabricator when I see that a patch would take too long or was too complicated is exactly what I would like to do.
   But remember: phabricator is dead for me.
2. PLURAL and GENDER support were among the easiest things I did for long. But they require imho that I test them (unlike pure message text amendments) and I do not have access to a working MediaWiki test installation. The latest failure to get one was that tools lab does not have composer, if I recall that right, and I cannot request that changed, see above.
   Thus I unset my name from all such tasks assigned to me at the moment.

1. I work under the assumption that WMF ops will eventually fix Phabricator for you... You could try emailing ops-requests@rt.wikimedia.org to ask help, IIRC this bridge still works.
2. In many cases, GENDER and PLURAL don't require testing: sometimes they don't even need code changes, because the developer just forgot to use the magic word in the English text. Anyway, that's fine; please assign the PLURAL and GENDER stuff back to me when you can't handle them, so that I remember to do what needed.

1. Just sent an e-mail.
2. Yes, you are right. It is only frustrating when I find that I have a fix but cannot test and submit it. Maybe I should learn to live with the risk ;-)

I've cleared the backlog of requests to me. Siebrand is also active reviewing patches here at the hackathon, so you may want to send some for a fast review. :)

Hi. Your claim for a cut in the rally bounty is unfortunately not yet valid. See the rally page for a detailed reason.

Hi,

I am working to add new features to Search Translations (link) and would like your feedback on the same. I have an idea of a new feature, called "text search with autosuggest" through which you can specify your search filters in the search box itself (apart from the UI), and also have autosuggest to show the possible values for the filter options. An example is this.

Please write a comment here about what you think of this feature. Also here you may read about the other improvements that are planned.

Thank you and I shall be waiting for your feedback.

I am sorry, I cannot access phabricator. Whenver I try, I see a web page that tells that I was going to receive an e-mail. The address is wrong. When I try to enter my correct e-mail address, which I was using in bugzilla, it tells me that my name belonged to someone else. When I try to log in via my account at Metawiki, the same happens. Apparently, up to now, I did not receive any response to my various complaints. --Purodha Blissenbach (talk) 09:17, 30 March 2015 (UTC)

This might help.

There is nothing helpful there.

The phabricator task description can be found here along with the example 1 and example 2.

Now we search first and then use filter to narrow down results. What do you think of the feature where you can apply filter in the search box itself (apart from UI) and get results on the search button click? As a translator would it be helpful to you or would you rather search first and then apply filter (e.g message group, language, etc)?

Hello, thanks for all your reports at Support. In the cases where you have already identified a solution (such as typo fixes, but also slightly more complex cases), have you considered sending a patch yourself? It's very easy (I learnt in few hours with no prior VCS experience) and would make the solution much faster, letting me instead pester the devs more about your reports which require more work. ;-)

I would like to send patches, and you may know that I did so often in the past.

Currently, I cannot. Despite having had some help last year, switching to git etc. did not work for me. I shall try it again during the next days - thank you for giving me the kick - and if I still cannot get it working this time, I shall report.

Thanks for not giving up!

If all else fails, remember you can also use https://tools.wmflabs.org/gerrit-patch-uploader/ We have great contributors who never sent patches to gerrit directly.

My try to start from scratch ended wih: https://tools.wmflabs.org/purodha-testing/core/index.php?title=Haupsigg

I cannot find out how to get skins. (After spending ~4 hours searching)

All links to download something static are not for me™ :-) What I need are instructions on how to clone the common skins as a git repository. I was not even able to find where they are. I understand that once I have a git repository of skins, I can link (or even copy) them to the skins directory local to my test installation of MediaWiki and proceed with them. See also Thread:Support/ About MediaWiki:Default-skin-not-found/en and MediaWiki:Default-skin-not-found-no-skins/en

Apparently they want you to use composer: mw:Download_from_Git#Fetch_external_libraries

But you can also download all skins separately: mw:Download from Git#Using Git to download MediaWiki skins

No. That is not what I want to use. I want to use git, as I wrote.

With some luck, and by trial and error, I found git clone ssh://purodha@gerrit.wikimedia.org:29418/mediawiki/skins.git which now brought me an apparently all emply repository which also did not help.

I am a bit further as it seems, I can get core, all extensions and all skins via git.

Only git review refuses to work from individual extension or skin directories:

     ~/extensiions/Translate > git review
     Enter passphrase for key '/home/.../.ssh/id_rsa':
     Problems encountered installing commit-msg hook
     /home/.../extensions/Translate/.git/hooks/commit-msg: Not a directory
     protocol error: expected control record
     ~/extensiions/Translate >

It also does not work from the extensions directory itself:

     ~/extensiions > git review
     Enter passphrase for key '/home/.../.ssh/id_rsa':
     remote: Processing changes: refs: 1, done
     To ssh://purodha@gerrit.wikimedia.org:29418/mediawiki/core.git
      ! [remote rejected] HEAD -> refs/for/master/master (no new changes)
     error: failed to push some refs to 'ssh://purodha@gerrit.wikimedia.org:29418/mediawiki/core.git'
     ~/extensiions >

So again, nothing I can do. Btw. although there are lots of wiki pages that should describe all this, some say different things, nothing working for me.

Another problem: Some of my hint here could to to bugzilla, and they were there already had not bugzilla been discontinued. Yet phabricator lets me login, then tells me that is was sending me an e-mail to a wrong address → dead end.

I managed to submit a patch to core.

The gerrit web site says it was erroneous - that is at least how I interpret the -1 in the Code-Review column - and there were 2 comments on it in this context. How or where can I find these comments, and how to find out what is wrong?

You have to click on "Side-by-Side" to open the diff view for the corresponding file, for example: https://gerrit.wikimedia.org/r/#/c/198300/1/includes/skins/SkinFallbackTemplate.php There you can see the comment (in this case on the right side, but it is also possible to add it to the left). You can also reply there. To publish a added comment you have to add a (empty) comment to the whole patch set.

I managed to submit a patch to an extension few minutes ago.

I used a method, however, that does not scale. I downloaded the extension individually as a git repository and set it up to use git review. If I had to do that for each skin and extension, I had to type my key pass phrase 3060 times, spending almost 26 hours typing pass phrases without a break. With waiting times between the prompts, that would add up to some 56 to 62 hours, not counting sleeping times, that is more than a working week. I refuse to do that. There must be a better solution.

You can use "ssh-add" to avoid retyping the passphrase.

How would I do that?  :-( seems not to work on several hosts.  man ssh-add does not enlighten me enough.

$ ssh-add -t 600 ~/.ssh/id_rsa
Could not open a connection to your authentication agent.
$

I don't know. I just type "ssh-add" on my machine.

That was my 1st try - yielding the same error message.

Hi Purodha,

I am a mediawiki contributor and currently I am preparing a proposal for improving translations search. I have seen that you have reported some bugs regarding translations search in the past. It would be really helpful if you could give me some feedback. Your feedback will be valuable. Thank you for your time.

For translatewiki.net, I would like to have different buttons next to the standard skins (vector, in my case) search box, ordered by my usage priority here:

1. Search in translations to 'my target language' only.
2. Search in 'my source language' only. Currently that is fixed to English, but may be different in the future.
3. Search in translations to any language only.
4. Standard search.

Whether or not source/target languages are the ones currently selected for translation or taken from the user preferences is of lesser concern. Both are useful, the current translations settings are both more flexible and probably more confusing. All of those should open a new tab/window as instances when I do not want to keep the original window are too few to warrant even a choice for me.

Sometimes, I wish to be able to strict string matches on parameters, markup, wikitext, special characters, and parts of words, such as "$1|$2]] userna", which currently does not work.

Rarely, a "hide matches" mode, which only lists page titles, and you need a mouse action to see the matched text and its environment, would be a time saver.

Also rarely, a regular expression match would be useful for me, but I doubt that I would implement it myself, even if I knew how, since it's really rare. But maybe, it is easy? :-)

The same holds for a "case (in)sensitive" switch.

Thank you a lot for your valuable feedback. :)

By the way, your question triggered that I re-evaluated the Special:Search/Translate page, which I did not even have in mind for my above answer, because at some time in the past I found it was 100% useless for me, so I simply forgot about its existence. I found it still bewildering and useless now.

• On AJAX translation pages, I see several untranslated messages with a certain word. I want to find out, how that word had been translated in the past.
  • I type it in the search box. I get "No matches for 'search term'" before I hit Enter.
  • I hit Enter: nothing happens
  • I click the button and after some waiting time, I see a looong list of messages in maaaany languages that I do not understand and that do not help me. The messages originally on screen are often not among them, or they might be buried somewhere at position 23415 which I did not check for too long lists.
• There are two more lists: few languages, some message groups, both with figures that I interpret as hit counters.
  • If I click a language, its list entry doubles and get a hit list, usually with considerably fewer entries than shown with the language, very often none.
  • When I click a message group, its name is bolded, and the same happens: I get a list of different length, usually less than announced, often empty.
  • When I want to see the translation of a message to my target language, I have to open it, get a restricted non-movabe non-resizeable miniature window filled with data in a superlarge font, have to scroll to my target language inside one of its sections which sometimes requires to scroll the browser window so as to make this part visible at all, select my target language from the list, if it is there, and remember that I must not accidentally hit the "save translation" button. This only works, because I have set my target language as a support language in my preferences. Usually, one deos not do that and thus cannot get to the translations to ones own languages from the search result list. But that was my initial target of interest, remember?

I stop here.

Suggestions:

1. have a "search for" box
   • possibly have a "case sensitive" checkbox
   • have a search type selection "match all words", "match any word", "string match, "regular expression match", "search in message keys"
2. have a "restrict search to message group(s)" multiselect list (with a choice "all")
3. have a "restrict search to language(s)" multiselect list (with choices: "any" and "support languages")
4. have a "show translations to language(s)" multiselect list (with choices: "any" and "support languages")

"search in message keys" needs to find int: references as well, word searches must not do so.

I think what the above should do is pretty self-explanatory. I would not mind having two or three search steps

1. select search topic and type + submit
2. select restrictioins depending on what was found by an unrestricted search + submit, and
3. possibly an extra step to select wanted translations depending on what was found before.

Thank you for your feedback. Your feedback has helped me make better proposal for search translations. Your valuable feedback is always welcome. :)

Hello,

You changed an instance of "What say you?" to "What do you say?" in one of my posts. "What say you?" is how I normally say it and is a perfectly fine way of saying it; if I wanted to say it differently, I would have said "What do you think?" and not "What do you say?".

I appreciate your looking out for others, but please don't do stuff like that unless you're absolutely sure you know what you're changing is wrong.

I am sorry,

I certainly did not mean to interfere with your style. What I read, when I read it, was a common typing error (in my perception) and I "corrected" it despite the fact that I usually to not "correct" personal statements of others.

Of course "What say you?" can be said in some English speaking communities. As an utterance or a direct quotation of one, it had triggered my inner automatism saying: "you must not write that" but I likely had not altered it. Please accept my apology. I learned writing English in a conservative British dominated environment when I was young. I am over 60 now. Teachers told us that we MUST write questions using "to do" always, absolutely no matter how they are uttered. We learned that, even in a word protocol of a speech, we have to write utterances like "What say you?" as "What do you say?", and we were allowed to loudly re-read it as "What say you?" if we knew positively from listening that it had been said so. As a language scientist, that I became meanwhile, I am far from supporting what we were taught, but it occasionaly bleeds through. Sorry again.

CLOSED This issue is closed by Nemo_bis

Hello! You have multiple question on Support. Could you think of grouping them together under a single title?

Actually, grouping is discouraged.

CLOSED This issue is closed by Purodha

Hi. For me and Ата your userpage looks like that. Could you fix it, please? I'd love to do it myself but it's code is too complicated so it would better if you fix it yourself. Thank you in advance.

I cannot fix ist. See bug 58875.

Hi, I have had to change your translation of MediaWiki:Zeroconfig-opt_bool/ksh because I have just removed the YES and NO messages from the main zero project. I am not sure why you used them though - that message indicates that the user can only have two values - either "true" or "false" -- the values themselves must be in english, as they are like computer code. Thanks!!!

Hello so thanks I did those steps in
https://translatewiki.net/wiki/Translatewiki.net_languages#Enabling_a_new_language_for_localisation_at_translatewiki.net
and this is lrc portal https://translatewiki.net/wiki/Portal:Lrc
and this is my basic request!! how can I translate a message in luri lrc?
and how can I add luri lrc in supported language in translatewiki same as english, arabic, germany and so on!!!!
please help me I need your urgent help so thanks for your help

Hi Purodha , the translatewiki.net development team is about to roll out some major design improvements to the translator interface and also adding new features to help improve the productivity of translators. Since you are an expert translator, I would like to request you to help us test these new features and give us your feedback on them.

If you are interested, please take a minute to fill in this usability test participation form. Once you have filled the form, we'll contact you to perform a short testing session (less than 30 min. in total) during this or next week. Also feel free to share this with other translators who would be interested to participate.

Thanks

Could you run the script for supported languages again when you have a minute? I think this was last done in September 2011. The original thread is here.

Please ignore the request. The script was run by Nemo today.

I ran the script seveeral times since last Septemper. Usually, there was nothing new to report. I had it on my schedule for last week, but since I was mostly travelling these days, postponed that until the 2nd part of next week. Thanks for letting me know that it's been done already, that saves me valuable time. Anyways, I'll keep running it every three to four months.

OK. Thanks for running the script. I won't ask for this again then, since no report means "nothing to report"!