Help:VisualEditor/FAQ
 |
주의사항: 이 문서를 편집하면 CC0에 따라 당신의 기여한 것을 배포하는 데 동의하는 것으로 간주됩니다. 자세한 내용은 퍼블릭 도메인 도움말 문서를 확인 하세요. | |
| 시각편집기 포털 |
|---|
 |
| 일반 |
| 소개 |
| 도입 준비를 돕기 |
일반
- 시각 편집기가 무엇인가요?
- 시각 편집기는 사람들이 위키문법을 배울 필요 없이 미디어위키에서 문서를 편집할 수 있도록 하는 위키미디어 재단의 소프트웨어 개발 계획입니다. 시각 편집기를 사용하면, 문서의 모양을 바꾸는 작업은 워드프로세서와 매우 유사한 방식으로 동작하게 될 것입니다. 즉 편집할 때 내용이 저장한 후의 문서 모양처럼 보이게 됩니다.
- VisualEditor is a software development initiative by the Wikimedia Foundation that will allow people to edit pages in MediaWiki without needing to learn wikitext syntax.
With VisualEditor, formatting pages will work very similarly to a word processor. While editing, the page will look very similar to what the page will look like after it is saved.
- The complex wiki markup syntax used by the old editing window is the biggest barrier to making the first edit, and therefore the biggest barrier to beginning the path that could lead to someone's becoming a productive, experienced member of the editing community.
To increase the number of successful first attempts at editing, we need a better editing system. Please read our longer explanation for more details.
- 어디로 가야 시각편집기 이용에 대해 더 알 수 있을까요?
- 시각편집기 사용자 가이드를 참조해 주십시오.
- Please see the VisualEditor User guide.
- 제가 활동하는 위키에서 시각 편집기가 언제 활성화되나요?
- 현재 계획으로, 변경될 가능성이 있습니다:
- 6월 24일: 영어 위키백과에서 A/B 테스트. 새로 등록한 계정의 50%에 시각 편집기가 적용됩니다.
- 7월 1일: 영어 위키백과에서 시각 편집기 적용 (모든 계정 사용자에게 적용)
- 7월 15일: 영어 위키백과에서 시각 편집기 적용 (모든 익명 및 계정 사용자에 적용)
- 7월 24일: de/es/fr/he/it/nl/pl/ru/sv 위키백과에 시각 편집기 적용 (모든 계정 등록 사용자에게 적용)
- 7월 29일: de/es/fr/he/it/nl/pl/ru/sv 위키백과에 시각 편집기 적용 (모든 익명 및 계정 등록 사용자에게 적용)
- 8월 말경: 모든 다른 위키백과에서 모든 사용자에게 시각 편집기 적용, 단 시각 편집기가 작동하지 않는 몇몇 위키(예: 중국어 위키백과)는 제외
- 현재, 계획상으로는 필요한 몇 가지의 변경 사항의 복잡성으로 인해 위키백과에서 먼저 시각 편집기를 적용하고, 2013년 12월 말까지 자매 프로젝트에 시각 편집기를 적용할 예정입니다.
- The current schedule for future rollouts is posted at VisualEditor/Rollouts.
More than half of Wikipedias received VisualEditor as an option for all users during 2013. VisualEditor is available as an opt-in Beta Feature to almost all logged-in users at all Wikimedia Foundation projects.
- 개발 완료되지 않은 소프트웨어를 배포하는 이유가 뭔가요?
- 소프트웨어의 기능이 추가되고, 이슈도 해결될 것입니다. 결과적으로 버그를 발견하고, 부족한 기능을 알아내는 가장 좋은 방법은 가능한 많은 사람들이 소프트웨어를 동작시켜보고 이용하는 것입니다. 버그들은 오래지 않아 문제를 일으켜서 빠르게 수정될 것이며, 사용하면서 수정해야 할 것들이 어떤 것인지 인지하게 해줄 것이기 때문입니다.
- The software has features to be added and issues to be resolved.
Ultimately, the best way to detect bugs and identify missing features is to have as many people as possible using the software and playing with it. While we know that bugs are disruptive in the short term, they will be fixed, and the current use is what lets us identify things that need fixing.
- 비주얼 에디터에 대한 문제점을 발견했습니다. 문제를 고치려면 어디에 알려야 하나요?
- 가능하다면, Phabricator에 이슈 보고하기에 있는 "VisualEditor" product를 이용해 주십시오. 대부분의 위키피디아 역시 비주얼 에디터의 피드백을 위한 별도의 위키 페이지가 있습니다.see the list on Wikidata. mediawiki.org의 central feedback page를 사용하셔도 됩니다.
- If you're willing and able, please report the issue in Phabricator in the "VisualEditor" product.
Most large Wikipedias also have a wiki page dedicated to feedback about VisualEditor; see the list on Wikidata. There is also a central feedback page on mediawiki.org.
- 시각편집기를 어떻게 끄나요?
- 직접 위키텍스트를 편집하려면, "편집" 대신 "원본 편집" 버튼을 클릭하면 됩니다. 문단의 편집 링크에서, 일반적인 "편집" 링크 대신 "원본 편집"을 클릭하면 해당 문단의 고전적인 위키텍스트 편집기를 열 수 있습니다. On wikis where VisualEditor is still a Beta Feature, you can simply uncheck its box in the Beta tab of your Preferences; on the other wikis, you can check the Temporarily disable VisualEditor while it is in beta box from the Editing tab instead.
- A feature is missing in VisualEditor. How do I ask you to add it?
- Some features are currently being developed or planned.
The Roadmap, the Wikimedia Engineering goals pages for 2015–2016 and the Phabricator workboard provide some additional information as well. If you can't find any reference to the new feature you'd like to suggest, please submit it using the same process used to report an issue.
- Will it still be possible to edit using wikitext after VisualEditor becomes the primary editing interface?
- Yes. While VisualEditor will eventually be offered to all users by default, a method for editing the underlying “source” text will continue to exist. There are no plans to remove wikitext editing.
- Can I use familiar wikimarkup like [[ ]] and {{ }} in VisualEditor?
- No. Currently, those shortcuts will trigger the link and the template tool respectively. If you use wikimarkup in the article, a warning message will appear. See VisualEditor User guide for more about how to use VisualEditor.
- Why is my browser not supported?
- Building a modern editing interface for Wikipedia and its sister wiki is a technical challenge, but it's possible using modern web technologies and standards.
Unfortunately, some browsers don't support many of the features we need for VisualEditor. We're doing our best to support the most common browsers: VisualEditor works well with recent versions of the most popular web browsers: Firefox 15 and up; Iceweasel 10 and up; Safari 7 and up; Chrome 19 and up; Opera 15 and up; Microsoft Internet Explorer 10 and up; Edge 12 and up. In some browsers, such as Internet Explorer 9, a warning message will still show up, but users shouldn't experience any major problems editing. Trying to work around the limitations of older browsers would divert resources from improvements that would benefit the majority of users. We encourage you to upgrade to a supported browser and, if you can't, to continue to edit using the source wikitext editor. (See target browser matrix for specific details.)
- Does VisualEditor work with Wikisource's ProofreadPage, or Wiktionary's templates, and other features that Wikipedia doesn't have?
- VisualEditor is flexible enough to be adapted to all Wikimedia sites. However, Wiktionary's heavy reliance on templates will require significant work by community members to provide TemplateData to their users, and Wikisource's ProofreadPage tool will require some additional work to integrate VisualEditor smoothly.
- Can I install VisualEditor on my personal wiki outside Wikimedia?
- Yes, at your own risk. VisualEditor and Parsoid extensions are available for download but they're still experimental; note that Parsoid requires nodeJS. If you do install and use them, please let us know what worked and what didn't in Phabricator.
- Does VisualEditor make automatic fixes to pages?
- In most cases, VisualEditor will not make changes to formatting on lines that are not being directly edited. In cases where markup already on the page is handled incorrectly (for example, with tables that are not closed), it may attempt to correct these.
- Will the visual editor be enabled on talk pages?
- No. This question comes up quite often.
- The visual editor is designed to edit content, plain pages of text.
- Talk pages aren't content. Many of the tools and design patterns that make VE nice to use to edit content make it poor to use for discussions.
- To make it usable for discussions, we would have to remove or break many of those patterns in VE. We have spent a lot of time researching with users what works best there.
- VE can't deal with structured discussions and plain-text discussions are not structured discussions.
- Discussions like they are on traditional talk pages are not structured discussions from a technical perspective, despite the fact there is a certain number of colons or bullet points added to each answer to provide a pseudo-structure. With the current design of classical discussions, a piece of software can't know who has replied to whom – only humans can. There is no real connection between posts (which post is the parent/child of which), which is the definition of a structured discussion.
- At the moment Flow deals with structured discussions. In Flow, each post is independent with a unique ID, linked to other posts and to a Topic (also with a unique ID), with a specific history, and all posts can be targeted precisely. It would be possible in the future to have conversations at multiple places, to move topics or replies, and to create sub-discussions with Flow. Classical talk pages, using VE or not, do not allow that.
- 제 질문이 여기에 없습니다. 어디서 물어보면 되나요?
- 사용자 위키의 시각편집기 피드백 문서(위키데이터의 목록 참고)나 mediawiki.org의 중앙 피드백 페이지에서 물어볼 수 있습니다.
Community resources
- Where can I read more about what communities can do to adapt the visual editor to their sites?
- You can find a sort of "checklist" here on mediawiki.org.
- Where can I find people experienced in this kind of effort?
- There is a list of names at Community Taskforce.
각주
- ↑ Based on James Forrester's message on wikimedia-l mailing-list, June 2016