gnome-software main - en to da translation catalogue (150 entries)

note: (itstool) path: info/desc (itstool) path: page/title
en: How to reinstall a Webapp
da: Sådan installeres et webprogram

note: (itstool) path: page/p
en: <app>Software</app> supports managing two types of web apps:
da: <app>Software</app> har understøttelse for to typer webprogrammer:

note: (itstool) path: item/p
en: Web apps for which AppStream metainfo has been shipped with <app>Software</app>. See <link href="https://gitlab.gnome.org/mwleeds/gnome-pwa-list/-/blob/main/README.md">README.md</link>.
da: Webprogrammer hvor AppStream-metainfo er leveret sammen med <app>Software</app>. Se <link href="https://gitlab.gnome.org/mwleeds/gnome-pwa-list/-/blob/main/README.md">README.md</link>.

note: (itstool) path: item/p
en: Web apps which have been installed using <link href="https://apps.gnome.org/Epiphany/">GNOME Web</link>.
da: Webprogrammer som er blevet installeret med <link href="https://apps.gnome.org/Epiphany/">GNOME Web</link>.

note: (itstool) path: page/p
en: The first type are displayed as available to install in <app>Software</app> (when this functionality has been enabled by the distribution), whereas the second type only show up in <app>Software</app> after they have been installed via GNOME Web. If you uninstall such an app and want to reinstall it, you must do so using GNOME Web.
da: Den første type vises som tilgængelig til installation i <app>Software</app> (når denne funktion er aktiveret af distributionen), mens den anden type kun vises i <app>Software</app>, efter at de er blevet installeret via GNOME Web. Hvis du afinstallerer sådan et program og ønsker at geninstallere det, skal du gøre det ved hjælp af GNOME Web.

note: (itstool) path: page/p
en: Here are the steps to install a web app using GNOME Web:
da: Følg disse trin for at installere et webprogram med GNOME Web:

note: (itstool) path: item/p
en: Click the app <gui style="button">Menu</gui> button in the top right as shown in the image below.
da: Klik på programmets <gui style="button">Menu</gui>-knap øverst til højre som vist på billedet nedenfor.

note: (itstool) path: item/p
en: Click on <gui style="menuitem">Install as Web App…</gui> menu item. This should open the web app creation dialog.
da: Klik på menupunktet <gui style="menuitem">Installér som webprogram …</gui>. Dette bør åbne dialogboksen til oprettelse af webprogrammer.

note: (itstool) path: item/p
en: Click the <gui style="button">Create</gui> button to create and install the web app.
da: Klik på knappen <gui style="button">Opret</gui> for at oprette og installere webprogrammet.

note: (itstool) path: page/p
en: The web app should now show up in <app>Software</app>’s <gui style="tab">Installed</gui> tab.
da: Webprogrammet bør nu vises i <app>Softwares</app> faneblad <gui style="tab">Installeret</gui> tab.

note: (itstool) path: p/link
en: Creative Commons Attribution-ShareAlike 3.0 Unported License
da: Creative Commons Kreditering-Deling på samme vilkår 3.0 Ikke porteret-licens

note: (itstool) path: license/p
en: This work is licensed under a <_:link-1/>.
da: Værket er licenseret under en <_:link-1/>.

note: (itstool) path: info/desc
en: Introduction on Software Licensing
da: Introduktion til softwarelicenser

note: (itstool) path: page/title
en: Software Licensing
da: Softwarelicenser

note: (itstool) path: section/title
en: Introduction
da: Introduktion

note: (itstool) path: section/p
en: Apps can be ‘free/open source software’ or ‘proprietary’. This affects the freedoms you as a user have. If an app is <link href="https://en.wikipedia.org/wiki/Free_and_open-source_software">free/open source software (FOSS)</link>, you have the freedom to use it, copy it, study and change its source code. Proprietary software does not provide you with those freedoms. FOSS software is often available for no charge, but this is not always true.
da: Programmer kan være “fri/open source-software” eller “proprietære”. Dette påvirker de friheder, du har som bruger. Hvis et program er <link href="https://da.wikipedia.org/wiki/Free/Libre_and_Open_Source_Software">free/libre and open source-software (FOSS)</link>, har du frihed til at bruge det, kopiere det, studere og ændre dets kildekode. Proprietær software giver dig ikke disse friheder. FOSS-software er ofte tilgængelig gratis, men dette er ikke altid tilfældet.

note: (itstool) path: section/p
en: Because the source code is available for FOSS software, users can get involved in its development, contributing features or translations to their language and fixing bugs which affect them. They can audit the code and check that changes to the software are not malicious. They can learn from the source code and use it as the basis for their own FOSS applications.
da: Da kildekoden til FOSS-software er tilgængelig, kan brugerne deltage i udviklingen ved at bidrage med funktioner eller oversættelser til deres sprog og rette fejl, der påvirker dem. De kan kontrollere koden og sikre sig, at ændringer i softwaren ikke er ondsindede. De kan lære af kildekoden og bruge den som grundlag for deres egne FOSS-programmer.

note: (itstool) path: section/p
en: FOSS apps are <link href="https://www.unesco.org/en/open-solutions">a public good</link>.
da: FOSS-software er <link href="https://www.unesco.org/en/open-solutions">et fælles gode</link>.

note: (itstool) path: section/p
en: Proprietary apps cannot be audited by their users, so you must trust that the developers of the app have your best interests in mind, and no conflicts of interest.
da: Proprietære programmer kan ikke kontrolleres af brugerne, så du må stole på, at programmets udviklere har dine interesser for øje og ikke har nogen interessekonflikter.

note: (itstool) path: section/p
en: Read more about <link href="https://en.wikipedia.org/wiki/Free_and_open-source_software#Benefits_over_proprietary_software">the benefits of FOSS over proprietary software</link>.
da: Læs mere om <link href="https://en.wikipedia.org/wiki/Free_and_open-source_software#Benefits_over_proprietary_software">fordelene ved FOSS sammenlignet med proprietær software</link>.

note: (itstool) path: info/desc
en: How <app>Software</app> uses metadata
da: Hvordan <app>Software</app> bruger metadata

note: (itstool) path: page/title
en: Software Metadata
da: Softwaremetadata

note: (itstool) path: section/title
en: Screenshots
da: Skærmbilleder

note: (itstool) path: section/p
en: <app>Software</app> displays the screenshots on the details page for an application. This typically should include screenshots of various windows / dialogs of the application, so the user would get a quick grasp of the application’s features, look and feel etc.
da: <app>Software</app> viser skærmbilleder på detaljesiden for et program. Dette bør typisk omfatte skærmbilleder af forskellige vinduer/dialogbokse i programmet, så brugeren hurtigt kan danne sig et overblik over programmets funktioner, udseende og funktionalitet osv.

note: (itstool) path: section/p
en: When more than one screenshot is present in the application’s metainfo file, <app>Software</app> will show the screenshots in a carousel.
da: Når der er mere end ét skærmbillede i programmets metainfofil, viser <app>Software</app> skærmbillederne i en karrusel.

note: (itstool) path: section/p
en: In cases when the application’s metainfo file doesn’t contain any screenshot, then a placeholder icon as below with <code>No Screenshots</code> will be displayed:
da: I tilfælde hvor programmets metainfofil ikke indeholder noget skærmbillede, vises et erstatningsikon som nedenfor med <code>Ingen skærmbilleder</code>:

note: (itstool) path: note/p
en: Placeholder icon might look different if you're using a custom icon theme.
da: Erstatningsikonet kan se anderledes ud, hvis du amvender et brugerdefineret ikontema.

note: (itstool) path: section/p
en: Screenshots might become outdated as the application’s UI changes. So, even if <app>Software</app> shows screenshots for an app, it’s important to check if these screenshots are up-to-date or outdated.
da: Skærmbilleder kan blive forældede, når programmets brugergrænseflade ændres. Så selvom <app>Software</app> viser skærmbilleder for et program, er det vigtigt at kontrollere, om disse skærmbilleder er opdaterede eller forældede.

note: (itstool) path: section/p
en: You can improve app screenshot information:
da: Du kan forbedre programmets skærmbilledoplysninger:

note: (itstool) path: item/p
en: <link xref="#how-to-add-missing-app-screenshots">How to add missing app screenshots</link>
da: <link xref="#how-to-add-missing-app-screenshots">Sådan tilføjes manglende programskærmbilleder</link>

note: (itstool) path: section/title
en: App context bar
da: Programmets kontekstbjælke

note: (itstool) path: section/p
en: The app context bar in <app>Software</app> is a collection of tiles on the details page for an application, which display the following details.
da: Programmets kontekstbjælke i <app>Software</app> er en samling fliser på programmets detaljeside, som viser følgende detaljer.

note: (itstool) path: item/p
en: <link xref="#storage">Storage</link>
da: <link xref="#storage">Lager</link>

note: (itstool) path: item/p
en: <link xref="#safety">Safety</link>
da: <link xref="#safety">Sikkerhed</link>

note: (itstool) path: item/p
en: <link xref="#hardware-support">Hardware support</link>
da: <link xref="#hardware-support">Understøttelse af hardware</link>

note: (itstool) path: item/p
en: <link xref="#age-rating">Age rating</link>
da: <link xref="#age-rating">Aldersvurdering</link>

note: (itstool) path: section/p Translators: Refer https://gitlab.gnome.org/GNOME/gnome-software/-/wikis/Help-Translation-Notes for steps to localize 'figures/app-context-bar.png' image.
en: This shows the app context bar for the <app>Software</app> app:
da: Dette viser programmets kontekstbjælke for programmet <app>Software</app>:

[ctx: _]
note: (itstool) path: p/media This is a reference to an external file such as an image or video. When the file changes, the md5 hash will change to let you know you need to update your localized copy. The msgstr is not used at all. Set it to whatever you like once you have updated your copy of the file.
en: external ref='figures/app-context-bar.png' md5='3badcd9309bde27a650b25eb5d89a4c6'
da: [strengen bruges ikke]

note: (itstool) path: section/p Translators: This text needs to be adjusted for RTL languages as the tiles will be reversed in the UI.
en: The tiles are displayed in the order listed above (starting with <code>Storage</code> tile on the left).
da: Fliserne vises i ovenstående rækkefølge (startende med flisen <code>Lager</code> til venstre).

note: (itstool) path: section/p
en: Each tile is covered in detail below.
da: Hver flise er beskrevet i detaljer nedenfor.

note: (itstool) path: section/title
en: Storage
da: Lager

note: (itstool) path: section/p
en: <app>Software</app> displays a storage tile on the details page for an application. If the application is not installed, this displays the estimated download size needed to install it. If the application is installed, it displays the storage space used by the application.
da: <app>Software</app> viser en lagerflise på et programs detaljeside. Hvis programmet ikke er installeret, vises den anslåede downloadstørrelse, der er nødvendig for at installere den. Hvis programmet er installeret, vises den lagerplads, som programmet bruger.

note: (itstool) path: section/p
en: The sizes are calculated from data provided by the <app>Software</app> backend (such as flatpak or an RPM), and are not specified in the metadata provided by the application. There is nothing you can do to affect this tile by editing an application’s metainfo file. It’s listed here for completeness.
da: Størrelserne beregnes ud fra data fra <app>Software</app>-backend (f.eks. flatpak eller RPM) og er ikke angivet i de metadata, der leveres af programmet. Du kan ikke ændre denne flise ved at redigere et programs metainfofil. Den er angivet her for fuldstændighedens skyld.

note: (itstool) path: section/title
en: Safety
da: Sikkerhed

note: (itstool) path: section/p
en: <app>Software</app> displays a safety tile on the details page for an application. This summarizes information about whether the app can be considered safe to install and run, or whether caution may be required before trusting it.
da: <app>Software</app> viser en sikkerhedsflise på et programs detaljeside. Denne opsummerer oplysninger om, hvorvidt programmet kan betragtes som sikkert at installere og køre, eller om der er grund til at udvise forsigtighed, før man stoler på det.

note: (itstool) path: section/p
en: This tile combines information about the permissions which the app requests when it runs (such as permission to read your files), with information about how the app was developed. Free software applications, where the source code is publicly readable, can be more secure than proprietary ones, as they can be audited.
da: Denne flise kombinerer oplysninger om de tilladelser, som programmet anmoder om, når det kører (f.eks. tilladelse til at læse dine filer), med oplysninger om, hvordan programmet er udviklet. Frie softwareprogrammer, hvor kildekoden er offentligt tilgængelig, kan være mere sikre end proprietære programmer, da de kan undersøges.

note: (itstool) path: section/p
en: The dialog which appears when the tile is clicked lists the different permissions the app requests, plus some information about its license and runtime.
da: Den dialog, der vises, når du klikker på flisen, viser de forskellige tilladelser, som programmer anmoder om, samt nogle oplysninger om dets licens og kørselstid.

note: (itstool) path: section/p
en: You can improve the safety information:
da: Du kan forbedre sikkerhedsoplysningerne:

note: (itstool) path: item/p
en: <link xref="#how-to-fix-incorrect-safety-and-permissions-information">How to fix incorrect safety and permissions information</link>
da: <link xref="#how-to-fix-incorrect-safety-and-permissions-information">Sådan rettes forkerte oplysninger om sikkerhed og tilladelser</link>

note: (itstool) path: section/title
en: Hardware support
da: Understøttelse af hardware

note: (itstool) path: section/p
en: <app>Software</app> displays a hardware support tile on the details page for an application. This combines information about the hardware requirements of the application, and the hardware capabilities of the computer, with the aim of highlighting incompatibilities or missing requirements — or to indicate that the application should work correctly with no incompatibilities.
da: <app>Software</app> viser en flise med hardwareunderstøttelse på et programs detaljeside. Denne flise kombinerer oplysninger om programmets hardwarekrav og computerens hardwarefunktioner med det formål at fremhæve inkompatibilitet eller manglende krav — eller for at angive, at programmet bør fungere korrekt uden inkompatibiliteter.

note: (itstool) path: section/p
en: The code looks at the following hardware. More may be supported in future.
da: Koden leder efter følgende hardware. Understøttelse af mere kan ske i fremtiden.

note: (itstool) path: item/p
en: Whether a touchpad, mouse or keyboard is present/needed
da: Om en pegeplade, mus eller tastatur er til stede/nødvendig

note: (itstool) path: item/p
en: Whether a gamepad is needed
da: Om en gamepad er nødvendig

note: (itstool) path: item/p
en: The minimum and recommended display size that the app can scale to
da: Den mindste og anbefalede skærmstørrelse programmet kan skaleres til

note: (itstool) path: section/p
en: It’s not possible to reliably detect whether a gamepad is <em>present</em>, as they are often left disconnected due to not being needed for normal computer use.
da: Det er ikke muligt at registrere pålideligt, om en gamepad er <em>til stede</em>, da de ofte er frakoblede, fordi de ikke er nødvendige til normal brug af computeren.

note: (itstool) path: section/p
en: The dialog which appears when the tile is clicked lists the different hardware requirements of the app, and whether any of them are not met.
da: Dialogen, der vises, når du klikker på flisen, viser programmets forskellige hardwarekrav og angiver, om nogle af dem ikke er opfyldt.

note: (itstool) path: section/p
en: You can improve the hardware information:
da: Du kan forbedre oplysningerne om hardware:

note: (itstool) path: item/p
en: <link xref="#how-to-add-missing-hardware-information">How to add missing hardware information</link>
da: <link xref="#how-to-add-missing-hardware-information">Sådan tilføjes manglende oplysninger om hardware</link>

note: (itstool) path: section/title
en: Age rating
da: Aldersvurdering

note: (itstool) path: section/p
en: <app>Software</app> displays an age rating tile on the details page for an application. This shows what age range the application should be suitable for, based on different kinds of content which the application has declared it contains. This information is summarized in a format similar to the game or film rating certificates for your country.
da: <app>Software</app> viser en flise indeholdende aldersvurdering på programmets detaljeside. Denne viser, hvilken aldersgruppe programmet er egnet til, baseret på de forskellige typer indhold, som programmet har angivet at indeholde. Disse oplysninger er sammenfattet i et format, der ligner de spil- eller filmklassificeringscertifikater, der findes i dit land.

note: (itstool) path: section/p
en: For example, this will highlight whether a game contains violence, or whether an application contains in-app advertising.
da: Dette vil f.eks. fremhæve, om et spil indeholder vold, eller om et program indeholder reklamer i appen.

note: (itstool) path: section/p
en: The dialog which appears when the tile is clicked lists the different types of content in the application and how severe that content is.
da: Dialogen, der vises, når du klikker på flisen, viser de forskellige typer indhold i programmet, og hvor alvorligt dette indhold er.

note: (itstool) path: section/p
en: You can improve the age rating information:
da: Du kan forbedre oplysningerne om aldersvurdering:

note: (itstool) path: item/p
en: <link xref="#how-to-add-missing-content-rating-information">How to add missing content rating information</link>
da: <link xref="#how-to-add-missing-content-rating-information">Sådan tilføjes oplysninger om indholdsvurdering</link>

note: (itstool) path: section/title
en: License
da: Licens

note: (itstool) path: section/p
en: <app>Software</app> displays a tile indicating whether an application is <link href="https://en.wikipedia.org/wiki/Free_and_open-source_software">free software</link> or whether its license is proprietary, special or unknown. This tile includes more detailed information about the project’s license. This tile also lists some of the benefits of free software. <link xref="software-licensing#introduction">Learn more</link>
da: <app>Software</app> viser en flise, der angiver, om et program er <link href="https://https://da.wikipedia.org/wiki/Free/Libre_and_Open_Source_Software">fri software</link>, eller om dets licens er proprietær, speciel eller ukendt. Denne flise indeholder mere detaljerede oplysninger om projektets licens. Flisen viser også nogle af fordelene ved fri software. <link xref="software-licensing#introduction">Læs mere her</link>.

note: (itstool) path: section/p
en: Sometimes the license information isn’t correct for an application, and hence an application which is actually free software will be shown as ‘proprietary’. Similarly, sometimes the license information is unknown.
da: Nogle gange er licensoplysningerne ikke korrekte for et program, og derfor vil et program, der faktisk er fri software, blive vist som “proprietært”. Tilsvarende er licensoplysningerne nogle gange ukendte.

note: (itstool) path: section/p
en: <app>Software</app> highlights free and open-source licenses in green, proprietary and special licenses in yellow as shown here. Unknown licenses are highlighted in grey.
da: <app>Software</app> fremhæver licenser for programmer, der er frie og open source med grønt, og proprietære og specielle licenser med gult, som vist her. Ukendte licenser fremhæves med gråt.

note: (itstool) path: section/p
en: You can add or improve the license information:
da: Du kan tilføje eller forbedre licensoplysningerne:

note: (itstool) path: item/p
en: <link xref="#how-to-fix-incorrect-licensing-information">How to fix incorrect licensing information</link>
da: <link xref="#how-to-fix-incorrect-licensing-information">Sådan rettes forkerte licensoplysninger</link>

note: (itstool) path: section/p
en: <app>Software</app> displays a list of application resource links in the link tile. They are as follows:
da: <app>Software</app> viser en liste over links til applikationsressourcer i linkflisen. De er som følger:

note: (itstool) path: td/p
en: Website link
da: Webstedslink

note: (itstool) path: td/p
en: Donation link
da: Donationslink

note: (itstool) path: td/p
en: Translation contribution link
da: Oversættelsesbidragslink

note: (itstool) path: td/p
en: Bug reporting link
da: Fejlrapporteringslink

note: (itstool) path: td/p
en: Help link
da: Hjælpelink

note: (itstool) path: td/p
en: Contact link
da: Kontaktlink

note: (itstool) path: section/p
en: Some or all of these links may be present depending on whether they are listed in the application’s metainfo file.
da: Nogle eller alle disse links kan være til stede, afhængigt af om de er angivet i programmets metainfofil.

note: (itstool) path: section/p
en: In cases when the application’s metainfo file doesn’t contain any link, the following tile with a question mark will be displayed.
da: I tilfælde, hvor programmets metainfofil ikke indeholder noget link, vises følgende flise med et spørgsmålstegn.

note: (itstool) path: section/p
en: You can improve the links:
da: Du kan forbedre linksene:

note: (itstool) path: item/p
en: <link xref="#how-to-add-missing-links">How to add missing links</link>
da: <link xref="#how-to-add-missing-links">Sådan tilføjes manglende links</link>

note: (itstool) path: section/title
en: Carousel tile
da: Karruselflise

note: (itstool) path: section/p
en: Applications which are featured by <app>Software</app> are displayed in a carousel at the top of the main window as shown here. Each carousel tile has a background color which is automatically extracted from the application’s icon. Sometimes this background color is not quite right for the application and needs to be specified explicitly by the application developer.
da: Programmer, der er udvalgt af <app>Software</app>, vises i en karrusel øverst i hovedvinduet, som vist her. Hver karruselflise har en baggrundsfarve, der automatisk udtrækkes fra programmets ikon. Nogle gange passer denne baggrundsfarve ikke helt til programmet og skal derfor angives eksplicit af programmets udvikler.

note: (itstool) path: section/p
en: The set of applications which are featured is decided by the Linux distribution maintainers.
da: Det sæt programmer, der vises, bestemmes af Linux-distributionsadministratorerne.

note: (itstool) path: section/p
en: You can improve the carousel tile:
da: Du kan forbedre karruselflisen:

note: (itstool) path: item/p
en: <link xref="#how-to-set-the-carousel-tile-background-colour">How to set the carousel tile background color</link>
da: <link xref="#how-to-set-the-carousel-tile-background-colour">Sådan indstilles karruselflisens baggrundsfarve</link>

note: (itstool) path: section/title
en: Where metadata comes from
da: Hvor kommer metadata fra?

note: (itstool) path: section/p
en: The metadata used to specify what hardware a piece of software requires, what ages of user it is suitable for, and factors which contribute to how safe it might be to install, all come from the metainfo file for that software.
da: Metadataene, der bruges til at angive, hvilken hardware et stykke software kræver, hvilken aldersgruppe det er egnet til, og faktorer, der bidrager til, hvor sikkert det er at installere, kommer alle fra metainfofilen for den pågældende software.

note: (itstool) path: section/p
en: The metainfo file is an XML file. Its file format is specified in the <link href="https://www.freedesktop.org/software/appstream/docs/">AppStream specification</link>.
da: Metainfofilen er en XML-fil. Dens filformat er specificeret i <link href="https://www.freedesktop.org/software/appstream/docs/">AppStream-specifikationen</link>.

note: (itstool) path: section/p
en: See the <link href="https://gitlab.gnome.org/GNOME/nautilus/-/blob/main/data/org.gnome.Nautilus.metainfo.xml.in.in">metainfo file for GNOME Files app</link>.
da: Se <link href="https://gitlab.gnome.org/GNOME/nautilus/-/blob/main/data/org.gnome.Nautilus.metainfo.xml.in.in">metainfofilen for GNOME Filer</link>.

note: (itstool) path: note/p
en: <em>appdata</em> is the older term for <em>metainfo</em>.
da: <em>appdata</em> er en ældre betegnelse for <em>metainfo</em>.

note: (itstool) path: section/title
en: What happens if metadata is missing
da: Hvad sker der, hvis metadata mangler?

note: (itstool) path: section/p
en: If some metadata is missing for an application, <app>Software</app> can only guess what it might be, and hence can’t present much information in its interfaces. The guesses <app>Software</app> makes are based on the fact that most software is designed for desktop computers.
da: Hvis nogle metadata mangler for et program, kan <app>Software</app> kun gætte på, hvad det kan være, og kan derfor ikke præsentere meget information i sine grænseflader. De gæt, som <app>Software</app> foretager, er baseret på det faktum, at de fleste programmer er designet til skrivebordscomputere.

note: (itstool) path: section/p
en: <em style="strong">You can help improve the metadata for an application!</em>
da: <em style="strong">Du kan hjælpe med at forbedre et programs metadata!</em>

note: (itstool) path: section/title
en: How to contribute missing information
da: Bidrag med manglende information

note: (itstool) path: section/p
en: If you find that an app’s page is missing information or has incorrect information, you can contribute in one of the two ways:
da: Hvis du opdager, at et programs side mangler oplysninger eller indeholder forkerte oplysninger, kan du bidrage på en af to måder:

note: (itstool) path: item/p
en: You can report the missing / incorrect metadata to the respective app’s bug tracker, so the app developer can fix it.
da: Du kan rapportere de manglende/forkerte metadata til det pågældende programs fejlsporingssystem, så udvikleren kan rette fejlen.

note: (itstool) path: item/p
en: You can fix the missing / incorrect metadata yourself. See the <em style="strong">How to</em> guide below on how to do that.
da: Du kan selv rette de manglende/forkerte metadata. Se vejledningen <em style="strong">Sådan gør du</em> nedenfor for at se, hvordan du gør.

note: (itstool) path: section/p
en: For both, you first need to find the app’s project page. The link to the project page should typically be available in the app’s page <link xref="#links">as shown here</link>. If not, you will need to find it with a simple search on Google.
da: I begge tilfælde skal du først finde programmets projektside. Linket til projektsiden skal normalt være tilgængeligt på programmets side <link xref="#links">som vist her</link>. Hvis ikke, skal du finde det ved hjælp af en simpel søgning f.eks. med brug af en søgemaskine som Qwant eller Ecosia.

note: (itstool) path: section/p
en: Apps are typically hosted in <link href="https://gitlab.com/explore?sort=stars_desc">GitLab</link> or <link href="https://github.com/explore">GitHub</link>. For example, GNOME apps are hosted in <link href="https://gitlab.gnome.org/GNOME?sort=stars_desc">gitlab.gnome.org</link>.
da: Programmer har typisk hjemme hos <link href="https://gitlab.com/explore?sort=stars_desc">GitLab</link> eller <link href="https://github.com/explore">GitHub</link>. GNOME-programmer ligger for eksempel på <link href="https://gitlab.gnome.org/GNOME?sort=stars_desc">gitlab.gnome.org</link>.

note: (itstool) path: section/title
en: How to add missing app screenshots
da: Sådan tilføjes manglende programskærmbilleder

note: (itstool) path: section/p
en: The screenshot information for an application is stored in the <link href="https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#tag-dapp-screenshots"><code>&lt;screenshots&gt;</code></link> element within the application’s <code>&lt;component&gt;</code> in its metainfo file.
da: Skærmbilledoplysningerne for et program gemmes i elementet <link href="https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#tag-dapp-screenshots"><code>&lt;screenshots&gt;</code></link> inden for programmets <code>&lt;component&gt;</code> i dets metainfofil.

note: (itstool) path: section/p
en: Recommended number of screenshots for an app is between 5 to 10. Screenshots should ideally be in the PNG format with 16:9 aspect ratio and minimum width of 620 pixels.
da: Det anbefalede antal skærmbilleder for et program er mellem 5 og 10. Skærmbilleder bør helst være i PNG-formatet med højde-breddeforholdet 16:9 og en minimumsbredde på 620 pixels.

note: (itstool) path: section/p
en: For example, here are the screenshot entries for the <app>Software</app> app:
da: Her er for eksempel skærmbillederne for programmet <app>Software</app>:

note: (itstool) path: section/title
en: How to fix incorrect safety and permissions information
da: Sådan rettes forkerte oplysninger om sikkerhed og tilladelser

note: (itstool) path: section/p
en: The safety and permissions information for an application comes from different sources depending on how the application is packaged. For traditionally packaged applications, for example in RPM or DEB format, there is no safety or permissions information available and nothing can be done to add it to an application.
da: Oplysninger om sikkerhed og tilladelser for et program kommer fra forskellige kilder, afhængigt af hvordan programmet distribueres. For traditionelt distribuerede programmer, f.eks. i RPM- eller DEB-format, findes der ingen sikkerheds- eller tilladelsesoplysninger, og der kan ikke gøres noget for at tilføje dem til et program.

note: (itstool) path: section/p
en: For flatpak applications, the information comes from the application’s <link href="https://docs.flatpak.org/en/latest/manifests.html">flatpak manifest</link>, specifying what holes in the sandbox the application requires. Each of these holes typically contributes to lowering the displayed safety level of the application in <app>Software</app> — moving it from ‘safe’ to ‘potentially unsafe’ to ‘unsafe’.
da: For flatpak-programmer kommer oplysningerne fra programmets <link href="https://docs.flatpak.org/en/latest/manifests.html">flatpak-manifest</link>, der angiver, hvilke huller i sandkassen programmet kræver. Hvert af disse huller bidrager typisk til at sænke det viste sikkerhedsniveau for programmet i <app>Software</app> — fra “sikker” til “potentielt usikker” til “usikker”.

note: (itstool) path: section/p
en: In order to improve the safety level of an application, its sandboxing must be made as tight as possible, by removing <link href="https://docs.flatpak.org/en/latest/sandbox-permissions.html">sandbox permissions</link> where they’re not needed, and using <link href="https://docs.flatpak.org/en/latest/desktop-integration.html#portals">portals</link> instead of sandbox permissions where possible. Use of portals does not lower the displayed safety level of an application in <app>Software</app>.
da: For at forbedre sikkerhedsniveauet for et program skal dets sandkassetilstand gøres så streng som muligt ved at fjerne <link href="https://docs.flatpak.org/en/latest/sandbox-permissions.html ">sandkassetilladelser</link>, hvor de ikke er nødvendige, og ved at bruge <link href="https://docs.flatpak.org/en/latest/desktop-integration.html#portals">portaler</link> i stedet for sandkassetilladelser, hvor det er muligt. Brug af portaler sænker ikke det viste sikkerhedsniveau for et program i <app>Software</app>.

note: (itstool) path: section/p
en: For example, if the application requests read/write access to the full file system (<code>--filesystem=host</code>), does it actually need that, or does it only need to access files in a few specific locations? If so, the <link href="https://docs.flatpak.org/en/latest/desktop-integration.html#portals">file portal</link> could be used, or more specific <link href="https://docs.flatpak.org/en/latest/sandbox-permissions.html#filesystem-access">file system permissions</link> could be specified.
da: Hvis programmet f.eks. anmoder om læse-/skriveadgang til hele filsystemet (<code>--filesystem=host</code>), har den så virkelig brug for det, eller behøver den kun at få adgang til filer på nogle få specifikke steder? I så fald kan <link href="https://docs.flatpak.org/en/latest/desktop-integration.html#portals">filportalen</link> bruges, eller der kan angives mere specifikke <link href="https://docs.flatpak.org/en/latest/sandbox-permissions.html#filesystem-access">filsystemtilladelser</link>.

note: (itstool) path: section/p
en: If the application works on Wayland, and only needs to work on X11 as a fallback, without using special X11 features, could it use <code>--socket=fallback-x11</code> rather than <code>--socket=x11</code>?
da: Hvis programmet fungerer på Wayland og kun skal fungere på X11 i nødstilfælde uden at bruge specielle X11-funktioner, kan den så bruge <code>--socket=fallback-x11</code> i stedet for <code>--socket=x11</code>?

note: (itstool) path: section/p
en: Guidance about specific permissions, or other packaging formats, may be added here in future.
da: Vejledning om specifikke tilladelser eller andre pakkeformater kan blive tilføjet her i fremtiden.

note: (itstool) path: section/p
en: Further reading:
da: Yderligere læsestof:

note: (itstool) path: section/title
en: How to add missing hardware information
da: Sådan tilføjes manglende oplysninger om hardware

note: (itstool) path: section/p
en: The hardware information for an application is stored in the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations"><code>&lt;requires&gt;</code>, <code>&lt;recommends&gt;</code> and <code>&lt;supports&gt;</code></link> elements within the application’s <code>&lt;component&gt;</code> in its metainfo file.
da: Hardwareoplysningerne for et program gemmes i elementerne <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations"><code>&lt;requires&gt;</code>, <code>&lt;recommends&gt;</code> og <code>&lt;supports&gt; </code></link> i programmets <code>&lt;component&gt;</code> i dets metainfofil.

note: (itstool) path: section/p
en: <app>Software</app> understands the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations-control"><code>&lt;control&gt;</code></link> and <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations-display_length"><code>&lt;display_length&gt;</code></link> elements.
da: <app>Software</app> forstår elementerne <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations-control"><code>&lt;control&gt; </code></link> og <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-relations-display_length"><code>&lt;display_length&gt;</code></link>.

note: (itstool) path: section/p
en: See <link href="https://tecnocode.co.uk/2021/07/12/add-metadata-to-your-app-to-say-what-inputs-and-display-sizes-it-supports/">this blog post</link> or <link href="https://blogs.gnome.org/tbernard/2021/09/07/ready-for-software-41/#device-support">this blog post</link> for examples of metadata.
da: Du kan finde eksempler på metadata i <link href="https://tecnocode.co.uk/2021/07/12/add-metadata-to-your-app-to-say-what-inputs-and-display-sizes-it-supports/">dette blogindlæg</link> eller <link href="https://blogs.gnome.org/tbernard/2021/09/07/ready-for-software-41/#device-support">dette blogindlæg</link>.

note: (itstool) path: section/title
en: How to add missing content rating information
da: Sådan tilføjes oplysninger om indholdsvurdering

note: (itstool) path: section/p
en: The content rating information for an application is stored in the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating"><code>&lt;content_rating&gt;</code></link> element within the application’s <code>&lt;component&gt;</code> in its metainfo file.
da: Oplysningerne om indholdsvurdering for et program gemmes i elementet <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating"><code>&lt;content_rating&gt;</code></link> inden for programmets <code>&lt;component&gt;</code> i dets metainfofil.

note: (itstool) path: section/p
en: Applications should use the OARS 1.1 standard to fill in this element. If the <code>&lt;content_rating&gt;</code> element is not specified, the application’s content rating is unknown. If it’s specified but empty, the application has no content which might be unsuitable for any audience.
da: Programmer bør bruge OARS 1.1-standarden til at udfylde dette element. Hvis elementet <code>&lt;content_rating&gt;</code> ikke er angivet, er programmets indholdsvurdering ukendt. Hvis det er angivet, men tomt, har applikationen ikke noget indhold, der kan være uegnet for nogen målgruppe.

note: (itstool) path: section/p
en: Use <link href="https://hughsie.github.io/oars/">the OARS generator</link> to produce suitable content rating information for an application.
da: Brug <link href="https://hughsie.github.io/oars/">OARS-generatoren</link> til at generere passende indholdsvurderingsoplysninger til et program.

note: (itstool) path: section/title
en: How to fix incorrect licensing information
da: Sådan rettes forkerte licensoplysninger

note: (itstool) path: section/p
en: The licensing information for an application is stored in the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-project_license"><code>&lt;project_license&gt;</code></link> element within the application’s <code>&lt;component&gt;</code> in its metainfo file.
da: Et programs licensoplysninger gemmes i elementet <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-project_license">&lt;project_license&gt;</link> inden for programmets <code>&lt;component&gt;</code> i dets metainfofil.

note: (itstool) path: section/p
en: The content in this element should be an <link href="https://spdx.org/specifications">SPDX expression</link> which describes the ‘main’ license for the project. This should typically be the license of the code, and not include the license of the documentation or ancillary content.
da: Indholdet i dette element skal være et <link href="https://spdx.org/specifications">SPDX-udtryk</link>, der beskriver projektets “hovedlicens”. Dette bør typisk være kildekodens licens og må ikke omfatte licensen for dokumentationen eller supplerende indhold.

note: (itstool) path: section/p
en: If the SPDX expression is a single license, or an ‘or’ combination of multiple licenses, which are all <link href="https://spdx.org/licenses/">FSF or OSI approved</link>, the application is considered ‘free software’ and the license tile says so. Otherwise, it’s considered ‘proprietary’.
da: Hvis SPDX-udtrykket er en enkelt licens eller en “eller”-kombination af flere licenser, som alle er <link href="https://spdx.org/licenses/">godkendt af FSF eller OSI</link>, betragtes programmet som “fri software”, og det fremgår af licensflisen. I modsat fald betragtes det som “proprietært”.

note: (itstool) path: section/p
en: If an application is being displayed as ‘proprietary’ when you think it shouldn’t be, it’s likely that the <code>&lt;project_license&gt;</code> element includes the documentation license for the project. Remove it.
da: Hvis et program vises som “proprietært”, selvom du mener, det ikke burde være det, er det sandsynligt, at elementet <code>&lt;project_license&gt;</code> indeholder projektets dokumentationslicens. Fjern det.

note: (itstool) path: section/p
en: <link href="https://gitlab.gnome.org/GNOME/meld/-/issues/579">For example</link>, change the license metadata from:
da: Ændr <link href="https://gitlab.gnome.org/GNOME/meld/-/issues/579">for eksempel</link> licensmetadata fra:

note: (itstool) path: section/p
en: to
da: til

note: (itstool) path: item/p
en: <link href="https://tecnocode.co.uk/2021/07/05/dont-generally-put-cc-by-sa-in-appdata/">Don’t (generally) put documentation license in appdata</link>
da: <link href="https://tecnocode.co.uk/2021/07/05/dont-generally-put-cc-by-sa-in-appdata/">Du bør (generelt) ikke placere dokumentationslicensen i appdata</link>

note: (itstool) path: section/title
en: How to add missing links
da: Sådan tilføjes manglende links

note: (itstool) path: section/p
en: The links for an application are stored as <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url"><code>&lt;url&gt;</code></link> elements within the application’s <code>&lt;component&gt;</code> in its metainfo file.
da: Et programs links gemmes som <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url"><code>&lt;url&gt;</code>-elementer inden for programmets <code>&lt;component&gt;</code> i dets metainfofil.

note: (itstool) path: section/p
en: Add as many of the link types documented in the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url">appstream specification</link> as are available for the application. If no suitable page exists for a given link type, it doesn’t have to be included.
da: Tilføj så mange af de linktyper, der er beskrevet i <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url">appstream-specifikationen</link>, som findes til programmet. Hvis der ikke findes en passende side til en given linktype, behøver den ikke at blive medtaget.

note: (itstool) path: section/p
en: For example, here are the resource links for the <app>Software</app> app:
da: Her er for eksempel links til ressourcerne for programmet <app>Software</app>:

note: (itstool) path: section/title
en: How to set the carousel tile background color
da: Sådan indstilles karruselflisens baggrundsfarve

note: (itstool) path: section/p
en: The carousel tile background color is normally extracted automatically from the application’s icon. If that color is unsatisfactory, however, it can be overridden by using the <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-branding">appstream’s <code>&lt;branding/&gt;</code> element</link> with declared colors (since 47.x series). The advantage is that more clients can use the colors.
da: Karruselflisens baggrundsfarve hentes normalt automatisk fra programmets ikon. Hvis den farve ikke er tilfredsstillende, kan den dog tilsidesættes ved at bruge <link href="https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-branding">appstreams <code>&lt;branding/&gt;</code>-element</link> med angivne farver (siden 47.x-serien). Fordelen er, at flere klienter kan bruge farverne.

note: (itstool) path: section/p
en: For example, here are some branding entries:
da: Her er nogle eksempler på branding:

note: (itstool) path: note/p
en: Note the <code>scheme_preference</code> attribute is ignored, <app>Software</app> chooses the better color for the theme on its own.
da: Bemærk, at attributten <code>scheme_preference</code> ignoreres; <app>Software</app> vælger selv den bedste farve til temaet.

note: (itstool) path: section/p
en: There is left, for backward compatibility, the possibility to add the following XML to the application’s metainfo <code>&lt;component&gt;</code> element:
da: Af hensyn til bagudkompatibilitet er det stadig muligt at tilføje følgende XML til programmets metainfo-<code>&lt;component&gt;</code>-element:

note: (itstool) path: section/p
en: but the <code>&lt;branding/&gt;</code> element has a precedence.
da: men <code>&lt;branding/&gt;</code>-elementet har forrang.

note: (itstool) path: section/p
en: The value of <code>GnomeSoftware::key-colors</code> is a text-format GVariant with type <code>a(yyy)</code>, and represents an unordered set of key colors for the application. Each element of the set is a color in RGB form ranging from <code>(0, 0, 0)</code> to <code>(255, 255, 255)</code>.
da: Værdien af <code>GnomeSoftware::key-colors</code> er en GVariant i tekstformat af typen <code>a(yyy)</code>, der repræsenterer en uordnet mængde af tastefarver til programmet. Hvert element i mængden er en farve i RGB-format, der spænder fra <code>(0, 0, 0)</code> til <code>(255, 255, 255)</code>.

note: (itstool) path: section/p
en: Colors should be chosen so that they:
da: Farver bør vælges så de:

note: (itstool) path: item/p
en: Are identifiable to the application, matching the application’s branding in some way, if possible.
da: Kan genkendes i forbindelse med programmet og om muligt på en eller anden måde matcher programmets branding.

note: (itstool) path: item/p
en: Contrast with the edge of the application’s icon, so that when they are used as a background behind it, the icon can be distinguished.
da: Står i kontrast til kanten af programmets ikon, så ikonet kan skelnes, når farverne bruges som baggrund bag det.

note: (itstool) path: item/p
en: Contrast with the foreground text color in the Adwaita theme (<code>#2e3436</code>) and in its dark variant (<code>#eeeeec</code>). This generally means choosing a color with a medium level of brightness.
da: Står i kontrast til forgrundstekstfarven i Adwaita-temaet (<code>#2e3436</code>) og i dets mørke variant (<code>#eeeeec</code>). Det betyder som regel, at man skal vælge en farve med en middel lysstyrke.

note: (itstool) path: item/p
en: Contrast can be checked using the <link href="https://flathub.org/apps/org.gnome.design.Contrast/">Contrast app</link>.
da: Kontrasten kan kontrolleres ved hjælp af programmet <link href="https://flathub.org/apps/org.gnome.design.Contrast/">Contrast</link>.

note: (itstool) path: section/p
en: At least one color should be specified. More can be specified if one color can’t satisfy all the requirements above, and <app>Software</app> will choose the most appropriate to use in the carousel tile. If exactly one color is specified, its brightness and saturation may be modified to improve contrast with the foreground color. If more than one color is specified, the one with the best contrast with the foreground color will be chosen, and its brightness and saturation will not be modified.
da: Der skal angives mindst én farve. Der kan angives flere, hvis én farve ikke kan opfylde alle ovenstående krav, og <app>Software</app> vælger den mest passende til brug i karruselflisen. Hvis der angives nøjagtigt én farve, kan dens lysstyrke og mætning ændres for at forbedre kontrasten til forgrundsfarven. Hvis der angives mere end én farve, vælges den med den bedste kontrast til forgrundsfarven, og dens lysstyrke og mætning ændres ikke.

note: (itstool) path: section/title
en: How to test carousel tile background color changes
da: Sådan testes ændringer i karruselflisens baggrundsfarve

note: (itstool) path: section/p
en: Modify the metainfo file for your application, and then run <app>Software</app> with:
da: Redigér dit programs metainfofil, og kør derefter <app>Software</app> med:

note: (itstool) path: section/p
en: <cmd>gnome-software --show-metainfo=<var>/path/to/app.metainfo.xml</var>,icon=<var>/path/to/app/icon.png</var></cmd>
da: <cmd>gnome-software --show-metainfo=<var>/sti/til/app.metainfo.xml</var>,icon=<var>/sti/til/app/icon.png</var></cmd>

note: (itstool) path: section/p
en: The details page for your application will be shown. If you navigate back to the overview page of <app>Software</app>, your application will be the only one in the ‘featured’ carousel.
da: Dit programs detaljeside vises. Hvis du går tilbage til oversigtssiden for <app>Software</app>, vil dit program være den eneste i karrusellen “Udvalgte”.
