Wikiknjige:Čitaonica

Čitaonica Dobro došli u Čitaonicu Wikiknjiga! U ovomu malom kutku Interneta možete osjetiti zajednički duh, postavljati pitanja, raspravljati o Wikiknjigama i ostalim Wikimedijinim projektima, davati prijedloge, i sve drugo čega se sjetite. Ako ne znate gdje postaviti neko pitanje, osjećajte se slobodnima pitati ovdje. Ipak, za raspravu o pojedinim modulima koristite njihove stranice za razgovor, u Čitaonici samo pozovite suradnike na dotičnu stranicu za razgovor. Dodajte novi komentar Pismohrana ove stranice: 1.

New print to pdf feature for mobile web readers

New print to pdf feature for mobile web readers

The Readers web team will be deploying a new feature this week to make it easier to download PDF versions of articles on the mobile website.

Providing better offline functionality was one of the highlighted areas from the research done by the New Readers team in Mexico, Nigeria, and India. The teams created a prototype for mobile PDFs which was evaluated by user research and community feedback. The prototype evaluation received positive feedback and results, so development continued.

For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.

The feature is available starting Wednesday, Nov 15. For more information, see the project page on MediaWiki.org.

Hvala Vam!

CKoerner (WMF) (talk) 23:07, 20. studenoga 2017. (CET)

Editing News #1—2018

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can now use the visual diff tool on any page?

Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

Recent changes

• The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
• The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [1]
• Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [2]
• The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together

• The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
• Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
• The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [3]
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Hvala Vam!

—Elitre (WMF)

21:56, 2. ožujka 2018. (CET)

AdvancedSearch

From May 8, AdvancedSearch will be available as a beta feature in your wiki. The feature enhances the search page through an advanced parameters form and aims to make existing search options more visible and accessible for everyone. AdvancedSearch is a project by WMDE Technical Wishes. Everyone is invited to test the feature and we hope that it will serve you well in your work!

Birgit Müller (WMDE) 16:53, 7. svibnja 2018. (CEST)

Update on page issues on mobile web

Update on page issues on mobile web

Molimo Vas, pomozite prevođenju na Vaš jezik Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

• The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
• Page issues make sense to readers and they understand how they work
• Readers care about page issues and consider them important
• Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues

Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.

CKoerner (WMF) (talk) 22:58, 12. lipnja 2018. (CEST)

Global preferences are available

Global preferences are now available, you can set them by visiting your new global preferences page. Visit mediawiki.org for information on how to use them and leave feedback. -- Keegan (WMF) (talk)

21:19, 10. srpnja 2018. (CEST)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

(Molimo Vas, pomozite prevođenju na Vaš jezik)

Hi all,

I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!

Thanks!
Tgr (talk) 10:45, 12. srpnja 2018. (CEST) (via global message delivery)

New user group for editing sitewide CSS/JS

(Molimo Vas, pomozite prevođenju na Vaš jezik)

Hi all!

To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.) A new user group, interface-admin, has been created. Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage).

You can learn more about the motivation behind the change here.

Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).

Thanks!
Tgr (talk) 15:08, 30. srpnja 2018. (CEST) (via global message delivery)

Editing of sitewide CSS/JS is only possible for interface administrators from now

(Molimo Vas, pomozite prevođenju na Vaš jezik)

Hi all,

as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Administratori sučelja) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.

Thanks!
Tgr (talk) 14:39, 27. kolovoza 2018. (CEST) (via global message delivery)

Read-only mode for up to an hour on 12 September and 10 October

Read this message in another language • Molimo Vas, pomozite prevođenju na Vaš jezik

The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the secondary data center on Wednesday, 12 September 2018. On Wednesday, 10 October 2018, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community. /User:Johan(WMF) (talk)

15:33, 6. rujna 2018. (CEST)

The GFDL license on Commons

This has been posted here because your wiki allows local file uploads. Molimo Vas, pomozite prevođenju na Vaš jezik.

Commons will no longer allow uploads of photos, paintings, drawings, audio and video that use the GFDL license and no other license. This starts after 14 October. Textbooks, manuals and logos, diagrams and screenshots from GFDL software manuals that only use the GFDL license are still allowed. Files licensed with both GFDL and an accepted license like Creative Commons BY-SA are still allowed.

There is no time limit to move files from other projects to Commons. The licensing date is all that counts. It doesn't matter when the file was uploaded or created. Every wiki that allows local uploads should check if bots, scripts and templates that are used to move files to Commons need to be updated. Also update your local policy documentation if needed.

The decision to allow files that only have a GFDL license, or not allow them, is a decision all wikis can make for themselves. Your wiki can decide to continue allowing the files that Commons will no longer allow after 14 October. If your wiki decides to continue to allow files after 14 October that Commons will no longer allow those files should not be moved to Commons. — Alexis Jazz, distributed by Johan using MassMessage

20:11, 20. rujna 2018. (CEST)

The Community Wishlist Survey

The Community Wishlist Survey. Molimo Vas, pomozite prevođenju na Vaš jezik.

Hey everyone,

The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.

The Community Tech team is focused on tools for experienced Wikimedia editors. You can post technical proposals from now until 11 November. The communities will vote on the proposals between 16 November and 30 November. You can read more on the wishlist survey page.

/User:Johan (WMF)

12:06, 30. listopada 2018. (CET)

Editing News #2—2018

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.

Remember to publish your changes when you're done.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes

• The Editing team has published an initial report about mobile editing.
• The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
• The Reading team is working on a separate mobile-based contributions project.
• The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar. You may choose another editing tool in your editing preferences, local gadgets, or beta features.
• The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
• The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published. [4]

Let's work together

• The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
• The Community Wishlist Survey begins next week.
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Hvala Vam!

—Whatamidoing (WMF) (talk)

15:17, 2. studenoga 2018. (CET)