View source for Thread:Support/Adding Skin:Citizen to the list of projects/reply
Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.Your request has been forgotten? Feel free to post a reply to bump the thread to the top. The thread summarization feature is broken, see Phab:T245109. Very old threads have been archived.
- [View source↑]
- [History↑]
Contents
 First page |
 Previous page |
 Next page |
 Last page |
Hi there! I am interested in adding Skin:Citizen to the list of projects to be translated. The skin is hosted on GitHub instead of Gerrit like most skins do, what should I do to add it for translation? Thanks!
You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page.
Return to Thread:Support/Adding Skin:Citizen to the list of projects/reply.
Yes I do, it's also under the same name as this.
Hello. I'm interested in adding WPCleaner to the list of projects which can be translated. What should I do?
WPCleaner is an open source tool for editing MediaWiki wikis, mostly designed to help fixing errors (lint errors, syntax, links to disambiguation pages...). The source code is available on GitHub, here. i18n is currently handled by gettext with .po files. Translation was handled at on launchpad.net, but a bug prevents me from updating the list of strings to translate there.
Thanks.
Hi NicoV,
Thanks for reaching out to us. I'll create a task to track this tomorrow.
Regards,
I've created a task on Phabricator: https://phabricator.wikimedia.org/T255101
If you have a Phabricator account, lets take the discussion there, otherwise we can continue talking here.
Regards,
This edit should be reverted. I have no access to editing.
Is there an sysop who likes to work on the Category:Candidates for speedy deletion? Some of the candidates are since one year in this category. Best Regards
See for example Thread:User talk:Nemo bis/Template:Delete and Category:Delete Requests. Users are creating processes here on their own without involving sysops. This creates mismatch of expectations that makes everybody unhappy.
As you can see on Succession plan#Translator_liaison we currently have nobody responsible for this area, so things don't happen fast here.
There's effectively the need for an admin to monitor the related category to lookup each deletion request. This may happen at any time, but ther's usually no emergency. Still the template is useful to mark pages that are discovered (don't forget to specidy a reason to help admins assert the reason, as instructed), but there's usually no emergency to delete a page (if a page causes some problems, its content may still be edited to remove the problem, e.g. spammed content can be blanked except the deleteion request, before it gets deleted by an admin who can inspect the page history to make sure that the deleteion request is valid and was not posted abusively after just looking at its current state; for example a page may have had its content fully replaced by spammed content, and the deletion request is then invalid as the previous conbtent should be restored from the history instead of posting a deletion request template; if some pages are abusively or repeatedly spammed, the author of these undesired changed should be signaled here so that some admin action can be taken against that abusing spammer).
Guys, Crosswatch's website is invalid or was closed. Is that translation discontinued?
Looks so indeed: https://phabricator.wikimedia.org/T144083
We are going to remove it from translation.
For some reason i'm unable to edit following pages.
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-result/bn
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-syntax/bn
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-description/bn
It says "You do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors." How can i edit these pages?
Please past the new translations here. I will add the translation then to these messages.
Please replace & with ও
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-result/bn গাঢ় & বাঁকা লেখা → গাঢ় ও বাঁকা লেখা
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-syntax/bn গাঢ় & বাঁকা লেখা → গাঢ় ও বাঁকা লেখা
- MediaWiki:Wikieditor-toolbar-help-content-bolditalic-description/bn গাঢ় & বাঁকা → গাঢ় ও বাঁকা
Done
I would like to request offline translator rights to upload translations. I will send my first file by email right now.
We have received the offline file, and it will be processed before the next translation export on Thursday. We will also review your request for offline translator rights.
Thanks for your contribution.
Regards,
I've imported the file sent by you. You can see the changes here - https://translatewiki.net/w/i.php?title=Special:Contributions&offset=&limit=500&target=L2212&namespace=1222&tagfilter=&start=&end=
I've also given you offline translator rights. Please do remember to avoid large message groups and do not work offline for extended periods of time.
Thanks for your contribution.
Regards,
How to change date format in this message ($3 parameter)? I would like to change it from YYYY-MM-DD to DD.-MM.-YYYY.
Correct date format is {{#timel:j. n. Y.}} and not {{#timel:d. m. Y.}} see Pomoć:Vremenska funkcija (or via interwiki).
We need to get this request as complete as possible, not just partially complete. Some of us at phab:T223988 requested the change of date format for Croatian, which revealed a hard-coded dot which produces formatting problems.
In the text Formatting and parsing dateTimes as strings, IBM Knowledge Center Home of IBM product documentation, last updated: 2020-04-03, accessed: 2020-05-19 — it is described what d. M. yyyy. and d. MMMM yyyy. mean. The two before mentioned forms are most appropriate in Croatian language translations. The form dd. MM. yyyy. is not a desirable solution.
Similarly, these are desirable solutions: %d. %m. %Y. or %d. %B %Y..
Even if there is some amount of mystery around what code the programmers would use, it is necessary to describe the problem in as many details as possible, in order for the better end result.
It would be great if we could filter recent additions by group. This feature would make it easier to track and translate new messages into the selected message group. For example, it would be easier for MediaWiki users to translate new MediaWiki messages, instead of messages from other projects and the like. What do you think about this?
Why would you prioritize translating new messages, if you are not close to 100% coverage?
In MediaWiki:Apihelp-changecontentmodel-param-summary/en is "Edit" a noun or a verb?
In MediaWiki:Apihelp-changecontentmodel-param-summary/en is "Edit" a noun or a verb?
Based on the message name I assume it's a noun: an edit summary that will be used as a log entry reason (but I'm not 100% sure)
I've installed Extension:Translate on my own wiki, and I want to translate some non-MediaWiki content (software interface text, in particular). How do I configure that, and what file formats are supported?
Also no, I don't feel like the project can/should be hosted on translatewiki.net.
First the bad news: it's a lot this time. The good news: I've made edit links with easy to copy/paste translations, and double checked everything.
Could someone please make these edit for me. Thanks a lot!
Translations[edit]
Omskriuwing
Wat jo yntype
Wat jo krije
https://translatewiki.net/w/i.php?title=MediaWiki:Wikieditor-toolbar-help-page-format/fy&action=edit
Opmaak
https://translatewiki.net/w/i.php?title=MediaWiki:Wikieditor-toolbar-help-page-link/fy&action=edit
Keppelings
Koppen
https://translatewiki.net/w/i.php?title=MediaWiki:Wikieditor-toolbar-help-page-list/fy&action=edit
Listen
[[Sidetitel]]<br />[[Sidetitel|Tekst keppeling]]
<a href='#'>Sidetitel</a><br /><a href='#'>Tekst keppeling</a>
[http://www.example.org Tekst keppeling]<br />[http://www.example.org]<br />http://www.example.org
<a href='#' class='external'>Tekst keppeling</a><br /><a href='#' class='external autonumber'>[1]</a><br /><a href='#' class='external'>http://www.example.org</a>
Kopke twadde nivo
Kopke tredde nivo
=== Koptekst ===
Kopke fjirde nivo
==== Koptekst ====
Kopke fyfte nivo
===== Koptekst =====
Puntelist
* Listrigel<br />* Listrigel
<ul><li>Listrigel</li><li>Listrigel</li></ul>
Nûmere list
# Listrigel<br /># Listrigel
<ol><li>Listrigel</li><li>Listrigel</li></ol>
Ynsletten bestân
[[$1:Eksimpel.png|$2|$3]]
Tekst byskrift
Referinsje
Sidetekst.<ref>[http://www.example.org Tekst keppeling], oanfoljende tekst.</ref>
Sidetekst.<sup><a href='#'>[1]</a></sup>
Neamde referinsje
Sidetekst.<ref name="test">[http://www.example.org Tekst keppeling]</ref>
Sidetekst.<sup><a href='#'>[2]</a></sup>
Fierder gebrûk fan deselde referinsje
Sidetekst.<sup><a href='#'>[2]</a></sup>
Referinsjes werjaan
<ol class='references'><li id='cite_note-test-0'><b><a title='' href='#'>^</a></b> <a rel='nofollow' title='http://www.example.org' class='external text' href='#'>Tekst keppeling</a>, oanfoljende tekst.</li><li id='cite_note-test-1'><b><a title='' href='#'>^</a></b> <a rel='nofollow' title='http://www.example.org' class='external text' href='#'>Tekst keppeling</a></li></ol>
Sinjatuer mei tiidstimpel
--<a href='#' title='$1:Meidochnamme'>Meidochnamme</a> (<a href='#' title='$2:Meidochnamme'>oerlis</a>) 10 jun 2009, 15.54 (UTC)
Sinjatuer
<a href='#' title='$1:Meidochnamme'>Meidochnamme</a> (<a href='#' title='$2:Meidochnamme'>oerlis</a>)
Ynspringe
Normale tekst<br />:Ynsprongen tekst<br />::Ynsprongen tekst
Normale tekst<dl><dd>Ynsprongen tekst<dl><dd>Ynsprongen tekst</dd></dl></dd></dl>
Is there a way to directly jump into a message in the list of all messages? I mean to be able to see the messages before/after it. For example the following URL shows the desired message, but filters out all other ones.
This could be useful for bookmarking the last string I was working on and quickly come back to it and continue the work.
Hi I'm requesting for change my name KaleemBhatti to Kaleem Bhatti please chanage my name
I'm considering changing our default skin to Timeless. My reasons are:
- Timeless has responsive design which works better on mobile devices (we get quite a few visitors from mobile devices, but not that many users), unlike the Vector skin. E.g. Google search has started penalizing sites which do not work well on mobile.
- I like Timeless and I have been using it here for a while. Most glitches with Timeless have been fixed by now.
Notes:
- Manually set skin preferences would not change, and Vector would still be available as a choice.
- Other option would be to install MobileFrontend extension, but that has not been tested and could break quite a few things.
- Vector is going through modernization, so it could get better mobile support in the future.
- Also tracked in phab:T248064
Please let me know what you think.
Personally I would stick to the Vector skin (thus I'd appreciate installing MobileFrontend and Minerva skin for better mobile support anyway) but I don't see anything against Timeless as the default skin. Do whatever you want.
The design of the Timeless skin is good, maybe we can add it as an option in user preferences.
I never used Timeless in a prodction system. So I changed here to Tineless and will try is the next days...
I also use Timeless here for a while; I hardly noticed the site notice about this thread… The font size is the same on Vector as well, but on Timeless it quickly gets covered by the top toolbar as I start scrolling. I think you should use the default font size so that users have a chance to notice it.
On-topic: I’m quite conservative, so even though I personally like Timeless, I’m not sure if the majority of the users do so. Also, the visual similarity to Wikipedia is IMHO more important than search engine optimization—are there users at all who come here from Google? This project is a rather background one, so I expect 99% of the users to come here from the translated projects’ sites (or experienced users using this wiki’s OpenSearch engine, arriving right to the message to translate).
Glitches: I still found three of them on Special:Translate for first sight.
- “Translate” link in the More toolbox (on the right on wide screens). This is the default tab on Vector, which appears in the place of the Article tab. It’s visually needed on Vector and Monobook, but makes no sense on other ones like Timeless, Modern or Cologne Blue. I’m not sure technically how, but it should not be there on Timeless.
- Language statistics, Message group statistics and Export. These three links are in the top right corner, all with default icons. This way the icons don’t have much purpose, but it’s particularly annoying on narrow screens, where only the icons appear, so the only way to tell them apart is by analyzing the URL, which is far from being user-friendly. I think this is a release-critical bug in terms of making Timeless default for all (often inexperienced) users.
- Message documentation on mobile. Because of the narrow screen, the message documentation pane and the translation pane overlaps on mobile. The documentation pane can be collapsed, but only one-by-one for each and every message, while often it doesn’t contain any information. Maybe it could be fixed by switching to a vertical layout on narrow screens. This should only display the message documentation by default, not the translation helpers (other languages, machine translation etc.), again to save space, which could be expanded if needed. Also maybe remembering the state between messages would be helpful.
Thanks for the feedback. Regarding your point about message documentation on mobile, isn't that same problem also present in Vector?
I'll look into the two other glitches.
For translators, you are right. But developers looking for alternatives come via search engines.
No, the message documentation windows (just like the user boxes mentioned below) have no such issues on mobile with Vector—since Vector is not responsible, mobile browsers use a so-called “virtual viewport” as a self-defense, which is much wider than the actual screen width (see Using the viewport meta tag to control layout on mobile browsers on MDN). This means that the text is maybe unreadably small, but at least the layout is not broken. Of course, this situation is much improved by the introduction of Timeless if Tux is made work well with narrow viewports.
For SEO: I see. This is a tough decision, however, as I still think that keeping consistency with Wikipedia is important, but I agree that letting developers find this site is just as important.
P.S. What about the site notice? Is there a reason not to increase its font size?
Regarding issues 1 and 2 (the navigation tabs), I see no easy way to fix it. I am not skilled enough to make distinct icons for them. I considered moving them elsewhere, but I have no control over where (filed Phab:T251258).
Regarding the 3rd issue, it would fall under Phab:T146134. Unfortunately I don't think I can fix it without re-doing the UI with a more responsive grid system, which is a lot of work.
I also noticed that my user page looks not-so-perfect on a narrow screen: the Babel boxes become 100% wide if the screen is less than 480px wide, while the other user boxes don’t. I think the best solution for this issue is installing mw:Extension:TemplateStyles and creating a responsive TemplateStyles subpage for {{Userbox}}.
+ 1 for Vector. EDIT: I abstain because of "Manually set skin preferences would not change, and Vector would still be available as a choice.", i.e. if you all agree on Timeless ... which should I stand in your way. :)
I don't like new skin and I think it should not be used as default (neither for new users). One reason is that it is more intuitive for Wikipedia editors to see same appearance here as it is on Wikipedia (Message, Discussion – Read, Edit, View history / More; What links here is moved to the right and was always to the left etc.). Also, Timeless skin is not full width. One thing I like with the proposed skin is that it is more interactive than current standard one (buttons).
I changed my skin to Timeless after seeing the ad.
It's mostly fine, but there are some issues. The most significant is perhaps this: The ULS control for changing the UI language is hidden under the user menu. It's not a thing that people often do once they settle on a language they want, but initially choosing the language for new users may become challenging.
Probably language selection should be part of the registration process. This not only overcomes this issue in case Timeless wins, but also, more importantly, makes even more users aware of the possibility to set their interface language. (And don’t be shy to tell all issues you found, so that Timeless will work as seamlessly as possible.)
I just use Vector on laptop with extended display for my translations, comparing pages, viewing reference pages and so on , so that I dont really use my tablette for that. Nothing against, till my environment remains available.
I like that Timeless is truly responsive, but I really do not like its design. If the skin by default was changed to Timeless, I would switch it back. It might be a good test as to see which pages are responsive or not (and need TemplateStyles / CSS changes), but I feel like that should be mostly a power-user thing.
I also feel like, with its Wikimedia colours being displayed quite prominently in the design, it doesn’t make much sense to use the skin as it is for a project that isn’t, formally, one of Wikimedia projects. But maybe I am reading too much into this and the only effect of the change would be ‘huh, skin is different from Wikipedia/Wiktionary/etc.’, since many people will probably not associate those colours with Wikimedia.
Hello, I have GrowthExperiments installed on my test wiki. Why is tag shown in message on wiki? This message: MediaWiki:Growthexperiments-homepage-suggestededits-difficulty-filters-article-count/sr-ec is related.
On english version of site everything is fine, so I think that problem is with translation. Is something wrong?
I don't see anything wrong with the translation. Can you give a screenshot of what you are seeing?
Edit: By tag I assume you mean the strong tags?
Regards,
It is fixed by another user already. Thanks in each case!
First page |
Previous page |
Next page |
Last page |