I am localising the group 'Wiki Editor' into Konkani:
It seems that 71 out of the 186 messages require the editinterface right. How can I enter these translations? Could I request for the editinterface right, at least on a temporary basis, or is there someplace where I save the translations to be entered by someone else?
For example, if I try to save this message:
There are around 70 messages in the 'Wiki Editor' group that require this permission. How can I enter these translations? Could I request for the 'interface-admin' permission, at least on a temporary basis, or is there some place where I save the translations to be entered by someone else?
Verdy p insists to put narrow non-break spaces (U+202F) everywhere instead of normal non-breaking spaces (U+00A0) before or after punctuation symbols in French translations. Narrow non-break spaces are not compatible with all browsers, notably Safari on macOS and iOS, which is a big part of the readership on Wikipedia and elsewhere. Instead of a space, there's no space at all.
In French typography, both are correct but the normal non-breaking spaces have the advantage of being compatible everywhere and being coherent with the choice made by MediaWiki, the French Wikipedia community and the other French-speaking projects.
He also use translations that are rarely used .
Can we do something?
Hello, I support the fact that we need to be accessible for all and Verdy_p doesn't help with that. He don’t want to understand this point.
Not compatible ??? They are standard since so many years. I've never seen any browser not supporting it since extremely long. May be your iPhone is very old. But your claim that iOS is a very large is false. It is a small minority (and even much smaller if you consider very old versions of iPhones with outdated fonts).
NBSP are incorrect in standard French, they were used 20 years ago but NNBSP was adopted after many requests from French publishers. They are even required for Mongolian (OK this is a minor language) and other Asian scripts where they are even DISTINCT from NBSP.
May be they are not used in wikitext of articles, because this is simpler, but they are used since very long in translate wiki for the UI.
Your claim of "incomplatiblity" is not justified by any proof. NNBSP is in Unicode since version 3.0. They are also standard in French translations for CLDR.
The source code of ICU for iOS perfectly handles NNBSP:
Lot of iOS/MacOS programmers are told about what to do: NNBSP support *is* highly recommanded and its support is integrated in many libraries
- ADE 2.0+ (more precisely RMDSK 9.2 and beyond) display correctly the nnbsp whatever may be the font. This applies to a lot of ebook-readers like Kobo. InDesign does the same.
No need of any font mapping for whitespaces. The Unicode properties are honored by compliant renderers (indepenantly of the supprot for the Mongolian script which is still problematic and still in discussion in 2019, these talks do not apply to the encoding of any other script)
Unicode states already (and agrees) that:
- NNBSP is non-breaking
- it has a fixed width in all contexts
- it is not expandable during justification (NBSP is expanded and is NOT usable as a group separator or punctuation separator).
- it MUST be narrower than a regular space or digit (FIGURE SPACE is like NNBSP but not suitable as a group separator, only as a digit replacement in tabular data when no zero should be visible). For monospaced environments, rendering it as a full space (like the FIGURE SPACE) is NOT acceptable.
- it should behave like the FULL STOP or COMMA in the middle of numbers or in sequences of punctuation signs.
- it is a significant character (not a format control like the Mongolian MVS, or ZWNBSP, or ZWSP, or WORD SEPARATOR).
- it is not necessarily ignorable in all locales for collations (e.g. when it is used to differentiate numeric codes)
Unicode really instructs auhtors to NEVER use NBPS for group separators in numbers, but use NNBSP instead. Since the origin, NNBPS was introduced to be script-agnostic (the claims made by some that NNBSP was only for Mongolian was wrong, this created a temporary bug in Apple's code, reclassifgying it incorrectly as neing for Mongolian, Apple fixed that very fast as it was their error). Initially NNBSP was flawless, even in iOS ! all other apps (including Discord on iOS) have fixed that (or they provide a workaround in their app-builtin renderer for the few remaining iOS phone versions affected by this bug committed incorrectly by a Apple programmer). These smae vertsion of iOS (only with their builtin bogous Safari browser and no other browser installed) are not even accessible (so the claim of "'accessibility" being broken only by NNBSP is false; these versions of iOS are not accessible at all for MANY other reasons). All this does not concern MacOSX and all newer products that have fixed this bug (and now support Mongolian much better).
The affected software versions are NO longer maintained by Apple, and this was a propriary bug on a very small set of specific implementations that is out of market since long. and Apple has made many tricks in iOS so that even these models are no logner usable with all the needed security and accessiblity features that are needed today. These old versions were even incompatible with Mongolian (and never supported that script correctly, allowing only very bogous and ugly rendering of Mongolain only in its horizontal form, but incorrectly rotating some glyphs and not rendering the basic required conjuncts correctly).
You also made a false claim that Discord is only for iPhones. I use Discord (on Windows, sometimes Linux, also on Android) but I've never used any iPhone. All modern browsers support ALL spaces (without even needing any font mapping, as they can be synthetized, given they have no glyph, and just suggested metrics that can be computed, and standard breaking properties). NO browser must display any "tofu" for characters that have a Whitespace property. This is effective since long.Unicode provides the fallback mechanism and explicitly says that the default fallback must be either nothing/zero-width (for languages like English or Mongolian, or in every monospaced rendering, including Chinese, Japanese, Korean) or NBSP (for French for example) if the browser cannot synthetize the metrics for proportional rendering.
Note that even if NNBSP was initially introduced for Mongolian, it was later replaced in the Mongolian script by MVS (Mongolian vowel suffix separator). It was not deprecated at all for other languages (FVS1, MVS, ZWJ are now recommended for Mongolian, which is a vertically written script, whereas NNBSP, ZWNJ, FVS3, FVS2 are deprecated only in Mongolian; the NNBSP remains the non-breaking equivalent of THINSP for all other scripts)
Thin space is not visible on my ipad (iOS, Safari), so I reverted your edit. Thin spaces are cool (we often use them in press and printing), but as long they don't work on all common OS/web browsers, don't use them.
tl;dr as well.
"May be your iPhone is very old."
Nope it's not.
"Your claim of "incomplatiblity" is not justified by any proof."
Here's a screenshot from Safari and another screenshots from Firefox, Chrome and Opera. All browsers on iOS must use the same web rendering engine as Safari anyway to be accepted in the App Store.
"You also made a false claim that Discord is only for iPhones."
I didn't say that, I said that Discord is often used on mobile and translations should be fully compatible on all current mobile operating systems, including iOS (all translations on this website should be). Btw I'm using Discord on my Windows PC right now.
FYI, I just tested on Safari 12.1 on macOS 10.14.4 (Mojave) and the thin space is invisible as well (screenshot).
Edit: Like Jules78120 said above, thin spaces are good for books and publishing but a bit overkill for interface messages and strings of text sent by a bot.
There is 2 problems here:
- the typography, thin space is in theory the good solution but it doesn't work
- the attitude of Verdy_p, unable of efficient and sane discussion
The first is technical, we can look at the facts and act accordingly.
For the second, I have no idea and I'm sorry but I prefer to let someone else do something about it.
Not compatible ? Only uninformed users. See:
Many places in Apple forums and documentation tell that NNBSP *is* supported and even strongly recommended (and no need to embed any font in your ePUB; as well there are other ePUB readers, and were's not even translating here any interfzace of old proprietary ePUB reader for Apple OSes). Apple has fixed its readers and published the details for authors.
So this is a problem of 'lazy' users refusing to read the recommendations that are largely adopted everywhere else (and remember that users of these old Apple devices are a very small community, ready to pay to lot to Apple, but refusing to upgrade their device, OSes or use a better software than the builtin default?) Accessibility is not a concern. All standards agree that NNBSP is and must be supported and the initial bug of Apple has been acknowledged by Apple, and tyhe work around has been made in all serious apps (including in Discord for iOS).
And if you feel offended by the term "lazy", this is a fact: I give many justifications and there are tons of links on the web and support not just from me. But if you don't want to read them, you don't need to talk here and just say "TLDR" (which is NOT a valid argument).
Ad hominem attacks are not arguments either.
"So this is a problem of [...] users refusing to read the recommendations that are largely adopted everywhere else"
That's the pot calling the kettle black, you refused to acknowledge that the Imprimerie nationale and the Office québécois de la langue française, two authorities when it comes to French typography, don't recommend thin spaces between French quotes.
And here this is about ":" and about a user not seeing the space which is present and visible in its own screenshot. And this is for the UI on specific smartphones or small tablets. No user will have to input this, as it is only displayed and convenient for them. And you have a very strange interpretation of "ad hominem". I gave many sources, and all standard bodies and even Apple have approved it, reaffirming that NNBSP was for this purpose (decommitting it only for the Mongolian script for which it was initially unified in the first encoding in Unicode 3.0). Unicode, CLDR, Apple, Microsoft all recognize that this is strongly supported (and was demanded by many publishers, including in France; do you remember that I have worked for many years for ALL publishers in France (for national and regional newspapers, magazines, books, guides, diaries... as well as professional/specialized press, and public papers) and also in Belgium, Luxembourg, Switerland, Italy, Spain, Canada, North Africa, Lebanon, and the Middle East: they all demanded that support in the composition softwares we were selling them. At that time, HTML was not used (it was insufficient and the NNBSP was not even existing in Unicode, but the character already existed in SGML and in their databases of encoded texts (they were represented using defined character entities). That "fine insécable" was (and has remained) required as the group separators in numbers and along with all punctuations needing extra spacing attached to them. Using NBSP was unacceptable, and in Unicode the NBSP is expansible like regular spaces, making it unsuitable (and totally incompatible even as group separators and in all financial applications as it would become confusable with figure spaces (which are also unexpansible) The two authorities you speak about made old recommandations for HTML but this was before Unicode 3.0. They were both asking for a proper support of NNBSP since years to the W3C and to ISO and Unicode. This was affirmed by them in the ISO standards and working groups for SGML (which was then their reference framework; their adoption of HTML came much later and now Imprimerie Nationale also uses HTML publications with NNBSP: the old recommendation for old versions of HTML3/4 and based on legacy 8-bit charsets is no longer applicable).
Your screenshot is using a font whose glyph for ":" is already enlarged, and Unicode also sayss that in such case it is perfectly acceptable for NNBSP to become invisible.
This is a same rationale with the ideographic rendering with fullwidth punctuation: they dont need extra spacing at all.
NNBSP is in the Times font recommanded for ePUB (and supported as one of the 7 default fonts for the Apple's iBok reader not needing any font embedding). It is used by default in serious publications.
If you use the default font for the web which uses enlarged characters for accessibility (or you tune Windows web browsers with Verdana instead of the default Arial or Segoe UI), NNBSP can legally be mapped or tuned by the browser to become invisible (this is legit, it remains fixed-width, non expandable by justification, and non-breaking as expected). NBSP breaks the text and is too large (it can be a valid fallback only for FIGURE SPACE, as long as it is not expanded in justification like regular SPACE).
NBSP does not have the needed properties. All standards agree : CLDR, IBM, Apple, Unicode, Mozilla, Microsoft, LibreOffice, Monotype, French typographic sources and publishers (including commercial ones, like Hachette, or public ones like the JORF), and even US publishers for English: they all use NNBSP for French punctuations and group separators.
NBSP was a temprary workaround used at the early stage of Unicode before version 3.0. When Unicode 3.0 was published, it was correctly supported as well by Apple, until they started creatging havoc and proposed a way to fix it. Renbdering NNBP as an invisible space is valid with the default proportional "sans-serif" fonts of MacOS/iOS whose glyph metrics already embed larger gaps between glyphs. Helvetica (licenced by Apple from Adobe) embeds the NNBSP character, but that old font is not recommended at all for reading the web on a screen (even with HiDPI screens) as it is not accessible and was only tuned for monochromatic laser printing at 150-300 dpi. Helvetica is deprecated but remains a default for old MacOS devices (not MacOSX that have better fonts with more accessible metrics).
Maybe your technical explanations are true (but not sure: my iPad, "given" by my employer, is not old and is up-to-date…), but what I can say is that on my iOS device, on Safari, the thin space is not displayed. Please stop arguing about the theory and take into consideration the reality…
And please stop to impose your thin space, as there is no consensus for it and while thin spaces are not displayed on iOS devices.
Why do you want to force a visible space here ? When your device uses a font with builtin enlarged punctuations ? With such a font with ugly punctuations like ":", NNBSP being rendered invisible is NOT a problem. This is legit. But NBSP is definitely bad (even worse with your font, it would be definitely too large). You msut know that NNBSP is used in so many places. Apple has made statements about how to cope with that. If you use the default builting sans-serif fonts even in browsers, haing it invisible is correct; if you render the page with a serif font, the default builtin font "Times" correctly renders that NNBSP. In both cases, it is supported.
If you use other fonts than these defaults, you will see the difference if you insist,, but such use is only for page design or when writing text, and even in the Wikitext editor you can see it with the monospaced font. But for the UI rendering it's still best to have it rendered as zero-width near punctuations (not at all an accessibility problem for this font). In fact it better fits the limited screen size on lowend iPhones.
And on the web, nothing forbids you to change the fonts (there are preferences for that in Apple's web browser). Did you read the links above ? Apps and other browsers can still work around this when they need, even if fonts don't map this character and EVEN if they are forced by Apple to use the Safari's internal rendering engine.
You don't care, but you're part of a very small minority and the large majority want to use the standards and official recommendations (that don't even break your device and makes the content inacessible to you if you don't want to change the device settings).
About the thing of uncommon translations, it is completely besides the point of this thread but you people should avoid just indiscriminately adopting English terms when you could use plainer terms, and in this case, “en source ouverte” is a direct, easy-to-understand equivalent of “open source”, understandable for people beyond geeks. Other Romance languages translate the term as well: de código abierto (es), de código aberto (pt), de codi obert (ca), de códigu abiertu (ast), cu sursă deschisă (ro)… Anglicisms can be necessary and I don’t censor them, but in this case it is gratuitous and avoidable.
C'est aussi mon point de vue. Je ne vois pas l'intérêt de l'anglicisme ici, nombre de geeks se foutent pas mal de leur langue tant qu'il parlent leur jargon technique et ne cherchent justement pas à impliquer les autres et se fichent pas mal de rendre leurs projets accessibles et compréhensibles par plus de monde.
Rien n'empêche de toute façon ensuite aux techniciens bilingues et les mieux formés d'utiliser le terme anglophone quand ils vont sur des espaces anglophones, mais puisqu'ils sont mieux formés je ne voit pas ce qu'il leur en coûte d'utiliser une terminologie française correcte dans une traduction française qui justement ne leur est pas destinée directement, mais qu'ils comprennent très bien.
Il n'y a rien de plus rebutant pour un novice de se confronter à autant d'anglicismes non nécessaires dans les projets collaboratifs supposés justement "ouverts", mais qui se replient justement à des petites communautés installées de techniciens qui se croient irremplaçables et indispensables et les seuls à "savoir" (alors qu'ils méprisent autant le savoir de langue humaine, au seul profit du jargon informatique où ils sont les "dieux"). Nos projets devraient être ouverts aux novices, et c'est encore plus important pour ici un terme qui veut dire ouvert à tout le monde, et dans un contexte aussi promoteur de l'éducation que le veut clairement Wikimedia. "Tout le monde" ne veut surtout pas dire "Tout le monde anglophone" (sachant aussi que le jargon informatique déforme et abuse aussi beaucoup la langue anglaise avec trop de raccourcis, et encore plus d'expressions ambiguës qui ensuite viennent "plomber" même le code écrit).
Faire comprendre un terme technique permet aussi d'éviter les mauvaises interprétations et les mauvais usages, même si ensuite l'association vers un terme anglophone correspondant est vite apprise. Tout est une question de respect et d'ouverture aux autres.
In general, MediaWiki tries to follow Unicode. We could debate forever on what to do with devices which have poor support for i18n. This is a matter of style, not semantics, so we ought to be consistent (ideally) but at the same there is no urgency justifying a mass edit war.
I use DjVu Serif and an edit like special:diff/9131394 adds a space for me before the colon, where previously there was none. It's clear that the translations did not follow a consistent rule.
I urge the French translators to have a discussion on portal talk:fr (in French is better), involving all those who used or did not use the various kinds of spaces in the past. It's important to find a consensus on 1) what space would be preferrable in an ideal world, 2) what space is recommended right now (this should be written on portal:fr so future translators can learn about it), 3) whether it's ok to perform mass changes to impose the recommended style.
I suspect the solution will come from software, just like we have a special exception in the MediaWiki parser to deal with French spaces. After you have a consensus on what an ideal world would look like, please post a feature request in MediaWiki-Internationalisation, so the devs can see whether spaces can be added/standardised on the display side (some even use CSS for this purpose, I believe), possibly based on the device as well.
In Portal:ksw, the English name for the S'gaw Karen language is not shown, it only have the native name. Please add the English name like any other language portal.
Typo Wikimedia:Wikipedia-ios-diff-thanks-sent/en: "set" should be replaced with "sent".
I spotted an edit which cannot in any sense of the word be considered an translation. This edit is , which adds an Icelandic male name to an field named "Add language". This is grossly inappropriate and I am requesting that his "offline translator" rights are removed due to this. You really can't expect other translators to clean up an mess like this one.
Is this a regular occurence or just a one-off? In assuming good faith, I would believe it's just an honest mistake. I could see myself doing the same thing – thinking I'm copypasting in one thing, then not noticing I copied the wrong thing. It can happen.
It is the worst edit of several bad ones (of those I have found, anyway). It has also happened that I have fixed his translations and then he just re-adds the old translation, that either can´t be considered an translation or contains a word that does not exist in the language.
It would be better if the user had normal translator rights only. An translator can in theory use their offline translator rights so that they use an old translating file and update from that. The problem with that is that that user would end up ignoring other peoples edits while doing so. I suspect that he has uploaded the same offline translator file more than once, and ignored any improvements by others in the proccess. So, I belive he would be an better translator with normal Translator rights only, as it would show him the most recent improvements every time.
It does not help matters either that there is an lack of vandalism tools here. There is no AbuseFilter, TitleBlacklist and so on.
@Snævar: OK, fair enough. But have you tried talking to him to tell about the problem? I can't see anything in the user talk page, but maybe you have some other communication channels. In any case I'm hesitant to call it vandalism, it seems more a case of not being careful enough. If you want I could post something on his talk page, but it might be better if you do it since you know the specific issues much better than I do, obviously.
Not sure where to submit a username change request. So I request it here.
I want to change my username as "A-lú-mih". Thanks.
Hi, can you provide me list of message groups which have less than 10 messages?
just use the Translation tool (from the sidebar).
- Select your language.
- Uncheck the box restricting the list to hide fully translated groups.
- Press the button to get the list of message groups
- Then click on the "Expand all" link displayed
- Click on the column header to sort the expanded list by messages count.
For the translations created by FuzzyBot that are created already fuzzied, the translation interface should be submitting them for our review, because they're fuzzied, but does not.
For example, on 9 May 2019, FuzzyBot inserted the following two translations, with summary "Importing a new version from external source":
- Wikimedia:Wikipedia-library-0907f2-Which authorization method doe/pt
- Wikimedia:Wikipedia-library-fc7cbf-Which authorization method doe/pt
Let's look at the first link, for example:
If you start editing the message directly from this page, it is definitely fuzzied:
But the edit interface does not show it in the list of "Outdated" strings. It is none of the six presented here:
The message appears in the list of "All" strings, as translated and not flagged as requiring any action whatsoever:
Worse still, if you open the message itself here through the translation interface, the software does not even show you that it is fuzzied. The whole !!FUZZY!! thing is totally hidden:
So, just to confirm again, if you go to edit the message directly from the edit interface, as follows (greyed out menu item):
you can confirm that the message is effectively fuzzied:
So, it has been there since 9 May needing review, but not to my knowledge.
Thanks for the report. I'll file task and see if I can mitigate this.
I have run script that fixes this for existing imports. https://phabricator.wikimedia.org/T237412 tracks how to prevent future cases of this. https://translatewiki.net/w/i.php?title=Special:Translate&group=wikipedia-library&language=pt&filter=fuzzy&action=translate contains a lot of fuzzy messages now.
Message group stats was not updated by the script, but they will hopefully "repair" itself over time.
Is FreeCol stopped to update/translate? Because they updated on 2016. If they are really stopped for that, oof.
It's not stopped, they just haven't been able to put out a release yet. We'll consider this in https://phabricator.wikimedia.org/T228072
I’m in conflict with Verdy_p about these messages:
Verdy_p wants to turn
<. However, entities are escaped in these messages where they are included, so the messages are displayed as they are (with entity codes). You can see that on Special:PageMigration (you need to be a translation admin), trying to type anything in the field then submitting.
You give a proof with a specific page used only by admins. But there's no double encoding of ampersands in Mediawiki. Everywhere else the "<" have to be escaped to avoid incorrect matches as candidate tags. valid numeric entities and at leastr the few basic standard characters (which are not "named entities" in HTML, but part of its required syntax) are implicitly recognized (they do not require any DTD, their supprot is mandatory in all HTML and XMS parsers, and in MediaWiki itself): "lt", "gt" for tags, and quotation marks and required for attributes and ampersands for URLs; the support is extended to numeric entities since HTML4 and in all versions of XML and mandatory in HTML5. It is mandatory since ever in all versions of MediaWiki (initially however it had limited support for Unicode and allowed numeric entities mapped to 8-bit only codepoints before UTF-8 became mandatory, which occured when HTML was fixed to require Unicode-only mapping of numeric entities, forbidding mappings to legacy codepages, even if the pages themselves would still be encoded with legacy charsets, this no longer applied to numeric entities). You're living in the early non-standard age of HTML of the end of the 1980's when MediaWiki did not exist, Translatewiki.net did not exist and HTML was full of ioncompatible proprietary versions derived inconsistantly from the initial CERN invention.
I'm not really sure but I have found this ticket on Phabricator: https://phabricator.wikimedia.org/T227244
I don't see any other security-related ticket, tho. However, as far as I know, this extension will be used on WMF wikis do you can assume it's secure enough.
Also thanks for your reply,
I'd say that technically the extension is ready, but the user experience is in alpha stage, so the translation may be also alpha as long as it has not been tested; there will likely be more to translate and explain how this should work and what ot do in case of problems of configuration and why this new Auth method would be preferable or not to another (the Phabricator task explicitly questions about how to work with multiple libraries trying to do the same thing, how they can be unified using a replacable hook allowing to evaluate also the implementations in terms of effective security, performance, cost of maintenance, debugging in case of problems. Also the testbed is still not in place, and they wonder how they'll recruit testers with usable inputs (or if automated monotoring can generate better results). In terms of pure UX, the testbed will receive some comments, several proposals will be made, as well as A/B tests. How many testers will be needed will also condition how many languages will be needed for these tests (they probably don't want to support many languages for now, but have enough inputs for specific needs in some countries where other authentication methods (possibly using thrid party services) are not supported very well, or have no good support and fow which alternate less demanding methods may be needed, but also more training for their users.
Still in all countries, 2FA is not enough known and not generalized, many users complain about how the current methods are implemented, and they also fear about privacy risks this causes to them (notably in countries like China with very active user monitoring by authorities, or with extreme social/economical and criminal risks like Russia or Mexico, or legal risks like US, or countries where users have no other choice to conenct to Wikimedia than using foreign VPNs, or slow mobile connections, or shared Internet access, or whose emails are heavily monitored
As well there's a worldwide threat caused by malwares that attempt to steal people's identity, and 2FA will sonn be not enough, we'll need more factors in a very near future. But how we'll configure all these to work correctly together may become really complex for many people, that will finally opt to protect their privacy by delegating everything to a commercial service provider like Apple, Google, Facebook or Amazon, and tie all their existence to a permanent dependency to these big players, creating lifetime monopoles and splitting the world in distinct proprietary universes.
I'll consider this. It's not on top of the TODO list so it can take a while.
$1 on both, the old and the new username. Shouldn't it use $1 for the first and $2 for the new one?
$2 is the proposed new name, it still does not exist under this name so it cannot be queried for gender. Both names refer to the same user currently named $1, who has the gender settings (these user settings will be applied later to the new name once it is applied; then $1 will no longer have its own settings, it may be deleted/hidden, or kept as a public redirect (possibly protected against deletion or modification of its user pages and talk pages). So this is the same gender of $1 which would apply to both names.
Note that the gender may be needed only in a few language for grammatical forms. If a translation does not need it, the GENDER marker must still be present but may containt empty text (in the English text, the text is the visible user name, not the gender itself, and there's no alternate gender variant of that name and no need to add any other personal gender particle which may be required in addition to the specific user names (I think these gender particles are needed only in some native African languages; in some Slavic languages, there are sometimes variations of user names depending on case on specific constructs, which are also dependant on gender).
during the last few dates I noticed that on the page Special:ContributionScores for my User for Last 7 days (Top 50) the number of contributions is marked as following:
Rank Score Pages Changes Username
49 9 9 9 Robby
while on  you may see that I made at least 50 edits on 31 August till 2nd September.
So there seems to be something broken on this.
49 or 50 edits, this is not a huge difference, and the statistics are not counted immediately; your last few edits were probably made after the statistic batch was run (so it counted only 49). Look at the statistics after 24 hours, you should see evolve it (but the count may still be off by the edits you made in the last few hours after the batch ran). Verdy p (talk) 23:35, 1 September 2019 (UTC)
I've the same problem since the last days of August. I'm on 27th overall ranking but my changes are stopped on 38201 (and the scores is stopped too). May be there's a bug?
You are mistakken 49 is the rank not the number of changes or pages these were 9 and there is quite some difference between 9 and over 50.
OK, but your actual statistics is not 50 but over 70,000. Still my comment remains valid: the statistics are not computed all the time continuously but with batches running periodically, so it's normal that it can ignore your most recent edits over the last shortest period. As well, the results depend on the activity of the job queue (which is very active on this wiki even if there's few edits, as the longest jobs are those created for SemanticWiki, some of them running for hours may lock temporarily not just some pages but also the updates of related statistics (which will be deferred). These statistics are not intended to be actualized in real time, they are just estimates. Computing them has a huge cost on the server, so they cannot be refreshed instantly, even if this is based on a live SQL request (which is already costly and quite long to reply for this page, because it has to lookup all existing users to sort them and then extract about 50 of them in each "top list"; the statistics however are quite accurate for least frequent users, but must frequent users are only roughly sorted, especially for the shortest period of 7 days). Note also that the computed statistics do not show the actual period of dates on which they were computed: the period may be off by more time than what you expect, and the "last 7 days" may be 7 days before the last run of statistics offline jobs which may have occured up to 7 days ago (possibly more of the database had long job lists, with some jobs taking several days to complete and deferring other pending Statistics jobs to run that, most probably, have lower priority than Semantic jobs and regular jobs built in MediaWiki).
This statistics page is not certainly the one to consult if you want to get your own personal edit statistics, that you can get using the live Mediawiki API:
For example: https://translatewiki.net/w/api.php?action=query&list=users&usprop=editcount&ususers=Robby
The same for Joe Taras: https://translatewiki.net/w/api.php?action=query&list=users&usprop=editcount&ususers=Joetaras (note: you must use the actual username, like in your user page, not the displayed username in your signature, and URL-encode it if needed in the URL) This gives a total on all periods. Computing this over a period is much more complex as it requires scanning your history, so this cannot be done directly with the live API. Doing that on all existing users (just to get the Top 50 lists) is even more complicate and costly.
Ok for me. Usually I've checked my stats and I've seen updated. Maybe there's a lot of traffic. No problem. Thank you for your reply
Dear, I must return on this issue. I've understood the performance is important but, if we can't see the updated information about edit count and other, please remove some functionality from Translatewiki, as follow:
The page SupportedLanguages is unuseful because if I check information about an user the information are not update, as the following image:
The page Contribution scores is unuseful because is not update, as the following image:
And these widgets
I'll wait for your response.
Have a nice day
Hi, I have one question. When I created my account here on translatewiki.net, I was asked what languages I know. So I chose English, Slovak and Czech. I translate English messages to Slovak through the Translate window and sometimes I just look for Czech messages that appear on Slovak wikiprojects since Czech is a fallback language for Slovak and because we don't have many contributors in Slovak at the moment, there are many Czech messages appearing on Slovak wikiprojects. I want to first translate all of them to Slovak and then look at the others. However, I can only see English messages and translate them to Slovak (with the help of Czech). Can I somehow see only all to-Czech translated messages which don't have Slovak translation?
Special:SearchTranslations should help, but why not focus on untranslated messages regardless of the status in other languages?
Special:SearchTranslations works only when you know the text of the translation but I need the very same interface as when I translate random messages from English to (language I choose). What would happen if I didn't choose English in the beginning? Then it wouldn't be able to show me English translations as the source. I want to achieve something like that, the source would be Czech. I thought I can change/add languages I know also after the registration but I haven't found anything in preferences...
Why translate Czech translations at first? Because I firstly care about what translations are (mostly) seen, then about the others which might not be seen that often. (As I said, Czech is a fallback language for Slovak and I first want to make sure that Slovak texts (not the Czech ones) are appearing on Slovak projects.)
Right, I had forgotten that we didn't finish the part of the work which involved adding a different source language. The interface is designed to allow it, though, so if you have some programming skills it might be easier to send a patch for that than to use manual methods.
What makes you think that the strings translated into Czech are the most seen? After the group of "top"/most used messages is translated, we have the main Wikimedia messages group which offers plenty of suggestions. Some of those messages are very important, for instance the new search features and notifications which are very visible.
I don't have programming skills to do that so could you please recommend me somebody who would be able to help me?
Seeing those Czech messages on Slovak projects makes me think that they are most seen.
Maybe, if I can suggest something, if it is not too hard and time-consuming, adding an option to switch the source language would be a very useful thing (at least for me).
Who is this user, and why he opens account which is IP address? See Special:Log/newusers.
That IPv6 is "mine", very strange because I'm logged in here.
If you look for it, you'll see that it belongs to the IPv6 space allocated by Free.fr for its fiber accesses (the IPv6 translates algorithmically into a regional location and default IPv4 address, normally, but this does not apply to me because my IPv4 (which is not shared by 4 users like it is by default in Free.fr, which uses NAT by assigning them 4 distinct ranges of 13684 port numbers for TCP and UDP, instead of the classic 65536 port numbers) was allocated to another space where I have a dedicated IPv4 address not passing through NAT.
This is visibly a bug of the "TranslateUserManager" bot, loosing some data about user sessions when we are connected via IPv6, or when some subrequests are coming with different address. Or may be there's a bug in this wiki in its antispam systems, which incorrectly assume that an IPV4 cannot be used simultaneously by two unrelated users. Anyway this is also a privacy bug that should be signaled (it does not conform to Wikimedia policies), and fails to map the related IPv4 and IPv6. I can't explain why this happens, but sessions are incorrectly managed by the frontends of this wiki.
This may be related to recent bugs in this wiki, with failure in its front end caches, also loosing sessions, mixing queries, corrupting the frontend caches with unrelated translations, and not returning the expected data and making incorrect logs for user accounts that it could not get.
I've never opened any such account and in fact the log is wrong as there was no account created at all. All this comes from an internal bot on this wiki.
This bug is visible since last August 15. I never had my IP "logged" like this even if I used this wiki before and did not change my ISP settings or subscription and was active even before.
Everyone sees their own ip. The users in those log entries no longer exist and those log entries should not be there.
What do you mean ? We don't see the same things in logs ? How can you be certain we have the right to see "deleted" log entries? Just because at one time we are using the same IP ? Anyway I do see all these log entries (about 4-5 listed each day since August 15, not any one before, but I see them in the log just since a few day; I many have not noticed that before). So you say that these log entries "no longer exist", but then why do I see them ? Was there a bug that caused IP accounts being created for logged in users, then immediately deleted after logon, but recreated later and repeatedly ? This is clearly a bug: there should not be any account creation before we submit an actual edit (just reading the wiki or logging in should log nothing, or you have a serious privacy issue for RGPD).
@Verdy p: The IP address I see is the one I'm using. It's not an IPv6 address. I agree it's a bug, and should be fixed, but there is no privacy breach when everyone sees their own IP address.
I thought that everyone saw my IPv6 address in this page, which then does not doisplay the same thing for everyone. Anyway these entries are spurious, It reveals that there are effectively lot of logs being made for non-sense account creations by a bot, which then gets rapidly reverted. I suspect this occurs each time we connect on the site. But in fact I tried to disconnect and waited for some minutes before revisiting once, then wait for other minutes, and come back later to login: 3 actions are logged. Any visitor from any IP may have an IP account instantly created, and logged, even if that accoutn is not used at all for any write action, jsut simply visiting. This means that this site is easily attackable: you can have lot of logs filling your disks and the database, and the site won't resist at all. This may explain why the site is sometimes SOOO long to refresh itself and has many antique statuses that can take sometimes days to be reflected.
The source text to translate from English in MediaWiki:Sanctions-row-button-execute/en actually contains a Korean word (not sure if this really means "Execute" as an imperative verb, and no indication for the capitalization of the button). Please fix it, thanks. Verdy p (talk) 01:11, 22 October 2019 (UTC)
Hi everyone! I'm from Georgian wiki. I'd like put some effort in wiki translation but as I figured I don't have rights yet. Can anyone help me out in getting this fixed? Thanks.