Help:VisualEditor/FAQ/da

Generelt

 * Hvad er VisualEditor?
 * VisualEditor er et initiativ for softwareudvikling fra Wikimedia-stiftelsen, der vil tillade folk at redigere sider i MediaWiki uden at behøve at lære wikitext-syntaks. Med VisualEditor vil formatering af sider fungere meget på samme måde som i et tekstbehandlingsprogram - under redigering vil teksten se ud som den kommer til at se ud, efter den er gemt.


 * Hvorfor indføres VisualEditor?
 * Den største hindring i at kunne lave den første redigering, og derfor den største hindring i vejen, der kunne føre til at en person bliver et aktivt og erfarent medlem af community'et, er den indviklede wiki-markup, der anvendes i det gamle redigeringssystem. For at øge antallet af succesfulde førstegangs-redigeringer, behøver vi et bedre redigeringssystem. Læs eventuelt den længere forklaring på engelsk.


 * 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.


 * Where do I go to learn more about using VisualEditor?
 * Please see the VisualEditor User guide.


 * Hvornår kommer VisualEditor til min wiki?
 * De fremtidige planer kan ses på mw:VisualEditor/Rollouts. VisualEditor blev lanceret i juli 2013 for de fleste større wikipediaer og mere en halvdelen af alle wikipediaer havde fået VisualEditor i løbet af anden halvdel af 2013. VisualEditor vil komme til næsten alle andre i 2014. I øjeblikket er planen at prioritere wikipediaer og først senere at indføre VisualEditor i andre søsterprojekter på grund af opgavens kompleksitet.


 * 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.


 * Hvorfor tages softwaren i brug allerede inden den er færdigudviklet?
 * Softwaren er helt klart ikke færdig; der mangler stadig funktioner samt findes problemer, der skal løses. I sidste ende er den bedste måde at finde fejl på at have så mange mennesker som muligt til at kigge på, bruge og lege med softwaren. Selvom vi anerkender at enhver fejl er generende på kort sigt, så vil de blive rettet, og at tage softwaren i brug vil gøre det muligt at identificere de ting, der behøver rettes.


 * 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.


 * Jeg har fundet et problem i VisualEditor. Hvordan kan jeg bede jer løse det?
 * Hvis du kan, så rapporter venligst problemet hos bugzilla i [$bugzilla kategorien "VisualEditor"]. De fleste større wiki'er har også en side, der er specielt beregnet til feedback. For den danske Wikipedia er det VisualEditor/Feedback. Der findes også en side for central feedback på mediawiki.org.


 * Hvordan undgår jeg at bruge VisualEditor?
 * For at fortsætte med at redigere wikiteksten direkte, så klik blot på knappen "" i stedet for "". Denne valgmulighed findes også øverst ved hvert tekstafsnit.

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.


 * En funktionalitet mangler i VisualEditor. Hvordan beder jeg jer om at tilføje den?
 * Nogle funktioner er i øjeblikket allerede ved at blive tilføjet eller er planlagt (som formatering af billeder, tilføjelse af rækker og kolonner til tabeller, og redigering af matematiske formler). Det er muligt at læse på engelsk om køreplanen og "Wikimedia engineering draft goals" for 2013 og 2014. Hvis du ikke kan finde nogen omtale af de funktioner som du ønsker, så rapporter venligst dit ønske på samme måde som hvis det var et problem i softwaren.


 * 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. and  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.


 * My question isn't here. Where do I ask?
 * You can ask on the VisualEditor feedback page on your wiki (see the list on Wikidata) or on the central feedback page on 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.