wikimedia/mediawiki-skins-MinervaNeue
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/skins/MinervaNeue synced 2024-11-16 10:50:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-skins-MinervaNeue/i18n/en.json

77 lines
4.4 KiB
JSON
Raw Normal View History

Add scaffolding for skin Change-Id: Ie9420dc85f658fa21a1524dca9374cb1e14fcad7
2017-04-11 02:30:17 +00:00
{
"@metadata": {
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"authors": []
Add scaffolding for skin Change-Id: Ie9420dc85f658fa21a1524dca9374cb1e14fcad7
2017-04-11 02:30:17 +00:00
},
i18n: Add Minerva specific message key for last modified bar This is currently defined in MobileFrontend which uses it for Special:MobileWatchlist. We shouldn't use two messages for 2 purposes so let's give it its own dedicated message. Change-Id: Id5df6aad20815b88b8bd2685514e7eb3237a5b3b
2017-08-16 19:55:05 +00:00
"minerva-last-modified-date": "Last edited on $1, at $2",
Use core watchstar code Apply the mediawiki core watchstar to the Minerva skin. Note, watchstars in search and other locations will continue to be provided by the MobileFrontend library (see follow up patch I7b748dc87089389400b0035c62a3b9a00c2e43f9) Bug: T234970 Change-Id: I11bbe976412b50dba76a55f37887e4c9235d0be1
2019-09-19 21:19:07 +00:00
"minerva-watchlist-cta": "Keep track of this page and all changes to it.",
Change minerva-talk-add-topic message to "Add topic" to match Vector Bug: T302502 Change-Id: I448bb41d833c3e228f9be7403bf026a85e292835
2022-02-24 15:33:25 +00:00
"minerva-talk-add-topic": "Add topic",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-cookies-required": "Cookies are required to switch view modes. Please enable them and try again.",
"mobile-frontend-editor-edit": "Edit",
Update: add secondary page actions submenu in AMC mode When advanced mobile contributions mode is enabled and `$wgMinervaOverflowInPageActions` is set, show a secondary overflow menu on main namespace articles and user namespace pages. The menu content varies for each namespace. The new submenu is *disabled* by default, even when AMC is active. This feature should not be deployed until instrumentation is available. The secondary menu is rendered in PHP using the existing menu system with some changes to the template. The checkbox hack is needed for no- JavaScript keyboard navigation until :focus-within is supported. CSS additions are documented in the source. All client side toolbar execution occurs in Toolbar.js. Enhancements are documented in the source. Minor changes to the existing download button: - Move download and edit button initialization to Toolbar. - Update copy (not visible) from "Download" to "Download PDF". - When the overflow menu is present, use the "hasText" / label style. Wikimedia UI icons are copied from OOUI at d00a0ac and seem useful to expose as HTTP URIs (not data URIs). The overflow menu does not show for pages provided by the content proxy since its entries depend on $tpl->data['nav_urls'] being populated. Bug: T216418 Depends-On: I0781151a8232b6a7b52f79a34298afcecb8e4271 Change-Id: I4b50a0e519024a7ab91dae6ab40b23cf14a03861
2019-04-04 21:20:39 +00:00
"minerva-download": "Download PDF",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-editor-redlink-create": "Create page",
"mobile-frontend-editor-redlink-explain": "This page has not yet been created.",
"mobile-frontend-editor-redlink-leave": "No, thanks.",
"mobile-frontend-history": "View edit history of this page.",
"mobile-frontend-home-button": "Home",
Shorten labels for page-actions menu items Updates the labels for: language, history, dropdown menu buttons in the page-actions menu Bug: T226562 Change-Id: I1141d570cf17d659a943659e8f44ebcdd166ca3c
2019-10-16 15:04:19 +00:00
"mobile-frontend-language-article-heading": "Language",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-languages-not-available": "This page is not available in other languages.",
"mobile-frontend-main-menu-button-tooltip": "Open main menu",
"mobile-frontend-main-menu-contributions": "Contributions",
"mobile-frontend-main-menu-login": "Log in",
"mobile-frontend-main-menu-logout": "Log out",
"mobile-frontend-main-menu-nearby": "Nearby",
"mobile-frontend-main-menu-settings": "Settings",
"mobile-frontend-main-menu-watchlist": "Watchlist",
"mobile-frontend-meta-data-issues": "Page issues",
"mobile-frontend-meta-data-issues-categories": "About this category",
CSS tweaks to issue overlay * Remove CSS rule updating the padding of issue-notice (this is no longer necessary after I1b880c46fa3debfc5b68d8b416ca642cca98ce7e which defines its own padding for the element) * Overlay title is updated to read "Page issues" Bug: T187916 Change-Id: I7e41d6f03c4cf9fa7563f2f608eec5be89c04a31
2018-03-13 23:15:04 +00:00
"mobile-frontend-meta-data-issues-header": "Page issues",
Section issues overlay has different heading Per https://phabricator.wikimedia.org/T197932#4417319 Note that given talk/category overlay does not use or display section issues, to simplify things any section other than 0 or all will use this heading. Bug: T197932 Change-Id: I737fb07aaadcea7772d0b08f8b0652dcf2f4623d
2018-07-11 21:13:19 +00:00
"minerva-meta-data-issues-section-header": "Section issues",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-meta-data-issues-header-talk": "About this page",
"mobile-frontend-meta-data-issues-talk": "About this talk page",
"mobile-frontend-notifications-filter": "Filter",
Remove a full stop from the end of the tooltip There are no full stops on other tooltips. Change-Id: I807b20eeeccc343baffb42e57f6e97ad03ea3d55
2017-07-22 07:27:42 +00:00
"mobile-frontend-pageaction-edit-tooltip": "Edit the lead section of this page",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-placeholder": "Search {{SITENAME}}",
"mobile-frontend-random-button": "Random",
Provide access to original redirect page on toasts Color progressive/destructive (blue and red) do not make sense on a black background, so we use white and underlined for both of these. Note these don't seem to be used currently so this is not a breaking change. Bug: T150189 Change-Id: I78a92b5b6c76638633b99fe32670911d355ce6f3
2019-07-31 23:28:27 +00:00
"mobile-frontend-redirected-from": "Redirected from \"[[$1]]\"",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-talk-back-to-filepage": "Return to the file \"$1\".",
"mobile-frontend-talk-back-to-page": "Return to \"$1\" page.",
"mobile-frontend-talk-back-to-projectpage": "Return to the project page \"$1\".",
"mobile-frontend-talk-back-to-userpage": "Return to the user page of \"{{GENDER:$1|$1}}\".",
Migrate 3 messages from MobileFrontend These were missed in the migration. Putting them where they belong. Change-Id: Ifb6a2f20b43d05610845c06e4c92035a5d3327a9
2017-07-13 16:02:47 +00:00
"mobile-frontend-user-button-tooltip": "Show my notifications",
Minerva is its own skin This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
2017-07-12 15:12:40 +00:00
"mobile-frontend-user-newmessages": "You have new messages on your talk page",
"mobile-frontend-user-page-contributions": "Contributions",
"mobile-frontend-user-page-member-since": "{{GENDER:$2|Joined}} $1",
"mobile-frontend-user-page-talk": "Talk",
[UI] [new] add user menu Add new user menu. The changes required include: - Break up AuthMenuEntry into reusable components. They're now simple, independent, static functions in AuthUtil that are easy to reason about and compose. There's lots of verbose code because of the builder and director patterns. That is, most of the code is for building the thing we actually want to build instead of just building it. It's easy to write but no fun to read--even simple configurations are extremely verbose expressions that must be threaded through the system. These builders are also single purpose and unlikely to be reusable unlike a URI builder, for example. As objects, they're not especially composable either. - Similarly, break up Menu/DefaultBuilder into BuilderUtil and ban inheritance. Inheritance has not worked well on the frontend of MobileFrontend. I don't think it's going to work well here. E.g., I could have made changes to the base class' getPersonalTools() method such that the client passes a parameter for the advanced config or maybe I just override it in the subclass. In either case, I think it makes the whole hierarchy nuanced and harder to reason about for something that should be simple. - Add ProfileMenuEntry and LogOutMenuEntry for the user menu. - Rename insertLogInOutMenuItem() to insertAuthMenuItem() which matches the entry name, AuthMenuEntry. - Extension:SandboxLink is needed to display the sandbox link in the user menu. - Performance note: the toolbar is now processed in MinervaTemplate, which corresponds to removing the buildPersonalUrls() override. - To mimic the design of main menu, the following steps would be necessary: 1. Create a user/Default and user/Advanced user menu builder and also a user/IBuilder interface. 2. Create a user/Director. 3. Create a service entry for Minerva.Menu.UserDirector in ServiceWiring. The Director is actually powerless and doesn't get to make any decisions--the appropriate builder is passed in from ServiceWiring which checks the mode. 4. Access the service in SkinMinerva to set a userMenuHTML data member on the Minerva QuickTemplate. 5. In MinervaTemplate, access the userMenuHTML QuickTemplate member and do the usual song and dance of inflating a Mustache template. This patch does everything except add a service, which was agreed to be unnecessary, so that logic is now in SkinMinerva. - Wrap the existing echo user notifications button and new user menu button in a nav element. This seems like a semantic improvement. - The existing styling and logic for the search bar and search overlay are pretty messy and delicate. Changes made to that LESS endeavored to be surgical. There's lots of room for improvement in the toolbar but it's out of scope. - Rename logout icon to logOut. Bug: T214540 Change-Id: Ib517864fcf4e4d611e05525a6358ee6662fe4e05
2019-06-25 20:12:58 +00:00
"minerva-user-menu-button": "User menu",
Fix: user navigation label when AMC is disabled At some point I introduced a bad label aria ID, minerva-user-menu-toggle, for the user navigation. This was the incorrect text and ID to use. Further, the ID is not present in non-AMC mode (which is what search engines use). This patches adds a new string, minerva-user-navigation, and replaces the aria-labelledby attribute with a direct aria-label. Bug: T242281 Change-Id: Ic247eb77609862b62025dc5e6af550c079df26d9
2020-01-10 22:23:04 +00:00
"minerva-user-navigation": "User navigation",
Shorten labels for page-actions menu items Updates the labels for: language, history, dropdown menu buttons in the page-actions menu Bug: T226562 Change-Id: I1141d570cf17d659a943659e8f44ebcdd166ca3c
2019-10-16 15:04:19 +00:00
"minerva-page-actions-overflow": "More",
Update: add secondary page actions submenu in AMC mode When advanced mobile contributions mode is enabled and `$wgMinervaOverflowInPageActions` is set, show a secondary overflow menu on main namespace articles and user namespace pages. The menu content varies for each namespace. The new submenu is *disabled* by default, even when AMC is active. This feature should not be deployed until instrumentation is available. The secondary menu is rendered in PHP using the existing menu system with some changes to the template. The checkbox hack is needed for no- JavaScript keyboard navigation until :focus-within is supported. CSS additions are documented in the source. All client side toolbar execution occurs in Toolbar.js. Enhancements are documented in the source. Minor changes to the existing download button: - Move download and edit button initialization to Toolbar. - Update copy (not visible) from "Download" to "Download PDF". - When the overflow menu is present, use the "hasText" / label style. Wikimedia UI icons are copied from OOUI at d00a0ac and seem useful to expose as HTTP URIs (not data URIs). The overflow menu does not show for pages provided by the content proxy since its entries depend on $tpl->data['nav_urls'] being populated. Bug: T216418 Depends-On: I0781151a8232b6a7b52f79a34298afcecb8e4271 Change-Id: I4b50a0e519024a7ab91dae6ab40b23cf14a03861
2019-04-04 21:20:39 +00:00
"minerva-page-actions-info": "Page information",
"minerva-page-actions-permalink": "Permanent link",
"minerva-page-actions-backlinks": "What links here",
"minerva-page-actions-cite": "Cite page",
Allow Users with permissions to do expanded actions in Minerva on mobile Allow Users with the needed permissions to delete, protect or move pages in Minerva on mobile version. Bug: T231291 Change-Id: I1e438b7d3683d288a8a6c5a9f5dcea6b3b3d9f71
2021-03-09 19:43:14 +00:00
"minerva-page-actions-move": "Move",
"minerva-page-actions-delete": "Delete",
"minerva-page-actions-protect": "Protect",
Menu: Add "unprotect" action when current user is an admin Accidentally via T231291, a regression was introduced such that, in AMC mode, when a page is protected to be edited only by admins, a corresponding unprotect action is not avaiable to reverse the protect action. This patch fixes that regression. Have tested locally and it works as expected. Bug: T285567 Change-Id: Ie20ca5d9c43fa54dff5d699eb59679585283bdb5
2021-06-30 17:20:39 +00:00
"minerva-page-actions-unprotect": "Unprotect",
Rename UserRights to UserGroups The "User Rights" is called "User groups" on desktop. The Mobile site should not provide it's onw naming but use the same names as desktop. Bug: T230694 Depends-On: Ic9b7033e3f52f415ec8aec845a65a8452d0e5d8f Change-Id: Iaf116a5cc54cc400451550d9fa958adbbccc35c5
2019-09-05 10:10:58 +00:00
"minerva-page-actions-user-groups": "User groups",
Update: add secondary page actions submenu in AMC mode When advanced mobile contributions mode is enabled and `$wgMinervaOverflowInPageActions` is set, show a secondary overflow menu on main namespace articles and user namespace pages. The menu content varies for each namespace. The new submenu is *disabled* by default, even when AMC is active. This feature should not be deployed until instrumentation is available. The secondary menu is rendered in PHP using the existing menu system with some changes to the template. The checkbox hack is needed for no- JavaScript keyboard navigation until :focus-within is supported. CSS additions are documented in the source. All client side toolbar execution occurs in Toolbar.js. Enhancements are documented in the source. Minor changes to the existing download button: - Move download and edit button initialization to Toolbar. - Update copy (not visible) from "Download" to "Download PDF". - When the overflow menu is present, use the "hasText" / label style. Wikimedia UI icons are copied from OOUI at d00a0ac and seem useful to expose as HTTP URIs (not data URIs). The overflow menu does not show for pages provided by the content proxy since its entries depend on $tpl->data['nav_urls'] being populated. Bug: T216418 Depends-On: I0781151a8232b6a7b52f79a34298afcecb8e4271 Change-Id: I4b50a0e519024a7ab91dae6ab40b23cf14a03861
2019-04-04 21:20:39 +00:00
"minerva-page-actions-logs": "Logs",
Add wikidata link to overflow menu The director is now passed the array from `BaseTemplate::getToolbox()` as all of the server rendered links we show in the main namespace/user namespace overflow menus (including wikibase) will be in the toolbox array except for the "Uploads" link in the User overflow menu which is added in the UserNamespaceOverflowBuilder. Bug: T222630 Change-Id: I280537c6b8b32036d68a5a004571bb5a41c2e703
2019-06-11 00:57:13 +00:00
"minerva-page-actions-wikibase": "{{WBREPONAME}} item",
On user pages, move language icon from Toolbar to Overflow menu The Language icon is not useful on user pages as most probably there are no translated user pages, thus there is no need to show all-time disabled Language icon. If overflow menu is available, don't show Language switcher icon in toolbar, show it as first item in the overflow menu. Bug: T224735 Follow-Up: I46d58758356e870c408a74b2c087a42d6ad0ddea Change-Id: I05be9e6457257a1f2eb224ca9ec5808814bc9ed7
2019-06-24 17:59:11 +00:00
"minerva-page-actions-language-switcher": "Languages",
Shorten labels for page-actions menu items Updates the labels for: language, history, dropdown menu buttons in the page-actions menu Bug: T226562 Change-Id: I1141d570cf17d659a943659e8f44ebcdd166ca3c
2019-10-16 15:04:19 +00:00
"minerva-page-actions-history": "History",
Render talk page as a tab instead of an overlay Following up on Jon's POC, this will get rid of the talk board component in favor of linking to the server rendered talk page. Additional Changes: * Cleaned up talk selenium tests. Removed talk_steps.rb which doesn't appear to be used anymore. * Changed talk add button classes to a single class * Moved "Add discussion" button to postheadinghtml per design mock * Added "...talk-explained", "...talk-explained-empty" messages to postheadinghtml per design mock * Due to undesirable jumps in window scroll caused by the section anchor & Toggler.js code when opening the TalkSectionOverlay (read fixme in code), a Promise is always returned from OverlayManager route to reset the scroll position to the top when the section overlay is opened. * Moved "mobile-frontend-talk-fullpage", "mobile-frontend-talk-reply-success", "mobile-frontend-talk-topic-feedback", "mobile-frontend-talk-explained" "mobile-frontend-talk-explained-empty" messages to minerva as minerva is the one who initiates those messages now. * Limited $talk selector to only `.talk` elements since amc talk tab does not need to be targeted * After saving a reply from TalkSectionOverlay, the DOM that is not part of the overlay becomes out of sync since a new reply was created. To get around this, an `onSaveComplete` callback was passed (similar to the TalkSectionAddOverlay) to execute a full page refresh. Although this is clunky, it is the easiest way to resync. Bug: T230695 Depends-On: I80201394fd7015db6700446142b0b4b20829f12e Change-Id: I243f1193bce0da9fa710fc3b5379f90b2d079680
2019-10-17 22:46:07 +00:00
"minerva-talk-explained": "Active discussions",
"minerva-talk-explained-empty": "There are no discussions on this page.",
"minerva-talk-full-page": "Read as wiki page",
"minerva-talk-topic-feedback": "New topic added to talk page!",
"minerva-talk-reply-success": "Your reply was saved to the talk page.",
Standardise on MinervaNeue's skin name (minerva) We will standardise on the key "minerva" and the styles in MediaWiki:Minerva.css for desktop since this is what is used for mobile. The name will however appear as MinervaNeue to be consistent with the skin repo name (not the code). Please merge I5fdb21243e0b599b07aa228107fd4b8c306c696c shortly after merging this to remove the remaining logic relating to this from MobileFrontend as otherwise two skins will appear in user preferences. Any existing users of MinervaNeue (key minervaneue on desktop) will be thrown back into the Vector skin and will need to opt into the MinervaNeue skin again. This is a minor disruption given the low amount of users and instability of the skin. Bug: T171644 Change-Id: Ieffb6334168047dcf05dcb60281865ab47056dc0
2017-08-17 22:35:39 +00:00
"skinname-minerva": "MinervaNeue",
Minerva should use FeatureManagers class Bug: T182362 Depends-On: I6cc4a2ebcd75c054294daf329d94d35a02e50f8e Change-Id: I6ba5bf49b9060c31ad2224a437072b3426a45619
2018-01-08 22:18:16 +00:00
"minerva-skin-desc": "A responsive mobile first skin",
Mobile page issues - visual styling changes Changes: * Introduce Jan's beautifully documented $wgMinervaABSamplingRate Set to 1 to A/B test 50% of the population * Split out ambox template styles into a separate file referenced by hacks.less * Update cleanuptemplates setup script to consider two buckets Test pages: * Shqiponja_Partizane * World_War_II_in_Albania * Liberation_of_Tirana * French_Consulate * Abd_ar-Rahman_IV * M109_howitzer * Aimoin * Transport_in_Brazil * Transport_in_Cape_Verde Bug: T191303 Change-Id: I8d11e655ccb847b7999e64dda57b225ad8b1c23a
2018-05-08 22:03:52 +00:00
"skin-minerva-issue-learn-more": "Learn more",
Replace categories button with HTML rendering Bug: T246049 Change-Id: Id8c7493a525844b43c1628a1f4f09ae716ece2ba
2021-04-28 21:58:51 +00:00
"skin-minerva-mobile-option-MinervaShowCategories": "Categories",
"skin-minerva-mobile-option-MinervaShowCategories-description": "View categories of pages",
page issues is feature flagged * New feature/skin option is added and value is read inside the pageIssues setup code * issues-group-a class is added to page on server side to remove the flash of unstyled content * issues-group-A class is dropped (it's not doing anything!) * The minerva-issues flag will now accept any value to avoid confusion. It is used to override the default setting of wgMinervaPageIssuesNewTreatment A note has been added that this can be removed in future. Bug: T206179 Change-Id: I3d98fd8f8e1adc818ea03589d2c8f68fe991e861
2018-11-12 20:32:28 +00:00
"skin-minerva-mobile-option-MinervaPageIssuesNewTreatment": "Improved page issues treatment",
Show warning when user tries to use enhanced RecentChanges view Bug: T228516 Change-Id: I16e3d69b410f20a3f70f4bb213a279664613f725
2019-07-31 14:57:27 +00:00
"skin-minerva-mobile-option-MinervaPageIssuesNewTreatment-description": "Page issues (Template:ambox) will be inlined in the article.",
Unify messages for skin specific CSS/JS overrides This should probably be following the same logic as other skins. Similar to Ib40a38dba553bf10. Change-Id: I881e46478b754a1322357493bea597e754fef63b
2020-02-20 11:35:38 +00:00
"skin-minerva-recentchanges-warning-enhanced-not-supported": "Unfortunately, grouping results by page is not available on mobile. If you would like to use the group by page feature please visit the desktop site.",
"minerva.css": "/* All CSS here will be loaded for users of the MinervaNeue skin */",
"minerva.js": "/* All JavaScript here will be loaded for users of the MinervaNeue skin */"
Remove a full stop from the end of the tooltip There are no full stops on other tooltips. Change-Id: I807b20eeeccc343baffb42e57f6e97ad03ea3d55
2017-07-22 07:27:42 +00:00
}
Reference in a new issue Copy permalink