사용자토론:Naturehead/보존문서2

부산대학교 알찬 글 해제 토론

부산대학교 문서에 대한 알찬 글 해제 토론(토론 링크)을 열었습니다. 참여를 부탁드립니다. --천리주단기 通 2011년 11월 17일 (목) 10:54 (KST)

특삭

지정하신 1개 판 이외에 14개 판을 더 보이지 않게 설정 했습니다. 해당 판 모두 개인정보가 있더군요.--Park4223 (토론) 2012년 2월 17일 (금) 11:34 (KST)

특삭 요청을 처음 해본 터라 전체를 다 요청해야 하는지 우물쭈물하다가 한개 판만 신청했는데, 알아서 처리해주셔서 감사합니다. --자연머리 (토론) 2012년 2월 17일 (금) 21:26 (KST)

기념 반스타 증정

	모임 참석 기념(지부 1차 모임)
	이번 지부모임에 나오신분께 반스타를 드립니다. --Dynamicwork (민원) 2012년 3월 11일 (일) 00:04 (KST)

감사합니다. :-) --자연머리 (토론) 2012년 3월 11일 (일) 00:46 (KST)

대문 수정 토론

위키백과토론:대문#최종 총의에서 대문 수정안에 대한 토론이 벌어지고 있습니다. 많은 참여 바랍니다 :) --관인생략 토론·기여·메일 2012년 3월 14일 (수) 15:43 (KST)

출처론 답변드립니다.

Reiro님, 근본적으로 상식과 출처를 결부시키는 것 자체가 논란의 빌미를 제공하게 되는 이유입니다. 그것이 정말 필요하냐 아니냐는 차치하고 말이죠. 편집자의 입장에서 보았을 때, 상식은 그것을 표현하는 '형식'에 상관없이 보편적으로 독자가 알고 있을 것으로 간주하고 적어내려가는 '내용'입니다. 여기에서 어디까지가 상식이고 어디까지가 전문적 지식인지를 따지는 것은 불필요한 일입니다. 행여 일부 사용자에게 그것이 상식으로 받아들여지지 않을 수 있는 가능성이 있다곤 치더라도 물 링크를 걸어놓으면 그만입니다. 위키백과에 수없이 얽혀있는 문서간의 연결고리는 첫째, 독자의 이해를 돕기 위한 것이며 둘째, 본문 내용보다 출처의 양이 지나치게 많아지는 것을 막기 위한 것이기도 합니다.

— 자연머리님

1. 제가 그 '상식론'을 싫어하는 부류이고, 그래서 출처를 중요시하죠. 2. '물 문서 자체'에서는 물의 끓는점에 대한 출처쯤은 있어야 하지 않을까요? 다른 곳서 링크를 걸어도 뭔가 "본 문서"에선 그것에 대한 출처쯤은 있어야 하지 않겠습니까.--Reiro (토론) 2013년 12월 30일 (월) 10:27 (KST)

말이 명확하지 않을 것 같아 좀 덧붙입니다. 애초에 보편적인 지식은 출처 안 붙여도 되네 하면서 말장난한 쪽은 제가 아니라 상대였고, 저는 그런 부분에까지 출처를 달아야 한다고 생각하는 부류입니다. 그리고 연결 고리를 그만두고라도, '물'문서 자체에는 '물의 끓는점'에 대한 출처를 적어야지요. 아니면 어디에 출처를 달까요? 끓는점 문서? 왜 물 문서에서 다루는 정보의 출처를 다른 문서까지 가서 봐야 합니까?

"편집자의 입장에서 보았을 때, 상식은 그것을 표현하는 '형식'에 상관없이 보편적으로 독자가 알고 있을 것으로 간주하고 적어내려가는 '내용'입니다"라 했는데, 위키백과에선 편집자가 문외한이라 가정하고 작성합니다. 당장 영어판 위키백과의 천체 문서 알찬글 아무 거나 한 번 뒤져보세요. 하다못해 지구의 모양에 대한 '보편적인' 정보까지 출처가 달려 있습니다. 하나 더 덧붙이자면, 저 토론에서 제가 제기한 볼츠만 공식은 이전 대선에서 새누리당이 안철수 흠집내기용으로 논문 표절 의혹을 제기한 덕분에 유명했습니다. 논문에 저것 출처 안 달았다고요. 그런데 서울대 연구진실성위원회는 인용 안 한 것이 보편적으로 사용되는 공식이어서 연구윤리를 위반한 것이라고 할 수 없다고 합니다.[1] 누가 '널리 알려졌으니 출처 필요 없어요'라 해도 그건 그 사람 이야기죠. 오히려 널리 알려진 이야기라면 당연히 출처 구하기가 더 쉽지 않을까요? 그럼 달면 되잖습니까. --Reiro (토론) 2013년 12월 30일 (월) 17:25 (KST)

1. 상식론을 싫어하고 좋아하고는 상관 없다고 생각하기 때문에 Reiro님의 주관이 논란의 빌미를 제공하게 된다고 적은 것입니다. 1에 이어서 2. 물론 물 문서 안에 물에 대한 끓는 점에 대한 출처쯤은 있어야 바람직하겠지요. 제 의도는 그러한 '상식적인' 수준의 지식은 그 지식이 가리키는 표제어에 대해 풀이하는 문서에서 풀어쓰고 다른 문서에서 문서 고리로 연결하면 그만이라는 뜻입니다. 물론 위키백과는 성장하고 있는 것이기 때문에 현재 [[물]] 문서에 물 끓는 점의 출처가 없을지도 모르죠. 편집자가 일일이 문서를 찾아다니면서 출처가 달려있는지 없는지 찾는 것보다 문서의 살을 찌우는 것에 집중하기 위해 문서고리를 달고 파란 문서들의 내용을 어느 정도 믿고 편집할 수 있는 것입니다. 행여 해당 문서에 끓는 점 출처가 없다고 해서 그것을 굳이 지금 편집하는 문서에 출처를 찾아 추가하는 의무로 받아들여서는 안되는 것입니다. 가능하다면 '물' 문서에 출처가 달려있는 것이 좋다는 것이지요.

이어 덧붙이신 '상대가 먼저 말장난했다'는 부분을 검토했는데요, '인물의 역사를 논할 때 큰 사건이므로 출처가 있어야 한다'는 의견에는 동의합니다만 그것이 건국이라는 사건의 주체인 나라, [[후금]] 문서에 있는 것이 더 좋다는 게 제 개인적인 입장입니다. [[후금]] 문서에조차 건국 년도에 대한 출처가 없는 것이 현재 상황이지요, Reiro님께서 '후금 문서에도 출처가 없으므로 건국을 주도한 [[아이신기오로 도르곤]] 문서를 편집하는 편집자가 나서서 출처를 달기 바란다.' 라는 의견을 피력하셨으면 좀 더 건설적인 결과가 나왔을 것이라고 생각합니다. 이것은 제가 [[월경 주기]]를 편집하면서 그 표제어보다도 좀 더 알려진 단어인 혈액 응고가 빨간 색(문서 없음)이라고 해서 해당 문서를 생성/편집할 의무가 있지 않은 것과 상통합니다. 단지 이 경우에는 좋은 글로서 알맞는가 부족한가를 따지면 되는 것이었죠. 게다가 애초에 논쟁이 불거진 좋은 글 선정 절차에서 Reiro님께서 보여주신 의견에 따라 그 후 문서에 출처가 보강되었으므로 저에게 출처를 달라 말라 물어보실 사안은 아니라고 생각합니다. 결과적으로 봤을 때 상대분도 어느정도 Reiro님의 의견을 납득했으니 출처를 달았겠지요. 덧붙여 저건 말장난이 아니라 의견 불일치에서 뒤따른 감정적인 반대의견이지 저런 표현을 말장난이라고 생각하신다니, Reiro님께서도 감정적으로 반응하고 계신 것 같습니다. 열좀 가라앉히세요. :)

아, 그리고 위에 적으신 편집자가 문외한이라 가정하고 부분에서 '편집자'가 아니라 '독자'로 적는 게 맞는 것 같습니다. 그렇다면 결국 제 말과 같은 뜻이네요. 편집자가 봤을 때 '문외한인 독자도 이해할 만한' 수준으로 편집하는 것이 위키백과입니다. 다른 사용자가 보았을 때 그 수준이 높다고 생각되면 누군가가 수정/보강하거나, 토론 문서에서 토론하는 거죠. 좋은 글 선정 때 수정될 수도 있는 것이고요. --자연머리 (토론) 2013년 12월 31일 (화) 00:22 (KST)

1.도르곤 문서에서 후금 건국일자까지 출처를 요구한 건 사학에서 년도가 특히 중요하기 때문입니다. 가령 쇼와 천황문서의 48번 출처는 "1931년 9월 18일 밤, 만주 사변이 일어났다"는 데에 붙어 있습니다. "만주 사변은 일반인이 모를 수도 있다" 이 문제가 아닙니다. 물 끓는점 역시 아예 '분야'가 다른 사회적 사건에 관련한 것이라면 모를까(익사 사건) 같은 계열인 '과학' 관련 문서라면 달려야겠죠. 그러니까 학문의 성격에 따라, 정보의 중요성이 조금씩 다르다는 겁니다. 물론 제가 초보자에게까지 이렇게 따지고 드는 건 별로 좋아하지 않지만 좋은글 수준이라면 이야기가 다르죠.

2.감정적이었던 건 반성합니다.--Reiro (토론) 2013년 12월 31일 (화) 05:24 (KST)

결국엔 이건 저도 비꼬는거군요. -- S.H.Yoon 論 · 기여 · F.A. 2013년 12월 31일 (화) 05:59 (KST)

어느 부분에서 비꼰다는 내용인지 모르겠습니다. 단지 학계에 따라 (수학,과학 등) 중요한 요소에는 출처 넣어야 한다고만 말한 것입니다. 어느 곳이 거슬렸는지 말해주시면 감사하겠습니다.--Reiro (토론) 2013년 12월 31일 (화) 10:40 (KST)

"애초에 보편적인 지식은 출처 안 붙여도 되네 하면서 말장난한 쪽은 제가 아니라 상대였고" 뭐죠? -- S.H.Yoon 論 · 기여 · F.A. 2013년 12월 31일 (화) 13:14 (KST)

Ready for translation: VisualEditor News #9—2014

Hi! This is an invitation to join translators working on the November's issue of the VisualEditor monthly newsletter, which will be widely delivered later this week. The previous bulletin was published in 10 languages, but the translation was completed only for three of them. Will we do better this month? We'd like to reach many more communities in their own language this time, as we're announcing interesting developments like the new ability to add tables and their elements. Thanks a lot for your help! Elitre (WMF) 2014년 11월 11일 (화) 06:27 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. If you need further help or would like to receive a talk page message to be notified of future translations, please contact me directly.

VisualEditor News #9—2014

Did you know?

VisualEditor is also available on the mobile version of Wikipedia. Log in and click the pencil icon to open the page you want to edit. Click on the gear-shaped settings button in the upper-right corner to pick which editor to use. Choose "⧼Mobile-frontend-editor-visual-editor⧽" to use VisualEditor, or "⧼Mobile-frontend-editor-source-editor⧽" to use the wikitext editor.

It will remember whether you used wikitext or VisualEditor, and use the same editor the next time you edit an article.

The user guide has information about how to use VisualEditor. Not all features are available on the mobile website.

Since the last newsletter, the Editing Team has fixed many bugs and requests, and worked on support for editing tables and for using non-Latin languages. Their weekly updates are posted on Mediawiki.org. Informal notes from the recent quarterly review were posted on Meta.

Recent improvements

Basic support for inserting tables and changing the number of rows and columns in them was just introduced to Wikipedias. Advanced features, like dragging columns to different places, will be added later.

To help editors find the most important items more quickly, some items in the toolbar menus are now hidden behind a "더 보기" item, such as "밑줄" in the styling menu.

The French Wikipedia should see better search results for links, templates, and media because the new search engine was turned on for everyone there. This change is expected at the Chinese and German Wikipedias this week, and the following week at the English Wikipedia.

The "pawn" system has been mostly replaced. Bugs in this system sometimes added a chess pawn character to wikitext. The replacement provides better support for non-Latin languages, with full support hopefully coming soon.

VisualEditor is now provided to editors who use Internet Explorer 10 or 11 on desktop and mobile devices. Internet Explorer 9 is not supported yet.

The keyboard shortcuts for items in the toolbar menus are now shown in the menus.

VisualEditor will replace the existing design with a new theme from the User Experience/Design group. The appearance of dialog boxes has already changed in the mobile version. The appearance on desktops will change soon. You are welcome to compare the old "Apex" design and the new "MediaWiki" theme which will replace it.

Several bugs were fixed for internal and external links. Improvements to MediaWiki's search solved an annoying problem: If you searched for the full name of the page or file that you wanted to link, sometimes the search engine could not find the page. A link inside a template to a local page that does not exist will now show red, exactly as it does when reading the page. Due to an error, for about two weeks this also affected all external links inside templates. Opening an auto-numbered link node like [2] with the keyboard used to open the wrong link tool. These problems have all been fixed.

TemplateData

The tool for quickly editing TemplateData has been deployed to all Wikimedia Foundation wikis on Thursday, 6 November. This tool was already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "틀데이터 관리" button at the top. Read the help page for TemplateData to learn more about it. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.

You can use the new autovalue setting to pre-load a value into a template. This can be used to substitute dates, as in this example, or to add the most common value for that parameter. The autovalue can be overridden by the editor, by typing something else in the field.

In TemplateData, you may define a parameter as "required". The template dialog box in VisualEditor will warn editors if they leave a "required" parameter empty, and they will not be able to delete that parameter. If the template can function without this parameter, then please mark it as "제안" or "선택 사항" in TemplateData instead.

Looking ahead

The VisualEditor team plans to add auto-fill features for citations soon. The appearance of the media search dialog will improve, to make picking between possible images easier and more visual. The team posts details about planned work on the VisualEditor roadmap.

The user guide is being updated to add information about editing tables. The translations of the user guide for most languages except Spanish, French, and Dutch are significantly out of date. Please help complete the current translations for users who speak your language. Talk to us if you need help exporting the translated guide to your wiki.

You can influence VisualEditor's design! Tell the VisualEditor team what you want changed during the office hours via IRC. The next sessions are on Wednesday, 19 November at 16:00 UTC and on Wednesday 7 January 2015 at 22:00 UTC. You can also share your ideas at mw:VisualEditor/Feedback.

Also, user experience researcher Abbey Ripstra is looking for editors to show her how they edit Wikipedia. Please sign up for the research program if you would like to hear about opportunities.

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. Subscribe or unsubscribe at Meta. Thank you! —Elitre (WMF)

2014년 11월 15일 (토) 08:28 (KST)

Ready for translation: VisualEditor News #10—2014

Hi! This is an invitation to join translators working on the December's issue of the VisualEditor monthly newsletter, which will be widely delivered later this week. The amazing translators' community has already found out about it prior to this announcement... But how is your language doing this time? Find out now and contribute! Thanks a lot for your help! Elitre (WMF) 2014년 12월 22일 (월) 16:35 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. If you need further help or would like to receive a talk page message to be notified of future translations, please contact me directly.

VisualEditor News #10—2014

알고 계십니까?

이제 시각편집기로 기본적인 표 편집이 가능합니다. 여러분은 표 작업 중에 버튼 하나로 행과 열을 더하거나 없앨 수 있습니다.

사용자 안내서에는 더 자세한 시각편집기 사용법이 나와있습니다.

Since the last newsletter, the Editing Team has fixed many bugs and worked on table editing and performance. Their weekly status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).

이번 개선사항

표 편집하기의 기본 기능이 도입되었습니다. 이제 여러분은 표의 추가 또는 삭제, 행과 열의 추가 또는 삭제, 표 설명문의 삽입과 삭제, 셀 합치기를 할 수 있습니다. 셀 내용을 변경하려면, 그 안을 더블클릭 하세요. 더 많은 기능은 수개월 내에 추가될 것입니다. 이에 더해서, 시각편집기는 이제 오류가 나거나 잘못된 rowspan 과 colspan 요소가 보이면 이를 고치려 하는 대신 무시하고 지나갑니다.

이제 시각편집기 내에서 도구 메뉴나 ^ Ctrl+F 또는 ⌘ Cmd+F 버튼을 통해 찾아 바꾸기 기능을 사용할 수 있습니다.

You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "문단" into a "상자 인용".

Some new keyboard sequences can be used to format content. At the start of the line, typing "* " will make the line a bullet list; "1." or "#" will make it a numbered list; "==" will make it a section heading; ": " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change.

There are also two other keyboard sequences: "[[" for opening the link tool, and "{{" for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ^ Ctrl+K to open the link editor, still work.

If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.

You can again create and edit galleries as wikitext code.

기대할 부분

The current VisualEditor design will be replaced with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at mediawiki.org in late December and on other sites in early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)

The Editing team plans to add auto-fill features for citations in January.

Planned changes to the media search dialog will make choosing between possible images easier.

다 같이 노력합시다

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Translations of the user guide for most languages are outdated. Only Ukrainian, Portuguese, Spanish, French, and Dutch translations are nearly current. Please help complete the current translations for users who speak your language.
• Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
• File requests for language-appropriate "굵게" and "기울임꼴" icons for the character formatting menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• 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. Subscribe or unsubscribe at Meta. Thank you!

— Elitre (WMF)

2014년 12월 27일 (토) 03:56 (KST)

Ready for translation: VisualEditor News #1—2015

Hi! Apologies if you're reading this message more than once. This is an invitation to join translators working on the February's issue of the VisualEditor multilingual newsletter. This time it features an important announcement about a series of meetings where VE tasks on Phabricator will be triaged live and publicly, starting next week. Since we want many people to be aware of this ASAP (especially volunteer developers!), we have a time constraint which means we'll deliver to the wikis on Thursday morning PST this week. Thanks a lot in advance, we know you'll do whatever it takes to keep your community up-to-date, and appreciate it a lot. m:User:Elitre (WMF), 2015년 2월 3일 (화) 07:08 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. If you need further help or would like to receive a talk page message to be notified of future translations, please contact me directly.

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)

2015년 2월 6일 (금) 03:08 (KST)

Ready for translation: VisualEditor News #2—2015

Hi! This is an invitation to join translators working on the April's issue of the VisualEditor monthly newsletter, which will be widely delivered towards the end of next week. The previous bulletin was published in 26 languages—the translation was completed only for ten of them. Will we do better this month? We'd like to reach many more communities in their own language this time, as VE recently became the main editor at other 50+ Wikipedias, and we're announcing interesting developments (auto-fill features for citations, improved special character inserter, drag and drop for categories, invisible templates now marked by a puzzle piece icon, and more). Thanks a lot for your help! Elitre (WMF) 2015년 4월 5일 (일) 07:38 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. If you need further help or would like to change the page where you're notified of future translations, please contact me directly.

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 "굵게" and "기울임꼴" 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)

2015년 4월 11일 (토) 04:45 (KST)

알림

현재 이 위키에는 새로운 버전의 ref툴바가 기본으로 지정되어 있습니다. 그러나 현재 귀하의 사용자 자바스크립트 문서(사용자:Naturehead/monobook.js)에는 이전 버전의 ref툴바가 지정되어 있어 이를 알려드리려고 합니다. 이전 ref툴바와 관련된 코드를 삭제하셔야 최신 버전을 원활하게 사용하실 수 있습니다.

만약 새로운 버전과의 충돌 없이 기존에 쓰시던 ref툴바를 계속 쓰고 싶으시다면, 환경 설정에서 ‘ref툴바’의 체크를 해제하면 됩니다. 감사합니다. (이전 코드를 지정한 사용자 모두에게 일괄적으로 남기는 글입니다.)--Namoroka (토론) 2015년 5월 16일 (토) 23:02 (KST)

Ready for translation: VisualEditor News #3—2015

Hi! This is an invitation to join translators working on the June's issue of the VisualEditor multilingual newsletter, which will be widely delivered at the end of this workweek. You may have noticed that the bulletin is now getting published once every two months more or less, but we're keeping the length manageable ;) Thanks a lot for your help! — Elitre (WMF) 2015년 6월 9일 (화) 02:41 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. If you need further help or would like to change the page where you're notified of future translations, please contact me directly.

PPS: Also, watch out for announcements of the upcoming VE-translathon! Everybody getting this message will be particularly welcome to join that activity during Wikimania.

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, "예시", 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)

2015년 6월 13일 (토) 19:45 (KST)

Early invitation: join VisualEditor's 2015 Translathon

Hello!

You are invited to join the 2nd edition of the VisualEditor Translathon! It is a translation rally, focused on interface messages and help pages related to VisualEditor.

In order to participate, you need to sign up on the Translathon page. The top 3 contributors will each win a Wikipedia t-shirt of their choice from the Wikipedia store. Translations made between July 15th and July 19th (CDT time zone) qualify.

If you are attending Wikimania Mexico this year, you are also welcome to join a related sprint during the Hackathon in Workplace 1 - Don Américo, Thursday 16 July at 4:00 p.m (CDT) at the conference venue, so you can meet other fellow translators and get support if you need some.

Interface messages have the priority. You will need to create an account at translatewiki.net in order to work on them, if you don't have one. It is recommended to create the account ASAP, so that it can be manually confirmed in time.

You can also help translate documentation pages about VisualEditor on mediawiki.org. You can use your Wikipedia account there. You will find instructions, links and other details on the Translathon page.

Thanks for your attention, and happy translating! Elitre (WMF) 2015년 7월 11일 (토) 11:59 (KST)

Ready for translation: VisualEditor News #4—2015

Hi! This is an invitation to join translators working on the August's issue of the VisualEditor multilingual newsletter, which will be widely delivered at the end of this workweek. Among other things, this month it features the names of the top contributors for the recent VisualEditor 2nd Translathon. Thanks a lot for your support, as usual! Elitre (WMF), 2015년 8월 11일 (화) 01:49 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones.

PPS: We are maintaining a list of editors who have worked on VE-related content (such as newsletters). We only use it to notify them of translation opportunities, to make sure they don't miss Translathons, etc. If you would like messages like this one to be delivered on your talk page at a different WMF project, need any help with translations related to VisualEditor or would like to remove your name from that list, please contact me directly.

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 "굵게" and "기울임꼴" 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), 2015년 8월 15일 (토) 07:27 (KST)

Ready for translation: VisualEditor News #5—2015

Hi! This is an invitation to join translators working on the October's issue of the VisualEditor multilingual newsletter, which will be widely delivered at the end of this workweek. Thanks a lot for your support, as usual! Elitre (WMF), 2015년 10월 27일 (화) 03:00 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones.

PPS: We are maintaining a list of editors who have worked on VE-related content (such as newsletters). We only use it to notify them of translation opportunities, to make sure they don't miss Translathons, etc. If you would like messages like this one to be delivered on your talk page at a different WMF project, need any help with translations related to VisualEditor or would like to remove your name from that list, please contact me directly.

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 "시각 편집으로 전환".

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 링크 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 "넣기 이미지 및 미디어" 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 "삭제" 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 Special: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 "편집" and "원본 편집" tabs into a single "편집" tab, similar to the system already used on the mobile website. The "편집" 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), 2015년 10월 31일 (토) 03:18 (KST)

Ready for translation: VisualEditor News #6—2015

Hi! This is an invitation to join translators working on the last issue of the VisualEditor multilingual newsletter for 2015, which will be widely delivered on Thursday (end of the day in Europe). Despite being a bit shorter than usual, it does feature important announcements, like the one about the single edit tab system, which people can already test and give feedback about. Thanks a lot for your support, as usual! Elitre (WMF), 2015년 12월 21일 (월) 23:15 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

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 Special: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 "편집" and "원본 편집" tabs into a single "편집" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "편집" 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 편집 tab of Special:Preferences in the drop-down menu about "편집 모드:".

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:
  • 마지막으로 사용한 편집기 기억하기,
  • 가능하면 항상 시각편집기 사용하기,
  • 항상 원본 편집기 사용하기, and
  • 양 쪽 편집 탭 보이기. (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. 감사합니다!

Elitre (WMF), 2015년 12월 25일 (금) 09:03 (KST)

Ready for translation: VisualEditor News #1—2016

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered as usual on Friday (end of the day in Europe). This time it features, among other things, updates about tables and about the single edit tab system (if you're looking for more translation opportunities, please consider the related overview). Thanks a lot for your support, as usual! Elitre (WMF), 2016년 2월 23일 (화) 06:37 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

VisualEditor News #1—2016

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

Did you know?

Among experienced editors, the visual editor's table editing is one of the most popular features.

If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.

Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor.

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. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.

Recent changes

You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.

Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.

You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.

The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.

Future changes

The single edit tab project will combine the "편집" and "원본 편집" tabs into a single "편집" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "편집" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the 편집 tab of Special:Preferences:

• 마지막으로 사용한 편집기 기억하기,
• 가능하면 항상 시각편집기 사용하기,
• 항상 원본 편집기 사용하기, and
• 양 쪽 편집 탭 보이기. (This is the state for people using the visual editor now.)

The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.

Let's work together

• Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
• Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

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. 감사합니다!

Elitre (WMF), 2016년 2월 27일 (토) 04:22 (KST)

A message for you

Hello: please see my request for you on my talk page. Thanks! --Elitre (WMF) (토론) 2016년 5월 24일 (화) 22:27 (KST)

Ready for translation: VisualEditor News #2—2016

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered this Sunday (end of the day in Europe). The "future changes" section is particularly interesting this time, and you're welcome to join and spread the word about the Community Taskforce. Thanks a lot for your support, as usual! Elitre (WMF), 2016년 6월 30일 (목) 19:52 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Editing News #2—2016

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

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "넣기" menu and click the "각주 목록" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "넣기" in the dialog to insert the 각주 목록. This list will change as you add more footnotes to the page.

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. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes

The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "편집" and "원본 편집" tabs into a single "편집" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "편집" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes

The "문서 저장" button will say "문서 게시". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

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

2016년 7월 4일 (월) 02:18 (KST)

Ready for translation: VisualEditor News #3—2016

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered this weekend. The goal this time is getting translations in over 20 languages, maybe even 25! Thanks a lot for your support, as usual! Elitre (WMF), --2016년 10월 12일 (수) 17:55 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Editing News #3—2016

다른 언어에서 이 메시지 읽기 • 다양한 언어로의 구독 목록

알고 계십니까?

시각편집기에서 세로줄이나 열을 쉽게 재정렬할 수 있게 되었다는 사실을 알고 계셨나요?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

여러분은 시각편집기를 어떻게 사용하는지에 대한 정보를 사용자 가이드를 통해 읽고 번역할 수 있습니다.

지난 소식지 이후로, 시각편집기 팀은 새로운 위키텍스트 편집기를 베이스로 시각편집기를 제작해 왔고, 몇몇 작은 특징 및 새로운 Map 편집 도구를 릴리즈했습니다. 이들의 활동은 파브리케이터에서 확인 가능합니다. 여러분은 끝난 작업을 mw:VisualEditor/Weekly triage meetings에서 확인하실 수 있습니다. 이들의 현재 우선 사항은 버그 수정, beta feature으로 2017년 위키텍스트 편집기 릴리즈하기, 그리고 번역 개량입니다.

최근 변경 사항

• 이제 여러분은 글자의 크기를 키우거나 줄일 수 있습니다.[3]
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[4] A similar feature will display the first part of hidden HTML comments.[5]
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[6]
• 많은 위키에서 여러분은 또한 이제 maps를 항목에 추가할 수 있게 됐습니다. Insert menu에서 'Maps' 아이템을 고르세요. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[7]
• 또한 "저장" 버튼 역시 약간 바뀌었는데, '페이지 저장'은 페이지를 새로 만들 때 표출되지만 '바뀜 저장'은 이미 존재하는 페이지를 편집할 때 표출됩니다.[8] 가까운 미래에는 '문서 저장' 버튼의 명칭이 '문서 게시'로 변경될 것입니다. 이는 시각편집기와 기존의 위키텍스트 편집 시스템에 모두 영향을 미칠 것입니다. 자세한 정보는 메타에서 확인하실 수 있습니다.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[9]

다음 변경 사항

The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

다 같이 노력합시다

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.

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

—Elitre (WMF)

2016년 10월 16일 (일) 02:48 (KST)

Request

Hello.

Could you create the article en:Education in Azerbaijan in Korean Wikipedia just like the article 러시아의 교육?

Thank you.

31.200.22.232 (토론) 2017년 1월 29일 (일) 19:43 (KST)

Ready for translation: Editing News #1—2017

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered when it's end of Friday in Central Europe, and that features, among other things, rumours about a much-desired syntax highlighting tool... Thanks for your help with this, it feels great to be back. --Elitre (WMF), 2017년 5월 9일 (화) 02:27 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Editing News #1—2017

다른 언어에서 소식지 읽기 • 다언어 소식지에 대한 구독 목록

알고 계십니까?

편집 차이를 '시각적'으로 확인하실 수 있다는 것을 알고 계십니까?

편집을 끝낸 후, 편집 요약을 작성하신 뒤 "바뀐 내용 검토" 버튼을 눌러 보세요.

시각 모드에서는 문서에 추가, 제거된 내용이나 새롭게 삽입된 링크가 강조됩니다. 사진의 크기 변경과 같은 다른 바뀜 유형의 경우 문서 옆쪽에 노트 형식으로 설명됩니다.

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

The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. 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 spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.

최근 변경 사항

• 데스크톱 모드에서 베타 기능으로 2017 새로운 위키텍스트 모드 편집 기능을 사용하실 수 있습니다. 이 기능은 시각편집기와 같은 툴바 및 형태를 띠고 있으며, Citoid 서비스 및 다른 모던 도구들 역시 사용하실 수 있습니다. ⧼Visualeditor-preference-newwikitexteditor-label⧽ 기능을 활성화하시고자 한다면 Special:Preferences#mw-prefsection-betafeatures을 방문하시기 바랍니다.
• A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [10]
• The team have added multi-column support for lists of footnotes. The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [11]
• You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [12]
• The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [13]
• The 분류 item has been moved to the top of the 문서 옵션 menu (from clicking on the "hamburger" icon) for quicker access. [14] There is also now a "Templates used on this page" feature there. [15]
• You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [16]
• Tables can be set as collapsed or un-collapsed. [17]
• The 특수 문자 menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [18]
• A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [19]
• There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K or Command+K respectively. [20]

다음 변경 사항

• The team is working on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [21]
• The kind of button used to 미리 보기, 차이 보기, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [22]
• The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors. See a list of editing tools on mediawiki.org if you are uncertain which one you use. [23]
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. 감사합니다!

—Elitre (WMF)

2017년 5월 13일 (토) 02:59 (KST)

Ready for translation: Editing News #1—2018

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered when it's end of Friday in Central Europe. Thanks in advance for your help with this: getting to interact with fellows so skilled like the translators are is among my favorite things about my job :) Best, Elitre (WMF) 2018년 2월 27일 (화) 19:29 (KST)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Editing News #1—2018

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

Did you know?

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

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

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

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

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

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

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

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

Recent changes

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

Let's work together

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

—Elitre (WMF)

2018년 3월 3일 (토) 05:54 (KST)

Translation: VisualEditor newsletter October 2018

Thank you for offering to help with translations. m:VisualEditor/Newsletter/2018/October is ready to translate now. /Whatamidoing (WMF)

2018년 10월 25일 (목) 03:20 (KST)

Editing News #2—2018

다른 언어로 읽기 • 다국어 구독 목록

알고 계십니까?

모바일 기기에서도 시각편집기를 이용하실 수 있다는 점을 알고 계십니까?

연필 아이콘을 눌러 편집을 하려고 할 경우 위키텍스트 편집기가 로드됩니다.

여러분은 도구 모음에서 또다른 연필 아이콘을 찾을 수 있습니다. 위키텍스트 편집기와 시각편집기를 서로 전환하려면 도구 모음의 연필 아이콘을 클릭하시면 됩니다.

편집을 마친 뒤 저장하는 것을 잊지 마세요.

여러분은 시각편집기의 사용 방법에 대한 더 많은 정보를 담고 있는 사용자 설명서를 읽고 번역할 수 있습니다.

지난 소식지 이후 편집 팀은 2017 위키텍스트 편집기와 시각 차이 도구에 대한 대부분의 작업을 마무리했습니다. 편집 팀은 모바일 기기를 사용하는 편집자들의 요구에 대한 조사를 시작했습니다. 팀의 활동은 파브리케이터에서 확인하실 수 있습니다. 그들의 우선 사항은 버그 수정 및 모바일 편집 향상입니다.

최근 바뀜

• 편집 팀이 모바일 편집에 대한 첫 보고서를 게시하였습니다.
• 편집 팀이 모바일 누리집에서의 시각편집에 관한 디자인 공부에 돌입했습니다. 새 편집자들은 스마트폰에서 링크 추가와 같은 기본적인 작업을 하는 데에도 어려움을 겪고 있었습니다. 여러분은 보고서를 읽으실 수 있습니다.
• 읽기 팀은 별도의 모바일 기반 기여 프로젝트를 진행하고 있습니다.
• 2006 위키텍스트 편집기는 더 이상 지원되지 않습니다. 여러분이 만약 이 사진 속 도구 모음을 사용하고 있을 경우, 여러분의 편집창에는 아무 도구 모음도 뜨지 않게 될 것입니다. 여러분은 다른 편집 도구를 편집 환경 설정이나 로컬 소도구, 베타 기능에서 선택하실 수 있습니다.
• 편집 팀이 시각편집기의 역사와 상태에 대해 설명하는 공개 발표를 하였습니다. 해당 발표는 이 영상에서 확인하실 수 있습니다(29분 30초 지점에서 시작).
• 지난달 국제 번역의 날, 언어 팀은 내용 번역 기능의 새 버전 (CX2)을 출시하였습니다. 이 버전부터는 시각편집기와 통합되어 틀, 표, 사진 등이 지원됩니다. 또한 번역된 문서를 게시할 때에는 과거보다 더 깔끔한 위키텍스트 형태로 저장됩니다. [27]

함께 노력합시다

• 편집 팀은 모바일 버전에서의 시각편집을 개선하고자 합니다. 편집 팀의 아이디어를 읽어보시고 여러분이 생각하기에 어떤 방법이 모바일 버전을 이용하는 편집자들을 도울 수 있을지 말씀해 주세요.
• 공동체 위시리스트 설문조사가 다음 주에 시작됩니다.
• 만약 이 문서가 여러분이 원하는 언어로 작성되어 있지 않다면, 소식지를 다른 언어로 번역하는 것을 도와주세요! 번역자 메일링 리스트를 구독하거나 저희와 직접 연락해 주세요. 다음 소식지에 대해 번역 준비가 완료되었을 때 알려드리겠습니다. 감사합니다!

—Whatamidoing (WMF) (talk)

2018년 11월 2일 (금) 23:15 (KST)

Editing News #1—July 2019

다른 언어로 읽기 • 이 다언어 소식지의 구독 명단

알고 계십니까?

휴대장치에서도 시각편집기를 이용할 수 있음을 알고 계십니까?

모든 문서는 상단에 연필 문양이 있습니다. 연필 문양을 눌러 편집을 시작할 수 있습니다.

편집 화면

This is what the new Edit Cards for editing links in the mobile visual editor look like. 여기서 시험판을 써볼 수 있습니다: 📲 편집 화면 써보기.

편집 소식지에 어서 오세요.

지난 소식지 이래로, 편집단은 모바일 시각편집기용 2가지 기능을 갱신하였고 3가지 기능을 새로이 개발하고 있습니다. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 편집 화면 써보기.

최근 갱신

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team recently launched two new features to improve the mobile visual editor:

1. Section editing
   • The purpose is to help contributors focus on their edits.
   • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
2. Loading overlay
   • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

새롭고 활동적인 항목

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

• Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲 Try Edit Cards.
• Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
• Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
• Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

내다보기

• Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to the team about how editing can be improved.
• Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

더 알아보기

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

2019년 7월 24일 (수) 03:33 (KST)

Editing News #2 – Mobile editing and talk pages

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

Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.

Help

What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!

Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team wants your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.

Talk pages project

The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.

The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.

Mobile visual editor

The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.

Edit Cards

What happens when you click on a link. The new Edit Card is bigger and has more options for editing links.

• On 3 September, the Editing team released version 3 of Edit Cards. Anyone could use the new version in the mobile visual editor.
• There is an updated design on the Edit Card for adding and modifying links. There is also a new, combined workflow for editing a link's display text and target.
• Feedback: You can try the new Edit Cards by opening the mobile visual editor on a smartphone. Please post your feedback on the Edit cards talk page.

Toolbar

The editing toolbar is changing in the mobile visual editor. The old system had two different toolbars. Now, all the buttons are together. Tell the team what you think about the new toolbar.

• In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
  • One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
  • New navigation: The buttons for moving forward and backward in the edit flow have changed.
  • Seamless switching: an improved workflow for switching between the visual and wikitext modes.
• Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.

Wikimania

The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.

Looking ahead

• Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
• Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
• Measuring the impact of Edit Cards: This study asks whether the project helped editors add links and citations. The Editing team hopes to share results in November. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

2019년 10월 29일 (화) 20:11 (KST)

Editing news 2020 #1 – Discussion tools

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

This early version of the Reply tool automatically signs and indents comments.

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

In a future update, the team plans to test a tool for easily linking to another user's name, a rich-text editing option, and other tools.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

• On 31 March 2020, the new 답변 tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
• The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
  • an easy way to mention another editor ("pinging"),
  • a rich-text visual editing option, and
  • other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

2020년 4월 9일 (목) 04:05 (KST)

Editing news 2020 #2

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

The new features include a toolbar. What do you think should be in the toolbar?

This issue of the Editing newsletter includes information the Talk pages project, an effort to help contributors communicate on wiki more easily.

• Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature is called "토론 도구". The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster now. Some other wikis will have a chance to try the Beta Feature in the coming months.
• New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
• New discussion tool: The Editing team is beginning work on a simpler process for starting new discussions. You can see the initial design on the project page.
• Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.

– Whatamidoing (WMF) (talk)

2020년 6월 18일 (목) 05:29 (KST)

Editing news 2020 #3

Editing news 2020 #3

다른 언어로 읽기 • 다국어 소식지 구독자 목록

데스크톱 시각편집기를 통한 편집이 5,000만 건을 돌파했습니다.

7년 전 이맘때 위키백과 편집자들이 사용할 수 있도록 Editing team의 시각편집기가 도입되었습니다. 이후 오늘날까지 편집자들은 여러 지표를 달성했습니다:

• 데스크톱 시각편집기를 통한 편집이 5,000만 건을 돌파했습니다.
• 시각편집기를 통해 생성된 문서 수가 200만 개를 돌파했습니다. 이들 중 2019년 한 해 동안 60만 개 이상의 새 문서가 생성되었습니다.
• 시각편집기의 역할은 시간이 지날수록 커지고 있습니다. 시각편집기가 도입된 이래 시각편집기를 이용한 편집의 비율은 매년 증가해 왔습니다.
• 2019년 한 해 동안 100회 미만의 기여 횟수를 한 새 사용자 계정에서 이루어진 편집 중 35%가 시각편집기를 통해 이루어졌습니다. 이 비율은 매년 증가해 왔습니다.
• 모바일에서는 500만 건에 달하는 편집이 시각편집기를 통해 이루어졌습니다. 대부분의 편집은 Editing team에서 모바일 시각편집기의 개발을 본격화한 2018년 이후의 건수입니다.
• 2019년 11월 17일에 있었던 대기권 외 우주 공간에서의 편집은 모바일 시각편집기를 통해 이루어졌습니다. 🚀 👩‍🚀
• 2017 위키텍스트 편집기를 통해 700만 건 이상의 편집이 이루어졌고 60만 개의 새 문서가 생성되었습니다. 2017 위키텍스트 편집기는 시각편집기 내장 위키텍스트 모드입니다. 여러분은 환경 설정에서 이 편집기를 활성화할 수 있습니다.

Whatamidoing (WMF) (토론)

2020년 7월 9일 (목) 21:48 (KST)

Editing news 2020 #4

다른 언어로 읽기 • 다국어 소식지 구독자 목록

답변 도구

2020년 3월부터 6월까지 답변 도구를 이용해 게시된 의견의 수입니다. 7,400건 이상의 의견이 답변 도구를 통해 게시되었습니다.

토론 도구(DiscussionTools)의 기능 중 하나인 답변 도구(Reply tool)가 2020년 3월 31일 아랍어, 네덜란드어, 프랑스어와 헝가리어 위키백과에 베타 기능으로 도입되었습니다. 도입 후 첫 통계는 긍정적인 결과를 보여주고 있습니다.

• 300명 이상의 편집자가 이 4곳의 위키백과에서 답변 도구를 사용했습니다. 통계를 낸 기간 동안 7,400건 이상의 의견이 게시되었습니다.
• 답변 도구를 이용한 사용자들 중 약 70%는 답변 도구를 여러 차례 사용했고, 60%는 여러 날에 걸쳐 계속해서 답변 도구를 이용했습니다.
• 위키백과 편집자들의 반응 또한 긍정적입니다. 한 사용자는 "أعتقد أن الأداة تقدم فائدة ملحوظة؛ فهي تختصر الوقت لتقديم رد بدلًا من التنقل بالفأرة إلى وصلة تعديل القسم أو الصفحة، التي تكون بعيدة عن التعليق الأخير في الغالب، ويصل المساهم لصندوق التعديل بسرعة باستخدام الأداة."(이 도구에 굉장히 큰 영향력이 있다고 생각합니다. 이전에는 의견에 답변을 달기 위해 스크롤을 한참 올려 편집 버튼을 누른 후 일일히 해당하는 문단이나 문서를 수정해야 했다면, 지금은 답변에 드는 시간이 굉장히 짧아졌고 답변 도구를 통해 편집창에 훨씬 빠르게 접근할 수 있습니다.)라고 의견을 남겼습니다.[28]

Editing team은 8월 초에 8개의 위키백과에 추가적으로 답변 도구를 베타 기능으로 도입했습니다. 중국어, 체코어, 조지아어, 세르비아어, 중부 쿠르드어(Sorani Kurdish), 스웨덴어, 카탈루냐어, 그리고 한국어 위키백과가 이에 해당합니다. 여러분의 위키에서도 답변 도구를 사용하고 싶으시다면 언제든지 User talk:Whatamidoing (WMF)에 말씀해 주세요.

답변 도구는 지속적으로 개발되고 있습니다. 네덜란드어 위키백과와 다른 일부 사용자의 요청으로, 답변 도구를 통해 의견을 남길 때 편집 요약을 개별적으로 설정할 수 있게 될 예정입니다. (현재 기본 편집 요약은 "답변"입니다.) 답변 도구의 시각 모드에서는 "핑" 기능을 이용할 수 있습니다. 이 기능은 토론에 참여한 사용자의 계정명을 자동으로 탐색하는데, 아랍어 위키백과에서의 요청으로 개별 위키별로 핑 부호를 '@'가 아닌 다른 부호로도 맞춤 설정할 수 있게 될 예정입니다. 또한 일본어 및 헝가리어 위키백과 사용자들의 요청으로 개별 위키에서 MediaWiki:Discussiontools-signature-prefix 문서를 수정하여 서명 접두 부호를 설정할 수 있게 됩니다. 일부 언어판 위키백과에서는 서명 앞에 띄어쓰기를 하지 않거나, 대시(--) 또는 줄 바꿈 없는 공백( )을 서명 접두 부호로 사용하고 있으며, 이를 토론 도구에 적용할 수 있게 된다는 것입니다.

사용자 서명에 대한 새 요구 사항

• 2020년 7월 6일, 사용자 서명에 대한 새 요구 사항이 시행되었습니다. 이 요구 사항을 충족하지 않는 서명을 사용하려 하실 경우 오류 메시지가 표출됩니다.
• 7월 6일 이전에 이미 설정된 서명 중 새 요구 사항을 충족하지 않는 서명의 경우 아직까지는 이러한 변경에 영향을 받지 않지만, 추후에는 모든 서명이 새 요구 사항을 충족하도록 요구됩니다. 여러분은 스스로의 서명을 확인해 보고, 현재 활동적인 사용자 중 누구의 서명이 수정을 필요로 하는지 확인해 볼 수 있습니다. 현재 봉사자들이 서명 수정을 필요로 하는 사용자에게 메시지를 남기고 있습니다. 만약 여러분의 서명에 대해 수정이 필요하다면 도움말 문서를 읽어보시기 바랍니다.

다음 업데이트: 새 주제 도구

저희 팀은 토론 문서에 새 주제를 빠르고 쉽게 열 수 있는 기능을 추가 개발할 예정입니다. 토론 도구의 개발을 추적하고 싶으시다면 새로운 토론 도구 프로젝트 문서를 주시문서에 추가하시기 바랍니다.

Whatamidoing (WMF) (토론)

2020년 9월 1일 (화) 00:11 (KST)

Editing news 2021 #1

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

Reply tool

Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this report.

The Reply tool is available at most Wikipedias.

• The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
• It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.

Research notes:

• As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
• We have preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments they start writing than those who use full-page wikitext editing.[29]
• The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[30] Some of the remaining changes are automatic corrections for Special:LintErrors.
• A large A/B test will start soon.[31] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias will have the Reply tool automatically enabled, and half will not. You can still turn it on or off for your own account in Special:Preferences.

New discussion tool

Screenshot of version 1.0 of the New Discussion Tool prototype.

The new tool for starting new discussions (new sections) will join the Discussion tools in Special:Preferences#mw-prefsection-betafeatures at the end of January. You can try the tool for yourself.[32] You can leave feedback in this thread or on the talk page.

Next: Notifications

During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at notifications-talk.

–Whatamidoing (WMF) (talk)

2021년 1월 22일 (금) 03:38 (KST)

Editing news 2021 #2

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

When newcomers had the Reply tool and tried to post on a talk page, they were more successful at posting a comment. (Source)

Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.

The key results were:

• Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
• The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.

These results give the Editing team confidence that the tool is helpful.

Looking ahead

The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.

The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.

You can turn on "토론 도구" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.

–Whatamidoing (WMF) (talk)

2021년 6월 24일 (목) 23:12 (KST)

뉴스 2022 #1 편집하기

다른 언어로 읽어보세요 • 이 다국어 뉴스레터 구독 목록

새로운 편집자는 이 새로운 도구로 더 성공적이었습니다.

새 주제 도구는 편집자가 토론 페이지에 새로운 ==섹션==을 만드는 데 도움이 됩니다. 새로운 편집자는 이 새로운 도구로 더 성공적입니다. 여러분은 보고서를 읽으실 수 있습니다. 곧 편집팀에서 테스트에 참여한 20개 위키백과의 모든 편집자에게 이 기능을 제공할 예정입니다. Special:Preferences#mw-prefsection-editing-discussion에서 끌 수 있습니다.

Whatamidoing (WMF) 2022년 5월 3일 (화) 03:43 (KST)