Hi Purodha. Welcome to Betawiki! Please create a user page on which you describe which language(s) you will be working on. If you are going to be an active user here, please also add your name to the languages you will be working on. Before you can use Special:Translate, and Special:Magic, please request translator rights. If you have a wiki where a lot of translations have already been made, you can make an import request. Other useful pages are linked in the translatewiki.net menu that comes with this message.
Once you have started translating, your work will be committed to the standard product every few days. If you want to explicitely request your work to be added, please make a request for commit.
I wish you a productive and pleasant stay. Cheers! Siebrand 18:22, 28 April 2008 (UTC)
Hi. I reverted r35802 in r35805. New languages are added for localisation on Betawiki locally. As soon as about 50% of the most often used messages have been translated, the language can be added to MediaWiki if it actually is a language that qualifies (i.e. having an ISO 639 code). Cheers! Siebrand 16:59, 3 June 2008 (UTC)
Hi. With the release of MediaWiki 1.13 coming up, I would like to ask you if you can please translate/correct the most often used messages for ksh as soon as possible. Thanks! Siebrand 20:14, 14 July 2008 (UTC)
The problem with these 33 is that, for the most I do not at once know to translate them, since I do not know about their context. How do I - generally - find a page that shows them? I'll try to look more closely as soon as I have some spare time to do it. --Purodha Blissenbach 20:11, 15 July 2008 (UTC)
See message documentation. Most of the most often used messages should have translation hints. Siebrand 21:58, 15 July 2008 (UTC)
[modifier]Mark how messages are treated technically, i.e. determine their possible contents
As far as I recall, User:Gangleri had been collecting a whole lot of that stuff once, and it should be likely still available somewhere.
For Mediawiki messages, I know that there are ones, distinguished by:
html markup
that message may contain any html markup
the message may contain inline elements of the html markup permitted by the wiki
the message may contain block elements of the html markup permitted by the wiki
that message must not contain html markup (if they do, it is rendered verbatim)
html entities
that message may contain html entities which are rendered as usual
that message must not make use of html entities (if it does, they are rendered verbatim)
inline wiki code (e.g. ''' or [...])
inline wiki code is accepted
categories
categories are ignored
pages using the message are added to the categories present in the message
interwikilinks
interwikilinks are ignored
interwikilinks are rendered on pages using the message
inline wiki code is not permitted (and rendered verbatim, if present)
block wiki code (e.g. === ... === or * at a beginning of a line)
block wiki code is accepted
block wiki code is not permitted (and rendered verbatim, if present)
placement or use
this message will show up for a $-placeholder in another message
the message is used as a block element, or to fill one, in the website
the message is used as an inline element, or inside one, rendered as a piece of standard text, outside a link etc., in the website
the message is used as a wiki-link target in the website
the message is used as the ancor text of a link in the website
the message is used as value of a title= tag, or similar, in an html element in the website
the message is used as value of an accesskey= tag in an html element in the website
the message is used as <fieldset> label element, or inside one
the message is used as <title> element of an html page header, or inside one
the message is used inside an e-mail
the message is used in print
Special — the message has special content as described in (URL), e.g.
MediaWiki:Sidebar.
List of regular expressions (black- and whitelists) with # comments.
Maybe, there are more cases.
Can we collect (re-collect and update) this type of info and have them included in the list of hints accompanying each message? It would be more helpful to just have it once, than to try and re-try for each and every case of uncertainty. If so, where and how would the info be collected? Added to the /qqq hint data? I'd rather want to keep most of it separate, since almost all of it is non-textual data. --Purodha Blissenbach 22:20, 19 July 2008 (UTC)
The only way for it be be useful is to put it in /qqq. Feel free to add. You can do it as well as anyone else. Please use templates as little as possible, as the /qqq is also exported into gettext files, and using templates will make it harder to use. Siebrand 22:42, 19 July 2008 (UTC)
These technical propertery data are highly repetitive and schematic, so imho template use would be hardly avoidable. Of course, we can try to get away with a single template eating a list of parameters from a pretty narrow set, see above.
I am rather uncertain, whether or not such formalized stuff should be intermingled with human readable text like the /qqq data. Using a template for it will make it easily extractable by various technical means, so I would not mind using the /qqq for the time being.
Is the data available somewhere somehow that Gangleri once collected? --Purodha Blissenbach 11:23, 20 July 2008 (UTC)
The way Gangleri facilitated localisation was way too technical. That's not the level we want to have in here again. Siebrand 09:32, 21 July 2008 (UTC)
So as to avoid broken messages and pages rendering broken bits and pieces, we need checks on a technical level that e.g. detects when a message that will display undesired markup verbatim. So as to configure such checks, we need to collect message properties of such technical nature. Whether or not, and how we present them to translators, is an independent isse. I for one - likely since I understand the technical stuff - would be pleased to select it to be shown to me when translating. --Purodha Blissenbach 12:59, 8 August 2008 (UTC)
Hello, You found no Wikipedia article you could read. I think maybe you searched for a misspelled word, English Wikipedia has Wikipedia:Chromaticity. (I write here since the discussion was archived from Support.) /Lejonel 07:18, 18 August 2008 (UTC)
ich glaube, du hast dich beim Bearbeiten der Spezialseiten-Aliase in der Sprache vertan. Deine Bearbeitung für Deutsch habe ich rückgängig gemacht. Schönen Abend noch. Raymond 19:27, 5 October 2008 (UTC)
Oops! Und ich hatte mich schon gewundert, warum da alles mögliche auf Deutsch "reset" war. Danke für Deine Aufmerksamkeit. Ich bin darauf hineingefallen, daß sich das Wiki rigoros die Sprache merkt, an der man zuletzt etwas bearbeitet hat. :-( --Purodha Blissenbach 09:55, 6 October 2008 (UTC)
Are you still having issues with this gadget? I tried to fix it, but I cannot test. – Nike 13:45, 25 December 2008 (UTC)
It looks pretty now. I cannot tell for sure at the moment wether the cause is your fix /which I believe though), or my recently updated browser version. When I am back home from my xmass visit to relatives tomorrow night, I'll try the old browser version. If it does not work, I'll report again, if I don't all is fine. Thank you!
You have a few comments to recent commits. See mw:Special:Code/MediaWiki/author/purodha. Please consider testing changes. The quality of your commits, and your understanding of what happens making changes will improve :) Siebrand 00:15, 31 December 2008 (UTC)
Unluckiliy, I do not have a test server at the moment, I must wait for some maintenance work done in its hosting premises. It's a bit stange to me that, there are so many variations of code that output messages, and the de-facto treatment of messages cannot be seen or determined from the messages themselves. I'll follow up once I can test again. Thank you for informing me.
[modifier]Requesting payment details for collecting your Betawiki bounty
Dear Purodha. You recently indicated that you would like to have your cut from the Betawiki end of year translation transferred to you. You have been send an e-mail today requesting details. In case you may not have received this e-mail, details are available. In case you have any unpaid bounties from the language project, these will be transferred to you too. Cheers! Siebrand 13:17, 18 January 2009 (UTC)
No details were received, and no change was made to the beneficiary. We have chosen to appoint Stichting Open Progress as beneficiary and repurpose your cut. Siebrand 22:58, 8 March 2009 (UTC)
Please try to archive as much as possible in one edit. Every edit the whole page is being saved, and when Support is large, archiving one topic at a time increases database size unnecessarily. Siebrand 08:37, 18 February 2009 (UTC)
Should we work together to solve this bug? – Nike 08:00, 7 April 2009 (UTC)
I'd love to. Only at the moment I'm not clear about what the outcome should be. Brions comment doesn't make it clearer to me.
Actually, I would like to have all special pages of all Wikipedias inter-language-linked (with parameter passing where applicable) for quickly checking things at various wikis. Exceptions are the Special:Random* pages, of course.
With the new parser, most, or all, of the previously working interwiki links, which I had put into messages of the pages, stopped working. They were, in my opinion, not a really good idea anyways, because:
We had to locally alter internationalized messages being used in special pages, adding an "interwiki to all Wikipedias|target-special-page" template, and thus lost the feed of message-updates coming to us. (Few were localized anyways, but an increasing number was not).
They were not able to pass URL parameters of the Special page via the interwiki link, both because:
they are not available as parameter(s) to a template being called in a message in a special page
interwiki links in most instances do not support them either (except the one-parameter case of [[lang:Special:page/singleparameter]] (Which I did not test with the new parser, btw.)
Some Special pages did not render interwikilinks, no matter wether or not they were in messages.
Should we reallow interwikilink rendering in all Special pages, or should we rather inhibit it everywhere, and if so persue a more programmatic solution, which allows e.g. switching interwiki links to all existing language versions of a wiki family on via a setting in Localsettings.php for all special pages? But then, how to sort them in the individual order of each wiki? Put it in Localsettings.php as well? Should we add an always empty message, ignored on translations, to each Special page, such as spacial-page-name-interwiki, which it to be localized so as to add interwiki links when wanted? In this case, it would be nice to reopen and fix the bug that asks to extend Extension:SiteMatrix by parser functions that make data in the site matrix available. --Purodha Blissenbach 11:14, 7 April 2009 (UTC)
Huh? Are you saying that all interwiki links at special pages stopped working after the new parser? – Nike 12:00, 7 April 2009 (UTC)
For your information. Plurals works ok with $wgOut->addWikiMsg, which is the recommended way. I can fix SpecialPageTranslation to not cause more conflicts. – Nike 20:42, 14 May 2009 (UTC)
Ok, I'll not touch it.
Interestingly, some time ago, someone (if I remember that right) told me, that I would have to use wfMsgExt() in such cases, see mwr:45122, e.g. --Purodha Blissenbach 21:22, 14 May 2009 (UTC)
The link doesn't show the full diff, but wfMsgExt needs to be used where $wgOut->addWikiMsg is not possible.– Nike 21:49, 14 May 2009 (UTC)
Die dort gemachten Änderungen an Systemnachrichten wurden nicht vom FuzzyBot importiert. Sollest du nachholen, da die Änderungen ja auch von dir sind. Vielen Dank. Der Umherirrende 14:00, 14 June 2009 (UTC)
Großartige Frage: Wie mache ich das denn? --Purodha Blissenbach 14:03, 14 June 2009 (UTC)
Ich würde sagen, die Seite einfach mit dem Inhalt anlegen. Das sollte keine Probleme darstellen, da damit ja der Seiteninhalt mit der Software übereinstimmt (was anderes macht der FuzzyBot ja auch nicht). Das würde ja reichen. Dadurch werden andere Benutzer später nicht als Ersteller der Nachricht erfasst, obwohl sie nur etwas ändern wollten und ein Versionsvergleich ist möglich. Der Umherirrende 14:10, 14 June 2009 (UTC)
Das hat so funktioniert. Beim Anlegen hat wurde mir sogar der Inhalt der gänderten Textnachrichten angezeit, so daß ich sie nur noch abzuspeichern brauchte. Danke für den Hinweis. Kommt das öfter vor, d.h. muß ich alle meine Änderungen an message files kontrollieren? --Purodha Blissenbach 14:15, 14 June 2009 (UTC)
Keine Ahnung, ob das kontrolliert werden muss. Ich weiß nicht, ob der FuzzyBot manuell angestoßen werden muss, von dem der die letzten SVN-Versionen synchronisiert (irgendeiner vom Staff) oder ob das automatisch funktioniert.
Ich habe deine Diskussionsseite auf der Beobachtungsliste, sodass ich deine Antwort hier mitbekomme. Eine Info bei mir ist nicht nötig. --Der Umherirrende 14:23, 14 June 2009 (UTC)
Purodha, warum hast du hier unter "qqq" den Text in Kölsch eingetragen? Der Text sollte in Englisch sein. --Michawiki 11:21, 15 June 2009 (UTC)
Vermutlich weil ich blöd war, oder müde? und automatisch weiter geschrieben habe, wie zuvor. Ich hab's übersetzt. Danke! --Purodha Blissenbach 12:15, 15 June 2009 (UTC)
[modifier]Use of code in OpenLayers message translation
Hi, Just wondered what your reason for adding code tags to OpenLayers tags was, currently exporting the OpenLayers messages and it would be helpful to know this. Thanks. RobertL 21:30, 25 June 2009 (UTC)
There are few intranslatable parts in these messages. These have to be marked as having a foreign language. (Also see this internationalisation hint). There are basically two ways, how this is customarily done with our language:
italics are used for textual elements in a foreign language inside sentences,
code is used for non-textual pieces, such as parameter names and values, when appearing verbatim, etc.
The same scheme is used with all MW messages and with all MW extensions alike. Although (X)HTML defines several more kinds of markup for these purposes, such as VAR, ARG, ABBREV, etc., these are not used for the sake of simplicity, and uniformity.
If you find errors or omissions, or things that deserve to be translated, please let me know. I had to make guesses here and there. --Purodha Blissenbach 11:06, 26 June 2009 (UTC)
Hallo Purodha! Das kommt davon wenn man nicht vorhersehen kann, wie ein Nachricht funktioniert ;-) Danke und Gruss, Als-Holder 16:09, 14 July 2009 (UTC)
Ich wette, ich hab bestimmt ein Hundert solche Fehler gemacht.
Und ich bin so froh darüber, daß ich jetzt bis zu 25 andere Übersetzungen sehe, wenn sie schon da sind, wenn ich meine mache. Da finde ich Unklarheiten überall leichter, selbst wenn ich nicht immer alle Feinheiten verstehe, und sehr viel Hilfe für gutes und richtiges Übersetzen. --Purodha Blissenbach 16:14, 14 July 2009 (UTC)
Hi. The newsletter bounced: 550 <publi@web.de> Benutzer hat zuviele Mails auf dem Server. / User has too many messages on the server.Siebrand 14:13, 9 August 2009 (UTC)
Приглашаю вас принять участие в развитии сайта Викиреальность — http://wikireality.ru. Сайт создан группой добровольцев для развития всего, связанного с викисредой. В статьях соблюдаются принципы нейтральности, отсутствия непроверенной информации. Каждый может принять участие в проекте — анонимно или представившись системе.
Проект работает на последней версии MediaWiki, установлены важные расширения. Уже написано более тысячи различных статей и собрано большое количество ценных архивных материалов. Приветствуется любой полезный вклад — можно зарегистрироваться, исправить какую-либо статью или написать новую. — Ferrer 19:30, 22 September 2009 (UTC)
Thanks for adding all that information to the CLDR page. I have made a few minor corrections to grammar and spelling. I have also deleted an abbreviation - afaics, on the assumption that I am not the only translator who won't have a clue what this means. I don't delete abbreviations on the discussion and talk pages, I sometimes just assume that if there is an abbreviation which is unfamiliar to me, then I won't understand the rest of the discussion either and just skip to the next discussion. But this is in an article which non-technically minded translators like myself are supposed to be able to understand, so I have deleted it. If you want to include the information contained in "afaics", whatever that may be, could you please have pity on us and write it in full?:)
We have explanations of many abbreviations at FAQ#Abbreviations, including afaics = as far as I can say. Nevertheless, I replaced it with "most likely" - I am just not 100% sure, but did not encounter any problem that I could track or relate to this item. Thank you for proofreading, anyways!
Thank you for replacing afaics with "most likely", which I understand straight away. I can't speak for anyone else, but at least I won't feel humiliated through not knowing what a jargon term means without having to look it up:)