documentation/locale/da/LC_MESSAGES/websites.po
2021-12-12 03:30:44 +01:00

4190 lines
174 KiB
Plaintext
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# jonas jensen <j.jensen@tcomp.dk>, 2021
# JonathanStein <jstein@image.dk>, 2021
# Per Rasmussen <perhgrasmussen@gmail.com>, 2021
# Ejner Sønniksen <ejner@vkdata.dk>, 2021
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2021
# lhmflexerp <lhm@flexerp.dk>, 2021
# Martin Trigaux, 2021
# Sanne Kristensen <sanne@vkdata.dk>, 2021
# Mads Søndergaard, 2021
# Mads Søndergaard, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-14 14:55+0200\n"
"PO-Revision-Date: 2021-05-14 13:23+0000\n"
"Last-Translator: Mads Søndergaard, 2021\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../content/applications/websites.rst:5
msgid "Websites"
msgstr "Websites"
#: ../../content/applications/websites/ecommerce.rst:5
msgid "eCommerce"
msgstr "Webshop"
#: ../../content/applications/websites/ecommerce/getting_started.rst:5
msgid "Get started"
msgstr "Kom igang"
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:3
msgid "How to customize my catalog page"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:6
msgid "Product Catalog"
msgstr "Varekartotek"
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:8
msgid ""
"All your published items show up in your catalog page (or *Shop* page)."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:13
msgid ""
"Most options are available in the *Customize* menu: display attributes, "
"website categories, etc."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:20
msgid "Highlight a product"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:22
msgid ""
"Boost the visibility of your star/promoted products: push them to top, make "
"them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop"
" page, switch to Edit mode and click any item to start customizing the grid."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:26
msgid ""
"See how to do it: "
"https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:29
msgid "Quick add to cart"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:31
msgid ""
"If your customers buy a lot of items at once, make their process shorter by "
"enabling purchases from the catalog page. To do so, add product description "
"and add to cart button. Turn on the following options in *Customize* menu: "
"Product Description, Add to Cart, List View (to display product description "
"better)."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:3
msgid "How to build a product page"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:5
msgid "On the website click *New Page* in the top-right corner."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:7
msgid "Then click *New Product* and follow the blinking tips."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:12
msgid "Here are the main elements of the Product page:"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:17
msgid "Many elements can be made visible from the *Customize* menu."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:22
msgid "See how to configure your products from links here below."
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:26
msgid ":doc:`../managing_products/variants`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:27
msgid ":doc:`/applications/sales/sales/products_prices/taxes`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:28
msgid ":doc:`../managing_products/stock`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:29
msgid ":doc:`../maximizing_revenue/cross_selling`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:30
msgid ":doc:`../maximizing_revenue/reviews`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:31
msgid ":doc:`../maximizing_revenue/pricing`"
msgstr ""
#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:32
msgid ":doc:`../../website/optimize/seo`"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products.rst:5
msgid "Manage my products"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:3
msgid "How to display several images per product"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:5
msgid ""
"By default your product web page displays the main image of your product "
"only. If you like to show your products under several angles, you can turn "
"the image into a carrousel."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:11
msgid ""
"Check *Several images per product* in :menuselection:`Website Admin --> "
"Configuration --> Settings`."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:13
msgid ""
"Open a product detail form and upload images from *Images* tab. Hit *Create*"
" in Edit mode to get the upload wizard."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:19
msgid "Such extra image are common to all the product variants (if any)."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:3
msgid "How to show product availability"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:5
msgid ""
"The availability of your products can be shown on the website to reassure "
"your customers."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:10
msgid ""
"To display this, open the *Sales* tab in the product detail form and select "
"an option in *Availability*."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:16
msgid ""
"A custom warning message can be anything related to a stock out, delivery "
"delay, etc."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:22
msgid "This tool does not require the Inventory app to be installed."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/stock.rst:25
msgid ""
"If one item is no longer sellable, unpublish it from your website. If it "
"comes to one particular product variant, deactivate the variant in the "
"backend (see :doc:`../maximizing_revenue/pricing`)."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3
msgid "How to manage product variants"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5
msgid ""
"Product variants are used to offer variations of the same product to your "
"customers on the products page. For example, the customer chooses a T-shirt "
"and then selects its size and color. In the example below, the customer "
"chooses a phone, and then selects the memory; color and Wi-Fi band from the "
"available options."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:15
msgid "How to create attributes & variants"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:17
msgid ""
"Turn on *Products can have several attributes, defining variants (Example: "
"size, color,...)* in :menuselection:`Sales --> Settings`."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:20
msgid "Select a product from the Products list, go to the *Variants* tab."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:22
msgid ""
"Add as many attributes as you need from 3 different types: radio buttons, "
"drop-down menu or color buttons. You get several variants as soon as there "
"are 2 values for 1 attribute."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:30
msgid "How to edit variants"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:32
msgid "See all the variants from the product template detail form."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:40
msgid "You can edit following data:"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:42
msgid "Picture (will update in real time on the website),"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:43
msgid "Barcode,"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:44
msgid "Internal Reference (SKU #),"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:45
msgid "Volume,"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:46
msgid "Weight,"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:47
msgid "Active (available in quotes & website)."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:50
msgid ""
"Both the Barcode and the Internal Reference are variant-specific. You need "
"to populate them once the variants generated."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:54
msgid ""
"See and edit all the variants from :menuselection:`Sales --> Sales --> "
"Product Variants` as well. This might be quicker if you manage lots of "
"variants."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:58
msgid "How to set specific prices per variant"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:60
msgid ""
"You can also set a specific public price per variant by clicking *Variant "
"Prices* in the product detail form (action in top-left corner)."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:66
msgid ""
"The Price Extra is added to the product price whenever the corresponding "
"attribute value is selected."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:76
msgid ""
"Pricelist formulas let you set advanced price computation methods for "
"product variants. See :doc:`../maximizing_revenue/pricing`."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:80
msgid "How to disable/archive variants"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82
msgid ""
"You can disable/archive specific variants so that they are no longer "
"available in quotes & website (not existing in your stock, deprecated, "
"etc.). Simply uncheck *Active* in their detail form."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:88
msgid ""
"To retrieve such archived items, hit *Archived* on searching the variants "
"list. You can reactivate them the same way."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue.rst:5
msgid "Maximize my revenue"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:3
msgid "How to sell accessories and optional products (cross-selling)"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:5
msgid ""
"You sell computers. Why not stimulating your customers to buy a top-notch "
"screen or an extra-warranty? That's the goal of cross-selling "
"functionalities:"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:8
msgid "Accessory products on checkout page,"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:9
msgid ""
"Optional products on a new *Add to Cart* screen (not installed by default)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:12
msgid "Accessory products when checking out"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:14
msgid ""
"Accessories (e.g. for computers: mouse, keyboard) show up when the customer "
"reviews the cart before paying."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:20
msgid "Select accessories in the *Sales* tab of the product detail page."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:26
msgid ""
"There is an algorithm to figure out the best accessories to display in case "
"several items are added to cart. If any item is the accessory of several "
"products added to cart, it is most likely that it will be atop the list of "
"suggested accessories."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:31
msgid "Optional products when adding to cart"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:33
msgid ""
"Optional products are directly related to the item added to cart (e.g. for "
"computers: warranty, OS software, extra components). Whenever the main "
"product is added to cart, such a new screen pops up as an extra step."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40
msgid "To publish optional products:"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:42
msgid ""
"Install *eCommerce Optional Products* addon in *Apps* menu. Remove the "
"default filter to search on addons as well, otherwise only main apps show "
"up."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:48
msgid "Select optional items from the *Sales* tab of the product detail form."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:54
msgid ""
"The quantity of optional items added to cart is the same than the main item."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:3
msgid "Adapt prices to website visitors"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:5
msgid ""
"This section sheds light on pricing features found in the eCommerce app:"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:7
msgid "force a price by geo-localization,"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:9
msgid "let the customer choose the currency."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:11
msgid ""
"As a pre-requisite, check out how to managing product pricing: "
":doc:`/applications/sales/sales/products_prices/prices/pricing`)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:15
msgid "Geo-IP automatically applies the right price"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:17
msgid ""
"Assign country groups to your pricelists. That way, visitors who aren't "
"logged in yet will get their own currency when landing on your website."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:20
msgid "Once logged in, they get the pricelist matching their country."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:23
msgid "Currency selector"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:25
msgid ""
"In the case that you sell in several currencies, you can let your customers "
"choose their own. Check the *Selectable* box to add the pricelist to the "
"website drop-down menu, which can be found in *Pricelists* under the "
"*Products* menu, located in the Website application."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:35
msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:36
msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:37
msgid ":doc:`promo_code`"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:3
msgid "How to create & share promotional codes"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:5
msgid ""
"Want to boost your sales for Xmas? Share promocodes through your marketing "
"campaigns and apply any kind of discounts."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:9
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:13
#: ../../content/applications/websites/website/publish/multi_website.rst:18
msgid "Setup"
msgstr "Opsætning"
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:11
msgid ""
"Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based"
" on formula* for *Sale Price*."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:14
msgid ""
"Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a"
" new pricelist with the discount rule (see :doc:`pricing`). Then enter a "
"code."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:21
msgid ""
"Make the promocode field available on your *Shopping Cart* page (option in "
"*Customize* menu). Add a product to cart to reach it."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:27
msgid ""
"Once turned on you see a new section on the right side. On clicking *Apply* "
"prices get automatically updated in the cart."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:33
msgid ""
"The promocode used by the customer is stored in the system so you can "
"analyze the performance of your marketing campaigns."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:39
msgid "Show sales per pricelists..."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:43
msgid ":doc:`pricing`"
msgstr ":doc:`prissætning`"
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:3
msgid "How to enable comments & rating"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:5
msgid ""
"Publishing and monitoring customer experience will help you gain the trust "
"of new customers and better engage with your community. In 2 clicks, allow "
"your customer to share their feedback!"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:15
msgid ""
"Activate comments & rating from the *Customize* menu of the product web "
"page."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:21
msgid ""
"Visitors must log in to share their comments. Make sure they are able to do "
"so (see Portal documentation)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:25
msgid "Review the posts in real time"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:27
msgid ""
"Whenever a post is published, the product manager and all the product "
"followers get notified in their Inbox (*Discuss* menu)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:34
msgid ""
"By default the user who created the product is automatically set as "
"follower."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:36
msgid ""
"Click the product name to open the detail form and review the comment (in "
"the product discussion thread)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:43
msgid "Moderate & unpublish"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:45
msgid ""
"You can easily moderate by using the chatter, either in the product detail "
"form or on the web page."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:48
msgid ""
"To unpublish the post, open the product web page and click the *Published* "
"button to turn it red (*Unpublished*)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:56
msgid "..tip::"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:55
msgid ""
"You can access the web page from the detail form by clicking the *Published*"
" smart button (and vice versa)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier alternative products (upselling)"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:5
msgid ""
"In order to maximize your revenue, suggesting pricier alternative products "
"is strongly advised for basic items. That way, your customer will spend more"
" time browsing your catalog."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:12
msgid "To do so:"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:14
msgid ""
"Select such *Alternative Products* in the *Sales* tab of the product detail "
"form. 3 alternatives are fine! Don't publish too many otherwise your "
"customers will be confused."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:20
msgid ""
"Turn on *Alternative Products* from the *Customize* menu of the product web "
"page."
msgstr ""
#: ../../content/applications/websites/ecommerce/overview.rst:5
#: ../../content/applications/websites/website/publish/translate.rst:6
msgid "Overview"
msgstr "Oversigt"
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:3
msgid "Introduction to Odoo eCommerce"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:10
msgid ""
"The documentation will help you go live with your eCommerce website in no "
"time. The topics follow the buying process:"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:13
msgid "Product Page"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:14
msgid "Shop Page"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:15
msgid "Pricing"
msgstr "Priser"
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:16
msgid "Taxes"
msgstr "Moms"
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:17
msgid "Checkout process"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:18
msgid "Upselling & cross-selling"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:19
msgid "Payment"
msgstr "Betaling"
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:20
msgid "Shipping & Tracking"
msgstr ""
#: ../../content/applications/websites/ecommerce/overview/introduction.rst:24
msgid ":doc:`../../website/publish/domain_name`"
msgstr ""
#: ../../content/applications/websites/ecommerce/publish.rst:5
msgid "Launch my website"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience.rst:5
msgid "Get paid"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:3
msgid "How to get paid with Authorize.Net"
msgstr "Hvordan man bliver betalt med Authorize.net"
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:5
msgid ""
"Authorize.Net is one of the most popular eCommerce payment platforms in "
"North America. Unlike most of the other payment acquirers compatible with "
"Odoo, Authorize.Net can be used as `payment gateway "
"<https://www.authorize.net/solutions/merchantsolutions/pricing/?p=gwo>`__ "
"only. That way you can use the `payment processor or merchant "
"<https://www.authorize.net/partners/resellerprogram/processorlist/>`__ that "
"you like."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:12
msgid "Create an Authorize.Net account"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:14
msgid ""
"Create an `Authorize.Net account <https://www.authorize.net>`__ by clicking "
"'Get Started'."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:16
msgid ""
"In the pricing page, press *Sign up now* if you want to use Authorize.net as"
" both payment gateway and merchant. If you want to use your own merchant, "
"press the related option."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:23
msgid "Go through the registration steps."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:24
msgid ""
"The account is set as a test account by default. You can use this test "
"account to process a test transaction from Odoo."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:26
msgid "Once ready, switch to **Production** mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:30
msgid "Set up Odoo"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:31
msgid ""
"Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or "
"Accounting --> Settings --> Payment Acquirers`."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:33
msgid "Enter both your **Login ID** and your **API Transaction Key**."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:39
msgid ""
"To get those credentials in Authorize.Net, you can rely on *API Login ID and"
" Transaction Key* video of `Authorize.Net Video Tutorials "
"<https://www.authorize.net/videos/>`__. Such videos give meaningful insights"
" about how to set up your Authorize.Net account according to your needs."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:47
msgid "Go live"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:48
msgid ""
"Your configuration is now ready! You can make Authorize.Net visible on your "
"merchant interface and activate the **Production** mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:55
msgid ""
"Credentials provided by Authorize.net are different for both test and "
"production mode. Don't forget to update them in Odoo when you turn on the "
"production mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:61
msgid "Assess Authorize.Net as payment solution"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:62
msgid ""
"You can test and assess Authorize.Net for free by creating a `developer "
"account <https://developer.authorize.net>`__."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:64
msgid ""
"Once the account created you receive sandbox credentials. Enter them in Odoo"
" as explained here above and make sure you are still in *Test* mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:68
msgid ""
"You can also log in to `Authorize.Net sandbox platform "
"<https://sandbox.authorize.net/>`__ to configure your sandbox account."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:71
msgid ""
"To perform fictitious transactions you can use fake card numbers provided in"
" the `Authorize.Net Testing Guide "
"<https://developer.authorize.net/hello_world/testing_guide/>`__."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:76
msgid ":doc:`payment`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/authorize.rst:77
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:111
msgid ":doc:`payment_acquirer`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:3
msgid "How to get paid with payment acquirers"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:5
msgid ""
"Odoo embeds several payment methods to get paid on eCommerce, Sales and "
"Invoicing apps."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:10
msgid "What are the payment methods available"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:13
msgid "Wire transfer"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:15
msgid ""
"Wire Transfer is the default payment method available. The aim is providing "
"your customers with your bank details so they can pay on their own via their"
" bank. This is very easy to start with but slow and inefficient process-"
"wise. Opt for online acquirers as soon as you can!"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:21
msgid "Payment acquirers"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:23
msgid ""
"Redirect your customers to payment platforms to collect money effortless and"
" track the payment status (call-back). Odoo supports more and more platforms"
" over time:"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:27
msgid "`Paypal <paypal.html>`__"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:28
msgid "Ingenico"
msgstr "Ingenico"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:29
msgid "Authorize.net"
msgstr "Authorize.net"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:30
msgid "Adyen"
msgstr "Adyen"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:31
msgid "Buckaroo"
msgstr "Buckaroo"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:32
msgid "PayUmoney"
msgstr "PayUmoney"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:33
msgid "Sips"
msgstr "Sips"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:34
msgid "Stripe"
msgstr "Stribe"
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:38
msgid "How to go live"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:40
msgid ""
"Once the payment method ready, make it visible in the payment interface and "
"activate the **Production** mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:48
msgid "How to let customers save and reuse credit cards"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:49
msgid ""
"To ease the payment of returning customers, you can let them save and reuse "
"a credit card if they want to. If so, a payment token will be saved in Odoo."
" This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:54
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:68
msgid "You can turn this on from the acquirer configuration form."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:61
msgid "How to debit credit cards to pay subscriptions"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:62
msgid ""
"`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to "
"bill services automatically on a recurring basis. Along with it, you can "
"have an automatic debit of the customer's credit card."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:66
msgid "This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:73
msgid ""
"That way a payment token will be recorded when the customer goes for the "
"subscription and an automatic debit will occur whenever an invoice is issued"
" from the subscription."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:79
msgid "How to use other acquirers (advanced)"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:81
msgid ""
"Odoo can submit single payment requests and redirect to any payment "
"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction"
" status. So you will confirm orders manually once you get paid."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:85
msgid "How to:"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:87
msgid "Switch to developer mode."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:89
msgid "Take the **Custom** payment method."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:91
msgid ""
"Set up the payment form (S2S Form Template) as instructed by your payment "
"acquirer. You can start from *default_acquirer_button* that you can "
"duplicate."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:96
msgid "Other configurations"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:98
msgid ""
"Odoo can also be used for more advanced payment processes like installment "
"plans (e.g. `Paypal Installment Plans "
"<https://developer.paypal.com/docs/classic/paypal-payments-"
"standard/integration-guide/installment_buttons>`__)."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:102
msgid ""
"Such a customization service is made on-demand by our technical experts "
"based on your own requirements. A business advisor can reach you out for "
"such matter. `Contact us. <https://www.odoo.com/page/contactus>`__"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:109
msgid ":doc:`paypal`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment.rst:110
msgid ":doc:`wire_transfer`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:3
msgid "How to manage orders paid with payment acquirers"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:5
msgid ""
"Odoo confirms orders automatically as soon as the payment is authorized by a"
" payment acquirer. This triggers the delivery. If you invoice based on "
"ordered quantities, you are also requested to invoice the order."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:12
msgid "What are the payment status"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:13
msgid ""
"At anytime, the salesman can check the transaction status from the order."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:18
msgid "*Draft*: transaction under processing."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:20
msgid ""
"*Pending*: the payment acquirer keeps the transaction on hold and you need "
"to authorize it from the acquirer interface."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:23
msgid ""
"*Authorized*: the payment has been authorized but not yet captured. In Odoo,"
" the order is already confirmed. Once the delivery done, you can capture the"
" amount from the acquirer interface (or from Odoo if you use Authorize.net)."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:28
msgid ""
"*Done*: the payment is authorized and captured. The order has been "
"confirmed."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:30
msgid ""
"*Error*: an error has occurred during the transaction. The customer needs to"
" retry the payment. The order is still in draft."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:34
msgid ""
"*Cancelled*: when the customer cancels the payment in the payment acquirer "
"form. They are taken back to Odoo in order to modify the order."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:37
msgid ""
"Specific messages are provided to your customers for every payment status, "
"when they are redirected to Odoo after the transaction. To edit such "
"messages, go to the *Messages* tab of the payment method."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:44
msgid "Auto-validate invoices at order"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:46
msgid ""
"When the order is confirmed you can also have an invoice automatically "
"issued and paid. This fully-automated made for businesses that invoice "
"orders straight on."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:53
msgid ""
"If you choose this mode you are requested to select a payment journal in "
"order to record payments in your books. This payment is automatically "
"reconcilied with the invoice, marking it as paid. Select your **bank "
"account** if you get paid immediately on your bank account. If you don't you"
" can create a specific journal for the payment acquirer (type = Bank). That "
"way, you can track online payments in an intermediary account of your books "
"until you get paid into your bank account (see `How to register credit card "
"payments "
"<../../accounting/receivables/customer_payments/credit_cards.html>`__)."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:64
msgid "Capture the payment after the delivery"
msgstr "Indhent betalingen efter leveringen."
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:65
msgid ""
"With this mode, the order is confirmed but the amount is kept on hold. Once "
"the delivery processed, you can capture the payment from Odoo. This mode is "
"only available with Authorize.net."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:72
msgid ""
"To capture the payment, open the transaction from the order. Then click "
"*Capture Transaction*."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:78
msgid ""
"With other payment acquirers, you can manage the capture in their own "
"interfaces, not from Odoo."
msgstr ""
"Med andre betalingsudbydere kan du administrere indfangsten i deres egne "
"brugerflader, ikke fra Odoo."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:3
msgid "Configure your Paypal account"
msgstr "Konfigurer din Paypal konto"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:5
msgid ""
"Paypal is available and popular worldwide. It doesnt charge any "
"subscription fee and creating an account is very easy. Thats why we "
"definitely recommend it for starters in Odoo. It works as a seamless flow "
"where the customer is routed to Paypal website to register the payment."
msgstr ""
"Payal er tilgængelig samt populær verden over. Den opkræver ingen "
"abonnements gebyrer, og det er nemt at oprette en konto. Det er derfor vi "
"anbefaler den til at begynde med i Odoo. Den fungere som en gnidningsfri "
"process hvor kunden dirigeres til Paypal hjemmesiden for at registrere "
"betalingen."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:12
msgid "Paypal account"
msgstr "Paypal konto"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:14
msgid ""
"A business account is needed to get paid with Paypal. Create a `Paypayl "
"Business Account "
"<https://www.paypal.com/us/merchantsignup/applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`__"
" or upgrade your Personal account to a Business account. Go to the Paypal "
"settings and click on *Upgrade to a Business account*. Then follow the few "
"configuration steps."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:18
msgid "Settings in Paypal"
msgstr "Indstillinger i Paypal"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:21
msgid ""
"First, lets see how to set up your Paypal account in order to build a "
"seamless customer experience with Odoo."
msgstr ""
"Først, lad os se på hvordan du opsætter din Paypal konto for at lave en "
"strømlinet kundeoplevelse med Odoo."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:23
msgid ""
"Log in and open the settings. Go to *Products & Services > Website payments*"
" and click *Update* on *Website preferences*."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:29
msgid "Auto Return"
msgstr "Auto Returnér"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:31
msgid ""
"*Auto Return* automatically redirects your customers to Odoo once the "
"payment is processed. Check *Auto Return* and enter your domain name "
"\"/shop/confirmation\" as *Return URL* (e.g. "
"https://yourcompany.odoo.com/shop/confirmation)."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:36
msgid ""
"This URL is requested in Paypal but not used in practice as Odoo transmits "
"it at each transaction. Dont worry if you manage several sales channels or "
"Odoo databases."
msgstr ""
"Denne URL er anmodet i Paypal men ikke anvendt i praksis eftersom Odoo "
"sender den ved hver transaktion. Vær ikke bekymret hvis du administrere "
"flere salgskanaler eller Odoo databaser."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:44
msgid "Payment Data Transfer (PDT)"
msgstr "Betalings Data Overførsel (BDO)"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:46
msgid ""
"*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as"
" it is processed. Without it, Odoo cannot end the sales flow. This setting "
"must be activated as well. When saving, an *Identity Token* is generated. "
"You will be later requested to enter it in Odoo."
msgstr ""
"*Betalingsdata Overførsel* levere betalingsbekræftelsen til Odoo så snart "
"den er behandlet. Uden den kan Odoo ikke afslutte salgs-processen. Denne "
"indstilling skal også være aktiveret. Når der gemmes genereres der en "
"*Identitets Token*. Du vil senere blive anmodet om at angive den i Odoo."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:54
msgid "Paypal Account Optional"
msgstr "Paypal Konto Valgfri"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:56
msgid ""
"We advise you to not prompt customers to log in with a Paypal account when "
"they get to pay. Let them pay with debit/credit cards as well, or you might "
"lose some deals. Make sure this setting is turned on."
msgstr ""
"Vi tilråder dig til ikke at prompte kunder til at logge ind med en Paypal "
"konto når de skal betale. Lad dem også betale med kreditkort, ellers kan du "
"tabe indtjening. Sørg for at denne indstilling er slået til."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:63
msgid "Instant Payment Notification (IPN)"
msgstr "Øjeblikkelig Betalings Notifikation (ØBN)"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:65
msgid ""
"PDT sends order confirmations once and only once. As a result, your site "
"must be running when it happens; otherwise, it will never receive the "
"message. Thats why we advise to activate the *Instant Payment Notification*"
" (IPN) on top. With IPN, delivery of order confirmations is virtually "
"guaranteed since IPN resends a confirmation until your site acknowledges "
"receipt."
msgstr ""
"PDT sender ordrebekræftelser én og kun én gang. Derfor skal din side være "
"kørende når det sker; ellers vil den aldrig modtage beskeden. Det er på "
"grund af dette at vi tilråder dig til at aktivere *Øjeblikkelig Betalings "
"Notifikation* (IPN) ovenpå. Med IPN af levering af ordrebekræftelser stort "
"set garanteret, siden IPN gensender en bekræftelse indtil din side anerkende"
" modtagelse deraf."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:72
msgid ""
"To activate IPN, get back to *Website payments* menu and click *Update* in "
"*Instant Payment Notification*."
msgstr ""
"Gå tilbage til *Hjemmeside betalinger* menuen og klik på *Opdater* i "
"*Øjeblikkelig Betalingsnotifikation* for at aktivere IPN."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:75
msgid ""
"The *Notification URL* to set is your domain name + “payment/paypal/ipn” "
"(e.g. https://yourcompany.odoo.com/payment/paypal/ipn)."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:81
msgid "Payment Messages Format"
msgstr "Betaling Beskeder Format"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:83
msgid ""
"If you use accented characters (or anything else than basic Latin "
"characters) for your customer names, addresses... you MUST configure the "
"encoding format of the payment request sent by Odoo to Paypal."
msgstr ""
"Hvis du anvende skrifttegn med accent (eller noget andet end standard "
"Latinske bogstaver) for dine kundenavne, adresser... SKAL du konfigurere "
"indkodnings formatet for betalingsanmodningerne sent af Odoo til Paypal."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:89
msgid ""
"If you don't configure this setting, some transactions fail without notice."
msgstr ""
"Hvis du ikke konfigurere denne indstilling, vil visse transaktioner fejle "
"uden underrettelse."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:91
msgid "To do so, open:"
msgstr "For at gøre dette, åben:"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:93
msgid ""
"`this page for a test account <https://sandbox.paypal.com/cgi-"
"bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
"`denne side for en test-konto <https://sandbox.paypal.com/cgi-"
"bin/customerprofileweb?cmd=_profile-language-encoding>`__"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:95
msgid ""
"`this page for a production account <https://www.paypal.com/cgi-"
"bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
"`denne side er for en produktionskonto <https://www.paypal.com/cgi-"
"bin/customerprofileweb?cmd=_profile-language-encoding>`__"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:97
msgid ""
"Then, click *More Options* and set the two default encoding formats as "
"**UTF-8**."
msgstr ""
"Klik derefter på *Flere Indstillinger* og angiv de to standard "
"indkodningsformater til at være **UTF-8**."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:105
msgid "Your Paypal account is ready!"
msgstr "Din Paypal konto er klar!"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:107
msgid ""
"If you want your customers to pay without creating a Paypal account, "
"**Paypal Account Optional** needs to be turned on."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:113
msgid ""
"For Encrypted Website Payments & EWP_SETTINGS error, please check the "
"`paypal documentation. <https://developer.paypal.com/docs/classic/paypal-"
"payments-standard/integration-guide/encryptedwebpayments/#encrypted-website-"
"payments-ewp>`__"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:117
msgid "Settings in Odoo"
msgstr "Indstillinger i Odoo"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:120
msgid "Activation"
msgstr "Aktivering"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:122
msgid ""
"Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce "
"apps, or from the configuration menu of *Payment Acquirers*."
msgstr ""
"Aktivér *Paypal* fra konfigurationsbjælken i Salg, Fakturering, og eHandel "
"applikationerne, eller fra konfigurationsmenuen i *Betalingsmodtagere*."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:126
msgid "Credentials"
msgstr "Kortoplysninger"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:128
msgid "Odoo requires three Paypal credentials:"
msgstr "Odoo påkræver tre Paypal legitimationsoplysninger:"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:130
msgid "*Email ID* is your login email address in Paypal."
msgstr "*Email ID* er din login email adresse i Paypal."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:132
msgid ""
"*Merchant ID* can be found in the settings of your Paypal account, in "
"*Profile > About the business*."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:134
msgid ""
"*Paypal PDT Token* is given in *Website payments* configuration as explained"
" here above."
msgstr ""
"*Paypal PDT Token* gives i *Hjemmeside betalinger* konfigurationen som "
"forklaret ovenfor."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:140
msgid "Transaction fees"
msgstr "Transaktionsgebyr"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:142
msgid ""
"You can charge extra fees to your customers for paying with Paypal; This to "
"cover the transaction fees Paypal charges you. Once redirected to Paypal, "
"your customer sees an extra applied to the order amount."
msgstr ""
"Du kan opkræve ekstra gebyrer af dine kunder for at betale via Paypal; dette"
" dækker omkostningsgebyrene Paypal pålægger dig. Når de er omdirigeret til "
"Paypal, vil dine kunder se en ekstra gebyr påført deres ordrebeløb."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:145
msgid ""
"To activate this, go to the Configuration tab of Paypal configuration in "
"Odoo and check *Add Extra Fees*."
msgstr ""
"For at aktivere dette, skal du gå til Konfigurations fanen i Paypal "
"konfigurationen i Odoo og markere *Tilføj Ekstra Gebyrer*."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:151
msgid ""
"You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-"
"fees>`__ to set up fees."
msgstr ""
"Du kan henvise til `Paypal Afgifter "
"<https://www.paypal.com/webapps/mpp/paypal-fees>`__ for at oprette afgifter."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:154
msgid ""
"..note:: `Traders in the EU "
"<https://europa.eu/youreurope/citizens/consumers/shopping/pricing-"
"payments/index_en.htm>`__ are not allowed to charge extra fees for paying "
"with credit cards."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:158
msgid "Go live!"
msgstr "Gå live!"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:160
msgid ""
"Your configuration is ready to roll. Make sure *Production* mode is on. Then"
" publish the payment method by clicking the *Published* button right next to"
" it."
msgstr ""
"Din konfiguration er klar til kamp. Tjek at *Produktion* tilstand er slåe "
"til. Udgiv derefter betalingsmetoden ved at klikke på *Udgivet* knappen lige"
" ved siden af den."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:169
msgid ""
"Paypal is now available in your payment form available in eCommerce, Sales "
"and Invoicing apps. Customers are redirected to Paypal website when hitting "
"*Pay Now*. They get back to a confirmation page in Odoo once the payment is "
"processed."
msgstr ""
"Paypal er nu tilgængelig i den betalingsformular, tilgængelig i eHandel, "
"Salg, og Regnskabs applikationer. Kunder omdirigeres til Paypals hjemmeside "
"når de trykker på *Betal Nu*. De vil komme tilbage til bekræftelses siden i "
"Odoo når betalingen er gennemført."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:178
msgid "Test environment"
msgstr "Test miljø"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:180
msgid ""
"You can test the entire payment flow in Odoo thanks to Paypal Sandbox "
"accounts."
msgstr ""
"Du kan teste hele betalingsforløbet i Odoo takket være Paypal Sandkasse "
"konto."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:182
msgid ""
"Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with "
"your Paypal credentials."
msgstr ""
"Log ind på `Paypal Udvikler Siden <https://developer.paypal.com/>`__ med "
"dine Paypal legitimationsoplysninger."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:184
msgid "This will create two sandbox accounts:"
msgstr "Dette vil oprette to sandkasse-konti:"
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:186
msgid ""
"A business account (to use as merchant, e.g. "
"`pp.merch01-facilitator@example.com "
"<mailto:pp.merch01-facilitator@example.com>`__)."
msgstr ""
"En finanskonto (til brug som forhandler, f.eks. "
"`pp.merch01-facilitator@example.com "
"<mailto:pp.merch01-facilitator@example.com>`__)."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:188
msgid ""
"A default personal account (to use as shopper, e.g. "
"`pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__)."
msgstr ""
"En standard personlig konto (til at bruge som handlende, f.eks. "
"`pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__)."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:190
msgid ""
"Log in to Paypal Sandbox with the merchant account and follow the same "
"configuration instructions. Enter your sandbox credentials in Odoo and make "
"sure Paypal is still set on *Test Environment*. Also, make sure the "
"automatic invoicing is not activated in your eCommerce settings, to not "
"generate invoices when a fictitious transaction is completed."
msgstr ""
"Log in i Paypal Sandbox med en forhandlerkonto og følg de samme "
"konfigurationsinstruktioner. Tilgå din sandbox login informationer i Odoo og"
" tjek at Paypal stadig er sat til *Test Miljø*. Tjek derudover at den "
"automatiske fakturering ikke er aktiveret i dine eHandels indstillinger, så "
"der ikke genereres faktura når en fiktionel transaktion gennemføres."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:196
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
"Kør en test transaktion fra Odoo ved hjælp af sandkassens personlige konto."
#: ../../content/applications/websites/ecommerce/shopper_experience/paypal.rst:200
msgid ":doc:`payment` :doc:`payment_acquirer`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:5
msgid ""
"It has never been so easy for your customers to access their customer "
"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are"
" suggested to sign up (name, email, password) when the order is placed, and "
"not before. Indeed, nothing is more annoying than going through a signup "
"process before buying something."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:14
msgid "Sign up"
msgstr "Tilmeld dig"
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:16
msgid ""
"The invitation to sign up shows up when the customer wants to visualize the "
"order from order confirmation email."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:23
msgid "Customer account"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:25
msgid ""
"Once logged in the customer will access the account by clicking *My Account*"
" in the login dropdown menu."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:31
msgid ""
"THere they find all their history. The main address (billing) can also be "
"modified."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:37
msgid ""
"If the customer is set as a contact of a company in your address book, they "
"will see all the documents whose the customer belongs to this company."
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:3
msgid "How to get paid with wire transfers"
msgstr "Hvordan man bliver betalt med bank overførsler"
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:5
msgid ""
"**Wire Transfer** is the default payment method available. The aim is "
"providing your customers with your bank details so they can pay on their "
"own. This is very easy to start with but slow and inefficient process-wise. "
"Opt for payment acquirers as soon as you can!"
msgstr ""
"**Bankoverførsel** er den betalingsmetode der er tilgængelig per standard. "
"Målet er at give dine kunder dine bankinformationer, så de kan betale på "
"egen hånd. Dette er meget nemt i starten, men er en langsommelig og "
"ueffektiv process. Vælg betalingsmodtagere så snart du kan!"
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:13
msgid "How to provide customers with payment instructions"
msgstr "Hvordan man udbyder betalingsinstruktioner til kunder"
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:14
msgid ""
"Put your payment instructions in the **Thanks Message** of your payment "
"method."
msgstr ""
"Læg dine betalings instruktioner i **Takke Beskeden** for din "
"betalingsmetode."
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:19
msgid "They will appear to the customers when they place an order."
msgstr "De vil vises til kunden når de placerer en ordre."
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:26
msgid "How to manage an order once you get paid"
msgstr "Hvordan man håndtere en ordre når du er blevet betalt"
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:28
msgid ""
"Whenever a customer pays by wire transfer, the order stays in an "
"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get "
"paid, you confirm the order manually to launch the delivery."
msgstr ""
"Hver gang en kunde betaler via en overførsel, vil ordren forblive i "
"mellemstadiet **Tilbud Afsendt** (dvs. ubetalt ordre). Når du modtager "
"betaling, bekræfter du ordren manuelt for at igangsætte leveringen."
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:35
msgid "How to create other manual payment methods"
msgstr "Hvordan man opretter andre manuelle betalingsmetoder"
#: ../../content/applications/websites/ecommerce/shopper_experience/wire_transfer.rst:37
msgid ""
"If you manage a B2B business, you can create other manually-processed "
"payment methods like paying by check. To do so, just rename *Wire Transfer* "
"or duplicate it."
msgstr ""
"Hvis du administrere en B2B virksomhed, kan du oprette andre manuelt "
"behandlede betalingsmetoder så som betaling via check. For at gøre dette, "
"skal du blot omdøbe eller kopiere *Bankoverførsel*."
#: ../../content/applications/websites/ecommerce/taxes.rst:5
msgid "Collect taxes"
msgstr ""
#: ../../content/applications/websites/livechat.rst:4
msgid "Live Chat"
msgstr "Live Chat"
#: ../../content/applications/websites/livechat.rst:7
msgid "Chat in real time with website visitors"
msgstr ""
#: ../../content/applications/websites/livechat.rst:9
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
msgstr ""
#: ../../content/applications/websites/livechat.rst:18
#: ../../content/applications/websites/website/optimize/link_tracker.rst:10
msgid "Configuration"
msgstr "Konfiguration"
#: ../../content/applications/websites/livechat.rst:20
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
msgstr ""
#: ../../content/applications/websites/livechat.rst:26
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:33
msgid "Add the live chat to an Odoo website"
msgstr ""
#: ../../content/applications/websites/livechat.rst:35
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
msgstr ""
#: ../../content/applications/websites/livechat.rst:44
msgid "Add the live chat to an external website"
msgstr ""
#: ../../content/applications/websites/livechat.rst:46
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
msgstr ""
#: ../../content/applications/websites/livechat.rst:53
msgid "Hide / display the live chat according to rules"
msgstr ""
#: ../../content/applications/websites/livechat.rst:55
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
msgstr ""
#: ../../content/applications/websites/livechat.rst:65
msgid "Prepare automatic messages"
msgstr ""
#: ../../content/applications/websites/livechat.rst:67
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
msgstr ""
#: ../../content/applications/websites/livechat.rst:75
msgid "Start chatting with customers"
msgstr ""
#: ../../content/applications/websites/livechat.rst:77
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:87
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
msgstr ""
#: ../../content/applications/websites/livechat.rst:91
msgid ""
"Conversations initiated by visitors also appear in the Discuss module in "
"addition to popping up as a direct message. Therefore, inquiries can be "
"answered wherever you are in Odoo."
msgstr ""
#: ../../content/applications/websites/livechat.rst:95
msgid ""
"If there are several operators who have all joined a channel, the system "
"will dispatch visitor sessions randomly between them."
msgstr ""
#: ../../content/applications/websites/livechat.rst:99
msgid "Use commands"
msgstr ""
#: ../../content/applications/websites/livechat.rst:101
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
msgstr ""
#: ../../content/applications/websites/livechat.rst:105
msgid "**/help** : show a helper message."
msgstr ""
#: ../../content/applications/websites/livechat.rst:107
msgid "**/helpdesk** : create a helpdesk ticket."
msgstr ""
#: ../../content/applications/websites/livechat.rst:109
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
msgstr ""
#: ../../content/applications/websites/livechat.rst:111
msgid "**/history** : see 15 last visited pages."
msgstr ""
#: ../../content/applications/websites/livechat.rst:113
msgid "**/lead** : create a new lead."
msgstr ""
#: ../../content/applications/websites/livechat.rst:115
msgid "**/leave** : leave the channel."
msgstr ""
#: ../../content/applications/websites/livechat.rst:118
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
msgstr ""
#: ../../content/applications/websites/livechat.rst:123
msgid "Send canned responses"
msgstr ""
#: ../../content/applications/websites/livechat.rst:125
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
msgstr ""
#: ../../content/applications/websites/livechat.rst:135
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
msgstr ""
#: ../../content/applications/websites/website.rst:5
msgid "Website"
msgstr "Hjemmeside"
#: ../../content/applications/websites/website/optimize.rst:5
msgid "Optimize"
msgstr "Optimér"
#: ../../content/applications/websites/website/optimize/google_analytics.rst:3
msgid "How to track your website's traffic in Google Analytics"
msgstr "Hvordan du sporer din hjemmesides trafik med Google Analytics"
#: ../../content/applications/websites/website/optimize/google_analytics.rst:5
msgid "To follow your website's traffic with Google Analytics:"
msgstr "For at følge din hjemmesides trafik med Google Analytics:"
#: ../../content/applications/websites/website/optimize/google_analytics.rst:7
msgid ""
"`Create a Google Analytics account <https://www.google.com/analytics/>`__ if"
" you don't have any."
msgstr ""
"`Opret en Google Analytics konto <https://www.google.com/analytics/>`__ hvis"
" du ikke har nogen."
#: ../../content/applications/websites/website/optimize/google_analytics.rst:10
msgid ""
"Go through the creation form and accept the conditions to get the tracking "
"ID."
msgstr ""
"Gennemgå oprettelses formularen og accepter betingelserne, for at få et "
"sporings ID."
#: ../../content/applications/websites/website/optimize/google_analytics.rst:15
msgid "Copy the tracking ID to insert it in Odoo."
msgstr "Kopier sporings ID'et til indsættelse i Odoo."
#: ../../content/applications/websites/website/optimize/google_analytics.rst:20
msgid ""
"Go to the *Configuration* menu of your Odoo's Website app. In the settings, "
"turn on Google Analytics and paste the tracking ID. Then save the page."
msgstr ""
"Gå til *Konfiguration* menuen i dit Odoos Hjemmeside app. I indstillinger "
"aktiverer du Google Analytics, og indsætter sporings ID'et. Gem derefter "
"siden."
#: ../../content/applications/websites/website/optimize/google_analytics.rst:27
msgid ""
"To make your first steps in Google Analytics, refer to `Google "
"Documentation. "
"<https://support.google.com/analytics/answer/1008015?hl=en/>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics.rst:31
msgid ":doc:`google_analytics_dashboard`"
msgstr ":doc:`google_analytics_instrumentbræt`"
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:3
msgid "How to track your website traffic from your Odoo Dashboard"
msgstr "Hvordan du sporer hjemmeside trafik fra dit Odoo Instrumentbræt"
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:5
msgid ""
"You can follow your traffic statistics straight from your Odoo Website "
"Dashboard thanks to Google Analytics."
msgstr ""
"Du kan følge dine trafik statistikker direkte fra dit Odoo Hjemmeside "
"Instrumentbræt, takket være Google Analytics."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:8
msgid ""
"A preliminary step is creating a Google Analytics account and entering the "
"tracking ID in your Website's settings (see :doc:`google_analytics`)."
msgstr ""
"Et forudgående skridt i oprettelsen af en Google Analytics konto og "
"indtastning af dit sporings ID i din hjemmesides indstillinger (se "
":doc:`google_analytics`)."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:11
msgid ""
"Go to `Google APIs platform <https://console.developers.google.com>`__ to "
"generate Analytics API credentials. Log in with your Google account."
msgstr ""
"Gå til `Google APIs platform <https://console.developers.google.com>`__ for "
"at generere Analytics API legitimationsoplysninger. Log ind med din Google "
"konto."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:14
msgid "Select Analytics API."
msgstr "Vælg Analytics API."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:19
msgid ""
"Create a new project and give it a name (e.g. Odoo). This project is needed "
"to store your API credentials."
msgstr ""
"Opret et nyt projekt og giv den et navn (f.eks. Odoo). Dette projekt er "
"nødvendig, for at gemme dine API legitimationsoplysninger."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:25
msgid "Enable the API."
msgstr "Aktiver API'en."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:30
msgid "Create credentials to use in Odoo."
msgstr "Opret legitimationsoplysninger til brug i Odoo."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:35
msgid ""
"Select *Web browser (Javascript)* as calling source and *User data* as kind "
"of data."
msgstr ""
"Vælg *Web browser (Javascript)* som kalds kilde, og *Bruger data* som slags "
"på data."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:41
msgid ""
"Then you can create a Client ID. Enter the name of the application (e.g. "
"Odoo) and the allowed pages on which you will be redirected. The *Authorized"
" JavaScript origin* is your Odoo's instance URL. The *Authorized redirect "
"URI* is your Odoo's instance URL followed by "
"'/google_account/authentication'."
msgstr ""
"Opret derefter et Klient ID. Angiv navnet på applikationen (f.eks. Odoo) og "
"de tilladte sider hvorfra du vil blive omdirigeret. *Autoriseret JavaScript "
"oprindelse* er din Odoo instans URL. *Autoriseret omdirigerings URI* er din "
"Odoo instans URL efterfulgt af '/google_account/authentication'."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:51
msgid ""
"Go through the Consent Screen step by entering a product name (e.g. Google "
"Analytics in Odoo). Feel free to check the customizations options but this "
"is not mandatory. The Consent Screen will only show up when you enter the "
"Client ID in Odoo for the first time."
msgstr ""
"Gennemgå Samtykke skærm trinet ved at angive et produktnavn (f.eks. Google "
"Analytics i Odoo). Du er velkommen til at tjekke tilpasningsmulighederne, "
"men det er ikke obligatorisk. Samtykke skærmen vil kun vises efter du har "
"angivet Klient ID'et i Odoo for første gang."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:56
msgid ""
"Finally you are provided with your Client ID. Copy and paste it in Odoo."
msgstr "Endelig tildeles du dit Klient ID. Kopier og indsæt det i Odoo."
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:61
msgid ""
"Open your Website Dashboard in Odoo and link your Analytics account. to past"
" your Client ID."
msgstr ""
"Åben dit Hjemmeside Instrumentbræt i Odoo, og forbind din Analytics konto, "
"for at indsætte dit Klient ID. "
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:67
msgid "As a last step, authorize Odoo to access Google API."
msgstr "Autorisér Odoos adgang til Google API, som et sidste skridt."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:3
msgid "Track clicks and visitors using Link Trackers"
msgstr "Spor klik og besøgende via Link sporere"
#: ../../content/applications/websites/website/optimize/link_tracker.rst:5
msgid ""
"Link Trackers allow you to track your marketing campaigns (emails, banner "
"ads, blog posts, social media posts, affiliate links, etc.). This way, you "
"are able to identify your best traffic sources and make informed decisions "
"about the distribution of your marketing budget."
msgstr ""
"Link sporere gør dig i stand til, at spore dine marketing kampagner (emails,"
" bannere, reklamer, blog indlæg, sociale medie indlæg, filial links, osv.). "
"På denne måde kan du identificere dine bedste trafik kilder, og foretage "
"informerede valg vedrørende distribueringen af dit marketing budget."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:12
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings` and activate "
"*Link Trackers*."
msgstr ""
"Gå til :menuselection:`Hjemmeside --> Konfiguration --> Indstillinger`og "
"aktiver *Link sporere*."
#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
msgid ""
"View of Website settings page emphasizing the link trackers field in Odoo "
"Website"
msgstr ""
#: ../../content/applications/websites/website/optimize/link_tracker.rst:19
msgid "Set up traceable URLs"
msgstr "Opsæt sporbare URL'er"
#: ../../content/applications/websites/website/optimize/link_tracker.rst:21
msgid ""
"Go to :menuselection:`Website --> Go to website --> Promote --> Track this "
"page`. Here, you are able to get a specific tracked URL based on the "
"campaign, medium, and source being used."
msgstr ""
"Gå til :menuselection:`Hjemmeside --> Gå til hjemmeside --> Promover --> "
"Spor denne side`. Her kan du hente en specifik sporet URL, baseret på "
"kampagne, medie, og kilde der anvendes."
#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
msgid "View of the link tracker fields for Odoo Website"
msgstr ""
#: ../../content/applications/websites/website/optimize/link_tracker.rst:28
msgid ""
"**URL**: url of the page you want to track (e.g. the home page or a "
"product's page)."
msgstr ""
"**URL**: URL på siden du vil følge (f.eks. forsiden eller et produkts side)."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:29
msgid "**Campaign**: context of your link (e.g. a special promotion)."
msgstr "**Kampagne**: Kontekst på dit link (f.eks. en særlig promovering)."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:30
msgid ""
"**Medium**: channel used to share (deliver) your link (e.g. an email or a "
"Facebook ad)."
msgstr ""
"**Medie**: Kanal brugt til at dele (levere) dit link (f.eks. en email eller "
"en Facebook reklame)."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:31
msgid ""
"**Source**: platform where the traffic originates (e.g. Google or Twitter)."
msgstr ""
"**Kilde**: Platform hvor trafikken oprinder fra (f.eks. Google eller "
"Twitter)."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:33
msgid ""
"Now, click on *Get tracked link* to generate a URL that you can post or send"
" by the source you have decided on."
msgstr ""
"Kluk nu på *Få sporet link* få et generere en URL som du kan postere og "
"sende via kilden du har bestemt dig for."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:37
msgid "Follow-up on tracked links"
msgstr "Følg op på sporede links"
#: ../../content/applications/websites/website/optimize/link_tracker.rst:39
msgid ""
"To look at statistics of your links, go to :menuselection:`Website --> Go to"
" website --> Promote --> Track this page`. Besides being able to see the "
"*Most Clicked* and *Recently Used* links, click on *Stats* to see complete "
"statistics about the number of clicks and the country of origin of those "
"clicks."
msgstr ""
"For at se statistikker på dine links, kan du gå til "
":menuselection:`Hjemmeside --> Gå til hjemmeside --> Promover --> Spor denne"
" side`. Udover at du kan se links med *Fleste klik* og som er *Anvendt for "
"nyligt*, kan du også klikke på *Statistikker* og se komplette statistikker "
"over antallet af klik samt oprindelseslandene for de klik."
#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
msgid ""
"View of the tracked list emphasizing the statistics buttons in Odoo Website"
msgstr ""
#: ../../content/applications/websites/website/optimize/link_tracker.rst:50
msgid ""
"You can also access the link tracker by typing *odoo.com/r* on your browser."
msgstr ""
"Du kan også tilgå link sporeren ved at skrive *odoo.com/r* i din browser."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:51
msgid ""
"Activate the developer mode (:menuselection:`Settings --> Activate the "
"developer mode`) and get access to the *Link Tracker* module and its back-"
"end functionalities."
msgstr ""
"Aktiver udvikler tilstand (:menuselection:`Indstillinger --> Aktiver "
"udvikler tilstanden`) og tilgå *Link sporer* modulet samt dets back-end "
"funktionaliteter."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:53
msgid ""
"Integrated with :doc:`Google Analytics <google_analytics>`, those trackers "
"allow you to see the number of clicks and visitors to keep you on top of "
"your marketing campaigns."
msgstr ""
"Integreret med :doc:`Google Analytics <google_analytics>`, vil de sporere "
"gør dig i stand til at se antallet af klik samt besøgende, for at holde dig "
"opdateret vedrørende dine marketing kampagner."
#: ../../content/applications/websites/website/optimize/link_tracker.rst:55
msgid ""
"The integration with the :doc:`CRM "
"</applications/sales/crm/track_leads/prospect_visits>` application allows "
"you to understand where your leads and opportunities are coming from."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:3
msgid "How to do Search Engine Optimisation in Odoo (SEO)"
msgstr "Hvordan man laver Søgemaskine Optimering (SEO) i Odoo"
#: ../../content/applications/websites/website/optimize/seo.rst:5
msgid ""
"Search Engine Optimization (SEO) is a set of good practices to optimize your"
" website so that you get a better ranking in search engines like Google. In "
"short, a good SEO allows you to get more visitors."
msgstr ""
"Søgemaskine Optimering (SEO) er et sæt af bedste praksis til at optimere din"
" hjemmeside, så at du får den bedste rangering på søgemaskiner så som "
"Google. Kort sagt, gør en god SEO det muligt for dig at få mange besøgende."
#: ../../content/applications/websites/website/optimize/seo.rst:9
msgid ""
"Some examples of SEO rules: your web pages should load fast, your page "
"should have one and only one title ``<h1>``, meta tags (alt-tag, title-tag) "
"should be consistent with the content, your website should have a "
"``/sitemap.xml`` file, etc."
msgstr ""
"Nogle eksempler på SEO regler: Din hjemmeside bør indlæses hurtigt, din side"
" bør have en, og kun én, titel ``<h1>``, meta tags (alt-tag, titel-tag) bør "
"være konsistente med indholdet, din hjemmeside bør have en ``/sitemap.xml`` "
"fil, osv."
#: ../../content/applications/websites/website/optimize/seo.rst:15
msgid ""
"To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo "
"abstracts all the technical complexities of SEO and handles everything for "
"you, in the best possible way. This will be explained here below."
msgstr ""
"For at garanterer at Odoo Hjemmeside og Odoo eHandel brugere har en god SEO,"
" sammenfatter Odoo alle de tekniske kompleksiteter ved SEO, og administrere "
"alt for dig, på den bedst mulige måde. Dette vil blive forklaret nedenunder."
#: ../../content/applications/websites/website/optimize/seo.rst:20
msgid ""
"But first, let see how you can easily boost your ranking by finetuning the "
"content and the meta tags of your website."
msgstr ""
"Men lad os først se, hvordan du nemt forøger din rangering, ved at "
"finjustere indholdet samt meta tags på din hjemmeside."
#: ../../content/applications/websites/website/optimize/seo.rst:24
msgid "Meta Tags"
msgstr "Meta Tags"
#: ../../content/applications/websites/website/optimize/seo.rst:27
msgid "Title, Description"
msgstr "Titel, Beskrivelse"
#: ../../content/applications/websites/website/optimize/seo.rst:29
msgid ""
"Every web page should define the ``<title>`` and ``<description>`` meta "
"data. These information elements are used by search engines to promote your "
"website. They are automatically generated based on page title & content, but"
" you can finetune them. Make sure they fit the content of the page, "
"otherwise you will be downgraded by search engines."
msgstr ""
"Enhver side bør definere ``<title>`` og ``<description>`` meta data. Disse "
"informations elementer bruges af søgemaskiner til at promovere din "
"hjemmeside. De genereres automatisk ud fra side titel og indhold, men du kan"
" finjustere dem. Tjek at de passer til indholdet på siden, for hvis ikke, "
"vil du blive nedgraderet på søgemaskiner."
#: ../../content/applications/websites/website/optimize/seo.rst:39
msgid "Keywords"
msgstr "Nøgleord"
#: ../../content/applications/websites/website/optimize/seo.rst:40
msgid ""
"In order to write quality content and boost your traffic, Odoo provides a "
"``<keyword>`` finder. Those keywords are the searches you want to head "
"towards your website. For each keyword, you see how it is used in the "
"content (H1, H2, page title, page description, page content) and what are "
"the related searches in Google. The more keywords are used the better."
msgstr ""
"For at skrive kvalitets indhold og forøge din trafik, tilbyder Odoo en "
"``<keyword>`` finder. Disse nøgleord er de søgninger du ønsker skal pege mod"
" din hjemmeside. For hvert nøgleord ser du hvordan det er anvendt på siden "
"(H1, H2, side titel, side beskrivelse, side indhold) og hvad de relaterede "
"søgninger er på Google. Dets flere nøgleord dets bedre."
#: ../../content/applications/websites/website/optimize/seo.rst:50
msgid ""
"If your website is in multiple languages, you can use the Promote tool for "
"every language of a single page and set specific title, description and "
"search tags."
msgstr ""
"Hvis din hjemmeside er på flere sprog, kan du bruge Promovér værktøjet for "
"hvert sprog for hver enkelt side, og angive specifik titel, beskrivelse, og "
"søgnings tags."
#: ../../content/applications/websites/website/optimize/seo.rst:55
msgid "Content is King"
msgstr "Indhold er Kongen"
#: ../../content/applications/websites/website/optimize/seo.rst:57
msgid ""
"When it comes to SEO, content is usually king. Odoo provides several modules"
" to help you build your website content:"
msgstr ""
"Når det gælder SEO, er indhold typisk kongen. Odoo tilbyder flere moduler "
"som hjælper dig med at opbygge din hjemmesides indhold:"
#: ../../content/applications/websites/website/optimize/seo.rst:60
msgid "**Odoo Blogs**: write great contents."
msgstr "**Odoo Blogs**: skriv fantastisk indhold."
#: ../../content/applications/websites/website/optimize/seo.rst:62
msgid ""
"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their "
"content is automatically indexed on the web page. Example: "
"`https://www.odoo.com/slides/public-channel-1 "
"<https://www.odoo.com/slides/public-channel-1>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:66
msgid ""
"**Odoo Forum**: let your community create contents for you. Example: "
"`https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of"
" Odoo.com landing pages)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:70
msgid ""
"**Odoo Mailing List Archive**: publish mailing list archives on your "
"website. Example: `https://www.odoo.com/groups/community-59 "
"<https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:76
msgid ""
"The 404 page is a regular page, that you can edit like any other page in "
"Odoo. That way, you can build a great 404 page to redirect to the top "
"content of your website when visitors get lost in invalid URLs."
msgstr ""
"404 Siden er en normal side, som du kan redigere som enhver anden side i "
"Odoo. På den måde kan du bygge en god 404 side til at omdirigere til toppen "
"af dit indhold på din hjemmeside, når besøgende farer vild og bruger "
"ugyldige URL'er."
#: ../../content/applications/websites/website/optimize/seo.rst:81
msgid "Use Social Networks"
msgstr "Brug Sociale netværk"
#: ../../content/applications/websites/website/optimize/seo.rst:83
msgid ""
"Social media is built for mass sharing. If lots of people share your content"
" on social media, then it's likely more people will link to it, and links "
"are a huge factor for SEO ranking."
msgstr ""
"Sociale medier er bygget til masse-deling. Hvis mange mennesker deler dit "
"indhold på sociale medier, er det sandsynligt, at flere vil linke til det, "
"og links er en kæmpe faktor i SEO rangering."
#: ../../content/applications/websites/website/optimize/seo.rst:87
msgid "Odoo embeds several tools to share content through social media:"
msgstr ""
"Odoo indlejrer flere værktøjer til deling af indhold via sociale medier:"
#: ../../content/applications/websites/website/optimize/seo.rst:90
msgid "Social Network"
msgstr "Social Netværk"
#: ../../content/applications/websites/website/optimize/seo.rst:92
msgid ""
"Odoo allows to link all your social network accounts in your website footer."
" All you have to do is to refer all your accounts in your company settings."
msgstr ""
"Odoo gør det muligt at forbinde alle dine sociale netværks konti i din "
"hjemmesides sidefod. Alt du skal gøre, er at referere dine konti i din "
"virksomheds indstillinger."
#: ../../content/applications/websites/website/optimize/seo.rst:99
msgid "Social Share"
msgstr "Social deling"
#: ../../content/applications/websites/website/optimize/seo.rst:101
msgid ""
"Drop the building block *Share* on any page you want your visitors to share."
" By clicking the icon, they are prompted to share the page in their social "
"media wall."
msgstr ""
"Smid byggeklodsen *Del* på enhver side, som du ønsker dine besøgende skal "
"dele. Ved at klikke på ikonet, spørges de, om de vil dele siden på deres "
"sociale medie væg."
#: ../../content/applications/websites/website/optimize/seo.rst:108
msgid ""
"Most social media use a picture of the picture to decorate the share post. "
"Odoo uses the website logo by default but you can choose any other image of "
"your page in the Promote tool."
msgstr ""
"De fleste sociale medier bruger et billede af billedet til at dekorere det "
"delte indlæg. Odoo bruger hjemmeside logoet per standard, men du kan vælge "
"ethvert andet billede på din side i Promovér værktøjet."
#: ../../content/applications/websites/website/optimize/seo.rst:116
msgid "Facebook Page"
msgstr "Facebook side"
#: ../../content/applications/websites/website/optimize/seo.rst:118
msgid ""
"Drop the building block *Facebook Page* to display a widget of your Facebook"
" business page and encourage visitors to follow it. You can display the "
"timeline, the next events and the messages."
msgstr ""
"Smid byggeklodsen *Facebook Side* for at vise en widget af din Facebook "
"virksomheds side, og opfordre besøgende til at følge den. Du kan vise "
"tidslinjen, de næste begivenheder, og beskederne."
#: ../../content/applications/websites/website/optimize/seo.rst:123
msgid "Twitter Scroller"
msgstr "Twitter Scroller"
#: ../../content/applications/websites/website/optimize/seo.rst:125
msgid ""
"Display the Twitter feeds with customer satifaction on your website. THis "
"will increase the number of tweets and shares."
msgstr ""
"Vis Twitter feedet med kunde tilfredshed på din hjemmeside. Dette vil forøge"
" antallet af tweets og delinger."
#: ../../content/applications/websites/website/optimize/seo.rst:129
msgid "Test Your Website"
msgstr "Test din hjemmeside"
#: ../../content/applications/websites/website/optimize/seo.rst:131
msgid ""
"You can compare how your website rank, in terms of SEO, against Odoo using "
"WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:136
msgid "URLs Handling"
msgstr "URL Håndtering"
#: ../../content/applications/websites/website/optimize/seo.rst:138
msgid "This section sheds some light on how Odoo makes URLs SEO-friendly."
msgstr "Denne sektion kaster lys på, hvordan Odoo gør URL'er SEO-venlige."
#: ../../content/applications/websites/website/optimize/seo.rst:141
msgid "URLs Structure"
msgstr "URL'er Struktur"
#: ../../content/applications/websites/website/optimize/seo.rst:143
msgid "A typical Odoo URL will look like this:"
msgstr "Et typisk Odoo URL vil se sådan her ud:"
#: ../../content/applications/websites/website/optimize/seo.rst:145
msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31"
msgstr "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31"
#: ../../content/applications/websites/website/optimize/seo.rst:147
msgid "With the following components:"
msgstr "Med de følgende komponenter:"
#: ../../content/applications/websites/website/optimize/seo.rst:149
msgid "**https://** = Protocol"
msgstr "**https://** = Protokol"
#: ../../content/applications/websites/website/optimize/seo.rst:151
msgid "**www.mysite.com** = your domain name"
msgstr "**www.minside.com** = Dit domæne navn"
#: ../../content/applications/websites/website/optimize/seo.rst:153
msgid ""
"**/fr\\_FR** = page language. This part of the URL is removed if the visitor"
" browses the main language of the website Thus, the main version of this "
"page is: https://www.mysite.com/shop/product/my-great-product-31"
msgstr ""
"**/fr\\_FR** = side sprog. Denne del af URL'en fjernes hvis den besøgende "
"kigger på modersmålet for hjemmesiden. Derfor er den primære version af "
"denne side: https://www.mysite.com/shop/product/my-great-product-31"
#: ../../content/applications/websites/website/optimize/seo.rst:158
msgid ""
"**/shop/product** = every module defines its own namespace (/shop is for the"
" catalog of the eCommerce module, /shop/product is for a product page)."
msgstr ""
"**/shop/produkt** = ethvert modul definere dets egen navneområde (/shop er "
"til kataloget tilhørende eHandel modulet, /shop/produkt er for en produkt "
"side)."
#: ../../content/applications/websites/website/optimize/seo.rst:162
msgid ""
"**my-great-product** = by default, this is the slugified title of the "
"product this page refers to. But you can customize it for SEO purposes. A "
"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending "
"on the namespace, this could be different objects (blog post, page title, "
"forum post, forum comment, product category, etc.)."
msgstr ""
"**mit-fantastiske-produkt** = per standard er dette den sidste såkaldt "
"slugificeret titel på produktet denne side henviser til. Du kan tilpasse den"
" i forhold til SEO. Et produkt ved navn \"Firkantet brød\" vil blive "
"slugificeret til \"firkantet-broed\". Afhængig af navneområdet, kan dette "
"være forskellige objekter (blog indlæg, side titler, forum indlæg, forum "
"kommentarer, produkt kategorier, osv.)."
#: ../../content/applications/websites/website/optimize/seo.rst:169
msgid "**-31** = the unique ID of the product"
msgstr "**-31** = Det unikke produkt ID"
#: ../../content/applications/websites/website/optimize/seo.rst:171
msgid ""
"Note that any dynamic component of an URL can be reduced to its ID. As an "
"example, the following URLs all do a 301 redirect to the above URL:"
msgstr ""
"Bemærk at enhver dynamisk komponent i en URL kan reduceres til dens ID. Som "
"et eksempel, kan følgende URL'er alle foretage en 301 omdirigering til "
"ovenstående URL:"
#: ../../content/applications/websites/website/optimize/seo.rst:174
msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)"
msgstr "https://www.mysite.com/fr\\_FR/shop/product/31 (kort version)"
#: ../../content/applications/websites/website/optimize/seo.rst:176
msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)"
msgstr "http://mysite.com/fr\\_FR/shop/product/31 (endnu kortere version)"
#: ../../content/applications/websites/website/optimize/seo.rst:178
msgid ""
"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product "
"name)"
msgstr ""
"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (gammelt navn "
"for produkt)"
#: ../../content/applications/websites/website/optimize/seo.rst:181
msgid ""
"Some URLs have several dynamic parts, like this one (a blog category and a "
"post):"
msgstr ""
"Visse URL'er har flere dynamiske dele, så som denne (en blog kategori og et "
"indlæg):"
#: ../../content/applications/websites/website/optimize/seo.rst:184
msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56"
msgstr "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56"
#: ../../content/applications/websites/website/optimize/seo.rst:186
msgid "In the above example:"
msgstr "I ovenstående eksempel:"
#: ../../content/applications/websites/website/optimize/seo.rst:188
msgid "*Company News* is the title of the blog"
msgstr "*Virksomheds nyheder* er titlen på bloggen"
#: ../../content/applications/websites/website/optimize/seo.rst:190
msgid "*The Odoo Story* is the title of a specific blog post"
msgstr "*Odoo historien* er titlen på et specifikt blog indlæg"
#: ../../content/applications/websites/website/optimize/seo.rst:192
msgid ""
"When an Odoo page has a pager, the page number is set directly in the URL "
"(does not have a GET argument). This allows every page to be indexed by "
"search engines. Example:"
msgstr ""
"Når en Odoo side har en pager, angives side nummeret direkte i URL'en (har "
"ikke et GET argument). Dette gør det muligt for enhver side at blive "
"indekseret af søgemaskiner. Eksempel:"
#: ../../content/applications/websites/website/optimize/seo.rst:196
msgid "https://www.odoo.com/blog/page/3"
msgstr "https://www.odoo.com/blog/page/3"
#: ../../content/applications/websites/website/optimize/seo.rst:199
msgid "Changes in URLs & Titles"
msgstr "Ændringer i URL'er & Titler"
#: ../../content/applications/websites/website/optimize/seo.rst:201
msgid ""
"When the URL of a page changes (e.g. a more SEO friendly version of your "
"product name), you don't have to worry about updating all links:"
msgstr ""
"Når en sides URL ændres (f.eks. en mere SEO-venlig udgave af dit produkt "
"navn), behøver du ikke bekymre dig om at opdatere alle links:"
#: ../../content/applications/websites/website/optimize/seo.rst:204
msgid "Odoo will automatically update all its links to the new URL."
msgstr "Odoo vil automatisk opdatere alle dets links til den nye URL."
#: ../../content/applications/websites/website/optimize/seo.rst:206
msgid ""
"If external websites still points to the old URL, a 301 redirect will be "
"done to route visitors to the new website."
msgstr ""
"Hvis eksterne hjemmesider stadig peger på den gamle URL, vil en 301 "
"omdirigering udføres, for at omdirigere besøgende til den nye hjemmeside."
#: ../../content/applications/websites/website/optimize/seo.rst:209
msgid "As an example, this URL:"
msgstr "Som et eksempel. Denne URL:"
#: ../../content/applications/websites/website/optimize/seo.rst:211
msgid "http://mysite.com/shop/product/old-product-name-31"
msgstr "http://mysite.com/shop/product/gammel-produkt-navn-31"
#: ../../content/applications/websites/website/optimize/seo.rst:213
msgid "Will automatically redirect to:"
msgstr "Vil automatisk omdirigere til:"
#: ../../content/applications/websites/website/optimize/seo.rst:215
msgid "http://mysite.com/shop/product/new-and-better-product-name-31"
msgstr "http://mysite.com/shop/product/nyt-og-bedre-produkt-navn-31"
#: ../../content/applications/websites/website/optimize/seo.rst:217
msgid ""
"In short, just change the title of a blog post or the name of a product, and"
" the changes will apply automatically everywhere in your website. The old "
"link still works for links coming from external websites, with a 301 "
"redirect to not lose the SEO link juice."
msgstr ""
"Kort sagt, kan du blot ændre titlen på et blog indlæg eller navnet på et "
"produkt, og ændringerne vil automatisk blive anvendt over alt på din "
"hjemmeside. Det gamle link virker stadig for trafik fra eksterne hjemmeside,"
" via en 301 omdirigering, for ikke at miste SEO link juice."
#: ../../content/applications/websites/website/optimize/seo.rst:223
msgid "HTTPS"
msgstr "HTTPS"
#: ../../content/applications/websites/website/optimize/seo.rst:225
msgid ""
"Search engines boost ranking of secure HTTPS/SSL websites. So, by default "
"all Odoo Online instances are fully based on HTTPS. If the visitor accesses "
"your website through a non HTTPS url, it gets a 301 redirect to its HTTPS "
"equivalent."
msgstr ""
"Søgemaskiner forøger rangeringen på sikre HTTPS/SSL hjemmesider. Derfor er "
"alle Odoo Online instanser fuldt ud baseret på HTTPS per standard. Hvis den "
"besøgende tilgår din hjemmeside via et URL som ikke er HTTPS, får de en 301 "
"omdirigering til dens tilsvarende HTTPS."
#: ../../content/applications/websites/website/optimize/seo.rst:231
msgid "Links: Nofollow Strategy"
msgstr "Links: Nofollow strategi"
#: ../../content/applications/websites/website/optimize/seo.rst:233
msgid ""
"The more a page is linked from external and quality websites, the better it "
"is for your SEO."
msgstr ""
"Dets mere en side linkes fra eksterne kvalitets hjemmesider, dets bedre er "
"det for din SEO."
#: ../../content/applications/websites/website/optimize/seo.rst:236
msgid "Here are Odoo strategies to manage links:"
msgstr "Her er Odoos strategier for håndtering af links:"
#: ../../content/applications/websites/website/optimize/seo.rst:238
msgid ""
"Every link you add to your website is \"dofollow\", which means that this "
"link will contribute to the SEO Juice for the linked page."
msgstr ""
"Ethvert link du tilføjer til din hjemmeside er \"dofollow\", hvilket "
"betyder, at dette link vil bidrage til SEO Juicen for den forbundne side."
#: ../../content/applications/websites/website/optimize/seo.rst:242
msgid ""
"Every link posted by a contributor (forum post, blog comment, etc.) that "
"links to your own website is \"dofollow\" too."
msgstr ""
"Ethvert link posteret af en bidragende (forum indlæg, blog kommentar, osv.) "
"som linker til din egen hjemmeside er også \"dofollow\". "
#: ../../content/applications/websites/website/optimize/seo.rst:245
msgid ""
"But every link posted by a contributor that links to an external website is "
"\"nofollow\". In that way, you do not run the risk of people posting links "
"on your website to third-party websites which have a bad reputation."
msgstr ""
"Men hvert link posteret af en bidrager som forbinder til en ekstern "
"hjemmeside er \"nofollow\". På den måde løber du ikke risikoen for, at folk "
"postere links på din hjemmeside, som peger mod tredjeparts hjemmesider med "
"et dårligt omdømme."
#: ../../content/applications/websites/website/optimize/seo.rst:250
msgid ""
"Note that, when using the forum, contributors having a lot of Karma can be "
"trusted. In such case, their links will not have any ``rel=\"nofollow\"`` "
"attribute."
msgstr ""
"Bemærk at, ved brug af forummet, kan man stole på bidragere med meget Karma."
" I sådanne tilfælde, vil deres links ikke have nogen ``rel=\"nofollow\"`` "
"egenskab."
#: ../../content/applications/websites/website/optimize/seo.rst:255
msgid "Multi-Language Support"
msgstr "Flersprogs understøttelse"
#: ../../content/applications/websites/website/optimize/seo.rst:258
msgid "Multi-Language URLs"
msgstr "Flersprogs URL'er"
#: ../../content/applications/websites/website/optimize/seo.rst:260
msgid ""
"If you run a website in multiple languages, the same content will be "
"available in different URLs, depending on the language used:"
msgstr ""
"Hvis du kører en hjemmeside på flere sprog, vil det samme indhold være "
"tilgængelig via forskellige URL'er, alt afhængig af hvilket sprog anvendes:"
#: ../../content/applications/websites/website/optimize/seo.rst:263
msgid ""
"https://www.mywebsite.com/shop/product/my-product-1 (main language, English "
"here)"
msgstr ""
"https://www.mywebsite.com/shop/product/my-product-1 (Primært sprog, her "
"Engelsk)"
#: ../../content/applications/websites/website/optimize/seo.rst:265
msgid ""
"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French "
"version)"
msgstr ""
"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (Fransk "
"udgave)"
#: ../../content/applications/websites/website/optimize/seo.rst:267
msgid ""
"In this example, fr\\_FR is the language of the page. You can even have "
"several variations of the same language: pt\\_BR (Portuguese from Brazil) , "
"pt\\_PT (Portuguese from Portugal)."
msgstr ""
"I dette eksempel, er fr\\_FR sproget på siden. Du kan sågar have flere "
"variationer af samme sprog: pt\\_BR (Brasiliansk Portugisisk), pt\\_PT "
"(Portugisisk Portugisisk). "
#: ../../content/applications/websites/website/optimize/seo.rst:272
msgid "Language Annotation"
msgstr "Sprog kommentarer"
#: ../../content/applications/websites/website/optimize/seo.rst:274
msgid ""
"To let search engines know that the second URL is the French translation of "
"the first URL, Odoo will add an HTML link element in the header. In the HTML"
" <head> section of the main version, Odoo automatically adds a link element "
"pointing to the translated versions of that webpage;"
msgstr ""
"For at lade søgemaskiner vide, at den sekundære URL er en Fransk "
"oversættelse af den primære URL, vil Odoo tilføje et HTML link element i "
"sidehovedet. I HTML kodens <head> sektion i den primære version, tilføjer "
"Odoo automatisk et link element, som peget på de oversatte udgaver af "
"hjemmesiden;"
#: ../../content/applications/websites/website/optimize/seo.rst:279
msgid ""
"<link rel=\"alternate\" hreflang=\"fr\" "
"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>"
msgstr ""
"<link rel=\"alternate\" hreflang=\"fr\" "
"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>"
#: ../../content/applications/websites/website/optimize/seo.rst:282
msgid "With this approach:"
msgstr "Med denne tilgang:"
#: ../../content/applications/websites/website/optimize/seo.rst:284
msgid ""
"Search engines will redirect to th right language according to the visitor "
"language."
msgstr ""
"Søgemaskiner vil omdirigere til det korrekte sprog, ud fra den besøgendes "
"sprog."
#: ../../content/applications/websites/website/optimize/seo.rst:287
msgid ""
"You do not get penalized by search engines if your page is not translated "
"yet. Indeed, it's not a duplicated content, but a different version of the "
"same content."
msgstr ""
"Du bliver ikke straffet af søgemaskiner hvis din side endnu ikke er oversat."
" Det er ikke kopieret indhold; det er en anden version af det samme indhold."
#: ../../content/applications/websites/website/optimize/seo.rst:292
msgid "Language Detection"
msgstr "Sprogregistrering"
#: ../../content/applications/websites/website/optimize/seo.rst:294
msgid ""
"When a visitor lands for the first time on your website (e.g. "
"yourwebsite.com/shop), they may automatically be redirected to a translated "
"version according to their browser language preference: (e.g. "
"yourwebsite.com/fr\\_FR/shop)."
msgstr ""
"Når en besøgende lander for første gang på din hjemmeside (f.eks. "
"dinhjemmeside.com/shop), kan de muligvis blive omdirigeret til en oversat "
"udgave automatisk, ud fra deres browsers sprog præference "
"(f.eks.dinhjemmeside.com/fr\\_FR/shop)."
#: ../../content/applications/websites/website/optimize/seo.rst:299
msgid ""
"Next time, it keeps a cookie of the current language to avoid any "
"redirection."
msgstr ""
"Næste gang beholder den en cookie over det nuværende sprog, for at undgå "
"omdirigering."
#: ../../content/applications/websites/website/optimize/seo.rst:302
msgid ""
"To force a visitor to stick to the default language, you can use the code of"
" the default language in your link, example: yourwebsite.com/en\\_US/shop. "
"This will always land visitors to the English version of the page, without "
"using the browser language preferences."
msgstr ""
"For at tvinge den besøgende til at holde sig til et standard sprog, kan du "
"bruge koden for standard sproget i dit link, for eksempel: "
"dinhjemmeside.com/en\\_US/shop. Dette vil gøre at besøgende altid lander på "
"den Engelske udgave af siden, uden at anvende browserens sprog præferencer."
#: ../../content/applications/websites/website/optimize/seo.rst:309
msgid "Page Speed"
msgstr "Side hastighed"
#: ../../content/applications/websites/website/optimize/seo.rst:312
msgid "Introduction"
msgstr "Introduktion"
#: ../../content/applications/websites/website/optimize/seo.rst:314
msgid ""
"The time to load a page is an important criteria for search engines. A "
"faster website not only improves your visitor's experience, but gives you a "
"better page ranking. Some studies have shown that, if you divide the time to"
" load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor "
"abandonment rate is also divided by two. (25% to 12.5%). One extra second to"
" load a page could `cost $1.6b to Amazon in sales "
"<http://www.fastcompany.com/1825005/how-one-second-could-cost-"
"amazon-16-billion-sales>`__."
msgstr ""
"Tiden det tager at indlæse en side er et vigtigt kriterie for søgemaskiner. "
"En hurtigere hjemmeside forbedre ikke kun dine besøgendes oplevelse, men "
"giver dig også en bedre side rangering. Visse studier har påvist, at hvis du"
" dividere tiden til at indlæse dine sider side med to (f.eks. 2 sekunder i "
"stedet for 4 sekunder), vil frafaldsraten for besøgende også blive divideret"
" med 2. (25% til 12,5%). Ét ekstra sekund til at indlæse en side kunne "
"`koste Amazon $1,6mia i salg <http://www.fastcompany.com/1825005/how-one-"
"second-could-cost-amazon-16-billion-sales>`__."
#: ../../content/applications/websites/website/optimize/seo.rst:325
msgid ""
"Fortunately, Odoo does all the magic for you. Below, you will find the "
"tricks Odoo uses to speed up your page loading time. You can compare how "
"your website ranks using these two tools:"
msgstr ""
"Heldigvis gør Odoo det hele for dig. Nedenunder finder du de tricks Odoo "
"bruger til at forøge hastigheden på din siders indlæsnings tid. Du kan "
"sammenligne hvordan din hjemmeside rangere via disse to værktøjer:"
#: ../../content/applications/websites/website/optimize/seo.rst:329
msgid ""
"`Google Page Speed "
"<https://developers.google.com/speed/pagespeed/insights/>`__"
msgstr ""
"`Google Side Hastighed "
"<https://developers.google.com/speed/pagespeed/insights/>`__"
#: ../../content/applications/websites/website/optimize/seo.rst:331
msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__"
msgstr ""
"`Pingdom Hjemmeside Hastigheds Test <http://tools.pingdom.com/fpt/>`__"
#: ../../content/applications/websites/website/optimize/seo.rst:334
msgid "Images"
msgstr "Billeder"
#: ../../content/applications/websites/website/optimize/seo.rst:336
msgid ""
"When you upload new images, Odoo automatically compresses them to reduce "
"their sizes (lossless compression for .PNG and .GIF and lossy compression "
"for .JPG)."
msgstr ""
"Når du lægger nye billeder op, komprimere Odoo dem automatisk for at "
"reducere deres størrelse (tabsløst komprimering for .PNG og .GIF samt "
"tabende komprimering for .JPG)."
#: ../../content/applications/websites/website/optimize/seo.rst:340
msgid ""
"From the upload button, you have the option to keep the original image "
"unmodified if you prefer to optimize the quality of the image rather than "
"performance."
msgstr ""
"Fra upload knappen har du mulighed for at beholde det oprindelige billede "
"uredigeret, hvis du foretrækker at optimere kvaliteten på biledet, i stedet "
"for ydeevnen."
#: ../../content/applications/websites/website/optimize/seo.rst:348
msgid ""
"Odoo compresses images when they are uploaded to your website, not when "
"requested by the visitor. Thus, it's possible that, if you use a third-party"
" theme, it will provide images that are not compressed efficiently. But all "
"images used in Odoo official themes have been compressed by default."
msgstr ""
"Odoo komprimerer billeder når de er lagt op på din hjemmeside, ikke når de "
"anmodes af den besøgende. Derfor er det muligt, hvis du anvender et "
"tredjeparts tema, at det bruger billeder som ikke er komprimeret effektivt. "
"Men alle billeder brugt i Odoos officielle temaer er blevet komprimeret per "
"standard."
#: ../../content/applications/websites/website/optimize/seo.rst:354
msgid ""
"When you click on an image, Odoo shows you the Alt and title attributes of "
"the ``<img>`` tag. You can click on it to set your own title and Alt "
"attributes for the image."
msgstr ""
"Når du klikker på et billede, viser Odoo dig Alt og titel egenskaber for "
"``<img>`` tagget. Du kan klikke på den for at angive din egen titel og Alt "
"egenskaber for billedet."
#: ../../content/applications/websites/website/optimize/seo.rst:361
msgid "When you click on this link, the following window will appear:"
msgstr "Når du klikker på dette link, vil det følgende vindue komme frem:"
#: ../../content/applications/websites/website/optimize/seo.rst:366
msgid ""
"Odoo's pictograms are implemented using a font (`Font Awesome "
"<https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes)."
" Thus, you can use as many pictograms as you want in your page, they will "
"not result in extra requests to load the page."
msgstr ""
"Odoos piktogrammer er implementeret via en font (`Font Awesome "
"<https://fortawesome.github.io/Font-Awesome/icons/>`__ i de fleste Odoo "
"temaer). Derfor kan du bruge så mange piktogrammer som du ønsker på din "
"side, og de vil ikke resultere i ekstra indlæsningstid for siden."
#: ../../content/applications/websites/website/optimize/seo.rst:375
msgid "Static Resources: CSS"
msgstr "Statisk ressourcer: CSS"
#: ../../content/applications/websites/website/optimize/seo.rst:377
msgid ""
"All CSS files are pre-processed, concatenated, minified, compressed and "
"cached (server-side and browser-side). The result:"
msgstr ""
"Alle CSS filer er forudbehandlet, sammenkædet, minificeret, komprimeret og "
"cachelagret (på serveren og i browseren). Resultatet:"
#: ../../content/applications/websites/website/optimize/seo.rst:380
msgid "only one CSS file request is needed to load a page"
msgstr "kun én CSS fil anmodning er nødvendig for at indlæse en side"
#: ../../content/applications/websites/website/optimize/seo.rst:382
msgid ""
"this CSS file is shared and cached amongst pages, so that when the visitor "
"clicks on another page, the browser doesn't have to even load a single CSS "
"resource."
msgstr ""
"denne CSS fil er delt og cachelagret iblandt sider, så når en besøgende "
"klikker på en anden side, skal browseren ikke engang indlæse én eneste CSS "
"ressource."
#: ../../content/applications/websites/website/optimize/seo.rst:386
msgid "this CSS file is optimized to be small"
msgstr "denne CSS fil er optimeret til at være lille"
#: ../../content/applications/websites/website/optimize/seo.rst:388
msgid ""
"**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a "
"theme might use another framework, most of `Odoo themes "
"<https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap "
"directly. Since Odoo supports Less and Sass, you can modify CSS rules "
"instead of overwriting them through extra CSS lines, resulting in a smaller "
"file."
msgstr ""
"**Forudbehandlet:** CSS rammen som anvendes af Odoo er Bootstrap. Selv om et"
" tema måske bruger en anden ramme, udvider og tilpasser de fleste af `Odoo "
"temaer <https://www.odoo.com/apps/themes>`__ Bootstrap direkte. Siden Odoo "
"understøtter Less og Sass, kan du redigere CSS regler, i stedet for at "
"overskrive dem via ekstra CSS linjer, hvilket resultere i en mindre fil."
#: ../../content/applications/websites/website/optimize/seo.rst:395
msgid ""
"**Concatenated:** every module or library you might use in Odoo has its own "
"set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having "
"several CSS files is great for the modularity, but not good for the "
"performance because most browsers can only perform 6 requests in parallel "
"resulting in lots of files loaded in series. The latency time to transfer a "
"file is usually much longer than the actual data transfer time, for small "
"files like .JS and .CSS. Thus, the time to load CSS resources depends more "
"on the number of requests to be done than the actual file size."
msgstr ""
"**Sammenkædet:** ethvert modul eller bibliotek som du kunne anvende i Odoo "
"har dets eget sæt af CSS, Less eller Sass filer (eHandel, blogs, temaer, "
"osv.). At have flere CSS filer er godt for modulariteten, men ikke godt for "
"ydeevnen, eftersom de fleste browsere kun can udføre 6 anmodninger "
"parallelt, hvilket resultere i at en masse filer indlæses i serier. "
"Ventetiden ved overførsel af en fil er normalt meget længere end den "
"faktiske overførsels tid på data, for små filer så som .JS og .CSS. Derfor "
"afhænger tiden det tager at indlæse CSS ressourcer af antallet af "
"anmodninger der skal udføres, en den faktiske filstørrelse."
#: ../../content/applications/websites/website/optimize/seo.rst:405
msgid ""
"To address this issue, all CSS / Less / Sass files are concatenated into a "
"single .CSS file to send to the browser. So a visitor has **only one .CSS "
"file to load** per page, which is particularly efficient. As the CSS is "
"shared amongst all pages, when the visitor clicks on another page, the "
"browser does not even have to load a new CSS file!"
msgstr ""
"For at imødekomme dette problem, er alle CSS / Less / Sass filer sammenkædet"
" til én enkelt .CSS fil til afsendelse til browseren. Derfor har en "
"besøgende **kun én .CSS fil til indlæsning** per side, hvilket er særdeles "
"effektivt. Eftersom CSS'en er delt iblandt alle sider, skal browseren end "
"ikke indlæse en ny CSS fil, når en bruger klikker på en anden side!"
#: ../../content/applications/websites/website/optimize/seo.rst:412
msgid "**Both files in the <head>**"
msgstr "**Begge filer i <head>'et**"
#: ../../content/applications/websites/website/optimize/seo.rst:412
msgid "**What the visitor gets (only one file)**"
msgstr "**Hvad den besøgende modtager (kun én fil)**"
#: ../../content/applications/websites/website/optimize/seo.rst:414
msgid "/\\* From bootstrap.css \\*/"
msgstr "/\\* Fra bootstrap.css \\*/"
#: ../../content/applications/websites/website/optimize/seo.rst:414
#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:421
#: ../../content/applications/websites/website/optimize/seo.rst:447
msgid ".text-muted {"
msgstr ".text-muted {"
#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:422
#: ../../content/applications/websites/website/optimize/seo.rst:448
msgid "color: #666;"
msgstr "farve: #666;"
#: ../../content/applications/websites/website/optimize/seo.rst:416
msgid "color: #777;"
msgstr "farve: #777;"
#: ../../content/applications/websites/website/optimize/seo.rst:416
msgid "background: yellow"
msgstr "baggrund: gul"
#: ../../content/applications/websites/website/optimize/seo.rst:417
msgid "background: yellow;"
msgstr "baggrund: gul;"
#: ../../content/applications/websites/website/optimize/seo.rst:417
#: ../../content/applications/websites/website/optimize/seo.rst:418
#: ../../content/applications/websites/website/optimize/seo.rst:423
#: ../../content/applications/websites/website/optimize/seo.rst:449
msgid "}"
msgstr "}"
#: ../../content/applications/websites/website/optimize/seo.rst:420
msgid "/\\* From my-theme.css \\*/"
msgstr "/\\* Fra my-theme.css \\*/"
#: ../../content/applications/websites/website/optimize/seo.rst:426
msgid ""
"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. "
"By doing this, additional page views from the same visitor will not have to "
"load CSS files at all. But some modules might include huge CSS/Javascript "
"resources that you do not want to prefetch at the first page because they "
"are too big. In this case, Odoo splits this resource into a second bundle "
"that is loaded only when the page using it is requested. An example of this "
"is the backend that is only loaded when the visitor logs in and accesses the"
" backend (/web)."
msgstr ""
"CSS'en afsendt til Odoo inkludere alle CSS / Less / Sass for alle sider / "
"moduler. Ved at gøre dette, vil yderligere side visninger fra den samme "
"besøgende ikke skulle indlæse yderligere CSS filer overhovedet. Men visse "
"moduler kan inkludere kæmpe CSS/Javascript ressourcer, som du ikke vil "
"indlæse på forhånd på den første side, fordi de er for store. I dette "
"tilfælde, deler Odoo denne ressoruce op i en sekundær bundt, som kun "
"indlæses når siden der skal anvende den bliver anmodet. Et eksempel på dette"
" er backend'en der kun indlæses, når en besøgende logger ind og tilgør "
"backenden (/web)."
#: ../../content/applications/websites/website/optimize/seo.rst:436
msgid ""
"If the CSS file is very big, Odoo will split it into two smaller files to "
"avoid the 4095 selectors limit per sheet of Internet Explorer. But most "
"themes fit below this limit."
msgstr ""
"Hvis CSS filen er meget stor, vil Odoo dele den op i to mindre filer, for at"
" undgå 4059 selector begrænsningen per ark for Internet Explorer. Men de "
"fleste temaer passer ind under denne grænse."
#: ../../content/applications/websites/website/optimize/seo.rst:440
msgid ""
"**Minified:** After being pre-processed and concatenated, the resulting CSS "
"is minified to reduce its size."
msgstr ""
"**Minificeret:** Efter at være forudbehandlet og sammenkædet, minificeres "
"den resulterende CSS, for at reducere dens størrelse."
#: ../../content/applications/websites/website/optimize/seo.rst:444
msgid "**Before minification**"
msgstr "**Før minificering**"
#: ../../content/applications/websites/website/optimize/seo.rst:444
msgid "**After minification**"
msgstr "**Efter minificering**"
#: ../../content/applications/websites/website/optimize/seo.rst:446
msgid "/\\* some comments \\*/"
msgstr "/\\* nogle kommentarer \\*/"
#: ../../content/applications/websites/website/optimize/seo.rst:446
msgid ".text-muted {color: #666}"
msgstr ".text-muted {color: #666}"
#: ../../content/applications/websites/website/optimize/seo.rst:452
msgid ""
"The final result is then compressed, before being delivered to the browser."
msgstr ""
"Det endelige resultat komprimeres derefter, før det leveres til browseren."
#: ../../content/applications/websites/website/optimize/seo.rst:455
msgid ""
"Then, a cached version is stored server-side (so we do not have to pre-"
"process, concatenate, minify at every request) and browser-side (so the same"
" visitor will load the CSS only once for all pages they visit)."
msgstr ""
"Derefter gemmes en cachelageret version på serveren (så vi ikke skal "
"forudbehandle, sammenkæde, og minificiere ved hver eneste efterspørgsel) "
"samt i browseren (så den samme besøgende vil indlæse CSS'en kun én gang for "
"alle sider de besøger)."
#: ../../content/applications/websites/website/optimize/seo.rst:461
msgid "Static Resources: Javascript"
msgstr "Statisk Ressourcer: Javascript"
#: ../../content/applications/websites/website/optimize/seo.rst:463
msgid ""
"As with CSS resources, Javascript resources are also concatenated, minified,"
" compressed and cached (server-side and browser-side)."
msgstr ""
"Som med CSS ressourcer, er Javascript ressourcer også sammenkædet, "
"minificeret, komprimeret, og cachelageret (på serveren og i browseren)."
#: ../../content/applications/websites/website/optimize/seo.rst:466
msgid "Odoo creates three Javascript bundles:"
msgstr "Odoo oprette tre Javascript bundter:"
#: ../../content/applications/websites/website/optimize/seo.rst:468
msgid ""
"One for all pages of the website (including code for parallax effects, form "
"validation, etc.)"
msgstr ""
"En for alle sider på hjemmesiden (inklusiv kode for parallax effekter, "
"formular godkendelse, osv.)"
#: ../../content/applications/websites/website/optimize/seo.rst:471
msgid ""
"One for common Javascript code shared among frontend and backend (Bootstrap)"
msgstr ""
"En for almindelig Javascript kode delt mellem frontend og backend "
"(Bootstrap)"
#: ../../content/applications/websites/website/optimize/seo.rst:474
msgid ""
"One for backend specific Javascript code (Odoo Web Client interface for your"
" employees using Odoo)"
msgstr ""
"En for backend specifik Javascript kode (Odoo Web Klient Interface for dine "
"ansatte som bruger Odoo)"
#: ../../content/applications/websites/website/optimize/seo.rst:477
msgid ""
"Most visitors of your website will only need the first two bundles, "
"resulting in a maximum of two Javascript files to load to render one page. "
"As these files are shared across all pages, further clicks by the same "
"visitor will not load any other Javascript resource."
msgstr ""
"De fleste besøgende på din hjemmeside vil kun have behov for de første to "
"bundter, hvilket resultere i maks 2 Javascript filer til indlæsning for at "
"gengive en side. Eftersom disse filer er delt iblandt alle sider, vil "
"yderligere klik fra samme besøgende ikke indlæse nogen anden Javascript "
"ressource."
#: ../../content/applications/websites/website/optimize/seo.rst:483
msgid ""
"If you work in debug mode, the CSS and Javascript are neither concatenated, "
"nor minified. Thus, it's much slower. But it allows you to easily debug with"
" the Chrome debugger as CSS and Javascript resources are not transformed "
"from their original versions."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:489
msgid "CDN"
msgstr "CDN"
#: ../../content/applications/websites/website/optimize/seo.rst:491
msgid ""
"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, "
"images) are loaded from a Content Delivery Network. Using a Content Delivery"
" Network has three advantages:"
msgstr ""
"Hvis du aktivere CDN funktionen i Odoo, indlæses statiske ressourcer "
"(Javascript, CSS, billeder) fra et Indholds Leverings Netværk (CDN). Brugen "
"af et Indholds Leverings Netværk har tre fordele:"
#: ../../content/applications/websites/website/optimize/seo.rst:495
msgid ""
"Load resources from a nearby server (most CDN have servers in main countries"
" around the globe)"
msgstr ""
"Indlæs ressourcer fra en nærliggende server (de fleste CDN har servere i "
"primære lande rundt omkring på kloden)"
#: ../../content/applications/websites/website/optimize/seo.rst:498
msgid ""
"Cache resources efficiently (no computation resources usage on your own "
"server)"
msgstr ""
"Cachelager ressourcer effektivt (ingen beregnings ressourcer tages i brug på"
" din egen server)"
#: ../../content/applications/websites/website/optimize/seo.rst:501
msgid ""
"Split the resource loading on different services allowing to load more "
"resources in parallel (since the Chrome limit of 6 parallel requests is by "
"domain)"
msgstr ""
"Del ressource indlæsningen ud på flere forskellige tjenester, hvilket gør "
"det muligt at indlæse flere ressourcer parallelt (siden Chrome grænsen er 6 "
"parallel anmodninger per domæne)"
#: ../../content/applications/websites/website/optimize/seo.rst:505
msgid ""
"You can configure your CDN options from the **Website Admin** app, using the"
" Configuration menu. Here is an example of configuration you can use:"
msgstr ""
"Du kan konfigurere dine CDN indstillinger fra **Hjemmeside Administrator** "
"applikationen, via Konfiguration menuen. Her er et eksempel på en "
"konfiguration du kan bruge:"
#: ../../content/applications/websites/website/optimize/seo.rst:512
msgid "HTML Pages"
msgstr "HTML Sider"
#: ../../content/applications/websites/website/optimize/seo.rst:514
msgid ""
"The HTML pages can be compressed, but this is usually handled by your web "
"server (NGINX or Apache)."
msgstr ""
"HTML Siderne kan komprimeres, men dette håndteres oftest af din web server "
"(NGINX eller Apache)."
#: ../../content/applications/websites/website/optimize/seo.rst:517
msgid ""
"The Odoo Website builder has been optimized to guarantee clean and short "
"HTML code. Building blocks have been developed to produce clean HTML code, "
"usually using Bootstrap and the HTML editor."
msgstr ""
"Odoo Hjemmeside byggeren er blevet optimeret til at garantere en ren og kort"
" HTML kode. Byggeklodserne er blevet udviklet til at producere ren HTML "
"kode, normalt via Bootstrap samt HTML editoren."
#: ../../content/applications/websites/website/optimize/seo.rst:521
msgid ""
"As an example, if you use the color picker to change the color of a "
"paragraph to the primary color of your website, Odoo will produce the "
"following code:"
msgstr ""
"Som et eksempel, hvis du burger farve vælgeren til at ændre farven på et "
"afsnit til den primære farve på din hjemmeside, vil Odoo producere den "
"følgende kode:"
#: ../../content/applications/websites/website/optimize/seo.rst:525
msgid "``<p class=\"text-primary\">My Text</p>``"
msgstr "``<p class=\"text-primary\">Min Tekst</p>``"
#: ../../content/applications/websites/website/optimize/seo.rst:527
msgid ""
"Whereas most HTML editors (such as CKEditor) will produce the following "
"code:"
msgstr ""
"Hvorimod de fleste HTML editorer (så som CKEditor) vil producere den "
"følgende kode:"
#: ../../content/applications/websites/website/optimize/seo.rst:530
msgid "``<p style=\"color: #AB0201\">My Text</p>``"
msgstr "``<p style=\"color: #AB0201\">Min Tekst</p>``"
#: ../../content/applications/websites/website/optimize/seo.rst:533
msgid "Responsive Design"
msgstr "Responsivt Design"
#: ../../content/applications/websites/website/optimize/seo.rst:535
msgid ""
"Websites that are not mobile-friendly are negatively impacted in search "
"engine rankings. All Odoo themes rely on Bootstrap to render efficiently "
"according to the device: desktop, tablet or mobile."
msgstr ""
"Hjemmesider som ikke er mobil-venlige påvirkes negativ i forhold til "
"søgemaskinernes rangering. Alle Odoo temaer afhænger af Bootstrap til "
"effektiv gengivelse, i forhold til enheden: PC, tablet, eller mobil."
#: ../../content/applications/websites/website/optimize/seo.rst:542
msgid ""
"As all Odoo modules share the same technology, absolutely all pages in your "
"website are mobile friendly."
msgstr ""
"Eftersom alle Odoo moduler bruger den samme teknologi, er samtlige sider på "
"din hjemmeside mobil-venlige."
#: ../../content/applications/websites/website/optimize/seo.rst:546
msgid "Browser Caching"
msgstr "Browser Cachelagring"
#: ../../content/applications/websites/website/optimize/seo.rst:548
msgid ""
"Javascript, images and CSS resources have an URL that changes dynamically "
"when their content change. As an example, all CSS files are loaded through "
"this URL: "
"`http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css "
"<http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. "
"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of "
"your website."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:555
msgid ""
"This allows Odoo to set a very long cache delay (XXX) on these resources: "
"XXX secs, while being updated instantly if you update the resource."
msgstr ""
"Dette gør det muligt for Odoo at anvende en meget stor cachelagrings "
"forsinkelse (XXX) vedrørende disse ressourcer: XXX sekunder, imens de "
"opdateres med det samme, hvis du opdatere ressourcen."
#: ../../content/applications/websites/website/optimize/seo.rst:560
msgid "Scalability"
msgstr "Skalérbarhed"
#: ../../content/applications/websites/website/optimize/seo.rst:562
msgid ""
"In addition to being fast, Odoo is also more scalable than traditional CMS "
"and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link "
"provides an analysis of the major open source CMS and eCommerce compared to "
"Odoo when it comes to high query volumes: "
"`*https://www.odoo.com/slides/slide/197* "
"<https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-"
"optimisation-197>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:568
msgid ""
"Here is the slide that summarizes the scalability of Odoo Website & "
"eCommerce."
msgstr ""
"Her er diassen der opsummere skalérbarheden for Odoo Hjemmeside & eHandel."
#: ../../content/applications/websites/website/optimize/seo.rst:574
msgid "Search Engines Files"
msgstr "Søgemaskiner Filer"
#: ../../content/applications/websites/website/optimize/seo.rst:577
msgid "Sitemap"
msgstr "Sitemap"
#: ../../content/applications/websites/website/optimize/seo.rst:579
msgid ""
"The sitemap points out pages to index to search engine robots. Odoo "
"generates a ``/sitemap.xml`` file automatically for you. For performance "
"reasons, this file is cached and updated every 12 hours."
msgstr ""
"Sitemappet udpeger sider til indeksering for søgemaskine robotter. Odoo "
"generere en ``/sitemap.xml`` fil automatisk for dig. Af hensyn til ydeevne, "
"lagres og opdateres denne fil hver 12. time."
#: ../../content/applications/websites/website/optimize/seo.rst:583
msgid ""
"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you "
"have a lot of pages, Odoo will automatically create a Sitemap Index file, "
"respecting the `sitemaps.org protocol "
"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 "
"chunks per file."
msgstr ""
"Per standard vil alle URL være i én enkelt ``/sitemap.xml`` fil, men hvis du"
" har mange sider, vil Odoo automatisk oprette en Sitemap Index fil, i "
"overensstemmelse med `sitemaps.org protokollen "
"<http://www.sitemaps.org/protocol.html>`__ , og gruppere sitemap URL i 45000"
" lunser per fil."
#: ../../content/applications/websites/website/optimize/seo.rst:589
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr "Alle sitemap anførelser har 4 egenskaber der udregnes automatisk:"
#: ../../content/applications/websites/website/optimize/seo.rst:591
msgid "``<loc>`` : the URL of a page"
msgstr "``<loc>``: URL på en side"
#: ../../content/applications/websites/website/optimize/seo.rst:593
msgid ""
"``<lastmod>`` : last modification date of the resource, computed "
"automatically based on related object. For a page related to a product, this"
" could be the last modification date of the product or the page."
msgstr ""
"``<lastmod>``: Den sidste dato hvor ressourcen blev redigeret, udregnet "
"automatisk baseret på relateret objekt. For en side relateret til et "
"produkt, kunne dette være den sidste dato hvor produktet eller siden blev "
"redigeret."
#: ../../content/applications/websites/website/optimize/seo.rst:598
msgid ""
"``<priority>`` : modules may implement their own priority algorithm based on"
" their content (example: a forum might assign a priority based on the number"
" of votes on a specific post). The priority of a static page is defined by "
"it's priority field, which is normalized (16 is the default)."
msgstr ""
"``<priority>``: Moduler kan implementerer deres egen prioritets algoritme, "
"baseret på deres indhold (eksempel: et fora kan tildele en prioritet baseret"
" på antallet af stemmer på et givent indlæg). Prioriteten på en statisk side"
" er defineret ud fra dens prioriterings felt, som er normaliseret (16 er "
"standard)."
#: ../../content/applications/websites/website/optimize/seo.rst:605
msgid "Structured Data Markup"
msgstr "Struktureret Data Markering"
#: ../../content/applications/websites/website/optimize/seo.rst:607
msgid ""
"Structured Data Markup is used to generate Rich Snippets in search engine "
"results. It is a way for website owners to send structured data to search "
"engine robots; helping them understand your content and create well-"
"presented search results."
msgstr ""
"Struktureret Data Markering bruges til at generere berigede Snippets i "
"søgemaskine resultater. Det er en måde hvorpå hjemmeside ejere kan sende "
"struktureret data til søgemaskine robotter; hvilket hjælper dem med at "
"forstå dit indhold, og oprette en god præsentation i søgeresultaterne."
#: ../../content/applications/websites/website/optimize/seo.rst:612
msgid ""
"Google supports a number of rich snippets for content types, including: "
"Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""
"Google understøtter et antal af indholds typer for berigede Snippets, "
"inklusiv: Anmeldelser, folk, produkter, virksomheder, begivenheder, og "
"organisationer."
#: ../../content/applications/websites/website/optimize/seo.rst:615
msgid ""
"Odoo implements micro data as defined in the `schema.org "
"<http://schema.org>`__ specification for events, eCommerce products, forum "
"posts and contact addresses. This allows your product pages to be displayed "
"in Google using extra information like the price and rating of a product:"
msgstr ""
"Odoo implementerer micro data som defineret i `schema.org "
"<http://schema.org>`__ specifikationen for begivenheder, eHandel produkter, "
"forum indlæg, og kontakt adresser. Dette gør det muligt for dine produkt "
"sider at blive fremvist på Google med ekstra information, så som pris og "
"bedømmelse af et produkt:"
#: ../../content/applications/websites/website/optimize/seo.rst:625
msgid "robots.txt"
msgstr "robots.txt"
#: ../../content/applications/websites/website/optimize/seo.rst:627
msgid ""
"When indexing your website, search engines take a first look at the general "
"indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, "
"etc.). Odoo automatically creates it. Its content is:"
msgstr ""
"Når de indekserer din hjemmeside, kigger søgemaskiner først på de generelle "
"indekserings regler i en ``/robots.txt`` fil (tilladte robotter, sitemap "
"sti, osv.). Odoo opretter den automatisk. Dens indhold er:"
#: ../../content/applications/websites/website/optimize/seo.rst:631
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
#: ../../content/applications/websites/website/optimize/seo.rst:634
msgid ""
"It means that all robots are allowed to index your website and there is no "
"other indexing rule than specified in the sitemap to be found at following "
"address."
msgstr ""
"Det betyder at alle robotter har tilladelse til at indeksere din hjemmeside,"
" og der er ingen andre indekserings regler for den følgende adresse, end "
"specificeret i sitemappet."
#: ../../content/applications/websites/website/optimize/seo.rst:638
msgid ""
"You can customize the file *robots* in developer mode from *Settings --> "
"Technical --> User Interface --> Views* (exclude robots, exclude some pages,"
" redirect to a custom Sitemap). Make the Model Data of the view *Non "
"Updatable* to not reset the file after system upgrades."
msgstr ""
#: ../../content/applications/websites/website/publish.rst:5
msgid "Publish"
msgstr "Publicer"
#: ../../content/applications/websites/website/publish/domain_name.rst:3
msgid "How to use my own domain name"
msgstr "Hvordan du bruger dit eget domæne navn"
#: ../../content/applications/websites/website/publish/domain_name.rst:5
msgid ""
"By default, your Odoo Online instance and website have a *.odoo.com* domain "
"name, for both the URL and the emails. But you can change to a custom one "
"(e.g. www.yourcompany.com)."
msgstr ""
"Per standard har din Odoo Online instans og hjemmeside et *.odoo.com* domæne"
" navn, for både URL og emails. Men du kan ændre til dit eget (f.eks. "
"www.dinvirksomhed.com)."
#: ../../content/applications/websites/website/publish/domain_name.rst:10
msgid "What is a good domain name"
msgstr "Hvad er et godt domæne navn"
#: ../../content/applications/websites/website/publish/domain_name.rst:11
msgid ""
"Your website address is as important to your branding as the name of your "
"business or organization, so put some thought into changing it for a proper "
"domain. Here are some tips:"
msgstr ""
"Din hjemmeside adresse er lige så vigtig for dit brand, som navnet på din "
"forretning eller virksomhed, så tænk over at ændre det til et ordentligt "
"domæne. Her er nogle råd:"
#: ../../content/applications/websites/website/publish/domain_name.rst:15
msgid "Simple and obvious"
msgstr "Enkelt og indlysende"
#: ../../content/applications/websites/website/publish/domain_name.rst:16
msgid "Easy to remember and spell"
msgstr "Nemt at huske og stave til"
#: ../../content/applications/websites/website/publish/domain_name.rst:17
msgid "The shorter the better"
msgstr "Jo kortere jo bedre"
#: ../../content/applications/websites/website/publish/domain_name.rst:18
msgid "Avoid special characters"
msgstr "Undgå specielle tegn"
#: ../../content/applications/websites/website/publish/domain_name.rst:19
msgid "Aim for a .com and/or your country extension"
msgstr "Gå efter en .com og / eller din landekode"
#: ../../content/applications/websites/website/publish/domain_name.rst:21
msgid ""
"Read more: `How to Choose a Domain Name for Maximum SEO "
"<https://www.searchenginejournal.com/choose-a-domain-name-maximum-"
"seo/158951/>`__"
msgstr ""
"Læs mere: `Hvordan man vælger et domæne navn for maksimal SEO "
"<https://www.searchenginejournal.com/choose-a-domain-name-maximum-"
"seo/158951/>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:24
msgid "How to buy a domain name"
msgstr "Hvordan man køber et domæne navn"
#: ../../content/applications/websites/website/publish/domain_name.rst:25
msgid "Buy your domain name at a popular registrar:"
msgstr "Køb dit domæne navn hos en populær registrator:"
#: ../../content/applications/websites/website/publish/domain_name.rst:27
msgid "`GoDaddy <https://www.godaddy.com>`__"
msgstr "`GoDaddy <https://www.godaddy.com>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:28
msgid "`Namecheap <https://www.namecheap.com>`__"
msgstr "`Namecheap <https://www.namecheap.com>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:29
msgid "`OVH <https://www.ovh.com>`__"
msgstr "`OVH <https://www.ovh.com>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:31
msgid ""
"Steps to buy a domain name are pretty much straight forward. In case of "
"issue, check out those easy tutorials:"
msgstr ""
"Skridt til at købe et domæne navn er stort set lige ud ad landevejen. I "
"tilfælde af problemer, kan du tjekke disse vejledninger:"
#: ../../content/applications/websites/website/publish/domain_name.rst:34
msgid "`GoDaddy <https://roadtoblogging.com/buy-domain-name-from-godaddy>`__"
msgstr "`GoDaddy <https://roadtoblogging.com/buy-domain-name-from-godaddy>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:35
msgid ""
"`Namecheap <https://www.loudtips.com/buy-domain-name-hosting-namecheap//>`__"
msgstr ""
"`Namecheap <https://www.loudtips.com/buy-domain-name-hosting-namecheap//>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:37
msgid ""
"Feel free to buy an email server to have email addresses using your domain "
"name. However don't buy any extra service to create or host your website. "
"This is Odoo's job!"
msgstr ""
"Du er velkommen til at købe en email server så du kan bruge email adresse "
"med dit domæne. Men køb dog ikke nogen ekstra tjenester til oprettelse eller"
" hosting af din hjemmeside. Det er Odoos job!"
#: ../../content/applications/websites/website/publish/domain_name.rst:45
msgid "How to apply my domain name to my Odoo instance"
msgstr "Hvordan anvender jeg mit domæne navn på min Odoo instans"
#: ../../content/applications/websites/website/publish/domain_name.rst:46
msgid ""
"First let's authorize the redirection (yourcompany.com -> "
"yourcompany.odoo.com):"
msgstr ""
"Las os først autorisere omdirigeringen (dinvirksomhed.com -> "
"dinvirksomhed.odoo.com):"
#: ../../content/applications/websites/website/publish/domain_name.rst:48
msgid "Open your Odoo.com account from your homepage."
msgstr "Åben din Odoo.com konto fra din hjemmeside."
#: ../../content/applications/websites/website/publish/domain_name.rst:53
msgid "Go to the *Manage Databases* page."
msgstr "Gå til *Administrer Databaser* siden."
#: ../../content/applications/websites/website/publish/domain_name.rst:58
msgid ""
"Click on *Domains* to the right of the database you would like to redirect."
msgstr ""
"Klik på *Domæner* til højre for databasen du gerne vil omdirigere til."
#: ../../content/applications/websites/website/publish/domain_name.rst:63
msgid ""
"A database domain prompt will appear. Enter your custom domain (e.g. "
"www.yourcompany.com)."
msgstr ""
"En database domæne prompt vil vises. Angiv dit eget domæne (f.eks. "
"www.dinvirksomhed.com)."
#: ../../content/applications/websites/website/publish/domain_name.rst:70
msgid ""
"We can now apply the redirection from your domain name's manager account:"
msgstr ""
"Vi kan nu anvende omdirigeringen fra din domænenavns administrationskonto:"
#: ../../content/applications/websites/website/publish/domain_name.rst:72
msgid "Log in to your account and search for the DNS Zones management page."
msgstr "Log ind på din konto og søg efter DNZ Zone håndteringssiden."
#: ../../content/applications/websites/website/publish/domain_name.rst:74
msgid ""
"Create a CNAME record *www.yourdomain.com* pointing to *mywebsite.odoo.com*."
" If you want to use the naked domain (e.g. yourdomain.com), you need to "
"redirect *yourdomain.com* to *www.yourdomain.com*."
msgstr ""
"Opret et CNAME datasæt *www.ditdomæne.com* som pege på "
"*minhjemmeside.odoo.com*. Hvis du vil bruge det nøgne domæne (f.eks. "
"ditdomæne.com), skal du omdirigere *ditdomæne.com* til *www.ditdomæne.com*."
#: ../../content/applications/websites/website/publish/domain_name.rst:78
msgid "Here are some specific guidelines to create a CNAME record:"
msgstr ""
"Her er nogle specifikke retningslinjer til oprettelse af CNAME datasæt:"
#: ../../content/applications/websites/website/publish/domain_name.rst:80
msgid "`GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__"
msgstr "`GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:81
msgid ""
"`Namecheap "
"<https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-"
"can-i-set-up-a-cname-record-for-my-domain>`__"
msgstr ""
"`Namecheap "
"<https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-"
"can-i-set-up-a-cname-record-for-my-domain>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:82
msgid ""
"`OVH "
"<https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__"
msgstr ""
"`OVH "
"<https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__"
#: ../../content/applications/websites/website/publish/domain_name.rst:85
msgid "How to enable SSL (HTTPS) for my Odoo instance"
msgstr "Hvordan du aktiverer SSL (HTTPS) for din Odoo instans"
#: ../../content/applications/websites/website/publish/domain_name.rst:87
msgid ""
"Until recently, Odoo users needed to use a third-party CDN service provider "
"such as CloudFlare to enable SSL."
msgstr ""
"Indtil for nyligt skulle Odoo brugere anvende en tredjeparts CDN udbyder, så"
" som CloudFlare, for at anvende SSL."
#: ../../content/applications/websites/website/publish/domain_name.rst:89
msgid ""
"It is not required anymore: Odoo generates the certificate for you "
"automatically, using integration with `Let's Encrypt Certificate Authority "
"and ACME protocol <https://letsencrypt.org/how-it-works/>`__. In order to "
"get this, simply add your domain name in your customer portal (a separate "
"certificate is generated for each domain name specified)."
msgstr ""
"Det er ikke nødvendigt længere: Odoo genererer certifikatet for dig "
"automatisk, via integration med `Let's Encrypt Certificate Authority and "
"ACME protocol <https://letsencrypt.org/how-it-works/>`__. For at få dette, "
"skal du blot tilføje dit domænenavn i din kundeportal (et særskilt "
"certifikat genereres for hvert domænenavn angivet)."
#: ../../content/applications/websites/website/publish/domain_name.rst:93
msgid "**Please note that the certificate generation may take up to 24h.**"
msgstr ""
"**Bemærk venligst at certifikat oprettelsen kan tage op til 24 timer.**"
#: ../../content/applications/websites/website/publish/domain_name.rst:95
msgid ""
"If you already use CloudFlare or a similar service, you can keep using it or"
" simply change for Odoo. The choice is yours."
msgstr ""
"Hvis du allerede bruger CloudFlare, eller en lignende tjeneste, kan du "
"fortsætte med at bruge det, eller blot ændre til Odoo. Det er op til dig."
#: ../../content/applications/websites/website/publish/domain_name.rst:98
msgid "My website is indexed twice by Google"
msgstr "Min hjemmeside er indekseret to gange af Google"
#: ../../content/applications/websites/website/publish/domain_name.rst:100
msgid ""
"If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.com*,"
" Google indexes your website under both names. This is a limitation of the "
"Odoo cloud platforms/"
msgstr ""
"Hvis du har oprettet et tilpasset domæne *mitdomæne.com* navn for "
"*mindatabase.odoo.com*, Google indekserer din hjemmeside under begge navne. "
"Dette er en begrænsning af Odoo Cloud platformene/"
#: ../../content/applications/websites/website/publish/domain_name.rst:105
msgid ":doc:`/applications/productivity/discuss/email_servers`"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:3
msgid "Manage Multi Websites"
msgstr "Administrer Flere Hjemmesider"
#: ../../content/applications/websites/website/publish/multi_website.rst:8
msgid ""
"Odoos Multi-Websites opens up broad possibilities of diversification and "
"customer segmentation for your business. A multiplied audience and boosted "
"revenue are now just a few clicks away!"
msgstr ""
"Odoos Multi-Hjemmesider åbner op for en bred vifte af muligheder for "
"diversificering og kunde segmentering for din virksomhed. Et mangedoblet "
"publikum og forøget omsætning er blot et par klik væk!"
#: ../../content/applications/websites/website/publish/multi_website.rst:12
msgid ""
"Each website can work in a fully independent way, with its theme, branding, "
"domain name, header & footer, pages, languages, products, blog posts, forum,"
" slides, events, live chat channels, etc. Lets go for a tour!"
msgstr ""
"Hver hjemmeside fungere på en fuldt ud uafhængig måde, med dets temaer, "
"branding, domænenavn, sidehoved- og fod, sider, sprog, produkter, blog "
"indlæg, fora, dias, begivenheder, live chat kanaler, osv. Lad os tage en "
"rundvisning!"
#: ../../content/applications/websites/website/publish/multi_website.rst:20
msgid ""
"To create a new website, go to :menuselection:`Website --> Configuration → "
"Settings`. The button, *Create a new website*, lays in the first section."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:28
msgid ""
"In the upcoming prompt, set a name for your new website and a specific "
"domain name. Leave empty to publish the new website under the default domain"
" of your Odoo database. You can later set some country groups to redirect "
"visitors to it using Geo IP."
msgstr ""
"Angiv et navn for din hjemmeside, og specificer et domænenavn, i den "
"kommende prompt. Lad den stå tom for at udgive den nye hjemmeside under "
"standard domænet for din Odoo database. Du kan senere angive nogle "
"landegrupper som omdirigerer besøgende til den via Geo IP."
#: ../../content/applications/websites/website/publish/multi_website.rst:36
msgid ""
"Then, select a theme. This new website might have an entirely different "
"purpose or audience than the first one. So feel free to go for a different "
"theme!"
msgstr ""
"Vælg så et tema. Denne nye hjemmeside kan har et helt andet formål eller "
"publikum end den første. Så du kan roligt prøve et andet tema!"
#: ../../content/applications/websites/website/publish/multi_website.rst:40
msgid ""
"Once the theme is selected, you can start to build the homepage of your "
"website. Follow the purple drops; they will help you in the first steps."
msgstr ""
"Når et tema er valgt, kan du begynde at bygge forsiden for din hjemmeside. "
"Følg de lilla dråber; de vil hjælpe dig med de første skridt."
#: ../../content/applications/websites/website/publish/multi_website.rst:47
msgid ""
"If you run Odoo Online, dont forget to redirect any new domain name to your"
" Odoo database (CNAME) and to authorize it Odoo-side. More information can "
"be found :doc:`here <domain_name>`."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:51
msgid "Create the menu"
msgstr "Opret menuen"
#: ../../content/applications/websites/website/publish/multi_website.rst:53
msgid ""
"The new website has a default menu with all the installed applications. To "
"edit it, click *Pages > Edit Menu*. Moving forward you only edit the menu of"
" the current website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:58
msgid "Switch from one website to another"
msgstr "Skift fra en hjemmeside til en anden"
#: ../../content/applications/websites/website/publish/multi_website.rst:61
msgid ""
"As easy as ABC! There is a website switcher in the right corner of the edit "
"bar. Switching to another website will connect to the domain of this "
"website. If you use another domain for the website, the user is requested to"
" sign in."
msgstr ""
"Så nemt som ABC! Der er en hjemmeside skifter i højre hjørne af "
"redigeringsbjælken. Skift til en anden hjemmeside vil forbinde til domænet "
"for denne hjemmeside. Hvis du bruger et andet domæne for hjemmesiden, bedes "
"brugeren om at logge ind igen."
#: ../../content/applications/websites/website/publish/multi_website.rst:70
msgid ""
"When switching, you are redirected to the same domain path on the other "
"website (e.g.,/shop/myproduct). If this URL is not used, you will be "
"redirected to a 404 page but suggested to create a new page from there."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:73
msgid "Add features"
msgstr "Tilføj funktioner"
#: ../../content/applications/websites/website/publish/multi_website.rst:75
msgid ""
"The website apps you install (e.g., Slides, Blogs) are made available on all"
" your websites. You can, of course, keep them hidden in one website by "
"removing the menu item."
msgstr ""
"De hjemmeside applikationer du installerer (f.eks. Dias, Blog) gøres "
"tilgængelige på alle dine hjemmesider. Du kan, selvfølgelig, holde dem "
"skjult på en hjemmeside ved at fjerne menu punktet."
#: ../../content/applications/websites/website/publish/multi_website.rst:79
msgid ""
"Each website comes with a high range of specific options in the settings. "
"First, select the website to configure."
msgstr ""
"Hver hjemmeside kommer med en lang række specifikke valgmuligheder i "
"indstillingerne. Vælg først hjemmesiden der skal konfigureres."
#: ../../content/applications/websites/website/publish/multi_website.rst:85
msgid ""
"Then, take a look at the options flagged with the earth icon. It means they "
"only impact the very website you are working on."
msgstr ""
"Tag derefter et kig på indstillingerne markeret med et jordklode-ikon. Det "
"betyder at de kun påvirker selve den hjemmeside du arbejder på."
#: ../../content/applications/websites/website/publish/multi_website.rst:91
msgid "You can, for instance, set specific :"
msgstr "Du kan, for eksempel, angive specifikke :"
#: ../../content/applications/websites/website/publish/multi_website.rst:93
msgid "languages,"
msgstr "sprog,"
#: ../../content/applications/websites/website/publish/multi_website.rst:95
msgid "domain names,"
msgstr "domænenavne,"
#: ../../content/applications/websites/website/publish/multi_website.rst:97
msgid "social media links,"
msgstr "links til sociale medier,"
#: ../../content/applications/websites/website/publish/multi_website.rst:99
msgid "customer portal mode (B2C vs. B2B),"
msgstr "kundeportal tilstande (B2C eller B2B),"
#: ../../content/applications/websites/website/publish/multi_website.rst:101
msgid "dedicated live chat channels,"
msgstr "dedikerede live chat kanaler,"
#: ../../content/applications/websites/website/publish/multi_website.rst:103
msgid "etc."
msgstr "etc."
#: ../../content/applications/websites/website/publish/multi_website.rst:105
msgid "The other options are global and apply to all your websites."
msgstr ""
"De andre indstillinger er globale, og gælder for alle dine hjemmesider."
#: ../../content/applications/websites/website/publish/multi_website.rst:108
msgid "Manage domain names"
msgstr "Administrer domænenavne"
#: ../../content/applications/websites/website/publish/multi_website.rst:110
msgid ""
"As said earlier, your websites can either share the same domain name or use "
"a specific one. If you share it and want to adapt the content per region, "
"set country groups in the setting of each website. Visitors will be "
"redirected to the right website using Geo IP."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:119
msgid ""
"Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, "
"dont forget to install *Geoip* library."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:122
msgid "`Read the full documentation about domain names here <domain_name>`__,"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:125
msgid "Customize the visitor experience"
msgstr "Tilpas den besøgendes oplevelse"
#: ../../content/applications/websites/website/publish/multi_website.rst:128
msgid ""
"The customer experience can be customized very profoundly thanks to the menu"
" \\*Customize\\*. All the visual options available there are specific to "
"each website. Go through the different pages to adapt them to this new "
"audience. Focus on workflows, and automatic pages (eCommerce checkout, "
"blogs, events, etc.) as the number of available options is higher there."
msgstr ""
"Kundeoplevelsen kan tilpasses i stor grad takket være menuen \\*Tilpas\\*. "
"Alle de visuelle indstillinger der er specifikke til hver hjemmeside. "
"Gennemgå de forskellige sider for at tilpasse dem til det nye publikum. "
"Fokuser på workflows og automatiske sider (eHandel check-ud, blogs, "
"begivenheder, osv.) eftersom antallet af tilgængelige indstillinger er "
"større der."
#: ../../content/applications/websites/website/publish/multi_website.rst:138
msgid "Publish specific content per website"
msgstr "Udgiv specifikt indhold per hjemmeside"
#: ../../content/applications/websites/website/publish/multi_website.rst:141
msgid ""
"Like static pages, any content created from the front-end (product, blog "
"post, etc.) is always only published in the current website. You can change "
"that from the edit form view in the backend and leave the *Website* field "
"blank. This will publish it in all the websites."
msgstr ""
"Som med statiske sider, udgives indhold oprettet i front-enden (produkt, "
"blog indlæg, osv.) altid på den nuværende hjemmeside. Du kan ændre dette fra"
" rediger form visningen i back-enden, ved at lade *Hjemmeside* feltet stå "
"tomt. Dette vil udgive det på alle hjemmesider."
#: ../../content/applications/websites/website/publish/multi_website.rst:149
msgid ""
"Here are all the objects that you can link to *either one or all the "
"websites*:"
msgstr ""
"Her er alle objekterne du kan forbinde til *enten en eller alle "
"hjemmesider*:"
#: ../../content/applications/websites/website/publish/multi_website.rst:152
msgid "Products"
msgstr "Varer"
#: ../../content/applications/websites/website/publish/multi_website.rst:154
msgid "Product Categories for eCommerce"
msgstr "Produktkategorier for eHandel"
#: ../../content/applications/websites/website/publish/multi_website.rst:156
msgid "Blogs"
msgstr "Blogs"
#: ../../content/applications/websites/website/publish/multi_website.rst:158
msgid "Slide Channels"
msgstr "Dias Kanaler"
#: ../../content/applications/websites/website/publish/multi_website.rst:160
msgid "Forums"
msgstr "Fora"
#: ../../content/applications/websites/website/publish/multi_website.rst:162
msgid "Events"
msgstr "Arrangementer"
#: ../../content/applications/websites/website/publish/multi_website.rst:164
msgid "Job Positions"
msgstr "Stillinger"
#: ../../content/applications/websites/website/publish/multi_website.rst:167
msgid ""
"When you create the record from the backend and publish it, typically a "
"product or an event, it is made available in all websites."
msgstr ""
"Når du opretter datasættet fra backenden og udgiver den - typisk et produkt "
"eller en begivenhed - gøres det tilgængelig på alle hjemmesider."
#: ../../content/applications/websites/website/publish/multi_website.rst:171
msgid "Publish a page in all websites"
msgstr "Udgiv en side på alle hjemmesider"
#: ../../content/applications/websites/website/publish/multi_website.rst:173
msgid ""
"A new static page is created and only made available in the current website."
" You can duplicate it to other websites from :menuselection:`Website --> "
"Configuration → Pages`. To do so, leave the *Website* field empty."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:177
msgid ""
"If you want to duplicate it in just one other website, duplicate the page "
"and set the new website."
msgstr ""
"Hvis du vil kopiere den til blot én anden hjemmeside, skal du kopiere siden "
"og angive den nye hjemmeside."
#: ../../content/applications/websites/website/publish/multi_website.rst:183
msgid ""
"When you edit the page again, the change only affects the current website. A"
" new page is duplicated and tied up to the website. The original page still "
"being linked to all websites."
msgstr ""
"Når du redigere siden igen, vil ændringen kun anvendes på den nuværende "
"hjemmeside. En ny side kopieres og bindes op på hjemmesiden. Den oprindelige"
" side vil fortsat være forbundet til alle hjemmesider."
#: ../../content/applications/websites/website/publish/multi_website.rst:188
msgid ""
"By grouping pages by URL in the page manager, you quickly find the original "
"page behind each edited page."
msgstr ""
"Ved at gruppere sider ud fra URL i sidehåndteringen, kan du hurtigt finde "
"den oprindelige side bag hver redigeret side."
#: ../../content/applications/websites/website/publish/multi_website.rst:195
msgid "Multi-companies"
msgstr "Multi-companies"
#: ../../content/applications/websites/website/publish/multi_website.rst:197
msgid ""
"Each website can be linked to a specific company of your system, in a multi-"
"companies environment."
msgstr ""
"Hver hjemmeside kan forbindes til en specifik virksomhed tilhørende dit "
"system, i et multi-virksomheds miljø."
#: ../../content/applications/websites/website/publish/multi_website.rst:203
msgid ""
"With such a configuration, only company-related data appear on the website "
"(products, jobs, events, etc.)."
msgstr ""
"Med en sådan konfiguration, vises kun virksomheds-relateret data på "
"hjemmesiden (produkter, stillinger, begivenheder, osv.)."
#: ../../content/applications/websites/website/publish/multi_website.rst:206
msgid ""
"Website editors can only view and edit the pages of the records they have "
"access to, typically the ones belonging to their current company (and to "
"their subsidiaries, or child companies in Odoo language). And so is it for "
"visitors."
msgstr ""
"Hjemmeside redigering kan kun vise og redigere siderne tilhørende de datasæt"
" de har adgang til, typisk dem der tilhører den nuværende virksomhed (og "
"deres datter selskaber, eller child companies på Odoo sprog). Og sådan er "
"det også for besøgende."
#: ../../content/applications/websites/website/publish/multi_website.rst:212
msgid ""
"If websites are multi-companies, you dont change company when switching "
"websites. To change the company and see the related content, use the company"
" selector in the menu."
msgstr ""
"Hvis hjemmesider er multi-virksomheder, ændre du ikke virksomhed ved at "
"skifte hjemmeside. For at ændre virksomheden og se relateret indhold, skal "
"du bruge virksomheds vælgeren i menuen."
#: ../../content/applications/websites/website/publish/multi_website.rst:218
msgid "Configure your eCommerce website"
msgstr "Konfigurer din eHandels hjemmeside"
#: ../../content/applications/websites/website/publish/multi_website.rst:220
msgid ""
"eCommerce is a crucial feature in the multi-websites environment. We made it"
" so that the entire flow can be customized to fit the very audience of each "
"website."
msgstr ""
"eHandel er en kritisk funktion i multi-virksomheds miljøet. Vi har sørget "
"for at hele flowet kan tilpasses til selve publikummet for hver hjemmeside."
#: ../../content/applications/websites/website/publish/multi_website.rst:225
msgid "Products only available on one website"
msgstr "Produkter kun tilgængelig på en hjemmeside"
#: ../../content/applications/websites/website/publish/multi_website.rst:227
msgid ""
"We already saw earlier how to publish a specific record in only one website."
" You will find the \\*Website\\* field in the eCommerce tab of the product "
"edit form. Empty means available in all websites."
msgstr ""
"Vi har tidligere set hvordan man udgiver et specifikt datasæt på kun én "
"hjemmeside. Du finder \\*Hjemmeside\\* feltet i eHandels fanen på produkt "
"redigerings formularen. Tom betyder at den er tilgængelig på alle "
"hjemmesider."
#: ../../content/applications/websites/website/publish/multi_website.rst:235
msgid "Products available on *some* websites"
msgstr "Produkter der er tilgængelige på *nogle* hjemmesider"
#: ../../content/applications/websites/website/publish/multi_website.rst:237
msgid ""
"To make a product available on some websites, but not all of them, you "
"should duplicate the product for each website."
msgstr ""
"For at gøre et produkt tilgængelig på nogle hjemmesider, men ikke dem alle, "
"bør du kopiere produktet for hver hjemmeside."
#: ../../content/applications/websites/website/publish/multi_website.rst:240
msgid ""
"If you need a unique reference to manage in your inventory, you should "
"install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each "
"kit will link each published “virtual” product to the main reference managed"
" in your inventory. That way, any item sold from your website will be "
"converted into the storable item in the delivery order."
msgstr ""
"Hvis du skal bruge en unik reference til at håndtere dit lager, bør du "
"installere *Produktion* og oprette *Sæt* styklister. Hvert sæt vil forbinde "
"hvert udgivet \"virtuelt\" produkt til den primær reference håndteret i dit "
"lager. På den måde vil ethvert produkt solgt fra din hjemmeside blive "
"omdannet til en lagerprodukt på leveringsordren."
#: ../../content/applications/websites/website/publish/multi_website.rst:247
msgid "Pricelists"
msgstr "Prislister"
#: ../../content/applications/websites/website/publish/multi_website.rst:249
msgid ""
"To manage specific prices by websites, you can activate *Multiple Sales "
"Prices per Product* in Website settings."
msgstr ""
"For at administrere specifikke priser på hjemmesider, kan du aktivere *Flere"
" Salgspriser per Produkt* i Hjemmeside indstillinger."
#: ../../content/applications/websites/website/publish/multi_website.rst:252
msgid ""
"Then, go to :menuselection:`Website --> Products → Pricelists` to create "
"additional pricelists. Read :doc:`Pricelists Documentation "
"<../../ecommerce/maximizing_revenue/pricing>`,"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:255
msgid ""
"If you need help. Select a website to make a pricelist only available on "
"this website."
msgstr ""
"Hvis du har behov for hjælp. Vælg en hjemmeside for at oprette en prisliste "
"der kun er tilgængelig på denne hjemmeside."
#: ../../content/applications/websites/website/publish/multi_website.rst:261
msgid ""
"Leaving the field empty means that you make it work in all websites if "
"*Selectable* is selected. Otherwise, it makes it only available for backend "
"operations of Sales and Point of Sale applications."
msgstr ""
"Ved at lade feltet stå tomt får du det til at virke på alle hjemmesider hvis"
" *Kan vælges* er angivet. Ellers gøres det kun tilgængeligt for backend "
"operationer for Salg og Point of Sale applikationer."
#: ../../content/applications/websites/website/publish/multi_website.rst:266
msgid "Payment Acquirers and Delivery Methods"
msgstr "Betalingsindløsere og Leveringsmetoder"
#: ../../content/applications/websites/website/publish/multi_website.rst:268
msgid ""
"By default, published payment acquirers and delivery methods are deployed in"
" all websites. You could already use specific payment acquirers per country "
"using Geo IP by defining countries in their configuration. Now you can also "
"do it per website by filling in the *Website* field."
msgstr ""
"Per standard sendes alle udgivede betalingsindløsere og leveringsmetoder på "
"alle hjemmesider. Du kunne allerede anvende specifikke betalingsindsløsere "
"per land via Geo IP, ved at definere lande i deres konfiguration. Nu kan du "
"også gøre det per hjemmeside ved at udfylde *Hjemmeside* feltet."
#: ../../content/applications/websites/website/publish/multi_website.rst:274
msgid "Customer accounts"
msgstr "Kundekonti"
#: ../../content/applications/websites/website/publish/multi_website.rst:276
msgid ""
"There is a setting to choose how to manage customer accounts in Website "
"settings. You can either allow customers to use one account through all the "
"websites or compel them to create one account for each website. This last "
"option is convenient if your websites shouldnt be related to each other in "
"the visitor mind."
msgstr ""
"I Hjemmeside indstillinger er der en indstilling til at vælge hvorledes "
"kundekonti skal administreres. Du kan enten tillade at kunde bruger én konto"
" på tværs af alle hjemmesider, eller tilskynde dem til at oprette en konto "
"for hver hjemmeside. Denne sidste mulighed er nyttig hvis dine hjemmesider "
"ikke bør være relateret til hinanden ud fra den besøgendes synspunkt."
#: ../../content/applications/websites/website/publish/multi_website.rst:286
msgid "Technical hints for customization"
msgstr "Teknisk råd til tilpasning"
#: ../../content/applications/websites/website/publish/multi_website.rst:288
msgid ""
"If you want to publish custom objects on the website, here are a few tips to"
" make it work with multi websites:"
msgstr ""
"Hvis du vil udgive tilpassede objekter på hjemmesiden, er her et par råd til"
" at få det til at virke med multi-hjemmesider:"
#: ../../content/applications/websites/website/publish/multi_website.rst:292
msgid "Sitemap: dont forget the domain in the route to only publish"
msgstr "Sitemap: glem ikke domænet i ruten hvor der kun skal udgives"
#: ../../content/applications/websites/website/publish/multi_website.rst:292
msgid "available records in each websites sitemap."
msgstr "tilgængelige datasæt i hver hjemmesides sitemap."
#: ../../content/applications/websites/website/publish/multi_website.rst:296
msgid "Access: you should call the method"
msgstr "Adgang: Du bør kalde metoden"
#: ../../content/applications/websites/website/publish/multi_website.rst:295
msgid ""
"*can_access_from_current_website* in the controller to make sure the visitor"
" can see a record in the current website."
msgstr ""
"*can_access_from_current_website* i controlleren for at forsikre at den "
"besøgende kan se et datasæt i den nuværende hjemmeside."
#: ../../content/applications/websites/website/publish/multi_website.rst:300
msgid "Search: when a list of records is displayed, dont forget to specify"
msgstr "Søg: Når en liste af datasæt vises, må du ikke glemme at specificerer"
#: ../../content/applications/websites/website/publish/multi_website.rst:299
msgid "the domain to only display records available for the current website."
msgstr ""
"domænet for kun at vise datasæt tilgængelig for den nuværende hjemmeside."
#: ../../content/applications/websites/website/publish/translate.rst:3
msgid "How to translate my website"
msgstr "Hvordan oversætter du din hjemmeside"
#: ../../content/applications/websites/website/publish/translate.rst:8
msgid ""
"In addition to creating great modern websites, Odoo gives you the "
"possibility to translate it in different languages."
msgstr ""
"Udover at oprette fantastiske moderne hjemmesider, giver Odoo dig også "
"mulighed for at oversætte dem til forskellige sprog."
#: ../../content/applications/websites/website/publish/translate.rst:12
msgid "Process"
msgstr "Behandl"
#: ../../content/applications/websites/website/publish/translate.rst:14
msgid ""
"Once your website is created, you have the opportunity to translate it in as"
" many different languages as you want."
msgstr ""
"Når din hjemmeside er oprettet, har du mulighed for at oversætte den til så "
"mange sprog som du ønsker."
#: ../../content/applications/websites/website/publish/translate.rst:17
msgid ""
"There are two ways to translate your website, you can do it manually or "
"automatically with the Gengo App. If you want to do it automatically, go to "
"the **App** module and Install **Automated translations through Gengo Api** "
"and **Website Gengo Translator**. If you want to do it manually, don't "
"install anything, and follow the next step."
msgstr ""
"Der er to måder hvorpå du kan oversætte din hjemmeside. Du kan gøre det "
"manuelt på egen hånd, eller automatisk med Gengo applikationen. Hvis du vil "
"gøre det automatisk, skal du gå til **App** modulet og installere "
"**Automated translations through Gengo Api** samt **Website Gengo "
"Translator**. Hvis du vil gøre det manuelt, skal du ikke installere noget, "
"og blot følge næste trin."
#: ../../content/applications/websites/website/publish/translate.rst:23
msgid ""
"Now go to your website. On the bottom right corner of the page, click on "
"**Add a language**."
msgstr ""
"Gå derefter til din hjemmeside. Klik på **Tilføj et sprog** nede i højre "
"hjørne af siden."
#: ../../content/applications/websites/website/publish/translate.rst:29
msgid ""
"Choose the language in which you want to translate your website and then "
"click on **Load.**"
msgstr ""
"Vælg det sprog som du vil oversætte din hjemmeside til, og klik på "
"**Indlæs**."
#: ../../content/applications/websites/website/publish/translate.rst:35
msgid ""
"You will see that Now, next to English there is also French, which means "
"that the page for the translation has been created. You can also see that "
"some of the text has been translated automatically."
msgstr ""
"Du vil nu se, at der ved siden af Engelsk også er Fransk, hvilket betyder at"
" siden for oversættelsen er blevet oprettet. Du kan også se at visse af "
"teksterne er blevet oversat automatisk."
#: ../../content/applications/websites/website/publish/translate.rst:42
msgid ""
"To translate the content of the website, click on **Translate** (here "
"**Traduire** since we want to translate the website in French)."
msgstr ""
"For at oversætte indholdet af hjemmesiden, skal du klikke på **Oversæt** "
"(her **Traduire** siden vi vil oversætte hjemmesiden til Fransk)."
#: ../../content/applications/websites/website/publish/translate.rst:45
msgid ""
"There, if you have installed the Gengo Translator, You will see that next to"
" the **Translate** button you also have a button **Translate "
"automatically**. Once you click on that button, you will be asked some "
"information on your account. If you don't have an account yet, go to "
"`*https://gengo.com/auth/form/login/* "
"<https://gengo.com/auth/form/login/>`__ in order to create one. You need to "
"ask for a public key and a private key."
msgstr ""
#: ../../content/applications/websites/website/publish/translate.rst:53
msgid ""
"The content you wish to translate will then be translated automatically."
msgstr "Indholdet du gerne vil oversætte vil blive oversat automatisk."
#: ../../content/applications/websites/website/publish/translate.rst:58
msgid ""
"Now you can see that most of the content is highlighted in yellow or in "
"green. The yellow represents the content that you have to translate by "
"yourself. The green represents the content that has already been translated "
"automatically."
msgstr ""
"Nu kan du se at det meste af indholdet er fremhævet med gult eller grønt. "
"Gult repræsenterer det indhold du skal oversætte selv. Grønt repræsenterer "
"det indhold der allerede er blevet oversat automatisk."