mediawiki-skins-MinervaNeue/i18n/en.json

75 lines
4.4 KiB
JSON
Raw Normal View History

{
"@metadata": {
"authors": []
},
"minerva-last-modified-date": "Last edited on $1, at $2",
"minerva-watchlist-cta": "Keep track of this page and all changes to it.",
"minerva-talk-add-topic": "Add discussion",
"mobile-frontend-cookies-required": "Cookies are required to switch view modes. Please enable them and try again.",
"mobile-frontend-editor-edit": "Edit",
"minerva-download": "Download PDF",
"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-footer-sitename": "{{SITENAME}}",
"mobile-frontend-history": "View edit history of this page.",
"mobile-frontend-home-button": "Home",
"mobile-frontend-language-article-heading": "Language",
"mobile-frontend-languages-not-available": "This page is not available in other languages.",
"mobile-frontend-logged-in-homepage-notification": "{{GENDER:$1|Welcome}}, $1!",
"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",
"mobile-frontend-meta-data-issues-header": "Page issues",
"minerva-meta-data-issues-section-header": "Section issues",
"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",
"mobile-frontend-pageaction-edit-tooltip": "Edit the lead section of this page",
"mobile-frontend-placeholder": "Search {{SITENAME}}",
"mobile-frontend-random-button": "Random",
"mobile-frontend-redirected-from": "Redirected from \"[[$1]]\"",
"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}}\".",
"mobile-frontend-user-button-tooltip": "Show my notifications",
"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",
"minerva-user-navigation": "User navigation",
"minerva-page-actions-overflow": "More",
"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",
"minerva-page-actions-user-groups": "User groups",
"minerva-page-actions-logs": "Logs",
"minerva-page-actions-wikibase": "{{WBREPONAME}} item",
"minerva-page-actions-language-switcher": "Languages",
"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.",
"skinname-minerva": "MinervaNeue",
"minerva-skin-desc": "A responsive mobile first skin",
"skin-minerva-issue-learn-more": "Learn more",
"skin-minerva-mobile-option-MinervaShowCategoriesButton": "Categories",
"skin-minerva-mobile-option-MinervaShowCategoriesButton-description": "View categories of pages",
"skin-minerva-mobile-option-MinervaPageIssuesNewTreatment": "Improved page issues treatment",
"skin-minerva-mobile-option-MinervaPageIssuesNewTreatment-description": "Page issues (Template:ambox) will be inlined in the article.",
"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 */"
}