MediaWiki - User contributions [en]

Beta Features/About/nl

2013-11-21T23:49:23Z

Myr:

{{PD Help Page}}

<languages />
[[File:BetaFeatures-Screenshot.png|thumb|240px|Schermafdruk van de nieuwe Beta-functiesvoorkeurpagina.]]

[[File:Media Viewer logo for BetaFeatures.svg|thumb|240px|Media Viewer is one of the new Beta Features being tested this week.]]

[[File:Typography logo for BetaFeatures.svg|thumb|240px|Typography Refresh is another of the new Beta Features being tested this week.]]

Welcome to [[mw:About Beta Features|Beta Features]], a new program that lets you test new features on Wikipedia and other Wikimedia sites before they are released for everyone.

The Beta Features program lets developers roll out new software in an environment where lots of users can use these features, then give feedback to help make them better. Think of it as a digital laboratory where community members can preview upcoming changes and help designers and engineers make improvements based on their suggestions.

== Eerste functies ==
Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

;[[mw:Multimedia/About Media Viewer|Media Viewer]]:Improve your multimedia viewing experience with this new tool. Media Viewer displays images in larger size on pages that have thumbnails. Images are shown in a nicer 'light box' overlay, and can also be viewed in full size. [[mw:Talk:Multimedia/Media Viewer|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/General|VisualEditor]]:VisualEditor makes it easy to edit pages [http://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ without having to learn wiki code]. Beta Features will include an opt-in version of this tool on sites where it is available but not enabled by default. We're also adding new experimental features that enhance VisualEditor (see below). [[mw:Talk:VisualEditor/Beta_Features/General|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/Formulae|VisualEditor Formulæ]]:With this opt-in feature, you can add support inside VisualEditor for creating and editing mathematical formulæ like algebra or equations on pages you're working on. [[mw:Talk:VisualEditor/Beta_Features/Formulae|Discuss this feature]].

;[[mw:Typography Update|Typography Refresh]]:This beta feature makes text more readable, accessible and consistent. It updates the Vector skin to use 'serif' fonts in section headings and 'sans serif' fonts in the body copy, for a better visual experience. <s>(This feature is now scheduled for release by November 14)</s>. [[mw:Talk:Typography Update|Discuss this feature]].

== How you can help ==

Can you help us test Beta Features in coming days? Our first features are now available for early testing by logged-in users on [[mw:Special:Preferences#mw-prefsection-betafeatures|MediaWiki.org]], on [[m:Special:Preferences#mw-prefsection-betafeatures|Meta.Wikimedia.org]] and on [[commons:Special:Preferences#mw-prefsection-betafeatures|Wikimedia Commons]]. Based on test results, we aim to release it on all wikis worldwide on 21 November, 2013.

To test new features, check the items you want in the [[mw:Special:Preferences#mw-prefsection-betafeatures|new BetaFeatures section]] of your user preferences — and click '{{int:saveprefs}}' (see screenshot). You can also automatically enable all new beta features as they are released or turn off any of these options at any time. To make it easier for you, a small '{{int:betafeatures-toplink}}' link will show up next to '{{int:mypreferences}}' in your personal menu when this extension is released worldwide in early November.

Try out Beta Features and let us know what you think of this program on [[mw:Talk:About_Beta_Features|this discussion page]]. You can also comment on each feature's discussion page (see links above and on your Beta Features preferences page). If you find any technical bugs, please [https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=BetaFeatures report them here]. For technical documentation, visit the [[mw:Extension:BetaFeatures|BetaFeatures extension page]].

To discuss this project with our team after this first release, we invite you to join our [[m:IRC_office_hours#Upcoming_office_hours|IRC office hours chat]] on Friday, 8 November, 2013 at 10:30am PST, 18:30 UTC. After testing and improving Beta Features for a couple weeks on these three sites, we plan to release this project on on all wikis worldwide on Thursday, 21 November, 2013.

Beta Features was created by the Wikimedia Foundation's [[mw:Design|Design]], [[mw:Multimedia|Multimedia team]] and [[mw:VisualEditor|VisualEditor]] teams. These and other teams will be adding more features every few weeks, going forward. We also invite community developers to start testing their new improvements in Beta Features in coming weeks by working closely with WMF designers and engineers. To prepare a new Beta Feature, read [[mw:Beta Features/Package|these helpful tips]], check [[mw:Extension:BetaFeatures|this technical documentation]] and post your submission on the [[mw:Beta Features/New Features|queue for new Beta Features]].

== Erkenningen ==

Beta Features was brought to you by many Wikimedia Foundation team members, including: [[mw:User:Fabrice Florin (WMF)|Fabrice Florin]], [[mw:User:Jdforrester_(WMF)|James Forrester]], [[mw:User:MarkTraceur|Mark Holmquist]], [[mw:User:JZimmerman_(WMF)|Jared Zimmerman]], [[w:User:Jon_(WMF)|Jon Robson]], [[mw:User:ESanders_(WMF)|Ed Sanders]], [[m:User:Tgr|Gergő Tisza]], [[mw:User:BDavis_(WMF)|Bryan Davis]], [[wmf:User:MGalloway (WMF)|May Galloway]], [[mw:User:Keegan (WMF)|Keegan Peterzell]], [[mw:User:Mdennis (WMF)|Maggie Dennis]], [[mw:User:Qgil|Quim Gil]], [[mw:User:Eloquence|Erik Moeller]], [[mw:User:Howief|Howie Fung]], [[mw:User:RobLa-WMF|Rob Lanphier]], and [[mw:User:Tfinc|Tomasz Finc]], to name but a few. We're also grateful to all the community and team members who helped create this system — and look forward to many more productive collaborations in the future.

Have fun, and don't forget to [[mw:Talk:About_Beta_Features|let us know what you think]]!

Translations:About Beta Features/6/nl

2013-11-21T23:49:22Z

Myr:

== Eerste functies ==
Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

Beta Features/About/nl

2013-11-21T23:48:11Z

Myr: Created page with "Schermafdruk van de nieuwe Beta-functiesvoorkeurpagina."

{{PD Help Page}}

<languages />
[[File:BetaFeatures-Screenshot.png|thumb|240px|Schermafdruk van de nieuwe Beta-functiesvoorkeurpagina.]]

[[File:Media Viewer logo for BetaFeatures.svg|thumb|240px|Media Viewer is one of the new Beta Features being tested this week.]]

[[File:Typography logo for BetaFeatures.svg|thumb|240px|Typography Refresh is another of the new Beta Features being tested this week.]]

Welcome to [[mw:About Beta Features|Beta Features]], a new program that lets you test new features on Wikipedia and other Wikimedia sites before they are released for everyone.

The Beta Features program lets developers roll out new software in an environment where lots of users can use these features, then give feedback to help make them better. Think of it as a digital laboratory where community members can preview upcoming changes and help designers and engineers make improvements based on their suggestions.

== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

;[[mw:Multimedia/About Media Viewer|Media Viewer]]:Improve your multimedia viewing experience with this new tool. Media Viewer displays images in larger size on pages that have thumbnails. Images are shown in a nicer 'light box' overlay, and can also be viewed in full size. [[mw:Talk:Multimedia/Media Viewer|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/General|VisualEditor]]:VisualEditor makes it easy to edit pages [http://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ without having to learn wiki code]. Beta Features will include an opt-in version of this tool on sites where it is available but not enabled by default. We're also adding new experimental features that enhance VisualEditor (see below). [[mw:Talk:VisualEditor/Beta_Features/General|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/Formulae|VisualEditor Formulæ]]:With this opt-in feature, you can add support inside VisualEditor for creating and editing mathematical formulæ like algebra or equations on pages you're working on. [[mw:Talk:VisualEditor/Beta_Features/Formulae|Discuss this feature]].

;[[mw:Typography Update|Typography Refresh]]:This beta feature makes text more readable, accessible and consistent. It updates the Vector skin to use 'serif' fonts in section headings and 'sans serif' fonts in the body copy, for a better visual experience. <s>(This feature is now scheduled for release by November 14)</s>. [[mw:Talk:Typography Update|Discuss this feature]].

== How you can help ==

Can you help us test Beta Features in coming days? Our first features are now available for early testing by logged-in users on [[mw:Special:Preferences#mw-prefsection-betafeatures|MediaWiki.org]], on [[m:Special:Preferences#mw-prefsection-betafeatures|Meta.Wikimedia.org]] and on [[commons:Special:Preferences#mw-prefsection-betafeatures|Wikimedia Commons]]. Based on test results, we aim to release it on all wikis worldwide on 21 November, 2013.

To test new features, check the items you want in the [[mw:Special:Preferences#mw-prefsection-betafeatures|new BetaFeatures section]] of your user preferences — and click '{{int:saveprefs}}' (see screenshot). You can also automatically enable all new beta features as they are released or turn off any of these options at any time. To make it easier for you, a small '{{int:betafeatures-toplink}}' link will show up next to '{{int:mypreferences}}' in your personal menu when this extension is released worldwide in early November.

Try out Beta Features and let us know what you think of this program on [[mw:Talk:About_Beta_Features|this discussion page]]. You can also comment on each feature's discussion page (see links above and on your Beta Features preferences page). If you find any technical bugs, please [https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=BetaFeatures report them here]. For technical documentation, visit the [[mw:Extension:BetaFeatures|BetaFeatures extension page]].

To discuss this project with our team after this first release, we invite you to join our [[m:IRC_office_hours#Upcoming_office_hours|IRC office hours chat]] on Friday, 8 November, 2013 at 10:30am PST, 18:30 UTC. After testing and improving Beta Features for a couple weeks on these three sites, we plan to release this project on on all wikis worldwide on Thursday, 21 November, 2013.

Beta Features was created by the Wikimedia Foundation's [[mw:Design|Design]], [[mw:Multimedia|Multimedia team]] and [[mw:VisualEditor|VisualEditor]] teams. These and other teams will be adding more features every few weeks, going forward. We also invite community developers to start testing their new improvements in Beta Features in coming weeks by working closely with WMF designers and engineers. To prepare a new Beta Feature, read [[mw:Beta Features/Package|these helpful tips]], check [[mw:Extension:BetaFeatures|this technical documentation]] and post your submission on the [[mw:Beta Features/New Features|queue for new Beta Features]].

== Erkenningen ==

Beta Features was brought to you by many Wikimedia Foundation team members, including: [[mw:User:Fabrice Florin (WMF)|Fabrice Florin]], [[mw:User:Jdforrester_(WMF)|James Forrester]], [[mw:User:MarkTraceur|Mark Holmquist]], [[mw:User:JZimmerman_(WMF)|Jared Zimmerman]], [[w:User:Jon_(WMF)|Jon Robson]], [[mw:User:ESanders_(WMF)|Ed Sanders]], [[m:User:Tgr|Gergő Tisza]], [[mw:User:BDavis_(WMF)|Bryan Davis]], [[wmf:User:MGalloway (WMF)|May Galloway]], [[mw:User:Keegan (WMF)|Keegan Peterzell]], [[mw:User:Mdennis (WMF)|Maggie Dennis]], [[mw:User:Qgil|Quim Gil]], [[mw:User:Eloquence|Erik Moeller]], [[mw:User:Howief|Howie Fung]], [[mw:User:RobLa-WMF|Rob Lanphier]], and [[mw:User:Tfinc|Tomasz Finc]], to name but a few. We're also grateful to all the community and team members who helped create this system — and look forward to many more productive collaborations in the future.

Have fun, and don't forget to [[mw:Talk:About_Beta_Features|let us know what you think]]!

Translations:About Beta Features/1/nl

2013-11-21T23:48:11Z

Myr: Created page with "Schermafdruk van de nieuwe Beta-functiesvoorkeurpagina."

[[File:BetaFeatures-Screenshot.png|thumb|240px|Schermafdruk van de nieuwe Beta-functiesvoorkeurpagina.]]

Beta Features/About/nl

2013-11-21T23:45:52Z

Myr: Created page with "== Erkenningen =="

{{PD Help Page}}

<languages />
[[File:BetaFeatures-Screenshot.png|thumb|240px|Screenshot of the new Beta Features preferences page.]]

[[File:Media Viewer logo for BetaFeatures.svg|thumb|240px|Media Viewer is one of the new Beta Features being tested this week.]]

[[File:Typography logo for BetaFeatures.svg|thumb|240px|Typography Refresh is another of the new Beta Features being tested this week.]]

Welcome to [[mw:About Beta Features|Beta Features]], a new program that lets you test new features on Wikipedia and other Wikimedia sites before they are released for everyone.

The Beta Features program lets developers roll out new software in an environment where lots of users can use these features, then give feedback to help make them better. Think of it as a digital laboratory where community members can preview upcoming changes and help designers and engineers make improvements based on their suggestions.

== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

;[[mw:Multimedia/About Media Viewer|Media Viewer]]:Improve your multimedia viewing experience with this new tool. Media Viewer displays images in larger size on pages that have thumbnails. Images are shown in a nicer 'light box' overlay, and can also be viewed in full size. [[mw:Talk:Multimedia/Media Viewer|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/General|VisualEditor]]:VisualEditor makes it easy to edit pages [http://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ without having to learn wiki code]. Beta Features will include an opt-in version of this tool on sites where it is available but not enabled by default. We're also adding new experimental features that enhance VisualEditor (see below). [[mw:Talk:VisualEditor/Beta_Features/General|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/Formulae|VisualEditor Formulæ]]:With this opt-in feature, you can add support inside VisualEditor for creating and editing mathematical formulæ like algebra or equations on pages you're working on. [[mw:Talk:VisualEditor/Beta_Features/Formulae|Discuss this feature]].

;[[mw:Typography Update|Typography Refresh]]:This beta feature makes text more readable, accessible and consistent. It updates the Vector skin to use 'serif' fonts in section headings and 'sans serif' fonts in the body copy, for a better visual experience. <s>(This feature is now scheduled for release by November 14)</s>. [[mw:Talk:Typography Update|Discuss this feature]].

== How you can help ==

Can you help us test Beta Features in coming days? Our first features are now available for early testing by logged-in users on [[mw:Special:Preferences#mw-prefsection-betafeatures|MediaWiki.org]], on [[m:Special:Preferences#mw-prefsection-betafeatures|Meta.Wikimedia.org]] and on [[commons:Special:Preferences#mw-prefsection-betafeatures|Wikimedia Commons]]. Based on test results, we aim to release it on all wikis worldwide on 21 November, 2013.

To test new features, check the items you want in the [[mw:Special:Preferences#mw-prefsection-betafeatures|new BetaFeatures section]] of your user preferences — and click '{{int:saveprefs}}' (see screenshot). You can also automatically enable all new beta features as they are released or turn off any of these options at any time. To make it easier for you, a small '{{int:betafeatures-toplink}}' link will show up next to '{{int:mypreferences}}' in your personal menu when this extension is released worldwide in early November.

Try out Beta Features and let us know what you think of this program on [[mw:Talk:About_Beta_Features|this discussion page]]. You can also comment on each feature's discussion page (see links above and on your Beta Features preferences page). If you find any technical bugs, please [https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=BetaFeatures report them here]. For technical documentation, visit the [[mw:Extension:BetaFeatures|BetaFeatures extension page]].

To discuss this project with our team after this first release, we invite you to join our [[m:IRC_office_hours#Upcoming_office_hours|IRC office hours chat]] on Friday, 8 November, 2013 at 10:30am PST, 18:30 UTC. After testing and improving Beta Features for a couple weeks on these three sites, we plan to release this project on on all wikis worldwide on Thursday, 21 November, 2013.

Beta Features was created by the Wikimedia Foundation's [[mw:Design|Design]], [[mw:Multimedia|Multimedia team]] and [[mw:VisualEditor|VisualEditor]] teams. These and other teams will be adding more features every few weeks, going forward. We also invite community developers to start testing their new improvements in Beta Features in coming weeks by working closely with WMF designers and engineers. To prepare a new Beta Feature, read [[mw:Beta Features/Package|these helpful tips]], check [[mw:Extension:BetaFeatures|this technical documentation]] and post your submission on the [[mw:Beta Features/New Features|queue for new Beta Features]].

== Erkenningen ==

Beta Features was brought to you by many Wikimedia Foundation team members, including: [[mw:User:Fabrice Florin (WMF)|Fabrice Florin]], [[mw:User:Jdforrester_(WMF)|James Forrester]], [[mw:User:MarkTraceur|Mark Holmquist]], [[mw:User:JZimmerman_(WMF)|Jared Zimmerman]], [[w:User:Jon_(WMF)|Jon Robson]], [[mw:User:ESanders_(WMF)|Ed Sanders]], [[m:User:Tgr|Gergő Tisza]], [[mw:User:BDavis_(WMF)|Bryan Davis]], [[wmf:User:MGalloway (WMF)|May Galloway]], [[mw:User:Keegan (WMF)|Keegan Peterzell]], [[mw:User:Mdennis (WMF)|Maggie Dennis]], [[mw:User:Qgil|Quim Gil]], [[mw:User:Eloquence|Erik Moeller]], [[mw:User:Howief|Howie Fung]], [[mw:User:RobLa-WMF|Rob Lanphier]], and [[mw:User:Tfinc|Tomasz Finc]], to name but a few. We're also grateful to all the community and team members who helped create this system — and look forward to many more productive collaborations in the future.

Have fun, and don't forget to [[mw:Talk:About_Beta_Features|let us know what you think]]!

Translations:About Beta Features/16/nl

2013-11-21T23:45:51Z

Myr: Created page with "== Erkenningen =="

== Erkenningen ==

Beta Features/About/nl

2013-11-21T23:45:24Z

Myr: Created page with "== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:"

{{PD Help Page}}

<languages />
[[File:BetaFeatures-Screenshot.png|thumb|240px|Screenshot of the new Beta Features preferences page.]]

[[File:Media Viewer logo for BetaFeatures.svg|thumb|240px|Media Viewer is one of the new Beta Features being tested this week.]]

[[File:Typography logo for BetaFeatures.svg|thumb|240px|Typography Refresh is another of the new Beta Features being tested this week.]]

Welcome to [[mw:About Beta Features|Beta Features]], a new program that lets you test new features on Wikipedia and other Wikimedia sites before they are released for everyone.

The Beta Features program lets developers roll out new software in an environment where lots of users can use these features, then give feedback to help make them better. Think of it as a digital laboratory where community members can preview upcoming changes and help designers and engineers make improvements based on their suggestions.

== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

;[[mw:Multimedia/About Media Viewer|Media Viewer]]:Improve your multimedia viewing experience with this new tool. Media Viewer displays images in larger size on pages that have thumbnails. Images are shown in a nicer 'light box' overlay, and can also be viewed in full size. [[mw:Talk:Multimedia/Media Viewer|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/General|VisualEditor]]:VisualEditor makes it easy to edit pages [http://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ without having to learn wiki code]. Beta Features will include an opt-in version of this tool on sites where it is available but not enabled by default. We're also adding new experimental features that enhance VisualEditor (see below). [[mw:Talk:VisualEditor/Beta_Features/General|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/Formulae|VisualEditor Formulæ]]:With this opt-in feature, you can add support inside VisualEditor for creating and editing mathematical formulæ like algebra or equations on pages you're working on. [[mw:Talk:VisualEditor/Beta_Features/Formulae|Discuss this feature]].

;[[mw:Typography Update|Typography Refresh]]:This beta feature makes text more readable, accessible and consistent. It updates the Vector skin to use 'serif' fonts in section headings and 'sans serif' fonts in the body copy, for a better visual experience. <s>(This feature is now scheduled for release by November 14)</s>. [[mw:Talk:Typography Update|Discuss this feature]].

== How you can help ==

Can you help us test Beta Features in coming days? Our first features are now available for early testing by logged-in users on [[mw:Special:Preferences#mw-prefsection-betafeatures|MediaWiki.org]], on [[m:Special:Preferences#mw-prefsection-betafeatures|Meta.Wikimedia.org]] and on [[commons:Special:Preferences#mw-prefsection-betafeatures|Wikimedia Commons]]. Based on test results, we aim to release it on all wikis worldwide on 21 November, 2013.

To test new features, check the items you want in the [[mw:Special:Preferences#mw-prefsection-betafeatures|new BetaFeatures section]] of your user preferences — and click '{{int:saveprefs}}' (see screenshot). You can also automatically enable all new beta features as they are released or turn off any of these options at any time. To make it easier for you, a small '{{int:betafeatures-toplink}}' link will show up next to '{{int:mypreferences}}' in your personal menu when this extension is released worldwide in early November.

Try out Beta Features and let us know what you think of this program on [[mw:Talk:About_Beta_Features|this discussion page]]. You can also comment on each feature's discussion page (see links above and on your Beta Features preferences page). If you find any technical bugs, please [https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=BetaFeatures report them here]. For technical documentation, visit the [[mw:Extension:BetaFeatures|BetaFeatures extension page]].

To discuss this project with our team after this first release, we invite you to join our [[m:IRC_office_hours#Upcoming_office_hours|IRC office hours chat]] on Friday, 8 November, 2013 at 10:30am PST, 18:30 UTC. After testing and improving Beta Features for a couple weeks on these three sites, we plan to release this project on on all wikis worldwide on Thursday, 21 November, 2013.

Beta Features was created by the Wikimedia Foundation's [[mw:Design|Design]], [[mw:Multimedia|Multimedia team]] and [[mw:VisualEditor|VisualEditor]] teams. These and other teams will be adding more features every few weeks, going forward. We also invite community developers to start testing their new improvements in Beta Features in coming weeks by working closely with WMF designers and engineers. To prepare a new Beta Feature, read [[mw:Beta Features/Package|these helpful tips]], check [[mw:Extension:BetaFeatures|this technical documentation]] and post your submission on the [[mw:Beta Features/New Features|queue for new Beta Features]].

== Acknowledgements ==

Beta Features was brought to you by many Wikimedia Foundation team members, including: [[mw:User:Fabrice Florin (WMF)|Fabrice Florin]], [[mw:User:Jdforrester_(WMF)|James Forrester]], [[mw:User:MarkTraceur|Mark Holmquist]], [[mw:User:JZimmerman_(WMF)|Jared Zimmerman]], [[w:User:Jon_(WMF)|Jon Robson]], [[mw:User:ESanders_(WMF)|Ed Sanders]], [[m:User:Tgr|Gergő Tisza]], [[mw:User:BDavis_(WMF)|Bryan Davis]], [[wmf:User:MGalloway (WMF)|May Galloway]], [[mw:User:Keegan (WMF)|Keegan Peterzell]], [[mw:User:Mdennis (WMF)|Maggie Dennis]], [[mw:User:Qgil|Quim Gil]], [[mw:User:Eloquence|Erik Moeller]], [[mw:User:Howief|Howie Fung]], [[mw:User:RobLa-WMF|Rob Lanphier]], and [[mw:User:Tfinc|Tomasz Finc]], to name but a few. We're also grateful to all the community and team members who helped create this system — and look forward to many more productive collaborations in the future.

Have fun, and don't forget to [[mw:Talk:About_Beta_Features|let us know what you think]]!

Translations:About Beta Features/6/nl

2013-11-21T23:45:24Z

Myr: Created page with "== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:"

== Eerste functies == Hier zijn de eerste beta-functies die we zullen testen vanaf volgende week:

Translations:About Beta Features/Page display title/nl

2013-11-21T23:45:18Z

Myr:

Over de Beta-functies

Beta Features/About/nl

2013-11-21T23:43:01Z

Myr: Created page with "Over de Beta Functies"

{{PD Help Page}}

<languages />
[[File:BetaFeatures-Screenshot.png|thumb|240px|Screenshot of the new Beta Features preferences page.]]

[[File:Media Viewer logo for BetaFeatures.svg|thumb|240px|Media Viewer is one of the new Beta Features being tested this week.]]

[[File:Typography logo for BetaFeatures.svg|thumb|240px|Typography Refresh is another of the new Beta Features being tested this week.]]

Welcome to [[mw:About Beta Features|Beta Features]], a new program that lets you test new features on Wikipedia and other Wikimedia sites before they are released for everyone.

The Beta Features program lets developers roll out new software in an environment where lots of users can use these features, then give feedback to help make them better. Think of it as a digital laboratory where community members can preview upcoming changes and help designers and engineers make improvements based on their suggestions.

== Initial features ==
Here are the first beta features which we will start testing next week:

;[[mw:Multimedia/About Media Viewer|Media Viewer]]:Improve your multimedia viewing experience with this new tool. Media Viewer displays images in larger size on pages that have thumbnails. Images are shown in a nicer 'light box' overlay, and can also be viewed in full size. [[mw:Talk:Multimedia/Media Viewer|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/General|VisualEditor]]:VisualEditor makes it easy to edit pages [http://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ without having to learn wiki code]. Beta Features will include an opt-in version of this tool on sites where it is available but not enabled by default. We're also adding new experimental features that enhance VisualEditor (see below). [[mw:Talk:VisualEditor/Beta_Features/General|Discuss this feature]].

;[[mw:VisualEditor/Beta_Features/Formulae|VisualEditor Formulæ]]:With this opt-in feature, you can add support inside VisualEditor for creating and editing mathematical formulæ like algebra or equations on pages you're working on. [[mw:Talk:VisualEditor/Beta_Features/Formulae|Discuss this feature]].

;[[mw:Typography Update|Typography Refresh]]:This beta feature makes text more readable, accessible and consistent. It updates the Vector skin to use 'serif' fonts in section headings and 'sans serif' fonts in the body copy, for a better visual experience. <s>(This feature is now scheduled for release by November 14)</s>. [[mw:Talk:Typography Update|Discuss this feature]].

== How you can help ==

Can you help us test Beta Features in coming days? Our first features are now available for early testing by logged-in users on [[mw:Special:Preferences#mw-prefsection-betafeatures|MediaWiki.org]], on [[m:Special:Preferences#mw-prefsection-betafeatures|Meta.Wikimedia.org]] and on [[commons:Special:Preferences#mw-prefsection-betafeatures|Wikimedia Commons]]. Based on test results, we aim to release it on all wikis worldwide on 21 November, 2013.

To test new features, check the items you want in the [[mw:Special:Preferences#mw-prefsection-betafeatures|new BetaFeatures section]] of your user preferences — and click '{{int:saveprefs}}' (see screenshot). You can also automatically enable all new beta features as they are released or turn off any of these options at any time. To make it easier for you, a small '{{int:betafeatures-toplink}}' link will show up next to '{{int:mypreferences}}' in your personal menu when this extension is released worldwide in early November.

Try out Beta Features and let us know what you think of this program on [[mw:Talk:About_Beta_Features|this discussion page]]. You can also comment on each feature's discussion page (see links above and on your Beta Features preferences page). If you find any technical bugs, please [https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=BetaFeatures report them here]. For technical documentation, visit the [[mw:Extension:BetaFeatures|BetaFeatures extension page]].

To discuss this project with our team after this first release, we invite you to join our [[m:IRC_office_hours#Upcoming_office_hours|IRC office hours chat]] on Friday, 8 November, 2013 at 10:30am PST, 18:30 UTC. After testing and improving Beta Features for a couple weeks on these three sites, we plan to release this project on on all wikis worldwide on Thursday, 21 November, 2013.

Beta Features was created by the Wikimedia Foundation's [[mw:Design|Design]], [[mw:Multimedia|Multimedia team]] and [[mw:VisualEditor|VisualEditor]] teams. These and other teams will be adding more features every few weeks, going forward. We also invite community developers to start testing their new improvements in Beta Features in coming weeks by working closely with WMF designers and engineers. To prepare a new Beta Feature, read [[mw:Beta Features/Package|these helpful tips]], check [[mw:Extension:BetaFeatures|this technical documentation]] and post your submission on the [[mw:Beta Features/New Features|queue for new Beta Features]].

== Acknowledgements ==

Beta Features was brought to you by many Wikimedia Foundation team members, including: [[mw:User:Fabrice Florin (WMF)|Fabrice Florin]], [[mw:User:Jdforrester_(WMF)|James Forrester]], [[mw:User:MarkTraceur|Mark Holmquist]], [[mw:User:JZimmerman_(WMF)|Jared Zimmerman]], [[w:User:Jon_(WMF)|Jon Robson]], [[mw:User:ESanders_(WMF)|Ed Sanders]], [[m:User:Tgr|Gergő Tisza]], [[mw:User:BDavis_(WMF)|Bryan Davis]], [[wmf:User:MGalloway (WMF)|May Galloway]], [[mw:User:Keegan (WMF)|Keegan Peterzell]], [[mw:User:Mdennis (WMF)|Maggie Dennis]], [[mw:User:Qgil|Quim Gil]], [[mw:User:Eloquence|Erik Moeller]], [[mw:User:Howief|Howie Fung]], [[mw:User:RobLa-WMF|Rob Lanphier]], and [[mw:User:Tfinc|Tomasz Finc]], to name but a few. We're also grateful to all the community and team members who helped create this system — and look forward to many more productive collaborations in the future.

Have fun, and don't forget to [[mw:Talk:About_Beta_Features|let us know what you think]]!

Translations:About Beta Features/Page display title/nl

2013-11-21T23:43:00Z

Myr: Created page with "Over de Beta Functies"

Over de Beta Functies

Help:Extension:Translate/Quality assurance/nl

2013-11-21T23:38:06Z

Myr: Created page with "Het is (momenteel) niet mogelijk om logboekvermeldingen van vertalingsbeoordelingen uit te sluiten van de controlelijst, e-mailberichten van de controlelijst of recente wijzig..."

<languages/>__NOEDITSECTION__

High quality can only be reached when everyone does their part: we have summarized some [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|translation best practices]] that should be followed. Whether you are a translator or a translation administrator, the Translate extension provides you the tools to produce higher quality translations. In [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|statistics and reporting]] we have described the many tools which allow translators to find where their effort is needed and translation administrators to monitor the progress. In this page we explain the '''quality assurance''' technical tools that encourage translators to work together to improve their translations. Translation reviewing is a very important task and the provided tools make it possible to increase and assess the quality of translations.

== Translation review features ==
[[File:Translate documentation - Quality - Review translator.png|thumb|300px|Translators are shown how many users have reviewed each translation; note the gray check-mark and the pencil icon which you have to click to edit the translation]]
The access to the review tools is controlled by user right. The Translate extension by default adds an user group called ''translation reviewers''. In review view the reviewers can indicate that they think the translation is correct and good by clicking a button.
The software keeps track of reviewed translations so that reviewers don't need to review same translations again. Users can only review translations they haven't made themselves. Multiple people can review any translation.

Message documentation plays an important role here as well. The reviewer needs to be sure not only that the translation has the correct spelling and terminology, but also that it is suitable for the context.

=== Voor vertalers ===

Het aantal mensen die een vertaling hebben beoordeeld wordt getoond naast de beoordelingsactie van elk bericht.

Of more interest, translators see in their watchlist when any of their translation has been reviewed. This is useful because they can see that someone is looking at their work and appreciating it, and that they're not left alone or ignored, so they can be more confident about translating.

Het is (momenteel) niet mogelijk om logboekvermeldingen van vertalingsbeoordelingen uit te sluiten van de controlelijst, e-mailberichten van de controlelijst of recente wijzigingen.
[[File:Translate documentation - Quality - Recent accept inline.png|thumb|300px|The small person icon indicates an own translation and replaces the review button. In this screenshot the new inline editor is shown too]]
=== For reviewers ===

Translation review is performed on [[Special:Translate|Special:Translate]]: the "mark as reviewed" check-mark is shown in the review view.
Reviewers can review translations for any message group or choose the ''Recent translations'' message group to review latest translations.

Translations made by yourself can be hidden by clicking the hide button in the action bar at the bottom of the view. If not hidden, they have a small person icon. Filled (black) check-mark means that you have already marked the translation as reviewed. Empty check-mark (white on gray background) means that you will be the first reviewer of the translation. Gray check-mark means that the translation has been already reviewed by others, but not by you.

=== For other reviewers ===

Other reviewers benefit from knowing that some messages have already been reviewed, and by how many users. In fact, they can choose to focus review efforts on unreviewed translations in the group, using the relevant selector. Such translations might also have been left unreviewed by an unsure reviewer and require more attention because there is no way for the translator to report an uncertain translation.
[[File:Translate documentation - Quality - Recent editor.png|thumb|300px|Reviewing the recent translation group, with the editor opened]]
== Reviewing recent translations ==

The "recent translations" group is perhaps the most useful translation review feature. It can replace [[Special:RecentChanges|Special:RecentChanges]] and [[Special:WatchList|Special:WatchList]] for some uses.

In this page you can immediately see all translations you can review (and only them, if you use the filter for own translations). Most of the needed information is there and more is shown when you open the translation editor.

The initial review of message groups is better done one group at a time rather than in chronological order. The next section provides you a divide and conquer solution to decrease the review backlog.

== Systematic review ==

Translation review makes into a real joy the hard job of proofreading a whole message group to keep it at an high level of quality and consistency.

If you know a message group well, you can open it for review and choose all translated messages and go through it all at once. Now you can check that messages have been correctly interpreted and improve their documentation; and ensure that source terms have been translated in the same way everywhere, with the help of the translation memory and the searchbar keyword-filter.

The next time, you'll only have to open the group again and skim it for the icons indicating new translations which need review; you won't need to closely follow recent changes nor to watchlist all messages, which are respectively too crowded and not practical.

Translation memory can help a little to keep the wording of similar messages consistent. It cannot enforce consistent use of terms in different kinds of messages. There is no technical solution for this problem yet, but you now have a handy tool to impose consistency piece by piece. It's a good achievement to have consistent translations at least across a whole message group, especially if it uses special terms which are hard to understand. In such cases more than usual, different translators might translate the messages, using different terms and resulting in a confusing overall translation. Moreover, if consistency is improved, the suggestions given by translation memory are more consistent and this should improve consistency among all message groups.
[[File:Translate manual - Translate example - 11. Outdated untranslated.png|thumb|300px|A message group with state (just set yet) on the top left]]
== Workflows ==

The Translate extension is designed for publishing translations as soon as possible to show translators the impact of their work. If you want to be sure that translations are of good quality before using them, you can use a more formal process. You can implement a workflow through [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states]].

Reviewing of translation does not have any effect on the appearance or usage of translations, so it's a quite different tool than the [[Extension:FlaggedRevs|Flagged revisions extension]]: the scope of translation reviewing is not to find and provide to its readers the best translation among those available, but to encourage quality work on translations.

Reviewing of translation can be combined with message group workflow states by having a proofreading state to be used by proofreaders to coordinate. As explained in more detail in the relevant page, the two features do not interact with each other: they are controlled separately by the users.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Quality assurance/9/nl

2013-11-21T23:38:05Z

Het is (momenteel) niet mogelijk om logboekvermeldingen van vertalingsbeoordelingen uit te sluiten van de controlelijst, e-mailberichten van de controlelijst of recente wijzigingen.

Help:Extension:Translate/Quality assurance/nl

2013-11-21T23:35:17Z

Myr: Created page with "Het aantal mensen die een vertaling hebben beoordeeld wordt getoond naast de beoordelingsactie van elk bericht."

<languages/>__NOEDITSECTION__

High quality can only be reached when everyone does their part: we have summarized some [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|translation best practices]] that should be followed. Whether you are a translator or a translation administrator, the Translate extension provides you the tools to produce higher quality translations. In [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|statistics and reporting]] we have described the many tools which allow translators to find where their effort is needed and translation administrators to monitor the progress. In this page we explain the '''quality assurance''' technical tools that encourage translators to work together to improve their translations. Translation reviewing is a very important task and the provided tools make it possible to increase and assess the quality of translations.

== Translation review features ==
[[File:Translate documentation - Quality - Review translator.png|thumb|300px|Translators are shown how many users have reviewed each translation; note the gray check-mark and the pencil icon which you have to click to edit the translation]]
The access to the review tools is controlled by user right. The Translate extension by default adds an user group called ''translation reviewers''. In review view the reviewers can indicate that they think the translation is correct and good by clicking a button.
The software keeps track of reviewed translations so that reviewers don't need to review same translations again. Users can only review translations they haven't made themselves. Multiple people can review any translation.

Message documentation plays an important role here as well. The reviewer needs to be sure not only that the translation has the correct spelling and terminology, but also that it is suitable for the context.

=== Voor vertalers ===

Het aantal mensen die een vertaling hebben beoordeeld wordt getoond naast de beoordelingsactie van elk bericht.

Of more interest, translators see in their watchlist when any of their translation has been reviewed. This is useful because they can see that someone is looking at their work and appreciating it, and that they're not left alone or ignored, so they can be more confident about translating.

It's (currently) not possible to exclude translation review log entries from the watchlist, watchlist email notifications or recent changes.
[[File:Translate documentation - Quality - Recent accept inline.png|thumb|300px|The small person icon indicates an own translation and replaces the review button. In this screenshot the new inline editor is shown too]]
=== For reviewers ===

Translation review is performed on [[Special:Translate|Special:Translate]]: the "mark as reviewed" check-mark is shown in the review view.
Reviewers can review translations for any message group or choose the ''Recent translations'' message group to review latest translations.

Translations made by yourself can be hidden by clicking the hide button in the action bar at the bottom of the view. If not hidden, they have a small person icon. Filled (black) check-mark means that you have already marked the translation as reviewed. Empty check-mark (white on gray background) means that you will be the first reviewer of the translation. Gray check-mark means that the translation has been already reviewed by others, but not by you.

=== For other reviewers ===

Other reviewers benefit from knowing that some messages have already been reviewed, and by how many users. In fact, they can choose to focus review efforts on unreviewed translations in the group, using the relevant selector. Such translations might also have been left unreviewed by an unsure reviewer and require more attention because there is no way for the translator to report an uncertain translation.
[[File:Translate documentation - Quality - Recent editor.png|thumb|300px|Reviewing the recent translation group, with the editor opened]]
== Reviewing recent translations ==

The "recent translations" group is perhaps the most useful translation review feature. It can replace [[Special:RecentChanges|Special:RecentChanges]] and [[Special:WatchList|Special:WatchList]] for some uses.

In this page you can immediately see all translations you can review (and only them, if you use the filter for own translations). Most of the needed information is there and more is shown when you open the translation editor.

The initial review of message groups is better done one group at a time rather than in chronological order. The next section provides you a divide and conquer solution to decrease the review backlog.

== Systematic review ==

Translation review makes into a real joy the hard job of proofreading a whole message group to keep it at an high level of quality and consistency.

If you know a message group well, you can open it for review and choose all translated messages and go through it all at once. Now you can check that messages have been correctly interpreted and improve their documentation; and ensure that source terms have been translated in the same way everywhere, with the help of the translation memory and the searchbar keyword-filter.

The next time, you'll only have to open the group again and skim it for the icons indicating new translations which need review; you won't need to closely follow recent changes nor to watchlist all messages, which are respectively too crowded and not practical.

Translation memory can help a little to keep the wording of similar messages consistent. It cannot enforce consistent use of terms in different kinds of messages. There is no technical solution for this problem yet, but you now have a handy tool to impose consistency piece by piece. It's a good achievement to have consistent translations at least across a whole message group, especially if it uses special terms which are hard to understand. In such cases more than usual, different translators might translate the messages, using different terms and resulting in a confusing overall translation. Moreover, if consistency is improved, the suggestions given by translation memory are more consistent and this should improve consistency among all message groups.
[[File:Translate manual - Translate example - 11. Outdated untranslated.png|thumb|300px|A message group with state (just set yet) on the top left]]
== Workflows ==

The Translate extension is designed for publishing translations as soon as possible to show translators the impact of their work. If you want to be sure that translations are of good quality before using them, you can use a more formal process. You can implement a workflow through [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states]].

Reviewing of translation does not have any effect on the appearance or usage of translations, so it's a quite different tool than the [[Extension:FlaggedRevs|Flagged revisions extension]]: the scope of translation reviewing is not to find and provide to its readers the best translation among those available, but to encourage quality work on translations.

Reviewing of translation can be combined with message group workflow states by having a proofreading state to be used by proofreaders to coordinate. As explained in more detail in the relevant page, the two features do not interact with each other: they are controlled separately by the users.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Quality assurance/7/nl

2013-11-21T23:35:16Z

Myr: Created page with "Het aantal mensen die een vertaling hebben beoordeeld wordt getoond naast de beoordelingsactie van elk bericht."

Het aantal mensen die een vertaling hebben beoordeeld wordt getoond naast de beoordelingsactie van elk bericht.

Help:Extension:Translate/nl

2013-11-21T23:32:46Z

Myr: Created page with "===Gerelateerd==="

<languages/>[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|The main special page of the extension, "[[Special:Translate]]", in its most common task, "view all untranslated messages"]]
__NOEDITSECTION__
The [[Extension:Translate|Translate extension]] enhances MediaWiki with essential features needed to do translation work. It can be used to translate the content pages, the interface of the wiki and even other software products, as it is used at [[translatewiki|translatewiki.net]]. The Translate extension comes with an easy to use translation interface and can separate the content structure from the text content that needs to be translated, showing only the translatable text to translators by splitting the content into manageable units. Each unit is automatically tracked for changes, and translators immediately see what needs updating on a specific page or throughout the wiki.

The Translate extension is used to translate the user interface of MediaWiki and other software projects at translatewiki.net by hundreds of translators every month. At [http://userbase.kde.org userbase.kde.org] it is used to translate almost a thousand content pages with user documentation. It is easy to start using the Translate extension, but at the same time it also scales up and provides advanced reporting, reviewing and workflow features.

== Functionaliteit ==
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|De tekstverwerker voor vertalingen: een bericht met een tip (niet zichtbaar in de afbeelding) en een suggesties van twee hulptalen]]

'''Interface:''' The main feature of the Translate extension is a simple yet functional translation interface. Besides the essential information like message definition and documentation, you can also view translations in other languages. If a definition has changed, you will see the changes. The extension comes with some built-in checks, that can help with common mistakes like unbalanced brackets and unused variables. Depending on the configuration, there are also suggestions from translation memory and machine translation services like those of Google Translate, Microsoft's Bing Translator and Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs than can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the [[:en:Gettext|Gettext po]] file format.

'''Message groups and tasks:''' Many of the features are built around two basic concepts: message groups and tasks.

A message group represents a collection of messages. One content page would be one message group, where, in the simplest form, each paragraph would be one message in that group. Messages used in each MediaWiki extension form a message group on translatewiki.net – a few of the largest extensions have multiple groups. You can also make a group of groups, like ''All newsletters'' or ''All Translate extension messages''. Many of the statistics and the tasks work on the message group basis.

The tasks, or in other words different listings of messages in a message group, facilitate different use cases. Normally a translator gets a list of all untranslated messages in a chosen message group, but there are tasks where you can review messages or just get a list of all messages, translated or not.

[[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Op deze speciale pagina wordt gerapporteerd over de vertaalstatus van iedere berichtengroep]]

'''Reporting and statistics:''' The extension has extensive [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|reporting features]] ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

'''Content translation:''' If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they can not work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the <nowiki><languages /></nowiki> tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form <nowiki>[[Special:MyLanguage/Pagename]]</nowiki>.

For more information see the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to set up a content page for translation]] and the [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|in-depth documentation of the page translation feature]].

'''Developers:''' The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

== Gebruiksmogelijkheden ==

You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general ''Translate'' performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are '''content translation''', '''local interface translation''' and '''software translation'''. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

=== Vertalen van pagina's ===
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|De vertaling is verouderd: verouderde delen worden vervangen door nieuwe brontekst en vertalers kunnen de te vernieuwen boodschappen met een enkele klik bereiken]]

De meeste wiki's hebben inhoud die ze beschikbaar willen stellen in meerdere talen. Of het nu over slechts enkele of honderden pagina's gaat, maakt daarbij niet uit. Om te voorkomen dat vertalers tijd verspillen, zouden pagina's slechts gemarkeerd mogen worden voor vertaling wanneer ze redelijk stabiel zijn. Elke wijziging die nadien gebeurt, kan tientallen of honderden vertalingen beïnvloeden en de tijd om die te vernieuwen, loopt snel op. U moet zich hiervan bewust zijn en onnodig werk vermijden, omdat vrijwillige vertalers tijd besteden aan het vertalen en updaten. Wanneer u de Translate-extensie gebruikt om pagina's te vertalen, bent u al op de goede weg om de vertaaltijd op een efficiënte en effectieve manier te benutten.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With ''Translate'', the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside <code><languages /><translate>..</translate></code> and follow the links, or follow the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to prepare a page for translation]].

=== Local interface translation in multilingual wikis ===

One thing almost every wiki has customized is the [[Manual:Sidebar|sidebar]]. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the <nowiki>{{int:}}</nowiki> magic word. The [[translatewiki:|translatewiki.net]] main page and some Wikimedia Commons templates are good examples of this. The magic word <nowiki>{{int:}}</nowiki> is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|How to make an interface message group]].

=== Vertalen van software ===

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate tens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including [[w:.properties|Java properties]], [[w:Gettext|Gettext]] and [[w:YAML|Yaml]] files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:en:Version control system|VCS]] repository checkout, where you can easily commit changes and new files.

== Meer informatie en leerprogramma's ==

=== Voor vertalers en beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Translation example |Hoe te vertalen]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|Translation best practices]]
* [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting |Statistics and reporting]]
* [[Special:MyLanguage/Help:Extension:Translate/Quality assurance |Kwaliteitscontrole]]
* [[Special:MyLanguage/Help:Extension:Translate/Message group states |Message group states]]
* [[Special:MyLanguage/Help:Extension:Translate/Off-line translation |Off-line translation]]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Glossary |Terminologie]]

=== Voor beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Page translation example |How to prepare a page for translation]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Page translation administration |Paginavertaalbeheer]]
* [[Special:MyLanguage/Help:Extension:Translate/Unstructured element translation|Interface message groups (localised sidebar, main page and templates)]] [Tutorial]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Group management |Message group management]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration |YAML configuration format]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration example |How to write YAML configuration for file based message groups]] [Tutorial]

=== Referentiedocumentatie voor ontwikkelaars ===
* [[Special:MyLanguage/Help:Extension:Translate/Installation |Installatie]] and [[Special:MyLanguage/Help:Extension:Translate/Configuration |Instellingen]]; [[MediaWiki Language Extension Bundle]] should be enough in most cases.
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Components |Translate explained for developers]]
** [[Special:MyLanguage/Help:Extension:Translate/Hooks |Hooks]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/Message groups |Berichtgroepen]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/File format support|File format support]]
** [[Special:MyLanguage/Help:Extension:Translate/Translation_aids |Translation aids]]
** [Unwritten] [[Special:MyLanguage/Help:Extension:Translate/API |Web API]]
** [[Special:MyLanguage/Help:Extension:Translate/Insertables|Insertables]]
* [[Special:MyLanguage/Help:Extension:Translate/Translation memories|Translation memories]]

===Gerelateerd===

* [[Extension:TranslationNotifications#Special_pages|Translation notifications]]
* [[Localisation/Tutorial]]: General localisation tutorial for developers, for use at hackathons & trainings
* [[Extension:TranslateSvg]]: Adds support for translating SVG files
* [[Universal Language Selector]]: Provides webfonts and input methods

== Todo ==

* Implementation on Meta: [[m:Meta:Translate extension]].
* See [[etherpad:translate-doc]] for specific tasks.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate{{LangCat|Extension:Translate}}| ]]

Translations:Help:Extension:Translate/38/nl

2013-11-21T23:32:44Z

Myr: Created page with "===Gerelateerd==="

===Gerelateerd===

Translations:Help:Extension:Translate/70/nl

2013-11-21T23:32:31Z

Myr: Created page with "Web API"

Web API

Help:Extension:Translate/nl

2013-11-21T23:32:24Z

Myr: Created page with "Berichtgroepen"

<languages/>[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|The main special page of the extension, "[[Special:Translate]]", in its most common task, "view all untranslated messages"]]
__NOEDITSECTION__
The [[Extension:Translate|Translate extension]] enhances MediaWiki with essential features needed to do translation work. It can be used to translate the content pages, the interface of the wiki and even other software products, as it is used at [[translatewiki|translatewiki.net]]. The Translate extension comes with an easy to use translation interface and can separate the content structure from the text content that needs to be translated, showing only the translatable text to translators by splitting the content into manageable units. Each unit is automatically tracked for changes, and translators immediately see what needs updating on a specific page or throughout the wiki.

The Translate extension is used to translate the user interface of MediaWiki and other software projects at translatewiki.net by hundreds of translators every month. At [http://userbase.kde.org userbase.kde.org] it is used to translate almost a thousand content pages with user documentation. It is easy to start using the Translate extension, but at the same time it also scales up and provides advanced reporting, reviewing and workflow features.

== Functionaliteit ==
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|De tekstverwerker voor vertalingen: een bericht met een tip (niet zichtbaar in de afbeelding) en een suggesties van twee hulptalen]]

'''Interface:''' The main feature of the Translate extension is a simple yet functional translation interface. Besides the essential information like message definition and documentation, you can also view translations in other languages. If a definition has changed, you will see the changes. The extension comes with some built-in checks, that can help with common mistakes like unbalanced brackets and unused variables. Depending on the configuration, there are also suggestions from translation memory and machine translation services like those of Google Translate, Microsoft's Bing Translator and Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs than can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the [[:en:Gettext|Gettext po]] file format.

'''Message groups and tasks:''' Many of the features are built around two basic concepts: message groups and tasks.

A message group represents a collection of messages. One content page would be one message group, where, in the simplest form, each paragraph would be one message in that group. Messages used in each MediaWiki extension form a message group on translatewiki.net – a few of the largest extensions have multiple groups. You can also make a group of groups, like ''All newsletters'' or ''All Translate extension messages''. Many of the statistics and the tasks work on the message group basis.

The tasks, or in other words different listings of messages in a message group, facilitate different use cases. Normally a translator gets a list of all untranslated messages in a chosen message group, but there are tasks where you can review messages or just get a list of all messages, translated or not.

[[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Op deze speciale pagina wordt gerapporteerd over de vertaalstatus van iedere berichtengroep]]

'''Reporting and statistics:''' The extension has extensive [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|reporting features]] ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

'''Content translation:''' If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they can not work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the <nowiki><languages /></nowiki> tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form <nowiki>[[Special:MyLanguage/Pagename]]</nowiki>.

For more information see the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to set up a content page for translation]] and the [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|in-depth documentation of the page translation feature]].

'''Developers:''' The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

== Gebruiksmogelijkheden ==

You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general ''Translate'' performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are '''content translation''', '''local interface translation''' and '''software translation'''. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

=== Vertalen van pagina's ===
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|De vertaling is verouderd: verouderde delen worden vervangen door nieuwe brontekst en vertalers kunnen de te vernieuwen boodschappen met een enkele klik bereiken]]

De meeste wiki's hebben inhoud die ze beschikbaar willen stellen in meerdere talen. Of het nu over slechts enkele of honderden pagina's gaat, maakt daarbij niet uit. Om te voorkomen dat vertalers tijd verspillen, zouden pagina's slechts gemarkeerd mogen worden voor vertaling wanneer ze redelijk stabiel zijn. Elke wijziging die nadien gebeurt, kan tientallen of honderden vertalingen beïnvloeden en de tijd om die te vernieuwen, loopt snel op. U moet zich hiervan bewust zijn en onnodig werk vermijden, omdat vrijwillige vertalers tijd besteden aan het vertalen en updaten. Wanneer u de Translate-extensie gebruikt om pagina's te vertalen, bent u al op de goede weg om de vertaaltijd op een efficiënte en effectieve manier te benutten.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With ''Translate'', the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside <code><languages /><translate>..</translate></code> and follow the links, or follow the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to prepare a page for translation]].

=== Local interface translation in multilingual wikis ===

One thing almost every wiki has customized is the [[Manual:Sidebar|sidebar]]. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the <nowiki>{{int:}}</nowiki> magic word. The [[translatewiki:|translatewiki.net]] main page and some Wikimedia Commons templates are good examples of this. The magic word <nowiki>{{int:}}</nowiki> is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|How to make an interface message group]].

=== Vertalen van software ===

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate tens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including [[w:.properties|Java properties]], [[w:Gettext|Gettext]] and [[w:YAML|Yaml]] files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:en:Version control system|VCS]] repository checkout, where you can easily commit changes and new files.

== Meer informatie en leerprogramma's ==

=== Voor vertalers en beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Translation example |Hoe te vertalen]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|Translation best practices]]
* [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting |Statistics and reporting]]
* [[Special:MyLanguage/Help:Extension:Translate/Quality assurance |Kwaliteitscontrole]]
* [[Special:MyLanguage/Help:Extension:Translate/Message group states |Message group states]]
* [[Special:MyLanguage/Help:Extension:Translate/Off-line translation |Off-line translation]]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Glossary |Terminologie]]

=== Voor beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Page translation example |How to prepare a page for translation]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Page translation administration |Paginavertaalbeheer]]
* [[Special:MyLanguage/Help:Extension:Translate/Unstructured element translation|Interface message groups (localised sidebar, main page and templates)]] [Tutorial]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Group management |Message group management]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration |YAML configuration format]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration example |How to write YAML configuration for file based message groups]] [Tutorial]

=== Referentiedocumentatie voor ontwikkelaars ===
* [[Special:MyLanguage/Help:Extension:Translate/Installation |Installatie]] and [[Special:MyLanguage/Help:Extension:Translate/Configuration |Instellingen]]; [[MediaWiki Language Extension Bundle]] should be enough in most cases.
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Components |Translate explained for developers]]
** [[Special:MyLanguage/Help:Extension:Translate/Hooks |Hooks]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/Message groups |Berichtgroepen]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/File format support|File format support]]
** [[Special:MyLanguage/Help:Extension:Translate/Translation_aids |Translation aids]]
** [Unwritten] [[Special:MyLanguage/Help:Extension:Translate/API |Web API]]
** [[Special:MyLanguage/Help:Extension:Translate/Insertables|Insertables]]
* [[Special:MyLanguage/Help:Extension:Translate/Translation memories|Translation memories]]

===Related===

* [[Extension:TranslationNotifications#Special_pages|Translation notifications]]
* [[Localisation/Tutorial]]: General localisation tutorial for developers, for use at hackathons & trainings
* [[Extension:TranslateSvg]]: Adds support for translating SVG files
* [[Universal Language Selector]]: Provides webfonts and input methods

== Todo ==

* Implementation on Meta: [[m:Meta:Translate extension]].
* See [[etherpad:translate-doc]] for specific tasks.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate{{LangCat|Extension:Translate}}| ]]

Translations:Help:Extension:Translate/65/nl

2013-11-21T23:32:23Z

Myr: Created page with "Berichtgroepen"

Berichtgroepen

Help:Extension:Translate/nl

2013-11-21T23:31:48Z

Myr: Created page with "Terminologie"

<languages/>[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|The main special page of the extension, "[[Special:Translate]]", in its most common task, "view all untranslated messages"]]
__NOEDITSECTION__
The [[Extension:Translate|Translate extension]] enhances MediaWiki with essential features needed to do translation work. It can be used to translate the content pages, the interface of the wiki and even other software products, as it is used at [[translatewiki|translatewiki.net]]. The Translate extension comes with an easy to use translation interface and can separate the content structure from the text content that needs to be translated, showing only the translatable text to translators by splitting the content into manageable units. Each unit is automatically tracked for changes, and translators immediately see what needs updating on a specific page or throughout the wiki.

The Translate extension is used to translate the user interface of MediaWiki and other software projects at translatewiki.net by hundreds of translators every month. At [http://userbase.kde.org userbase.kde.org] it is used to translate almost a thousand content pages with user documentation. It is easy to start using the Translate extension, but at the same time it also scales up and provides advanced reporting, reviewing and workflow features.

== Functionaliteit ==
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|De tekstverwerker voor vertalingen: een bericht met een tip (niet zichtbaar in de afbeelding) en een suggesties van twee hulptalen]]

'''Interface:''' The main feature of the Translate extension is a simple yet functional translation interface. Besides the essential information like message definition and documentation, you can also view translations in other languages. If a definition has changed, you will see the changes. The extension comes with some built-in checks, that can help with common mistakes like unbalanced brackets and unused variables. Depending on the configuration, there are also suggestions from translation memory and machine translation services like those of Google Translate, Microsoft's Bing Translator and Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs than can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the [[:en:Gettext|Gettext po]] file format.

'''Message groups and tasks:''' Many of the features are built around two basic concepts: message groups and tasks.

A message group represents a collection of messages. One content page would be one message group, where, in the simplest form, each paragraph would be one message in that group. Messages used in each MediaWiki extension form a message group on translatewiki.net – a few of the largest extensions have multiple groups. You can also make a group of groups, like ''All newsletters'' or ''All Translate extension messages''. Many of the statistics and the tasks work on the message group basis.

The tasks, or in other words different listings of messages in a message group, facilitate different use cases. Normally a translator gets a list of all untranslated messages in a chosen message group, but there are tasks where you can review messages or just get a list of all messages, translated or not.

[[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Op deze speciale pagina wordt gerapporteerd over de vertaalstatus van iedere berichtengroep]]

'''Reporting and statistics:''' The extension has extensive [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|reporting features]] ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

'''Content translation:''' If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they can not work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the <nowiki><languages /></nowiki> tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form <nowiki>[[Special:MyLanguage/Pagename]]</nowiki>.

For more information see the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to set up a content page for translation]] and the [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|in-depth documentation of the page translation feature]].

'''Developers:''' The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

== Gebruiksmogelijkheden ==

You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general ''Translate'' performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are '''content translation''', '''local interface translation''' and '''software translation'''. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

=== Vertalen van pagina's ===
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|De vertaling is verouderd: verouderde delen worden vervangen door nieuwe brontekst en vertalers kunnen de te vernieuwen boodschappen met een enkele klik bereiken]]

De meeste wiki's hebben inhoud die ze beschikbaar willen stellen in meerdere talen. Of het nu over slechts enkele of honderden pagina's gaat, maakt daarbij niet uit. Om te voorkomen dat vertalers tijd verspillen, zouden pagina's slechts gemarkeerd mogen worden voor vertaling wanneer ze redelijk stabiel zijn. Elke wijziging die nadien gebeurt, kan tientallen of honderden vertalingen beïnvloeden en de tijd om die te vernieuwen, loopt snel op. U moet zich hiervan bewust zijn en onnodig werk vermijden, omdat vrijwillige vertalers tijd besteden aan het vertalen en updaten. Wanneer u de Translate-extensie gebruikt om pagina's te vertalen, bent u al op de goede weg om de vertaaltijd op een efficiënte en effectieve manier te benutten.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With ''Translate'', the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside <code><languages /><translate>..</translate></code> and follow the links, or follow the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to prepare a page for translation]].

=== Local interface translation in multilingual wikis ===

One thing almost every wiki has customized is the [[Manual:Sidebar|sidebar]]. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the <nowiki>{{int:}}</nowiki> magic word. The [[translatewiki:|translatewiki.net]] main page and some Wikimedia Commons templates are good examples of this. The magic word <nowiki>{{int:}}</nowiki> is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|How to make an interface message group]].

=== Vertalen van software ===

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate tens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including [[w:.properties|Java properties]], [[w:Gettext|Gettext]] and [[w:YAML|Yaml]] files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:en:Version control system|VCS]] repository checkout, where you can easily commit changes and new files.

== Meer informatie en leerprogramma's ==

=== Voor vertalers en beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Translation example |Hoe te vertalen]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|Translation best practices]]
* [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting |Statistics and reporting]]
* [[Special:MyLanguage/Help:Extension:Translate/Quality assurance |Kwaliteitscontrole]]
* [[Special:MyLanguage/Help:Extension:Translate/Message group states |Message group states]]
* [[Special:MyLanguage/Help:Extension:Translate/Off-line translation |Off-line translation]]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Glossary |Terminologie]]

=== Voor beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Page translation example |How to prepare a page for translation]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Page translation administration |Paginavertaalbeheer]]
* [[Special:MyLanguage/Help:Extension:Translate/Unstructured element translation|Interface message groups (localised sidebar, main page and templates)]] [Tutorial]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Group management |Message group management]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration |YAML configuration format]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration example |How to write YAML configuration for file based message groups]] [Tutorial]

=== Referentiedocumentatie voor ontwikkelaars ===
* [[Special:MyLanguage/Help:Extension:Translate/Installation |Installatie]] and [[Special:MyLanguage/Help:Extension:Translate/Configuration |Instellingen]]; [[MediaWiki Language Extension Bundle]] should be enough in most cases.
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Components |Translate explained for developers]]
** [[Special:MyLanguage/Help:Extension:Translate/Hooks |Hooks]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/Message groups |Message groups]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/File format support|File format support]]
** [[Special:MyLanguage/Help:Extension:Translate/Translation_aids |Translation aids]]
** [Unwritten] [[Special:MyLanguage/Help:Extension:Translate/API |Web API]]
** [[Special:MyLanguage/Help:Extension:Translate/Insertables|Insertables]]
* [[Special:MyLanguage/Help:Extension:Translate/Translation memories|Translation memories]]

===Related===

* [[Extension:TranslationNotifications#Special_pages|Translation notifications]]
* [[Localisation/Tutorial]]: General localisation tutorial for developers, for use at hackathons & trainings
* [[Extension:TranslateSvg]]: Adds support for translating SVG files
* [[Universal Language Selector]]: Provides webfonts and input methods

== Todo ==

* Implementation on Meta: [[m:Meta:Translate extension]].
* See [[etherpad:translate-doc]] for specific tasks.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate{{LangCat|Extension:Translate}}| ]]

Translations:Help:Extension:Translate/50/nl

2013-11-21T23:31:47Z

Myr: Created page with "Terminologie"

Terminologie

Help:Extension:Translate/nl

2013-11-21T23:31:39Z

Myr: Created page with "Kwaliteitscontrole"

<languages/>[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|The main special page of the extension, "[[Special:Translate]]", in its most common task, "view all untranslated messages"]]
__NOEDITSECTION__
The [[Extension:Translate|Translate extension]] enhances MediaWiki with essential features needed to do translation work. It can be used to translate the content pages, the interface of the wiki and even other software products, as it is used at [[translatewiki|translatewiki.net]]. The Translate extension comes with an easy to use translation interface and can separate the content structure from the text content that needs to be translated, showing only the translatable text to translators by splitting the content into manageable units. Each unit is automatically tracked for changes, and translators immediately see what needs updating on a specific page or throughout the wiki.

The Translate extension is used to translate the user interface of MediaWiki and other software projects at translatewiki.net by hundreds of translators every month. At [http://userbase.kde.org userbase.kde.org] it is used to translate almost a thousand content pages with user documentation. It is easy to start using the Translate extension, but at the same time it also scales up and provides advanced reporting, reviewing and workflow features.

== Functionaliteit ==
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|De tekstverwerker voor vertalingen: een bericht met een tip (niet zichtbaar in de afbeelding) en een suggesties van twee hulptalen]]

'''Interface:''' The main feature of the Translate extension is a simple yet functional translation interface. Besides the essential information like message definition and documentation, you can also view translations in other languages. If a definition has changed, you will see the changes. The extension comes with some built-in checks, that can help with common mistakes like unbalanced brackets and unused variables. Depending on the configuration, there are also suggestions from translation memory and machine translation services like those of Google Translate, Microsoft's Bing Translator and Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs than can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the [[:en:Gettext|Gettext po]] file format.

'''Message groups and tasks:''' Many of the features are built around two basic concepts: message groups and tasks.

A message group represents a collection of messages. One content page would be one message group, where, in the simplest form, each paragraph would be one message in that group. Messages used in each MediaWiki extension form a message group on translatewiki.net – a few of the largest extensions have multiple groups. You can also make a group of groups, like ''All newsletters'' or ''All Translate extension messages''. Many of the statistics and the tasks work on the message group basis.

The tasks, or in other words different listings of messages in a message group, facilitate different use cases. Normally a translator gets a list of all untranslated messages in a chosen message group, but there are tasks where you can review messages or just get a list of all messages, translated or not.

[[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Op deze speciale pagina wordt gerapporteerd over de vertaalstatus van iedere berichtengroep]]

'''Reporting and statistics:''' The extension has extensive [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|reporting features]] ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

'''Content translation:''' If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they can not work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the <nowiki><languages /></nowiki> tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form <nowiki>[[Special:MyLanguage/Pagename]]</nowiki>.

For more information see the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to set up a content page for translation]] and the [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|in-depth documentation of the page translation feature]].

'''Developers:''' The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

== Gebruiksmogelijkheden ==

You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general ''Translate'' performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are '''content translation''', '''local interface translation''' and '''software translation'''. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

=== Vertalen van pagina's ===
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|De vertaling is verouderd: verouderde delen worden vervangen door nieuwe brontekst en vertalers kunnen de te vernieuwen boodschappen met een enkele klik bereiken]]

De meeste wiki's hebben inhoud die ze beschikbaar willen stellen in meerdere talen. Of het nu over slechts enkele of honderden pagina's gaat, maakt daarbij niet uit. Om te voorkomen dat vertalers tijd verspillen, zouden pagina's slechts gemarkeerd mogen worden voor vertaling wanneer ze redelijk stabiel zijn. Elke wijziging die nadien gebeurt, kan tientallen of honderden vertalingen beïnvloeden en de tijd om die te vernieuwen, loopt snel op. U moet zich hiervan bewust zijn en onnodig werk vermijden, omdat vrijwillige vertalers tijd besteden aan het vertalen en updaten. Wanneer u de Translate-extensie gebruikt om pagina's te vertalen, bent u al op de goede weg om de vertaaltijd op een efficiënte en effectieve manier te benutten.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With ''Translate'', the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside <code><languages /><translate>..</translate></code> and follow the links, or follow the tutorial [[Special:MyLanguage/Help:Extension:Translate/Page translation example|How to prepare a page for translation]].

=== Local interface translation in multilingual wikis ===

One thing almost every wiki has customized is the [[Manual:Sidebar|sidebar]]. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the <nowiki>{{int:}}</nowiki> magic word. The [[translatewiki:|translatewiki.net]] main page and some Wikimedia Commons templates are good examples of this. The magic word <nowiki>{{int:}}</nowiki> is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|How to make an interface message group]].

=== Vertalen van software ===

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate tens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including [[w:.properties|Java properties]], [[w:Gettext|Gettext]] and [[w:YAML|Yaml]] files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:en:Version control system|VCS]] repository checkout, where you can easily commit changes and new files.

== Meer informatie en leerprogramma's ==

=== Voor vertalers en beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Translation example |Hoe te vertalen]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Translation best practices|Translation best practices]]
* [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting |Statistics and reporting]]
* [[Special:MyLanguage/Help:Extension:Translate/Quality assurance |Kwaliteitscontrole]]
* [[Special:MyLanguage/Help:Extension:Translate/Message group states |Message group states]]
* [[Special:MyLanguage/Help:Extension:Translate/Off-line translation |Off-line translation]]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Glossary |Glossary]]

=== Voor beheerders van vertalingen ===

* [[Special:MyLanguage/Help:Extension:Translate/Page translation example |How to prepare a page for translation]] [Tutorial]
* [[Special:MyLanguage/Help:Extension:Translate/Page translation administration |Paginavertaalbeheer]]
* [[Special:MyLanguage/Help:Extension:Translate/Unstructured element translation|Interface message groups (localised sidebar, main page and templates)]] [Tutorial]
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Group management |Message group management]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration |YAML configuration format]]
* [[Special:MyLanguage/Help:Extension:Translate/Group configuration example |How to write YAML configuration for file based message groups]] [Tutorial]

=== Referentiedocumentatie voor ontwikkelaars ===
* [[Special:MyLanguage/Help:Extension:Translate/Installation |Installatie]] and [[Special:MyLanguage/Help:Extension:Translate/Configuration |Instellingen]]; [[MediaWiki Language Extension Bundle]] should be enough in most cases.
* [In progress] [[Special:MyLanguage/Help:Extension:Translate/Components |Translate explained for developers]]
** [[Special:MyLanguage/Help:Extension:Translate/Hooks |Hooks]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/Message groups |Message groups]]
** [In progress] [[Special:MyLanguage/Help:Extension:Translate/File format support|File format support]]
** [[Special:MyLanguage/Help:Extension:Translate/Translation_aids |Translation aids]]
** [Unwritten] [[Special:MyLanguage/Help:Extension:Translate/API |Web API]]
** [[Special:MyLanguage/Help:Extension:Translate/Insertables|Insertables]]
* [[Special:MyLanguage/Help:Extension:Translate/Translation memories|Translation memories]]

===Related===

* [[Extension:TranslationNotifications#Special_pages|Translation notifications]]
* [[Localisation/Tutorial]]: General localisation tutorial for developers, for use at hackathons & trainings
* [[Extension:TranslateSvg]]: Adds support for translating SVG files
* [[Universal Language Selector]]: Provides webfonts and input methods

== Todo ==

* Implementation on Meta: [[m:Meta:Translate extension]].
* See [[etherpad:translate-doc]] for specific tasks.

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate{{LangCat|Extension:Translate}}| ]]

Translations:Help:Extension:Translate/47/nl

2013-11-21T23:31:37Z

Myr: Created page with "Kwaliteitscontrole"

Kwaliteitscontrole

Wikimedia Engineering/Report/2013/April/summary/nl

2013-05-28T19:17:59Z

Myr: Created page with ":''Deze inhoud is gemaakt om opgenomen te worden in de rapportage van de Wikimedia Foundation over april 2013. Het is een verkort..."

<languages/>
<div class="plainlinks">
{{nav
| title = Samenvatting van het [[Wikimedia engineering report/2013/April|Wikimedia engineering report van april 2013]]
| previous = [[Special:MyLanguage/Wikimedia engineering report/2013/March/summary|Samenvatting voor maart 2013]]
| next = [[Special:MyLanguage/Wikimedia engineering report/2013/May/summary|Samenvatting voor mei 2013]]
}}

:''Deze inhoud is gemaakt om opgenomen te worden in de [[m:Wikimedia Foundation Report, April 2013|rapportage van de Wikimedia Foundation over april 2013]]. Het is een verkorte en vereenvoudigde versie van de volledige rapportage die alleen in het Engels beschikbaar is: [[mw:Wikimedia engineering report/2013/April|Wikimedia engineering report voor april 2013]]. Voor het lezen van deze samenvatting is geen bijzondere technische kennis nodig.''

Major news in April include:
* the start of recruitment for a [https://blog.wikimedia.org/2013/04/08/breaking-through-walls-of-text-richer-wikimedia-experience/ multimedia engineering team];
* a [https://blog.wikimedia.org/2013/04/09/language-engineering-sprint-update-translation-user-experience-improvements-testing-and-coverage/ better translation interface], a new [https://blog.wikimedia.org/2013/04/22/a-new-translation-home-page-the-maven-program-and-other-updates-from-language-engineering/ home page for translators] and a [https://blog.wikimedia.org/2013/04/26/join-the-language-mavens/ language outreach program];
* the release of [https://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/ Kiwix of Android], an app to download and view Wikimedia content offline on mobile devices;
* the migration of Wikidata, and the English and German Wikipedias, to the [https://blog.wikimedia.org/2013/04/22/wikipedia-adopts-mariadb/ MariaDB] database system;
* the [https://blog.wikimedia.org/2013/04/25/the-wikidata-revolution/ second phase of Wikidata], whose content can now be displayed in Wikipedia articles;
* the deployment of [https://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ VisualEditor's first version] to 14 more language versions of Wikipedia;
* a new [https://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ login and account creation interface];
* the ramp-up of [https://blog.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/ technical mentorship programs];
* the launch of an [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ official Wikimedia Commons app for iOS and Android].

=== [[mw:VisualEditor|VisualEditor]] ===

In April, the VisualEditor team continued to work on major new features that will be added in the coming months. The goal is for VisualEditor to become the default editor for all Wikipedia users in July 2013, capable of letting them edit the majority of content without needing to use the legacy wikitext editor. The team has focused on four substantial areas of work: adding support for references, templates, categories and media items, all of which are currently disabled for editing in VisualEditor. Editing around images is now designed and partially implemented in our experimental code, and editing around categories is almost complete and nearly ready for activation.

The early ("alpha") version of VisualEditor currently enabled on a few select sites was updated three times in April, adding speed and interface improvements, fixing bugs and making deeper changes behind the scenes to better support the new features. We also were able to enable the alpha version of VisualEditor [//blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ on fourteen more Wikipedias as an opt-in]. This has encouraged feedback from the community on what works and is broken, and identifying language- and locale-specific issues that are now being fixed.

As for the [[mw:Parsoid|Parsoid]] (the program that serves as translator between wikitext code and annotated HTML, behind the scenes of VisualEditor), the team successfully activated the cumulative work done over the last four months. This includes support for non-English wikis, a rewritten system to reduce artifacts when editing with VisualEditor, support for basic template parameter editing, and a long list of other fixes and improvements.

Several other features for the July target are on track. Specifications to support more features were written and are currently being implemented. This includes images and thumbnails, whose options for embedding in wiki pages will soon be ready. The team also continued to evaluate the performance of Parsoid. Caching was developed to minimize the server load, and new servers were ordered.

=== [[mw:New editor engagement|Editor engagement]] ===

In April, the Editor engagement team (E2) activated the [[mw:Echo (Notifications)|Notifications]] feature on the [[w:Wikipedia:Notifications|English Wikipedia]] and mediawiki.org. This first version aims to inform users about new activity that affects them on Wikipedia, such as talk page messages, page reviews, mentions, edit reverts and thanks. The team developed a new feature that lets users mark all notifications as read, and updated the fly-out and archive page. The development of metrics dashboards also started.

The final version of Article Feedback v5 (a quality assessment feature) was activated on the [[:w:Special:ArticleFeedbackv5|English]], [[:w:fr:Sp%C3%A9cial:ArticleFeedbackv5|French]] and [[:w:de:Spezial:Artikelrückmeldungen v5|German]] Wikipedias. A number of bugs were fixed, the feedback page was simplified, and other features such as feedback links and auto-archival were finalized. Development for this feature is now wrapping up.

Design continues for the first version of [[mw:Flow|Flow]], a feed-like interface to enable users to better interact with their projects. An [http://lists.wikimedia.org/pipermail/design/2013-April/000495.html interactive prototype] is being built to help describe multiple functions.

The Editor Engagement Experiments team (E3) focused on its redesign of the [http://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ account creation and log-in interface]. The first phase of the launch invited editors and readers on all Wikimedia projects to test the new forms on an opt-in basis, to identify bugs and localization issues across wikis. The new interface is expected to replace the legacy version in May.

For the ''[[mw:Onboarding new Wikipedians|Onboarding new Wikipedians]]'' project, the E3 team completed [[:m:R:OB4|quantitative analysis]] of the latest version of the ''GettingStarted'' landing page, and began prototyping a new version and a navigation system, which will be used for usability testing prior to further development. The launch is expected in early May as well.

=== [[mw:Wikimedia Mobile engineering|Mobile]] ===

An official [[mw:Apps/Commons|Wikimedia Commons app]] for smartphones was released for [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ both iOS and Android devices] in April. The team also added support for categories.

Work on [[mw:Wikipedia Zero|Wikipedia Zero]] mostly happened behind the scenes this month, with changes made to the configuration system to better support carrier preferences.

The team also experimented with a log-in/sign-up call to action for logged-out users from the [[mw:Mobile design/Uploads|in-article upload feature]] on the mobile site. This resulted in a spike in new contributors, but the quality of their uploads was lower than anticipated, and the quantity of inappropriate uploads was a burden on the Commons community. The call to action was therefore disabled, and uploading reserved to existing users, leading to a vast improvement in the quality of the uploads: 3/4th of the files are retained on Commons, as compared to less than 1/4 when brand-new users were uploading. To create a more focused uploading workflow, and let mobile uploaders discover more articles to illustrate, a ''Nearby'' view was added to the beta site, showing users a list of articles near them and highlighting the ones that need images. This feature is expected to be activated on the full mobile web site next month.

</div>

Translations:Wikimedia Engineering/Report/2013/April/summary/4/nl

2013-05-28T19:17:59Z

Myr: Created page with ":''Deze inhoud is gemaakt om opgenomen te worden in de rapportage van de Wikimedia Foundation over april 2013. Het is een verkort..."

:''Deze inhoud is gemaakt om opgenomen te worden in de [[m:Wikimedia Foundation Report, April 2013|rapportage van de Wikimedia Foundation over april 2013]]. Het is een verkorte en vereenvoudigde versie van de volledige rapportage die alleen in het Engels beschikbaar is: [[mw:Wikimedia engineering report/2013/April|Wikimedia engineering report voor april 2013]]. Voor het lezen van deze samenvatting is geen bijzondere technische kennis nodig.''

Wikimedia Engineering/Report/2013/April/summary/nl

2013-05-28T19:16:10Z

Myr: Created page with "Samenvatting voor mei 2013"

<languages/>
<div class="plainlinks">
{{nav
| title = Samenvatting van het [[Wikimedia engineering report/2013/April|Wikimedia engineering report van april 2013]]
| previous = [[Special:MyLanguage/Wikimedia engineering report/2013/March/summary|Samenvatting voor maart 2013]]
| next = [[Special:MyLanguage/Wikimedia engineering report/2013/May/summary|Samenvatting voor mei 2013]]
}}

:''This content is prepared for inclusion in the [[m:Wikimedia Foundation Report, April 2013|April 2013 Wikimedia Foundation report]]. It is a shorter and simpler version of the full [[Wikimedia engineering report/2013/April|Wikimedia engineering report for April 2013]] that does not assume specialized technical knowledge.''

Major news in April include:
* the start of recruitment for a [https://blog.wikimedia.org/2013/04/08/breaking-through-walls-of-text-richer-wikimedia-experience/ multimedia engineering team];
* a [https://blog.wikimedia.org/2013/04/09/language-engineering-sprint-update-translation-user-experience-improvements-testing-and-coverage/ better translation interface], a new [https://blog.wikimedia.org/2013/04/22/a-new-translation-home-page-the-maven-program-and-other-updates-from-language-engineering/ home page for translators] and a [https://blog.wikimedia.org/2013/04/26/join-the-language-mavens/ language outreach program];
* the release of [https://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/ Kiwix of Android], an app to download and view Wikimedia content offline on mobile devices;
* the migration of Wikidata, and the English and German Wikipedias, to the [https://blog.wikimedia.org/2013/04/22/wikipedia-adopts-mariadb/ MariaDB] database system;
* the [https://blog.wikimedia.org/2013/04/25/the-wikidata-revolution/ second phase of Wikidata], whose content can now be displayed in Wikipedia articles;
* the deployment of [https://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ VisualEditor's first version] to 14 more language versions of Wikipedia;
* a new [https://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ login and account creation interface];
* the ramp-up of [https://blog.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/ technical mentorship programs];
* the launch of an [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ official Wikimedia Commons app for iOS and Android].

=== [[mw:VisualEditor|VisualEditor]] ===

In April, the VisualEditor team continued to work on major new features that will be added in the coming months. The goal is for VisualEditor to become the default editor for all Wikipedia users in July 2013, capable of letting them edit the majority of content without needing to use the legacy wikitext editor. The team has focused on four substantial areas of work: adding support for references, templates, categories and media items, all of which are currently disabled for editing in VisualEditor. Editing around images is now designed and partially implemented in our experimental code, and editing around categories is almost complete and nearly ready for activation.

The early ("alpha") version of VisualEditor currently enabled on a few select sites was updated three times in April, adding speed and interface improvements, fixing bugs and making deeper changes behind the scenes to better support the new features. We also were able to enable the alpha version of VisualEditor [//blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ on fourteen more Wikipedias as an opt-in]. This has encouraged feedback from the community on what works and is broken, and identifying language- and locale-specific issues that are now being fixed.

As for the [[mw:Parsoid|Parsoid]] (the program that serves as translator between wikitext code and annotated HTML, behind the scenes of VisualEditor), the team successfully activated the cumulative work done over the last four months. This includes support for non-English wikis, a rewritten system to reduce artifacts when editing with VisualEditor, support for basic template parameter editing, and a long list of other fixes and improvements.

Several other features for the July target are on track. Specifications to support more features were written and are currently being implemented. This includes images and thumbnails, whose options for embedding in wiki pages will soon be ready. The team also continued to evaluate the performance of Parsoid. Caching was developed to minimize the server load, and new servers were ordered.

=== [[mw:New editor engagement|Editor engagement]] ===

In April, the Editor engagement team (E2) activated the [[mw:Echo (Notifications)|Notifications]] feature on the [[w:Wikipedia:Notifications|English Wikipedia]] and mediawiki.org. This first version aims to inform users about new activity that affects them on Wikipedia, such as talk page messages, page reviews, mentions, edit reverts and thanks. The team developed a new feature that lets users mark all notifications as read, and updated the fly-out and archive page. The development of metrics dashboards also started.

The final version of Article Feedback v5 (a quality assessment feature) was activated on the [[:w:Special:ArticleFeedbackv5|English]], [[:w:fr:Sp%C3%A9cial:ArticleFeedbackv5|French]] and [[:w:de:Spezial:Artikelrückmeldungen v5|German]] Wikipedias. A number of bugs were fixed, the feedback page was simplified, and other features such as feedback links and auto-archival were finalized. Development for this feature is now wrapping up.

Design continues for the first version of [[mw:Flow|Flow]], a feed-like interface to enable users to better interact with their projects. An [http://lists.wikimedia.org/pipermail/design/2013-April/000495.html interactive prototype] is being built to help describe multiple functions.

The Editor Engagement Experiments team (E3) focused on its redesign of the [http://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ account creation and log-in interface]. The first phase of the launch invited editors and readers on all Wikimedia projects to test the new forms on an opt-in basis, to identify bugs and localization issues across wikis. The new interface is expected to replace the legacy version in May.

For the ''[[mw:Onboarding new Wikipedians|Onboarding new Wikipedians]]'' project, the E3 team completed [[:m:R:OB4|quantitative analysis]] of the latest version of the ''GettingStarted'' landing page, and began prototyping a new version and a navigation system, which will be used for usability testing prior to further development. The launch is expected in early May as well.

=== [[mw:Wikimedia Mobile engineering|Mobile]] ===

An official [[mw:Apps/Commons|Wikimedia Commons app]] for smartphones was released for [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ both iOS and Android devices] in April. The team also added support for categories.

Work on [[mw:Wikipedia Zero|Wikipedia Zero]] mostly happened behind the scenes this month, with changes made to the configuration system to better support carrier preferences.

The team also experimented with a log-in/sign-up call to action for logged-out users from the [[mw:Mobile design/Uploads|in-article upload feature]] on the mobile site. This resulted in a spike in new contributors, but the quality of their uploads was lower than anticipated, and the quantity of inappropriate uploads was a burden on the Commons community. The call to action was therefore disabled, and uploading reserved to existing users, leading to a vast improvement in the quality of the uploads: 3/4th of the files are retained on Commons, as compared to less than 1/4 when brand-new users were uploading. To create a more focused uploading workflow, and let mobile uploaders discover more articles to illustrate, a ''Nearby'' view was added to the beta site, showing users a list of articles near them and highlighting the ones that need images. This feature is expected to be activated on the full mobile web site next month.

</div>

Translations:Wikimedia Engineering/Report/2013/April/summary/3/nl

2013-05-28T19:16:10Z

Myr: Created page with "Samenvatting voor mei 2013"

Samenvatting voor mei 2013

Wikimedia Engineering/Report/2013/April/summary/nl

2013-05-28T19:15:58Z

Myr: Created page with "Samenvatting voor maart 2013"

<languages/>
<div class="plainlinks">
{{nav
| title = Samenvatting van het [[Wikimedia engineering report/2013/April|Wikimedia engineering report van april 2013]]
| previous = [[Special:MyLanguage/Wikimedia engineering report/2013/March/summary|Samenvatting voor maart 2013]]
| next = [[Special:MyLanguage/Wikimedia engineering report/2013/May/summary|Summary for May 2013]]
}}

:''This content is prepared for inclusion in the [[m:Wikimedia Foundation Report, April 2013|April 2013 Wikimedia Foundation report]]. It is a shorter and simpler version of the full [[Wikimedia engineering report/2013/April|Wikimedia engineering report for April 2013]] that does not assume specialized technical knowledge.''

Major news in April include:
* the start of recruitment for a [https://blog.wikimedia.org/2013/04/08/breaking-through-walls-of-text-richer-wikimedia-experience/ multimedia engineering team];
* a [https://blog.wikimedia.org/2013/04/09/language-engineering-sprint-update-translation-user-experience-improvements-testing-and-coverage/ better translation interface], a new [https://blog.wikimedia.org/2013/04/22/a-new-translation-home-page-the-maven-program-and-other-updates-from-language-engineering/ home page for translators] and a [https://blog.wikimedia.org/2013/04/26/join-the-language-mavens/ language outreach program];
* the release of [https://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/ Kiwix of Android], an app to download and view Wikimedia content offline on mobile devices;
* the migration of Wikidata, and the English and German Wikipedias, to the [https://blog.wikimedia.org/2013/04/22/wikipedia-adopts-mariadb/ MariaDB] database system;
* the [https://blog.wikimedia.org/2013/04/25/the-wikidata-revolution/ second phase of Wikidata], whose content can now be displayed in Wikipedia articles;
* the deployment of [https://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ VisualEditor's first version] to 14 more language versions of Wikipedia;
* a new [https://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ login and account creation interface];
* the ramp-up of [https://blog.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/ technical mentorship programs];
* the launch of an [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ official Wikimedia Commons app for iOS and Android].

=== [[mw:VisualEditor|VisualEditor]] ===

In April, the VisualEditor team continued to work on major new features that will be added in the coming months. The goal is for VisualEditor to become the default editor for all Wikipedia users in July 2013, capable of letting them edit the majority of content without needing to use the legacy wikitext editor. The team has focused on four substantial areas of work: adding support for references, templates, categories and media items, all of which are currently disabled for editing in VisualEditor. Editing around images is now designed and partially implemented in our experimental code, and editing around categories is almost complete and nearly ready for activation.

The early ("alpha") version of VisualEditor currently enabled on a few select sites was updated three times in April, adding speed and interface improvements, fixing bugs and making deeper changes behind the scenes to better support the new features. We also were able to enable the alpha version of VisualEditor [//blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ on fourteen more Wikipedias as an opt-in]. This has encouraged feedback from the community on what works and is broken, and identifying language- and locale-specific issues that are now being fixed.

As for the [[mw:Parsoid|Parsoid]] (the program that serves as translator between wikitext code and annotated HTML, behind the scenes of VisualEditor), the team successfully activated the cumulative work done over the last four months. This includes support for non-English wikis, a rewritten system to reduce artifacts when editing with VisualEditor, support for basic template parameter editing, and a long list of other fixes and improvements.

Several other features for the July target are on track. Specifications to support more features were written and are currently being implemented. This includes images and thumbnails, whose options for embedding in wiki pages will soon be ready. The team also continued to evaluate the performance of Parsoid. Caching was developed to minimize the server load, and new servers were ordered.

=== [[mw:New editor engagement|Editor engagement]] ===

In April, the Editor engagement team (E2) activated the [[mw:Echo (Notifications)|Notifications]] feature on the [[w:Wikipedia:Notifications|English Wikipedia]] and mediawiki.org. This first version aims to inform users about new activity that affects them on Wikipedia, such as talk page messages, page reviews, mentions, edit reverts and thanks. The team developed a new feature that lets users mark all notifications as read, and updated the fly-out and archive page. The development of metrics dashboards also started.

The final version of Article Feedback v5 (a quality assessment feature) was activated on the [[:w:Special:ArticleFeedbackv5|English]], [[:w:fr:Sp%C3%A9cial:ArticleFeedbackv5|French]] and [[:w:de:Spezial:Artikelrückmeldungen v5|German]] Wikipedias. A number of bugs were fixed, the feedback page was simplified, and other features such as feedback links and auto-archival were finalized. Development for this feature is now wrapping up.

Design continues for the first version of [[mw:Flow|Flow]], a feed-like interface to enable users to better interact with their projects. An [http://lists.wikimedia.org/pipermail/design/2013-April/000495.html interactive prototype] is being built to help describe multiple functions.

The Editor Engagement Experiments team (E3) focused on its redesign of the [http://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ account creation and log-in interface]. The first phase of the launch invited editors and readers on all Wikimedia projects to test the new forms on an opt-in basis, to identify bugs and localization issues across wikis. The new interface is expected to replace the legacy version in May.

For the ''[[mw:Onboarding new Wikipedians|Onboarding new Wikipedians]]'' project, the E3 team completed [[:m:R:OB4|quantitative analysis]] of the latest version of the ''GettingStarted'' landing page, and began prototyping a new version and a navigation system, which will be used for usability testing prior to further development. The launch is expected in early May as well.

=== [[mw:Wikimedia Mobile engineering|Mobile]] ===

An official [[mw:Apps/Commons|Wikimedia Commons app]] for smartphones was released for [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ both iOS and Android devices] in April. The team also added support for categories.

Work on [[mw:Wikipedia Zero|Wikipedia Zero]] mostly happened behind the scenes this month, with changes made to the configuration system to better support carrier preferences.

The team also experimented with a log-in/sign-up call to action for logged-out users from the [[mw:Mobile design/Uploads|in-article upload feature]] on the mobile site. This resulted in a spike in new contributors, but the quality of their uploads was lower than anticipated, and the quantity of inappropriate uploads was a burden on the Commons community. The call to action was therefore disabled, and uploading reserved to existing users, leading to a vast improvement in the quality of the uploads: 3/4th of the files are retained on Commons, as compared to less than 1/4 when brand-new users were uploading. To create a more focused uploading workflow, and let mobile uploaders discover more articles to illustrate, a ''Nearby'' view was added to the beta site, showing users a list of articles near them and highlighting the ones that need images. This feature is expected to be activated on the full mobile web site next month.

</div>

Translations:Wikimedia Engineering/Report/2013/April/summary/2/nl

2013-05-28T19:15:58Z

Myr: Created page with "Samenvatting voor maart 2013"

Samenvatting voor maart 2013

Wikimedia Engineering/Report/2013/April/summary/nl

2013-05-28T19:15:45Z

Myr: Created page with "Samenvatting van het Wikimedia engineering report van april 2013"

<languages/>
<div class="plainlinks">
{{nav
| title = Samenvatting van het [[Wikimedia engineering report/2013/April|Wikimedia engineering report van april 2013]]
| previous = [[Special:MyLanguage/Wikimedia engineering report/2013/March/summary|Summary for March 2013]]
| next = [[Special:MyLanguage/Wikimedia engineering report/2013/May/summary|Summary for May 2013]]
}}

:''This content is prepared for inclusion in the [[m:Wikimedia Foundation Report, April 2013|April 2013 Wikimedia Foundation report]]. It is a shorter and simpler version of the full [[Wikimedia engineering report/2013/April|Wikimedia engineering report for April 2013]] that does not assume specialized technical knowledge.''

Major news in April include:
* the start of recruitment for a [https://blog.wikimedia.org/2013/04/08/breaking-through-walls-of-text-richer-wikimedia-experience/ multimedia engineering team];
* a [https://blog.wikimedia.org/2013/04/09/language-engineering-sprint-update-translation-user-experience-improvements-testing-and-coverage/ better translation interface], a new [https://blog.wikimedia.org/2013/04/22/a-new-translation-home-page-the-maven-program-and-other-updates-from-language-engineering/ home page for translators] and a [https://blog.wikimedia.org/2013/04/26/join-the-language-mavens/ language outreach program];
* the release of [https://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/ Kiwix of Android], an app to download and view Wikimedia content offline on mobile devices;
* the migration of Wikidata, and the English and German Wikipedias, to the [https://blog.wikimedia.org/2013/04/22/wikipedia-adopts-mariadb/ MariaDB] database system;
* the [https://blog.wikimedia.org/2013/04/25/the-wikidata-revolution/ second phase of Wikidata], whose content can now be displayed in Wikipedia articles;
* the deployment of [https://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ VisualEditor's first version] to 14 more language versions of Wikipedia;
* a new [https://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ login and account creation interface];
* the ramp-up of [https://blog.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/ technical mentorship programs];
* the launch of an [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ official Wikimedia Commons app for iOS and Android].

=== [[mw:VisualEditor|VisualEditor]] ===

In April, the VisualEditor team continued to work on major new features that will be added in the coming months. The goal is for VisualEditor to become the default editor for all Wikipedia users in July 2013, capable of letting them edit the majority of content without needing to use the legacy wikitext editor. The team has focused on four substantial areas of work: adding support for references, templates, categories and media items, all of which are currently disabled for editing in VisualEditor. Editing around images is now designed and partially implemented in our experimental code, and editing around categories is almost complete and nearly ready for activation.

The early ("alpha") version of VisualEditor currently enabled on a few select sites was updated three times in April, adding speed and interface improvements, fixing bugs and making deeper changes behind the scenes to better support the new features. We also were able to enable the alpha version of VisualEditor [//blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ on fourteen more Wikipedias as an opt-in]. This has encouraged feedback from the community on what works and is broken, and identifying language- and locale-specific issues that are now being fixed.

As for the [[mw:Parsoid|Parsoid]] (the program that serves as translator between wikitext code and annotated HTML, behind the scenes of VisualEditor), the team successfully activated the cumulative work done over the last four months. This includes support for non-English wikis, a rewritten system to reduce artifacts when editing with VisualEditor, support for basic template parameter editing, and a long list of other fixes and improvements.

Several other features for the July target are on track. Specifications to support more features were written and are currently being implemented. This includes images and thumbnails, whose options for embedding in wiki pages will soon be ready. The team also continued to evaluate the performance of Parsoid. Caching was developed to minimize the server load, and new servers were ordered.

=== [[mw:New editor engagement|Editor engagement]] ===

In April, the Editor engagement team (E2) activated the [[mw:Echo (Notifications)|Notifications]] feature on the [[w:Wikipedia:Notifications|English Wikipedia]] and mediawiki.org. This first version aims to inform users about new activity that affects them on Wikipedia, such as talk page messages, page reviews, mentions, edit reverts and thanks. The team developed a new feature that lets users mark all notifications as read, and updated the fly-out and archive page. The development of metrics dashboards also started.

The final version of Article Feedback v5 (a quality assessment feature) was activated on the [[:w:Special:ArticleFeedbackv5|English]], [[:w:fr:Sp%C3%A9cial:ArticleFeedbackv5|French]] and [[:w:de:Spezial:Artikelrückmeldungen v5|German]] Wikipedias. A number of bugs were fixed, the feedback page was simplified, and other features such as feedback links and auto-archival were finalized. Development for this feature is now wrapping up.

Design continues for the first version of [[mw:Flow|Flow]], a feed-like interface to enable users to better interact with their projects. An [http://lists.wikimedia.org/pipermail/design/2013-April/000495.html interactive prototype] is being built to help describe multiple functions.

The Editor Engagement Experiments team (E3) focused on its redesign of the [http://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ account creation and log-in interface]. The first phase of the launch invited editors and readers on all Wikimedia projects to test the new forms on an opt-in basis, to identify bugs and localization issues across wikis. The new interface is expected to replace the legacy version in May.

For the ''[[mw:Onboarding new Wikipedians|Onboarding new Wikipedians]]'' project, the E3 team completed [[:m:R:OB4|quantitative analysis]] of the latest version of the ''GettingStarted'' landing page, and began prototyping a new version and a navigation system, which will be used for usability testing prior to further development. The launch is expected in early May as well.

=== [[mw:Wikimedia Mobile engineering|Mobile]] ===

An official [[mw:Apps/Commons|Wikimedia Commons app]] for smartphones was released for [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ both iOS and Android devices] in April. The team also added support for categories.

Work on [[mw:Wikipedia Zero|Wikipedia Zero]] mostly happened behind the scenes this month, with changes made to the configuration system to better support carrier preferences.

The team also experimented with a log-in/sign-up call to action for logged-out users from the [[mw:Mobile design/Uploads|in-article upload feature]] on the mobile site. This resulted in a spike in new contributors, but the quality of their uploads was lower than anticipated, and the quantity of inappropriate uploads was a burden on the Commons community. The call to action was therefore disabled, and uploading reserved to existing users, leading to a vast improvement in the quality of the uploads: 3/4th of the files are retained on Commons, as compared to less than 1/4 when brand-new users were uploading. To create a more focused uploading workflow, and let mobile uploaders discover more articles to illustrate, a ''Nearby'' view was added to the beta site, showing users a list of articles near them and highlighting the ones that need images. This feature is expected to be activated on the full mobile web site next month.

</div>

Translations:Wikimedia Engineering/Report/2013/April/summary/1/nl

2013-05-28T19:15:44Z

Myr: Created page with "Samenvatting van het Wikimedia engineering report van april 2013"

Samenvatting van het [[Wikimedia engineering report/2013/April|Wikimedia engineering report van april 2013]]

Wikimedia Engineering/Report/2013/April/summary/nl

2013-05-28T19:15:07Z

Myr: Created page with "Wikimedia engineering report/2013/April/samenvatting"

<languages/>
<div class="plainlinks">
{{nav
| title = Summary of the [[Wikimedia engineering report/2013/April|Wikimedia engineering April 2013 report]]
| previous = [[Special:MyLanguage/Wikimedia engineering report/2013/March/summary|Summary for March 2013]]
| next = [[Special:MyLanguage/Wikimedia engineering report/2013/May/summary|Summary for May 2013]]
}}

:''This content is prepared for inclusion in the [[m:Wikimedia Foundation Report, April 2013|April 2013 Wikimedia Foundation report]]. It is a shorter and simpler version of the full [[Wikimedia engineering report/2013/April|Wikimedia engineering report for April 2013]] that does not assume specialized technical knowledge.''

Major news in April include:
* the start of recruitment for a [https://blog.wikimedia.org/2013/04/08/breaking-through-walls-of-text-richer-wikimedia-experience/ multimedia engineering team];
* a [https://blog.wikimedia.org/2013/04/09/language-engineering-sprint-update-translation-user-experience-improvements-testing-and-coverage/ better translation interface], a new [https://blog.wikimedia.org/2013/04/22/a-new-translation-home-page-the-maven-program-and-other-updates-from-language-engineering/ home page for translators] and a [https://blog.wikimedia.org/2013/04/26/join-the-language-mavens/ language outreach program];
* the release of [https://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/ Kiwix of Android], an app to download and view Wikimedia content offline on mobile devices;
* the migration of Wikidata, and the English and German Wikipedias, to the [https://blog.wikimedia.org/2013/04/22/wikipedia-adopts-mariadb/ MariaDB] database system;
* the [https://blog.wikimedia.org/2013/04/25/the-wikidata-revolution/ second phase of Wikidata], whose content can now be displayed in Wikipedia articles;
* the deployment of [https://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ VisualEditor's first version] to 14 more language versions of Wikipedia;
* a new [https://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ login and account creation interface];
* the ramp-up of [https://blog.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/ technical mentorship programs];
* the launch of an [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ official Wikimedia Commons app for iOS and Android].

=== [[mw:VisualEditor|VisualEditor]] ===

In April, the VisualEditor team continued to work on major new features that will be added in the coming months. The goal is for VisualEditor to become the default editor for all Wikipedia users in July 2013, capable of letting them edit the majority of content without needing to use the legacy wikitext editor. The team has focused on four substantial areas of work: adding support for references, templates, categories and media items, all of which are currently disabled for editing in VisualEditor. Editing around images is now designed and partially implemented in our experimental code, and editing around categories is almost complete and nearly ready for activation.

The early ("alpha") version of VisualEditor currently enabled on a few select sites was updated three times in April, adding speed and interface improvements, fixing bugs and making deeper changes behind the scenes to better support the new features. We also were able to enable the alpha version of VisualEditor [//blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/ on fourteen more Wikipedias as an opt-in]. This has encouraged feedback from the community on what works and is broken, and identifying language- and locale-specific issues that are now being fixed.

As for the [[mw:Parsoid|Parsoid]] (the program that serves as translator between wikitext code and annotated HTML, behind the scenes of VisualEditor), the team successfully activated the cumulative work done over the last four months. This includes support for non-English wikis, a rewritten system to reduce artifacts when editing with VisualEditor, support for basic template parameter editing, and a long list of other fixes and improvements.

Several other features for the July target are on track. Specifications to support more features were written and are currently being implemented. This includes images and thumbnails, whose options for embedding in wiki pages will soon be ready. The team also continued to evaluate the performance of Parsoid. Caching was developed to minimize the server load, and new servers were ordered.

=== [[mw:New editor engagement|Editor engagement]] ===

In April, the Editor engagement team (E2) activated the [[mw:Echo (Notifications)|Notifications]] feature on the [[w:Wikipedia:Notifications|English Wikipedia]] and mediawiki.org. This first version aims to inform users about new activity that affects them on Wikipedia, such as talk page messages, page reviews, mentions, edit reverts and thanks. The team developed a new feature that lets users mark all notifications as read, and updated the fly-out and archive page. The development of metrics dashboards also started.

The final version of Article Feedback v5 (a quality assessment feature) was activated on the [[:w:Special:ArticleFeedbackv5|English]], [[:w:fr:Sp%C3%A9cial:ArticleFeedbackv5|French]] and [[:w:de:Spezial:Artikelrückmeldungen v5|German]] Wikipedias. A number of bugs were fixed, the feedback page was simplified, and other features such as feedback links and auto-archival were finalized. Development for this feature is now wrapping up.

Design continues for the first version of [[mw:Flow|Flow]], a feed-like interface to enable users to better interact with their projects. An [http://lists.wikimedia.org/pipermail/design/2013-April/000495.html interactive prototype] is being built to help describe multiple functions.

The Editor Engagement Experiments team (E3) focused on its redesign of the [http://blog.wikimedia.org/2013/04/25/try-new-login-accountcreation/ account creation and log-in interface]. The first phase of the launch invited editors and readers on all Wikimedia projects to test the new forms on an opt-in basis, to identify bugs and localization issues across wikis. The new interface is expected to replace the legacy version in May.

For the ''[[mw:Onboarding new Wikipedians|Onboarding new Wikipedians]]'' project, the E3 team completed [[:m:R:OB4|quantitative analysis]] of the latest version of the ''GettingStarted'' landing page, and began prototyping a new version and a navigation system, which will be used for usability testing prior to further development. The launch is expected in early May as well.

=== [[mw:Wikimedia Mobile engineering|Mobile]] ===

An official [[mw:Apps/Commons|Wikimedia Commons app]] for smartphones was released for [https://blog.wikimedia.org/2013/04/29/announcing-the-official-commons-app-for-ios-and-android/ both iOS and Android devices] in April. The team also added support for categories.

Work on [[mw:Wikipedia Zero|Wikipedia Zero]] mostly happened behind the scenes this month, with changes made to the configuration system to better support carrier preferences.

The team also experimented with a log-in/sign-up call to action for logged-out users from the [[mw:Mobile design/Uploads|in-article upload feature]] on the mobile site. This resulted in a spike in new contributors, but the quality of their uploads was lower than anticipated, and the quantity of inappropriate uploads was a burden on the Commons community. The call to action was therefore disabled, and uploading reserved to existing users, leading to a vast improvement in the quality of the uploads: 3/4th of the files are retained on Commons, as compared to less than 1/4 when brand-new users were uploading. To create a more focused uploading workflow, and let mobile uploaders discover more articles to illustrate, a ''Nearby'' view was added to the beta site, showing users a list of articles near them and highlighting the ones that need images. This feature is expected to be activated on the full mobile web site next month.

</div>

Translations:Wikimedia Engineering/Report/2013/April/summary/Page display title/nl

2013-05-28T19:15:06Z

Myr: Created page with "Wikimedia engineering report/2013/April/samenvatting"

Wikimedia engineering report/2013/April/samenvatting

Translations:Help:Extension:Translate/Translation example/Page display title/nl

2013-05-28T11:36:09Z

Myr:

Help:Extension:Translate/Voorbeeld vertalen

Help:Extension:Translate/Translation example/nl

2013-05-28T11:27:00Z

Myr: Created page with "De vertaling is verouderd en zoals gewoonlijk vind men bovenaan de pagina de link om te vertalen: Klik op de link "vertaalde versie"."

<languages/>__NOEDITSECTION__

[[Image:Translate manual - Translate example - 03. LanguageStats short.png|thumb|300px|[[Special:LanguageStats|The translator dashboard]] shows that Fréttinga needs translation: Click on its title to translate it.]]
[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Bekijk alle onvertaalde berichten]]

Welcome, glorious translator. We have a lot of work to do: let's get over the basics very quickly so that you can start as soon as possible. After this tutorial you'll know how to use your personal translation tool set. '''The effects will be permanent, so if you don't want to learn how to use it, please stop reading now.'''

We hope that wherever you come from, the translation administrators have already setup something to translate. This tutorial uses the ''Fréttinga'' page that is created in the [[Special:MyLanguage/Help:Extension:Translate/Page translation example|tutorial for translation administrators]]. The things covered here do not depend on that particular page, and apply to everything you can translate with this tool.

Maybe you already have a link from someone asking you to translate something. If not, you can check [[Special:LanguageStats|Special:LanguageStats, the translator dashboard]], ''in your wiki'' for something to translate. If you just want to see how it works in general, you can still read along and watch the screenshots to get an impression of it.

Usually you cannot make translations without asking for permissions. Some wikis however have enabled translation to all users. You will quickly notice if you lack the rights to translate. If this is the case, contact a translation administrator of your wiki. Let's start with getting to the translation view.

* 1a. Go to the Fréttinga page.
* 2a. Click the "Translate this page" link (if it does not show up you don't have permission to translate).

Or you can try:

* 1b. Go to the [[Special:LanguageStats|translator dashboard]].
* 2b. Click the name of any message group that has untranslated messages.

Messages to translate are grouped by "message group": Each translatable page is a message group, but there can be other kinds of message groups too.

* 3. Choose a language other than the language of the source text (which usually is English or <code>en</code>).

== Translation editor ==

This view and variations of it are the basic interface you will working in. The long list of messages still to be translated may occasionally depress you, but fortunately we don't actually need to watch that list so often. You should see at least some untranslated messages here. Let's make your first translation. Click a link in the left column to get a popup window with the translation editor; you can also double click a message to get the editor inline. You will see the source text you need to translate and a text area where you can write your translation. If you clicked the first message listed for the page ''Fréttinga,'' it should say "Fréttinga" as the content. Since it is a name, you don't usually need to change it, except if your language uses a different writing system, in which case you can choose to transliterate it. Then just click save and you are done!

* 4. Click the message name on the left column.
* 5. In the editor dialog, write the translation of the source text in the place reserved for it.
* 6. Click "Save".
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|A message with a tip and a suggestion from an assistant language]]
Depending on the configuration of the wiki, you may also see other things in the editor besides the source text. There may be suggestions from translation memories or machine translation systems. There can be a section for ''tips'' that provide crucial information that you need to use to make a correct translation. So if there are tips, read them carefully. If there are no tips and you feel like you need them, ask someone in the wiki to add them; if you are knowledgeable enough about the text that needs translation, add them yourself. These tips help you to translate better and faster. Don't feel ashamed to ask for clarifications – it's highly likely that the other tens or hundreds translators are wasting their time thinking of the same issues.

One more thing about the translation aids: if you benefit from seeing the message translated into other languages as additional tip, go to ''[[Special:Preferences|your preferences]] –> Editing –> Translation options'' and add one or more assistant languages for yourself.

Usually there is no need to add a summary if you are making a new translation, unless you want to clarify some decisions you made in terminology or formatting. When changing existing translations it's polite to mention ''"Fixed a spelling error"'' or ''"Use term X consistently"'' and so on, to help other translators understand and improve collaboration. Feel free to make a few more translations and try out the other buttons. Clicking a small downwards-pointing arrow next to suggestions and source text will immediately paste that text in the text area, overwriting anything already in that text area.

== Vertalingweergave ==

Here we are again, watching the list with untranslated messages. If you refresh the page, the list should now be shorter, or even empty. The view has the usual paging controls and description of the group, but more interesting at the top you can choose language, message group and task.

All message groups function the same way, and you don't need to worry about them too much. The important thing is that you always need to choose a message group to work on, and things like statistics and completion percentages are calculated on message group level.
[[Image:Translate manual - Translate example - 08. Review all.png|thumb|300px|Review all messages view, with status in top right]]From the task selector or the tabs at the very top, you can switch to the view suitable for doing other tasks, like review. Depending on the configuration, you should see at least "Review all translations" and possibly "Accept translations". Choose "Review all" and you should see the translations you made together with the source texts. Again, depending on the configuration, you may also see buttons that say "Accept", but grayed out because you cannot accept your own translations. Read more about reviewing translations and other quality assurance methods in the [[Special:MyLanguage/Help:Extension:Translate/Quality assurance|quality assurance page]].

The page can also contain the message group status in the top right corner of the message group description, which can be set for each language of the group; if you see a dropdown selector of the possible states, it means that you can change it, and you should update it when you are working on the translation or if you are reviewing it. See more about workflow states in the [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states page]].

== Belangrijke concepten ==
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|De vertaling is verouderd en zoals gewoonlijk vind men bovenaan de pagina de link om te vertalen: Klik op de link "vertaalde versie".]]
You already know what a message group or a task is, and have seen the translation editor and assistant languages. Now the translation administrator may have continued their [[Special:MyLanguage/Help:Extension:Translate/Page translation example|page translation tutorial]] and changed the contents of the page Fréttinga. When the text that must be translated changes, it will show up again in the list of untranslated messages, prefixed with the text "<code><nowiki>!</nowiki>!FUZZY!!</code>". This is just a marker to make it obvious that a translation needs updating.

When updating translations, be sure to remove the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text if the translation is okay, otherwise it isn't considered translated by the wiki. In some cases you should even add yourself the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text to a translation, if you know it is incorrect, but don't know how to fix it. Be careful about the syntax, it must be exactly right. "<code><nowiki>!</nowiki>!FUZZY!!</code>" may also be added automatically when a new translation is saved, if the automatic checks find likely issues in the translation, like for example unbalanced link syntax missing the other "]" character. You should also get a warning about these when translating.

The outdated translations of translatable pages are marked with a reddish color, shown on the screenshot. If you now return to the translated page by clicking the link on the message group description, you should see that your translations are already there. Most of the translations you will make are applied immediately, with exception about fuzzy messages and some message groups, like many of those in translatewiki.net, where the translation are regularly and manually exported by translation administrators to the software they are used in.

One more useful tip when translating translatable pages: magic words like <tt><nowiki>{{FORMATNUM}}</nowiki></tt> will format the output in the translation language, not in the language of the source text. If you like, you can [[Help:Magic words#Localisation|read more on how magic words work]] and should be used in translations. This is not required reading, though.
<gallery widths=450 heights=400>
Image:Translate manual - Translate example - 06. Editor arrow.png|Translating the first message and using the arrow to copy the suggestion
Image:Translate manual - Translate example - 12. Editor fuzzy.png|Updating a fuzzied or outdated message
Image:Translate manual - Translate example - 15. Translation memory.png|An example with suggestions from the translation memory. The percentage indicates the quality of the suggestion and there's a bullet for each occurrence of the suggestion, which links to the message which contains it.
</gallery>

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]
[[Category:Translate extension tutorials|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Translation example/26/nl

2013-05-28T11:26:59Z

Myr: Created page with "De vertaling is verouderd en zoals gewoonlijk vind men bovenaan de pagina de link om te vertalen: Klik op de link "vertaalde versie"."

De vertaling is verouderd en zoals gewoonlijk vind men bovenaan de pagina de link om te vertalen: Klik op de link "vertaalde versie".

Help:Extension:Translate/Translation example/nl

2013-05-28T11:24:42Z

Myr: Created page with "== Belangrijke concepten =="

<languages/>__NOEDITSECTION__

[[Image:Translate manual - Translate example - 03. LanguageStats short.png|thumb|300px|[[Special:LanguageStats|The translator dashboard]] shows that Fréttinga needs translation: Click on its title to translate it.]]
[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Bekijk alle onvertaalde berichten]]

Welcome, glorious translator. We have a lot of work to do: let's get over the basics very quickly so that you can start as soon as possible. After this tutorial you'll know how to use your personal translation tool set. '''The effects will be permanent, so if you don't want to learn how to use it, please stop reading now.'''

We hope that wherever you come from, the translation administrators have already setup something to translate. This tutorial uses the ''Fréttinga'' page that is created in the [[Special:MyLanguage/Help:Extension:Translate/Page translation example|tutorial for translation administrators]]. The things covered here do not depend on that particular page, and apply to everything you can translate with this tool.

Maybe you already have a link from someone asking you to translate something. If not, you can check [[Special:LanguageStats|Special:LanguageStats, the translator dashboard]], ''in your wiki'' for something to translate. If you just want to see how it works in general, you can still read along and watch the screenshots to get an impression of it.

Usually you cannot make translations without asking for permissions. Some wikis however have enabled translation to all users. You will quickly notice if you lack the rights to translate. If this is the case, contact a translation administrator of your wiki. Let's start with getting to the translation view.

* 1a. Go to the Fréttinga page.
* 2a. Click the "Translate this page" link (if it does not show up you don't have permission to translate).

Or you can try:

* 1b. Go to the [[Special:LanguageStats|translator dashboard]].
* 2b. Click the name of any message group that has untranslated messages.

Messages to translate are grouped by "message group": Each translatable page is a message group, but there can be other kinds of message groups too.

* 3. Choose a language other than the language of the source text (which usually is English or <code>en</code>).

== Translation editor ==

This view and variations of it are the basic interface you will working in. The long list of messages still to be translated may occasionally depress you, but fortunately we don't actually need to watch that list so often. You should see at least some untranslated messages here. Let's make your first translation. Click a link in the left column to get a popup window with the translation editor; you can also double click a message to get the editor inline. You will see the source text you need to translate and a text area where you can write your translation. If you clicked the first message listed for the page ''Fréttinga,'' it should say "Fréttinga" as the content. Since it is a name, you don't usually need to change it, except if your language uses a different writing system, in which case you can choose to transliterate it. Then just click save and you are done!

* 4. Click the message name on the left column.
* 5. In the editor dialog, write the translation of the source text in the place reserved for it.
* 6. Click "Save".
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|A message with a tip and a suggestion from an assistant language]]
Depending on the configuration of the wiki, you may also see other things in the editor besides the source text. There may be suggestions from translation memories or machine translation systems. There can be a section for ''tips'' that provide crucial information that you need to use to make a correct translation. So if there are tips, read them carefully. If there are no tips and you feel like you need them, ask someone in the wiki to add them; if you are knowledgeable enough about the text that needs translation, add them yourself. These tips help you to translate better and faster. Don't feel ashamed to ask for clarifications – it's highly likely that the other tens or hundreds translators are wasting their time thinking of the same issues.

One more thing about the translation aids: if you benefit from seeing the message translated into other languages as additional tip, go to ''[[Special:Preferences|your preferences]] –> Editing –> Translation options'' and add one or more assistant languages for yourself.

Usually there is no need to add a summary if you are making a new translation, unless you want to clarify some decisions you made in terminology or formatting. When changing existing translations it's polite to mention ''"Fixed a spelling error"'' or ''"Use term X consistently"'' and so on, to help other translators understand and improve collaboration. Feel free to make a few more translations and try out the other buttons. Clicking a small downwards-pointing arrow next to suggestions and source text will immediately paste that text in the text area, overwriting anything already in that text area.

== Vertalingweergave ==

Here we are again, watching the list with untranslated messages. If you refresh the page, the list should now be shorter, or even empty. The view has the usual paging controls and description of the group, but more interesting at the top you can choose language, message group and task.

All message groups function the same way, and you don't need to worry about them too much. The important thing is that you always need to choose a message group to work on, and things like statistics and completion percentages are calculated on message group level.
[[Image:Translate manual - Translate example - 08. Review all.png|thumb|300px|Review all messages view, with status in top right]]From the task selector or the tabs at the very top, you can switch to the view suitable for doing other tasks, like review. Depending on the configuration, you should see at least "Review all translations" and possibly "Accept translations". Choose "Review all" and you should see the translations you made together with the source texts. Again, depending on the configuration, you may also see buttons that say "Accept", but grayed out because you cannot accept your own translations. Read more about reviewing translations and other quality assurance methods in the [[Special:MyLanguage/Help:Extension:Translate/Quality assurance|quality assurance page]].

The page can also contain the message group status in the top right corner of the message group description, which can be set for each language of the group; if you see a dropdown selector of the possible states, it means that you can change it, and you should update it when you are working on the translation or if you are reviewing it. See more about workflow states in the [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states page]].

== Belangrijke concepten ==
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|The translation is outdated, and as usual the top of the page gives us the link to translate: Click the link "translated version".]]
You already know what a message group or a task is, and have seen the translation editor and assistant languages. Now the translation administrator may have continued their [[Special:MyLanguage/Help:Extension:Translate/Page translation example|page translation tutorial]] and changed the contents of the page Fréttinga. When the text that must be translated changes, it will show up again in the list of untranslated messages, prefixed with the text "<code><nowiki>!</nowiki>!FUZZY!!</code>". This is just a marker to make it obvious that a translation needs updating.

When updating translations, be sure to remove the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text if the translation is okay, otherwise it isn't considered translated by the wiki. In some cases you should even add yourself the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text to a translation, if you know it is incorrect, but don't know how to fix it. Be careful about the syntax, it must be exactly right. "<code><nowiki>!</nowiki>!FUZZY!!</code>" may also be added automatically when a new translation is saved, if the automatic checks find likely issues in the translation, like for example unbalanced link syntax missing the other "]" character. You should also get a warning about these when translating.

The outdated translations of translatable pages are marked with a reddish color, shown on the screenshot. If you now return to the translated page by clicking the link on the message group description, you should see that your translations are already there. Most of the translations you will make are applied immediately, with exception about fuzzy messages and some message groups, like many of those in translatewiki.net, where the translation are regularly and manually exported by translation administrators to the software they are used in.

One more useful tip when translating translatable pages: magic words like <tt><nowiki>{{FORMATNUM}}</nowiki></tt> will format the output in the translation language, not in the language of the source text. If you like, you can [[Help:Magic words#Localisation|read more on how magic words work]] and should be used in translations. This is not required reading, though.
<gallery widths=450 heights=400>
Image:Translate manual - Translate example - 06. Editor arrow.png|Translating the first message and using the arrow to copy the suggestion
Image:Translate manual - Translate example - 12. Editor fuzzy.png|Updating a fuzzied or outdated message
Image:Translate manual - Translate example - 15. Translation memory.png|An example with suggestions from the translation memory. The percentage indicates the quality of the suggestion and there's a bullet for each occurrence of the suggestion, which links to the message which contains it.
</gallery>

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]
[[Category:Translate extension tutorials|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Translation example/25/nl

2013-05-28T11:24:41Z

Myr: Created page with "== Belangrijke concepten =="

== Belangrijke concepten ==

Help:Extension:Translate/Translation example/nl

2013-05-28T11:23:44Z

Myr: Created page with "== Vertalingweergave =="

<languages/>__NOEDITSECTION__

[[Image:Translate manual - Translate example - 03. LanguageStats short.png|thumb|300px|[[Special:LanguageStats|The translator dashboard]] shows that Fréttinga needs translation: Click on its title to translate it.]]
[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Bekijk alle onvertaalde berichten]]

Welcome, glorious translator. We have a lot of work to do: let's get over the basics very quickly so that you can start as soon as possible. After this tutorial you'll know how to use your personal translation tool set. '''The effects will be permanent, so if you don't want to learn how to use it, please stop reading now.'''

We hope that wherever you come from, the translation administrators have already setup something to translate. This tutorial uses the ''Fréttinga'' page that is created in the [[Special:MyLanguage/Help:Extension:Translate/Page translation example|tutorial for translation administrators]]. The things covered here do not depend on that particular page, and apply to everything you can translate with this tool.

Maybe you already have a link from someone asking you to translate something. If not, you can check [[Special:LanguageStats|Special:LanguageStats, the translator dashboard]], ''in your wiki'' for something to translate. If you just want to see how it works in general, you can still read along and watch the screenshots to get an impression of it.

Usually you cannot make translations without asking for permissions. Some wikis however have enabled translation to all users. You will quickly notice if you lack the rights to translate. If this is the case, contact a translation administrator of your wiki. Let's start with getting to the translation view.

* 1a. Go to the Fréttinga page.
* 2a. Click the "Translate this page" link (if it does not show up you don't have permission to translate).

Or you can try:

* 1b. Go to the [[Special:LanguageStats|translator dashboard]].
* 2b. Click the name of any message group that has untranslated messages.

Messages to translate are grouped by "message group": Each translatable page is a message group, but there can be other kinds of message groups too.

* 3. Choose a language other than the language of the source text (which usually is English or <code>en</code>).

== Translation editor ==

This view and variations of it are the basic interface you will working in. The long list of messages still to be translated may occasionally depress you, but fortunately we don't actually need to watch that list so often. You should see at least some untranslated messages here. Let's make your first translation. Click a link in the left column to get a popup window with the translation editor; you can also double click a message to get the editor inline. You will see the source text you need to translate and a text area where you can write your translation. If you clicked the first message listed for the page ''Fréttinga,'' it should say "Fréttinga" as the content. Since it is a name, you don't usually need to change it, except if your language uses a different writing system, in which case you can choose to transliterate it. Then just click save and you are done!

* 4. Click the message name on the left column.
* 5. In the editor dialog, write the translation of the source text in the place reserved for it.
* 6. Click "Save".
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|A message with a tip and a suggestion from an assistant language]]
Depending on the configuration of the wiki, you may also see other things in the editor besides the source text. There may be suggestions from translation memories or machine translation systems. There can be a section for ''tips'' that provide crucial information that you need to use to make a correct translation. So if there are tips, read them carefully. If there are no tips and you feel like you need them, ask someone in the wiki to add them; if you are knowledgeable enough about the text that needs translation, add them yourself. These tips help you to translate better and faster. Don't feel ashamed to ask for clarifications – it's highly likely that the other tens or hundreds translators are wasting their time thinking of the same issues.

One more thing about the translation aids: if you benefit from seeing the message translated into other languages as additional tip, go to ''[[Special:Preferences|your preferences]] –> Editing –> Translation options'' and add one or more assistant languages for yourself.

Usually there is no need to add a summary if you are making a new translation, unless you want to clarify some decisions you made in terminology or formatting. When changing existing translations it's polite to mention ''"Fixed a spelling error"'' or ''"Use term X consistently"'' and so on, to help other translators understand and improve collaboration. Feel free to make a few more translations and try out the other buttons. Clicking a small downwards-pointing arrow next to suggestions and source text will immediately paste that text in the text area, overwriting anything already in that text area.

== Vertalingweergave ==

Here we are again, watching the list with untranslated messages. If you refresh the page, the list should now be shorter, or even empty. The view has the usual paging controls and description of the group, but more interesting at the top you can choose language, message group and task.

All message groups function the same way, and you don't need to worry about them too much. The important thing is that you always need to choose a message group to work on, and things like statistics and completion percentages are calculated on message group level.
[[Image:Translate manual - Translate example - 08. Review all.png|thumb|300px|Review all messages view, with status in top right]]From the task selector or the tabs at the very top, you can switch to the view suitable for doing other tasks, like review. Depending on the configuration, you should see at least "Review all translations" and possibly "Accept translations". Choose "Review all" and you should see the translations you made together with the source texts. Again, depending on the configuration, you may also see buttons that say "Accept", but grayed out because you cannot accept your own translations. Read more about reviewing translations and other quality assurance methods in the [[Special:MyLanguage/Help:Extension:Translate/Quality assurance|quality assurance page]].

The page can also contain the message group status in the top right corner of the message group description, which can be set for each language of the group; if you see a dropdown selector of the possible states, it means that you can change it, and you should update it when you are working on the translation or if you are reviewing it. See more about workflow states in the [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states page]].

== Important concepts ==
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|The translation is outdated, and as usual the top of the page gives us the link to translate: Click the link "translated version".]]
You already know what a message group or a task is, and have seen the translation editor and assistant languages. Now the translation administrator may have continued their [[Special:MyLanguage/Help:Extension:Translate/Page translation example|page translation tutorial]] and changed the contents of the page Fréttinga. When the text that must be translated changes, it will show up again in the list of untranslated messages, prefixed with the text "<code><nowiki>!</nowiki>!FUZZY!!</code>". This is just a marker to make it obvious that a translation needs updating.

When updating translations, be sure to remove the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text if the translation is okay, otherwise it isn't considered translated by the wiki. In some cases you should even add yourself the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text to a translation, if you know it is incorrect, but don't know how to fix it. Be careful about the syntax, it must be exactly right. "<code><nowiki>!</nowiki>!FUZZY!!</code>" may also be added automatically when a new translation is saved, if the automatic checks find likely issues in the translation, like for example unbalanced link syntax missing the other "]" character. You should also get a warning about these when translating.

The outdated translations of translatable pages are marked with a reddish color, shown on the screenshot. If you now return to the translated page by clicking the link on the message group description, you should see that your translations are already there. Most of the translations you will make are applied immediately, with exception about fuzzy messages and some message groups, like many of those in translatewiki.net, where the translation are regularly and manually exported by translation administrators to the software they are used in.

One more useful tip when translating translatable pages: magic words like <tt><nowiki>{{FORMATNUM}}</nowiki></tt> will format the output in the translation language, not in the language of the source text. If you like, you can [[Help:Magic words#Localisation|read more on how magic words work]] and should be used in translations. This is not required reading, though.
<gallery widths=450 heights=400>
Image:Translate manual - Translate example - 06. Editor arrow.png|Translating the first message and using the arrow to copy the suggestion
Image:Translate manual - Translate example - 12. Editor fuzzy.png|Updating a fuzzied or outdated message
Image:Translate manual - Translate example - 15. Translation memory.png|An example with suggestions from the translation memory. The percentage indicates the quality of the suggestion and there's a bullet for each occurrence of the suggestion, which links to the message which contains it.
</gallery>

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]
[[Category:Translate extension tutorials|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Translation example/19/nl

2013-05-28T11:23:43Z

Myr: Created page with "== Vertalingweergave =="

== Vertalingweergave ==

Help:Extension:Translate/Translation example/nl

2013-05-28T11:16:15Z

Myr: Created page with "Bekijk alle onvertaalde berichten"

<languages/>__NOEDITSECTION__

[[Image:Translate manual - Translate example - 03. LanguageStats short.png|thumb|300px|[[Special:LanguageStats|The translator dashboard]] shows that Fréttinga needs translation: Click on its title to translate it.]]
[[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Bekijk alle onvertaalde berichten]]

Welcome, glorious translator. We have a lot of work to do: let's get over the basics very quickly so that you can start as soon as possible. After this tutorial you'll know how to use your personal translation tool set. '''The effects will be permanent, so if you don't want to learn how to use it, please stop reading now.'''

We hope that wherever you come from, the translation administrators have already setup something to translate. This tutorial uses the ''Fréttinga'' page that is created in the [[Special:MyLanguage/Help:Extension:Translate/Page translation example|tutorial for translation administrators]]. The things covered here do not depend on that particular page, and apply to everything you can translate with this tool.

Maybe you already have a link from someone asking you to translate something. If not, you can check [[Special:LanguageStats|Special:LanguageStats, the translator dashboard]], ''in your wiki'' for something to translate. If you just want to see how it works in general, you can still read along and watch the screenshots to get an impression of it.

Usually you cannot make translations without asking for permissions. Some wikis however have enabled translation to all users. You will quickly notice if you lack the rights to translate. If this is the case, contact a translation administrator of your wiki. Let's start with getting to the translation view.

* 1a. Go to the Fréttinga page.
* 2a. Click the "Translate this page" link (if it does not show up you don't have permission to translate).

Or you can try:

* 1b. Go to the [[Special:LanguageStats|translator dashboard]].
* 2b. Click the name of any message group that has untranslated messages.

Messages to translate are grouped by "message group": Each translatable page is a message group, but there can be other kinds of message groups too.

* 3. Choose a language other than the language of the source text (which usually is English or <code>en</code>).

== Translation editor ==

This view and variations of it are the basic interface you will working in. The long list of messages still to be translated may occasionally depress you, but fortunately we don't actually need to watch that list so often. You should see at least some untranslated messages here. Let's make your first translation. Click a link in the left column to get a popup window with the translation editor; you can also double click a message to get the editor inline. You will see the source text you need to translate and a text area where you can write your translation. If you clicked the first message listed for the page ''Fréttinga,'' it should say "Fréttinga" as the content. Since it is a name, you don't usually need to change it, except if your language uses a different writing system, in which case you can choose to transliterate it. Then just click save and you are done!

* 4. Click the message name on the left column.
* 5. In the editor dialog, write the translation of the source text in the place reserved for it.
* 6. Click "Save".
[[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|A message with a tip and a suggestion from an assistant language]]
Depending on the configuration of the wiki, you may also see other things in the editor besides the source text. There may be suggestions from translation memories or machine translation systems. There can be a section for ''tips'' that provide crucial information that you need to use to make a correct translation. So if there are tips, read them carefully. If there are no tips and you feel like you need them, ask someone in the wiki to add them; if you are knowledgeable enough about the text that needs translation, add them yourself. These tips help you to translate better and faster. Don't feel ashamed to ask for clarifications – it's highly likely that the other tens or hundreds translators are wasting their time thinking of the same issues.

One more thing about the translation aids: if you benefit from seeing the message translated into other languages as additional tip, go to ''[[Special:Preferences|your preferences]] –> Editing –> Translation options'' and add one or more assistant languages for yourself.

Usually there is no need to add a summary if you are making a new translation, unless you want to clarify some decisions you made in terminology or formatting. When changing existing translations it's polite to mention ''"Fixed a spelling error"'' or ''"Use term X consistently"'' and so on, to help other translators understand and improve collaboration. Feel free to make a few more translations and try out the other buttons. Clicking a small downwards-pointing arrow next to suggestions and source text will immediately paste that text in the text area, overwriting anything already in that text area.

== Translation view ==

Here we are again, watching the list with untranslated messages. If you refresh the page, the list should now be shorter, or even empty. The view has the usual paging controls and description of the group, but more interesting at the top you can choose language, message group and task.

All message groups function the same way, and you don't need to worry about them too much. The important thing is that you always need to choose a message group to work on, and things like statistics and completion percentages are calculated on message group level.
[[Image:Translate manual - Translate example - 08. Review all.png|thumb|300px|Review all messages view, with status in top right]]From the task selector or the tabs at the very top, you can switch to the view suitable for doing other tasks, like review. Depending on the configuration, you should see at least "Review all translations" and possibly "Accept translations". Choose "Review all" and you should see the translations you made together with the source texts. Again, depending on the configuration, you may also see buttons that say "Accept", but grayed out because you cannot accept your own translations. Read more about reviewing translations and other quality assurance methods in the [[Special:MyLanguage/Help:Extension:Translate/Quality assurance|quality assurance page]].

The page can also contain the message group status in the top right corner of the message group description, which can be set for each language of the group; if you see a dropdown selector of the possible states, it means that you can change it, and you should update it when you are working on the translation or if you are reviewing it. See more about workflow states in the [[Special:MyLanguage/Help:Extension:Translate/Message group states|message group states page]].

== Important concepts ==
[[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|The translation is outdated, and as usual the top of the page gives us the link to translate: Click the link "translated version".]]
You already know what a message group or a task is, and have seen the translation editor and assistant languages. Now the translation administrator may have continued their [[Special:MyLanguage/Help:Extension:Translate/Page translation example|page translation tutorial]] and changed the contents of the page Fréttinga. When the text that must be translated changes, it will show up again in the list of untranslated messages, prefixed with the text "<code><nowiki>!</nowiki>!FUZZY!!</code>". This is just a marker to make it obvious that a translation needs updating.

When updating translations, be sure to remove the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text if the translation is okay, otherwise it isn't considered translated by the wiki. In some cases you should even add yourself the "<code><nowiki>!</nowiki>!FUZZY!!</code>" text to a translation, if you know it is incorrect, but don't know how to fix it. Be careful about the syntax, it must be exactly right. "<code><nowiki>!</nowiki>!FUZZY!!</code>" may also be added automatically when a new translation is saved, if the automatic checks find likely issues in the translation, like for example unbalanced link syntax missing the other "]" character. You should also get a warning about these when translating.

The outdated translations of translatable pages are marked with a reddish color, shown on the screenshot. If you now return to the translated page by clicking the link on the message group description, you should see that your translations are already there. Most of the translations you will make are applied immediately, with exception about fuzzy messages and some message groups, like many of those in translatewiki.net, where the translation are regularly and manually exported by translation administrators to the software they are used in.

One more useful tip when translating translatable pages: magic words like <tt><nowiki>{{FORMATNUM}}</nowiki></tt> will format the output in the translation language, not in the language of the source text. If you like, you can [[Help:Magic words#Localisation|read more on how magic words work]] and should be used in translations. This is not required reading, though.
<gallery widths=450 heights=400>
Image:Translate manual - Translate example - 06. Editor arrow.png|Translating the first message and using the arrow to copy the suggestion
Image:Translate manual - Translate example - 12. Editor fuzzy.png|Updating a fuzzied or outdated message
Image:Translate manual - Translate example - 15. Translation memory.png|An example with suggestions from the translation memory. The percentage indicates the quality of the suggestion and there's a bullet for each occurrence of the suggestion, which links to the message which contains it.
</gallery>

{{Translatable navigation template|Extension-Translate}}

[[Category:Extension:Translate|{{SUBPAGENAME}}]]
[[Category:Translate extension tutorials|{{SUBPAGENAME}}]]

Translations:Help:Extension:Translate/Translation example/2/nl

2013-05-28T11:16:14Z

Myr: Created page with "Bekijk alle onvertaalde berichten"

Bekijk alle onvertaalde berichten