Wikipedia:A Taberna (técnica)/Arquivo 13

Este é un arquivo da sección A Taberna (técnica) da Taberna
Nesta páxina atópanse algúns dos fíos de conversa tratados nesta sección da Taberna que foron arquivados. Por favor, non edites esta páxina. Para reavivar calquera destes debates, comeza un novo tema na páxina actual.
< Conversas vellas | Arquivos: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18

Melloras no Modelo:Vía

Estiven a facer melloras neste modelo, promovidas por Castelao. Reorganiceino, dividino en varias seccións e doteino de novas etiquetas para precisar información nos artigos sobre rúas e prazas, fundamentalmente. Agora só falta o detalle da personalización para as rúas das grandes cidades galegas, que é algo que inda non conseguín con éxito.

Un saúdo, Pontevedra78 conversa 4 de xaneiro de 2015 ás 21:39 (UTC)

Santa Comba de Orizón

Quizais hai un problema co modelo:Lp Santa Comba de Orizon, que se visualiza mal en Santa Comba de Orizón, Castro de Rei. Pode alguén botarlle un ollo? --Estevo(aei)^{pa o que queiras...} 9 de xaneiro de 2015 ás 01:27 (UTC)

Feito! Penso que xa está amañado. Saúdos, --Elisardojm (conversa) 9 de xaneiro de 2015 ás 03:09 (UTC)

Modelo:Ficha de documento

Veño de crear o Modelo:Ficha de documento, mais non consigo que funcione correctamente. Se alguén que entenda algo pode botarlle unha ollada faríame un enorme favor. Grazas. --AMPERIO (conversa) 4 de febreiro de 2015 ás 17:08 (UTC)

Tiven que poñer os parámetros en inglés porque o módulo, que non modelo, Infobox está nese idioma xa que non é doado traducilo. Fixen que funcionara pero non revisei que todo saíra ben nin revisei que a documentación. Como nota, o módulo Infobox non recibe as imaxes só co nome do ficheiro, hai que pasarllas poñendo [[Ficheiro:Nome_da_imaxe.extensión|tamaño_imaxepx]]. Saúdos, --Elisardojm (conversa) 4 de febreiro de 2015 ás 18:23 (UTC)

VisualEditor News #1—2015

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.

Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

Recent improvements

The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:

• starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
• takes a constructive action, like inserting a citation: green ,
• might remove or lose your work, like removing a link: red , or
• is neutral, like opening a link in a new browser window: gray .

The TemplateData editor has been completely re-written to use a different design based on the same OOjs UI system as VisualEditor. (T67815, T73746.) This change fixed a couple of existing bugs and improved usability. (T73077, T73078.)

Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once.(T78234.)

Editors at the Hebrew and Russian Wikipedia requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace. (T86688, T87027.) If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.

Looking ahead

The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.

We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Please help complete translations of the user guide for users who speak your language.
• Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC); information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins, and you can also contact James F. to learn more about this initiative.
• Talk to the Editing team during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
• Subscribe or unsubscribe at Meta. If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

5 de febreiro de 2015 ás 18:30 (UTC)

Modelo:Imaxe conxunta

Creei este modelo a partir da en.wiki para a visualización dun conxunto de imaxes con rectángulo e pé de foto, probei a usalo no artigo Pobo galego pero non se visualiza. Alguén sabe onde está o erro? --Breogan2008 (conversa) 14 de febreiro de 2015 ás 10:32 (UTC)

E porque non empregas os modelos que xa temos e que están probados e funcionan ben? ({{Imaxe dupla}}, {{Imaxe múltiple}}, {{Montaxe fotográfica}}...) --. HombreDHojalata.^conversa 14 de febreiro de 2015 ás 11:58 (UTC)

Feito. O problema estaba no módulo que usa, Módulo:Imaxe conxunta, cambieille os nomes dos argumentos para que recoñeca os que se lle pasan ao modelo. É un modelo semellante ao de {{Montaxe fotográfica}} que comentas HombreDHojalata, pero neste polo visto todos teñen pé de imaxe no canto de estar pegadas unhas a outras. Hai que revisar unha das imaxes nese artigo, parece que non existe, polo resto queda listo :) ☣Banjo ^{tell me} 14 de febreiro de 2015 ás 13:34 (UTC)

Quedou perfecto!! Moitas grazas --Breogan2008 (conversa) 14 de febreiro de 2015 ás 13:36 (UTC)

VisualEditor News #2—2015

Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:

Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:

After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance ​on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead. (T90734)

Looking ahead

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users at the English Wikipedia, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon. (T90666)

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
• The design research team wants to see how real editors work. Please sign up for their research program.
• File requests for language-appropriate "Negra" and "Cursiva" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

10 de abril de 2015 ás 19:48 (UTC)

Tradución resumida:

Di que se poden enviarse erros do Editor Visual a Phabricator e que aumentou bastante a súa velocidade. Agora están traballando nun sistema de axuda ás citas pero que aínda está en probas. Tamén están traballando nas versión de idiomas con caracteres raros como os asiáticos. Agora, os modelos que non se visualizan no artigo aparecen como unha ficha de crebacabezas para poder configuralos. Saúdos, Elisardojm (conversa) 11 de abril de 2015 ás 22:40 (UTC)

Problemiña nun gráfico

Boas, fixen un gráfico para reflectir a participación nas distintas eleccións municipais en Pontedeume e teño un problema cos resultados do ano 1987. Resulta que ao intruducir a liña para a porcentaxe de abstención dese ano:

from:76 till:100 color:Abs text:Abs(24%)

aparece a seguinte mensaxe de erro:

EasyTimeline 1.90

Timeline generation failed: 1 error found

Line 29: from:76 till:100 color:Abs text:Abs(24%)

- Unknown constant. 'Define $25 = ... ' expected.

Non sei a que se debe pois a liña é idéntica á correspondente aos demais anos, sen que apareza esa mensaxe no resto dos casos. Alguén pode axudarme a resolver o problema? Grazas, --Xosé Antonio (fálame sempre) 12 de abril de 2015 ás 15:18 (UTC)

Amañado por Breogan2008. --. HombreDHojalata.^conversa 12 de abril de 2015 ás 21:02 (UTC)

A verdade é que o problemiña continúa, saúdos --Xosé Antonio (fálame sempre) 14 de xuño de 2015 ás 20:56 (UTC)

Moi posiblemente un bug no cálculo do total... raro que non se dea en outros casos. Queda "apañado" (que non arranxado) con 25% no canto de 24%. Debería comentarse en mw:Extension_talk:EasyTimeline para que revisen o caso. ☣Banjo ^{tell me} 14 de xuño de 2015 ás 21:11 (UTC)

Grazas polo apaño. O que dis do bug sóame a chinés. É mellor que o comentes ti na páxina que dis pois eu, a parte do que expliquei aquí, non sabería que dicir respecto aos aspectos técnicos. Saúdos, --Xosé Antonio (fálame sempre) 14 de xuño de 2015 ás 21:18 (UTC)

Retiro o dito, Banjo. Xa deixo eu un comentario nesa páxina. Saúdos, --Xosé Antonio (fálame sempre) 14 de xuño de 2015 ás 21:22 (UTC)

Atopei un apaño. Non é o desexable, nin moito menos, pero permite mostrar o dato correcto (24%) no canto dun incorrecto (25%). Trátase de poñer o número 4 en código HTML decimal. É dicir, escribir 24%. Como xa dixen, non é moi bonito, mais funciona. A ver se responde alguén na páxina de MediaWiki que poida botar unha man co erro. Eu estiven revisando o código e mais o erro e non sei que o pode causar. O único que logrei foi descubrir que se pode modificar a parte do erro 'Define $25 = ... ' por 'Define $29 = ... ' suprimindo o carácter da porcentaxe. Por algún motivo o software interpreta mal ese anaco de código, así que eu me inclinaría tamén por que se trata dun bug da extensión. Encárgome eu de dar conta en Phabricator se ninguén responde en MediaWiki esta semana. --Toliño ^{Fala aquí comigo} 16 de xuño de 2015 ás 12:04 (UTC)

Grazas polo interese, Toliño. Eu non entendo do tema pero visto desde fóra eche ben raro, saúdos, --Xosé Antonio (fálame sempre) 16 de xuño de 2015 ás 20:01 (UTC)

Finalmente, informei do problema en Phabricator: T103492. --Toliño ^{Fala aquí comigo} 23 de xuño de 2015 ás 09:59 (UTC)

VisualEditor News #3—2015

Did you know?

When you click on a link to an article, you now see more information:

The link tool has been re-designed:

There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector. (T98085)

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Exemplo", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
• If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
• If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

13 de xuño de 2015 ás 10:44 (UTC)

Modelos sen categoría

Repasando "Categorías requeridas" fun bater con esta: Categoría:Wikipedia templates to be automatically substituted. Contén tres modelos: Modelo:Chembox subst, Modelo:Chembox subst explosive, e Modelo:Subst only.

Alguén que entenda disto debería botarlles un vistazo e eliminalos ou categorizalos onde corresponda. Pedro --Lameiro ^(conversa) 23 de xuño de 2015 ás 19:42 (UTC)

Máis: Outra categoría inexistente, Categoría:Páxinas nas que se supera a profundidade de expansión, que contén dous modelos: Modelo:Luaj, e Modelo:Luaj/uso.

Pedro --Lameiro ^(conversa) 23 de xuño de 2015 ás 20:01 (UTC)

A segunda é unha categoría automática do sistema para levar conta das páxinas nas que hai demasiados bucles aniñados (derivados do uso dalgún modelo). Con respecto á outra categoría, simplemente é froito dun copia-e-pega do modelo "Subst only" de en.wp sen traducir nada. Como ningún dos tres modelos citados ("Chembox subst", "Chembox subst explosive", "Subst only") ten uso, procedo a borralos. Procedo a amañar as cousas. --Toliño ^{Fala aquí comigo} 24 de xuño de 2015 ás 10:39 (UTC)

Mapas de localización, problemas

Depois de moito escornar, vexo que hai dous tipos de Mapas de localización: uns referenciados con coordenadas de límite de bordo e centro, como [1]; outros cuns "valores determinantes" XY, como [2]. Pois ben, os segundos resultan imposíbeis de utilizar, polo menos con coordenadas xeográficas normais, e sempre sae unha mensaxe de erro. Ademáis vexo que os mapas de localización están sempre arrimados á esquerda, e non responden ao parámetro de localización.--Gradebo (conversa) 11 de xullo de 2015 ás 20:08 (UTC)

Non entendín exactamente cal é o problema. Queres empregar unhas coordenadas GPS nun formato concreto para indicalas nun mapa, é eso? Sobre un mapa esas coordendas tanto ten a precisión que teñan, o mapa soe ser o suficientemente pequeno para resultar irrelevante esa precisión. Polo tanto empregar coordenadas gps non ten moito senso-prioridade. Se o que queres é que se amosen esas coordenadas sobre o mapa hai exemplos na páxina de axuda sobre como crear táboas indicando sobre imaxes (mapas) puntos concretos. 80.232.216.127 13 de agosto de 2015 ás 11:09 (UTC)

O problema é exactamente o que digo. Vexo que ninguén controla.—o anterior comentario sen asinar foi feito por Gradebo (conversa • contribucións) 6/11/2015 14:29

As mesmas, exactamente as mesmas, plantillas de mapa de localización, funcionan en en.wikipedia, e en gl.wikipedia non. Isto escápaseme totalmente... que alguén o mire, home!—o anterior comentario sen asinar foi feito por Gradebo (conversa • contribucións) 6 de novembro de 2015 ás 15:48

O que pasa é que na wiki en inglés usan un novo módulo e nós aquí temos o Modelo:Mapa de localización que é máis antigo. Habería que mirar ese módulo e ver se pode traerse á Galipedia e se funciona, pero iso levará un tempo porque antes de cambiar nada hai que facer probas de que o módulo funcione correctamente nos artigos nos que está a usarse o modelo, e obviamente esas probas non poden facerse nos artigos porque poderían facer que apareceran mal centos de artigos. Eu agora mesmo estou liado co wikimaratón de mañá, quizais podería miralo nun par de días. Saúdos, --Elisardojm (conversa) 6 de novembro de 2015 ás 17:33 (UTC)

Trebello ventás emerxentes

O trebello Wikipedia:Trebellos/Ventás emerxentes de navegación leva ~un par de días indicando que o script que usa está sen manter dende 2009 e suxire empregar a función en probas de Ventás emerxentes. Eu teño usado este trebello algunha que outra vez, pero xa o desactivei, e persoalmente non uso a nova función. Non sei ata que punto é popular o trebello en sí entre os editores habituais. Polo momento non hai problemas en deixalo habilitado para quen o requira, pero no momento no que a funcionalidade nova das ventás estea fora de probas case habería que deshabilitar o trebello este en favor dela. ☣Banjo ^{tell me} 12 de agosto de 2015 ás 14:07 (UTC)

VisualEditor News #4—2015

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

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

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

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Negra" and "Cursiva" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

—Elitre (WMF), 14 de agosto de 2015 ás 22:28 (UTC)

VisualEditor News #4—2015

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

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

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

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Negra" and "Cursiva" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

—Elitre (WMF), 15 de agosto de 2015 ás 02:40 (UTC)

Trebello traducións

Aínda que con moitas eivas o trebello de traducións da wikipedia fornece datos moi interesantes Especial:ContentTranslationStats. Así do galego fixéronse 33 traducións: 17 ao castelán, 10 ao portugués, 3 ao catalán, 2 ao esperanto e 1 ao inglés. E ao galego realizáronse 184 traducións:65 do español, 56 do inglés, 16 do portugués, 15 do francés, 11 do catalán, 7 do alemán, 6 do asturiano, etc. A primeira lingua en cantidade de traducións é o catalán con máis de 2900 (a inmensa maioría procedentes do inglés e o español) e da que máis se traduce é do inglés con máis de 13000.--HacheDous=0 (conversa) 20 de setembro de 2015 ás 15:33 (UTC)

A ferramenta traduce bastante ben, e axuda bastante a traer artigos, sobre todo do castelán e do catalán, porque mantén a estrutura dos artigos e busca as ligazóns internas. A pega é que aínda está en probas e teñen que rematar cousas, por exemplo o outro día vin que non ten ningunha sección para traducir as referencias e quedan mal formatadas. Saúdos, --Elisardojm (conversa) 20 de setembro de 2015 ás 20:57 (UTC)

Novo Trebello: Xustificar parágrafos

Ola a todos!

Hai un novo trebello dispoñible para o seu uso, é totalmente opcional, e podedes atopalo en Preferencias-> Trebellos como é habitual, neste caso ao final da lista, na sección "Aparencia". O trebello en sí chámase Xustificar os parágrafos.

É unha pequena modificación visual, que fai que tódolos parágrafos de texto vaian xustificados á marxe dereita. Podedes probalo nalgún artigo de certa extensión para comprobar ben a diferenza visual.

Eu acabo de activalo, e para mín xa é imprescindible :) Saúdos! ☣Banjo ^{tell me} 1 de outubro de 2015 ás 13:55 (UTC)

Grazas polo aviso, vouno probar agora mesmo :) Saúdos, --Elisardojm (conversa) 1 de outubro de 2015 ás 21:01 (UTC)

Refundir dous artigos

Boas: Igual sería bo refundir os artigos Departamento de ultramar e Departamentos e territorios de ultramar de Francia, porque teño para min que tratan de mesmo. Se estades de acordo, eu mesmo o fago. Angeldomcer (conversa) 5 de outubro de 2015 ás 09:36 (UTC)

Tratan do mesmo si, por min adiante. Cando quede todo o contido movido nun só artigo definitivo marca o outro artigo duplicado co marcador {{fusión|NomeDoArtigoQueVaiQuedar}} e xa me encargo eu da fusión de historiais. Grazas! ☣Banjo ^{tell me} 5 de outubro de 2015 ás 09:49 (UTC)

Categoría:Wikipedia:Páxinas con erros de referencia

Ola a todos. Dende a semana do 12 de outubro a nova versión de MediaWiki inclúe unha nova categoría interna de mantemento, Categoría:Wikipedia:Páxinas con erros de referencia. Nesta categoría inclúense automáticamente tódolos artigos que teñan algún problema na definición das referencias, normalmente por usos incorrectos ou omisións das etiquetas <ref>...</ref> ou <references>. Os mensaxes de erro nestes casos adoitan ser explicativos e indicar específicamente a causa do problema, polo que en xeral son de doada solución. Aínda así se houbese calquera dúbida avisade e reviso sen problema :) Saúdos! ☣Banjo ^{tell me} 26 de outubro de 2015 ás 07:22 (UTC)

Ala, máis leña! :) Grazas polo aviso Banjo. Saúdos, --Elisardojm (conversa) 26 de outubro de 2015 ás 09:32 (UTC)

VisualEditor News #5—2015

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

Did you know?

You can use the visual editor on smartphones and tablets.

Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Cambiar á edición visual".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.

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

Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements

Educational features: The first time ever you use the visual editor, it now draws your attention to the Ligazón and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.

Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Inserir Imaxes e ficheiros multimedia" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.

Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use it on all devices regardless of size if they wish. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Borrar" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Especial:Preferences.

Future changes

You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Editar" and "Editar a fonte" tabs into a single "Editar" tab, similar to the system already used on the mobile website. The "Editar" tab will open whichever editing environment you used last time.

Let's work together

• Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

—Elitre (WMF), 30 de outubro de 2015 ás 18:18 (UTC)

Modelo:ZWEb

Ao fusionar historiais con unha das redireccións que apuntaba a esta páxina quedou unha "auto-redirección", o sistema non me permite editar/mover/borrar a páxina. Abrín unha petición no Phabricator, T120140. En cando reciba novas actualizo aquí. ☣Banjo ^{tell me} 2 de decembro de 2015 ás 22:42 (UTC)

Solucionado. ☣Banjo ^{tell me} 2 de decembro de 2015 ás 22:49 (UTC)

Grazas Banjo :) Saúdos, Elisardojm (conversa) 3 de decembro de 2015 ás 08:57 (UTC)

VisualEditor News #6—2015

Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Especial:Preferences and choosing the setting that you want:

The current plan is for the default setting to have the Edit button open the editing environment you used most recently.

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

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

Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements

You can switch from the wikitext editor to the visual editor after you start editing. The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

Future changes

The single edit tab project will combine the "Editar" and "Editar a fonte" tabs into a single "Editar" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Editar" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Edición tab of Especial:Preferences in the drop-down menu about "Modo de edición:".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

Testing opportunities

• Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
  • Lembrar o último editor usado,
  • Sempre amosarme o editor visual se é posible,
  • Sempre amosarme o editor de código, and
  • Amosarme as dúas lapelas de edición. (This is the current state for people already using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Grazas!

Elitre (WMF), 25 de decembro de 2015 ás 00:06 (UTC)