documentation/locale/nl/LC_MESSAGES/website.po
2020-03-22 01:32:42 +01:00

2195 lines
77 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters

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) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Erwin van der Ploeg <erwin@odooexperts.nl>, 2019
# Cas Vissers <casvissers@brahoo.nl>, 2019
# Martin Trigaux, 2019
# Yenthe Van Ginneken <yenthespam@gmail.com>, 2019
# Gunther Clauwaert <gclauwae@hotmail.com>, 2019
# Pol Van Dingenen <pol.vandingenen@vanroey.be>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Pol Van Dingenen <pol.vandingenen@vanroey.be>, 2019\n"
"Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: nl\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../website.rst:5
msgid "Website"
msgstr "Website"
#: ../../website/optimize.rst:3
msgid "Optimize"
msgstr "Optimaliseren"
#: ../../website/optimize/google_analytics.rst:3
msgid "How to track your website's traffic in Google Analytics"
msgstr "Hoe het verkeer op uw website traceren in Google Analytics"
#: ../../website/optimize/google_analytics.rst:5
msgid "To follow your website's traffic with Google Analytics:"
msgstr "Om uw website trafiek te volgen met Google Analytics:"
#: ../../website/optimize/google_analytics.rst:7
msgid ""
"`Create a Google Analytics account <https://www.google.com/analytics/>`__ if"
" you don't have any."
msgstr ""
"Maak een Google Analytics-account aan <https://www.google.com/analytics/> "
"`__ als je nog geen hebt."
#: ../../website/optimize/google_analytics.rst:10
msgid ""
"Go through the creation form and accept the conditions to get the tracking "
"ID."
msgstr ""
"Ga door het aanmaak formulier en accepteer de voorwaarden om de tracking id "
"te krijgen."
#: ../../website/optimize/google_analytics.rst:15
msgid "Copy the tracking ID to insert it in Odoo."
msgstr "Kopieer het tracking-ID om het in Odoo op te slaan"
#: ../../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 ""
"Ga naar het menu *Instellingen* van uw Odoo's website app. In instellingen "
"kopieer-en-plak jouw Google Analytics tracking-ID. Sla daarna op."
#: ../../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 ""
#: ../../website/optimize/google_analytics.rst:32
msgid ":doc:`google_analytics_dashboard`"
msgstr ":doc:`google_analytics_dashboard`"
#: ../../website/optimize/google_analytics_dashboard.rst:3
msgid "How to track your website traffic from your Odoo Dashboard"
msgstr "Hoe uw website trafiek opvolgen vanuit uw Odoo dashboard"
#: ../../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 ""
"U kan uw website trafiek opvolgen vanuit uw Odoo website dashboard dankzij "
"Google Analytics."
#: ../../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 ""
"Een voorafgaande stap is een Google Analytics account aan te maken en de "
"tracking ID in te geven bij je Website's instellingen (zie "
":doc:'google_analytics')."
#: ../../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 ""
"Ga naar `Google APIs platform <https://console.developers.google.com>`__ om "
"analytics API inloggegevens te genereren. Log in met uw Google account."
#: ../../website/optimize/google_analytics_dashboard.rst:14
msgid "Select Analytics API."
msgstr "Selecteer Analytics API."
#: ../../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 ""
"Maak een nieuw project aan en geef het een naam (bijvoorbeeld Odoo). Dit "
"project is nodig om uw API logingegevens te bewaren."
#: ../../website/optimize/google_analytics_dashboard.rst:25
msgid "Enable the API."
msgstr "Schakel de API in."
#: ../../website/optimize/google_analytics_dashboard.rst:30
msgid "Create credentials to use in Odoo."
msgstr "Maak inloggegevens aan om te gebruiken in Odoo."
#: ../../website/optimize/google_analytics_dashboard.rst:35
msgid ""
"Select *Web browser (Javascript)* as calling source and *User data* as kind "
"of data."
msgstr ""
"Selecteer *web browser (Javascript) als bron en *Gebruiker data* als type "
"data."
#: ../../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 ""
"Vervolgens creëer je een Client ID. Vul de naam in van de applicatie (bv. "
"Odoo) en de toegestane pagina's van deze zullen doorgestuurd worden. De "
"*Geautoriseerde JavaScript oorsprong* is jou Odoo's instantie URL. De "
"*Goedgekeurde doorgestuurde URL* is jou Odoo's instatie URL gevolgd door "
"'/google_account/authentication'."
#: ../../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 ""
"Ga naar de Toestemming stap door een product naam in te geven (bv. Google "
"Analytics in Odoo). Voel je vrij om de aanpassingen opties te controleren "
"maar dit is niet verplicht. Het Toestemming scherm zal enkel getoond worden "
"wanneer je de Client ID in Odoo ingeeft voor de eerste keer."
#: ../../website/optimize/google_analytics_dashboard.rst:56
msgid ""
"Finally you are provided with your Client ID. Copy and paste it in Odoo."
msgstr "Uiteindelijk krijgt u uw client ID. Kopieer en plak deze in Odoo."
#: ../../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 ""
"Open uw website dashboard in Odoo en link uw Analytics account door uw "
"cliënt ID in te geven."
#: ../../website/optimize/google_analytics_dashboard.rst:67
msgid "As a last step, authorize Odoo to access Google API."
msgstr ""
"Autoriseer Odoo om toegang te krijgen tot de Google API als laatste stap."
#: ../../website/optimize/seo.rst:3
msgid "How to do Search Engine Optimisation in Odoo (SEO)"
msgstr ""
#: ../../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 ""
"Zoekmachine optimalisatie (SEO) is een set van goede werkwijzes om uw "
"website te optimaliseren zodat deze een betere ranking heeft in zoekmachines"
" zoals Google. Kort samengevat zorgt goede SEO ervoor dat u meer bezoekers "
"krijgt."
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:24
msgid "Meta Tags"
msgstr "Meta Tags"
#: ../../website/optimize/seo.rst:27
msgid "Title, Description"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:39
msgid "Keywords"
msgstr "Sleutelwoorden"
#: ../../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 ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:55
msgid "Content is King"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:60
msgid "**Odoo Blogs**: write great contents."
msgstr "**Odoo Blogs**: schrijf geweldige inhoud."
#: ../../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: `odoo.com/slides"
"/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
msgstr ""
#: ../../website/optimize/seo.rst:66
msgid ""
"**Odoo Forum**: let your community create contents for you. Example: "
"`odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com"
" landing pages)"
msgstr ""
#: ../../website/optimize/seo.rst:70
msgid ""
"**Odoo Mailing List Archive**: publish mailing list archives on your "
"website. Example: `odoo.com/groups/community-59 "
"<https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:81
msgid "Use Social Networks"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:87
msgid "Odoo embeds several tools to share content through social media:"
msgstr ""
#: ../../website/optimize/seo.rst:90
msgid "Social Network"
msgstr "Sociale netwerk"
#: ../../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 ""
#: ../../website/optimize/seo.rst:99
msgid "Social Share"
msgstr "Sociaal delen"
#: ../../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 ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:116
msgid "Facebook Page"
msgstr "Facebook pagina"
#: ../../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 ""
#: ../../website/optimize/seo.rst:123
msgid "Twitter Scroller"
msgstr "Twitter Scroller"
#: ../../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 ""
#: ../../website/optimize/seo.rst:129
msgid "Test Your Website"
msgstr "Test uw website"
#: ../../website/optimize/seo.rst:131
msgid ""
"You can compare how your website rank, in terms of SEO, against Odoo using "
"WooRank free services: `woorank.com <https://www.woorank.com>`_"
msgstr ""
#: ../../website/optimize/seo.rst:136
msgid "URLs Handling"
msgstr ""
#: ../../website/optimize/seo.rst:138
msgid "This section sheds some light on how Odoo makes URLs SEO-friendly."
msgstr ""
#: ../../website/optimize/seo.rst:141
msgid "URLs Structure"
msgstr "URL's structuur"
#: ../../website/optimize/seo.rst:143
msgid "A typical Odoo URL will look like this:"
msgstr "Een typische Odoo URL ziet er als volgt uit:"
#: ../../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"
#: ../../website/optimize/seo.rst:147
msgid "With the following components:"
msgstr "Met de volgende componenten:"
#: ../../website/optimize/seo.rst:149
msgid "**https://** = Protocol"
msgstr "**https://** = Protocol"
#: ../../website/optimize/seo.rst:151
msgid "**www.mysite.com** = your domain name"
msgstr "**www.mysite.com** = uw domeinnaam"
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:169
msgid "**-31** = the unique ID of the product"
msgstr "**-31** = het unieke ID van het product"
#: ../../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 ""
"Merk op dat eender welk dynamisch deel van een URL gereduceerd kan worden "
"naar een ID. Bijvoorbeeld, de volgende URL's doen allemaal een 301 "
"doorverwijzing naar de bovenstaande URL:"
#: ../../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 (korte versie)"
#: ../../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 (nog kortere versie)"
#: ../../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 (oude "
"productnaam)"
#: ../../website/optimize/seo.rst:181
msgid ""
"Some URLs have several dynamic parts, like this one (a blog category and a "
"post):"
msgstr ""
"Sommige URL's hebben verschillende dynamische onderdelen, zoals deze (een "
"blogcategorie en een post):"
#: ../../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"
#: ../../website/optimize/seo.rst:186
msgid "In the above example:"
msgstr "In het bovenstaande voorbeeld:"
#: ../../website/optimize/seo.rst:188
msgid "*Company News* is the title of the blog"
msgstr ""
#: ../../website/optimize/seo.rst:190
msgid "*The Odoo Story* is the title of a specific blog post"
msgstr ""
#: ../../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 ""
"Wanneer een Odoo pagina een pager heeft zal het paginanummer direct in de "
"URL worden gezet (heeft geen GET argument). Dit staat toe dat elke pagina "
"geïndexeerd wordt door zoekmachines. Bijvoorbeeld:"
#: ../../website/optimize/seo.rst:196
msgid "https://www.odoo.com/blog/page/3"
msgstr "https://www.odoo.com/blog/page/3"
#: ../../website/optimize/seo.rst:199
msgid "Changes in URLs & Titles"
msgstr "Wijzigingen in URL's & titels"
#: ../../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 ""
"Wanneer de URL van een pagina wijzigt (bijvoorbeeld een vriendelijkere SEO "
"versie van uw productnaam), hoeft u zich geen zorgen te maken over het "
"updaten van alle links:"
#: ../../website/optimize/seo.rst:204
msgid "Odoo will automatically update all its links to the new URL."
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:209
msgid "As an example, this URL:"
msgstr "Als een voorbeeld, deze URL:"
#: ../../website/optimize/seo.rst:211
msgid "http://mysite.com/shop/product/old-product-name-31"
msgstr "http://mysite.com/shop/product/old-product-name-31"
#: ../../website/optimize/seo.rst:213
msgid "Will automatically redirect to:"
msgstr ""
#: ../../website/optimize/seo.rst:215
msgid "http://mysite.com/shop/product/new-and-better-product-name-31"
msgstr "http://mysite.com/shop/product/new-and-better-product-name-31"
#: ../../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 ""
#: ../../website/optimize/seo.rst:223
msgid "HTTPS"
msgstr "HTTPS"
#: ../../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 ""
#: ../../website/optimize/seo.rst:231
msgid "Links: Nofollow Strategy"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:236
msgid "Here are Odoo strategies to manage links:"
msgstr ""
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
"Maar elke link geplaatst door een bijdrager die linkt naar een externe "
"website is \"nofollow'. Op deze manier loopt u niet het risico dat mensen "
"links plaatsen op uw website die linken naar externe websites die een "
"slechte reputatie hebben."
#: ../../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 ""
#: ../../website/optimize/seo.rst:255
msgid "Multi-Language Support"
msgstr ""
#: ../../website/optimize/seo.rst:258
msgid "Multi-Language URLs"
msgstr ""
#: ../../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 ""
"Indien u een website in meerdere talen heeft zal dezelfde inhoud beschikbaar"
" zijn in verschillende URL's, afhankelijk van de gebruikte taal:"
#: ../../website/optimize/seo.rst:263
msgid ""
"https://www.mywebsite.com/shop/product/my-product-1 (main language, English "
"here)"
msgstr ""
#: ../../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 (Franse "
"versie)"
#: ../../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 ""
"In dit voorbeeld is de taal van de pagina fr\\_FR. U kan zelfs verschillende"
" variaties van dezelfde taal hebben: pt\\_BR (Portugees van Brazilië), "
"pt\\_PT (Portugees van Portugal). "
#: ../../website/optimize/seo.rst:272
msgid "Language Annotation"
msgstr ""
#: ../../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 ""
#: ../../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\"/>"
#: ../../website/optimize/seo.rst:282
msgid "With this approach:"
msgstr "Met deze aanpak:"
#: ../../website/optimize/seo.rst:284
msgid ""
"Search engines will redirect to th right language according to the visitor "
"language."
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:292
msgid "Language Detection"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:299
msgid ""
"Next time, it keeps a cookie of the current language to avoid any "
"redirection."
msgstr ""
#: ../../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 ""
"Om een bezoeker te forceren om de standaard taal te gebruiken kan u de code "
"gebruiken van de standaard taal in uw link, bijvoorbeeld: "
"uwwebsite.com/en\\_US/shop. Dit zal bezoekers altijd doen landen op de "
"Engelse versie van de pagina, zonder de browser voorkeuren te gebruiken."
#: ../../website/optimize/seo.rst:309
msgid "Page Speed"
msgstr ""
#: ../../website/optimize/seo.rst:312
msgid "Introduction"
msgstr "Introductie"
#: ../../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 ""
#: ../../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 ""
"Gelukkig doet Odoo alle magie voor u. Hieronder vind u trucks die Odoo "
"gebruikt om de laadsnelheid te verhogen. U kan vergelijken hoe uw website "
"presteert met deze twee tools:"
#: ../../website/optimize/seo.rst:329
msgid ""
"`Google Page Speed "
"<https://developers.google.com/speed/pagespeed/insights/>`__"
msgstr ""
"`Google pagina snelheid "
"<https://developers.google.com/speed/pagespeed/insights/>`__"
#: ../../website/optimize/seo.rst:331
msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__"
msgstr "`Pingdom Website snelheidstest <http://tools.pingdom.com/fpt/>`__"
#: ../../website/optimize/seo.rst:334
msgid "Images"
msgstr "Afbeeldingen"
#: ../../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 ""
#: ../../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 ""
"Vanuit de upload knop heeft u de optie om het originele bestanden "
"ongewijzigd te houden indien u de kwaliteit van de afbeelding wilt "
"optimaliseren in plaats van de performantie."
#: ../../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 comprimeert afbeeldingen wanneer ze geüpload worden naar uw website, "
"niet wanneer ze opgevraagd worden door de bezoeker. Dus is het mogelijk dat,"
" indien u een derde partij thema gebruikt, het afbeeldingen aanbiedt die "
"niet efficiënt gecomprimeerd zijn. Maar alle afbeeldingen gebruikt in de "
"officiële Odoo thema's zijn standaard gecomprimeerd."
#: ../../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 ""
"Wanneer u klikt op een afbeelding toont Odoo u de Alt en titel attributen "
"van de ``<img>`` tag. U kan hierop klikken om uw eigen titel en Alt "
"attributen in te stellen voor de afbeelding."
#: ../../website/optimize/seo.rst:361
msgid "When you click on this link, the following window will appear:"
msgstr "Wanneer u klikt op deze link, zal het volgende venster verschijnen:"
#: ../../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 ""
"Odoo's pictogrammen zijn geïmplementeerd met het gebruikt van een font "
"(`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in de"
" meeste Odoo thema's). Dus kan u zoveel pictogrammen gebruiker als u wilt in"
" uw pagina, ze hebben geen extra aanvragen nodig om de pagina te laden."
#: ../../website/optimize/seo.rst:375
msgid "Static Resources: CSS"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:380
msgid "only one CSS file request is needed to load a page"
msgstr "slechts één CSS bestandsverzoek is nodig om een pagina te laden"
#: ../../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 ""
"dit CSS bestand is gedeeld en gecached over verschillende pagina's, zodat "
"wanneer bezoekers klikken op een andere pagina, de browser geen enkel CSS "
"bestand moet inladen."
#: ../../website/optimize/seo.rst:386
msgid "this CSS file is optimized to be small"
msgstr "dit CSS bestand is geoptimaliseerd om klein te zijn"
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
"Om dit probleem aan te pakken worden alle CSS / Less / Sass bestanden "
"geconcateneerd in één .CSS bestand dat naar de browser wordt gestuurd. Zodat"
" een bezoeker **slechts één .CSS bestand moet laden** per pagina, wat vooral"
" efficiënt is. Als de CSS gedeeld wordt over alle pagina's hoeft de browser "
"geen nieuw CSS bestand te laden wanneer een andere pagina wordt open gedaan!"
#: ../../website/optimize/seo.rst:412
msgid "**Both files in the <head>**"
msgstr "**Beide bestanden in het <head>**"
#: ../../website/optimize/seo.rst:412
msgid "**What the visitor gets (only one file)**"
msgstr "**Wat de bezoekers krijgen (slechts één bestand)**"
#: ../../website/optimize/seo.rst:414
msgid "/\\* From bootstrap.css \\*/"
msgstr "/\\* Van bootstrap.css \\*/"
#: ../../website/optimize/seo.rst:414 ../../website/optimize/seo.rst:415
#: ../../website/optimize/seo.rst:421 ../../website/optimize/seo.rst:447
msgid ".text-muted {"
msgstr ".text-muted {"
#: ../../website/optimize/seo.rst:415 ../../website/optimize/seo.rst:422
#: ../../website/optimize/seo.rst:448
msgid "color: #666;"
msgstr "color: #666;"
#: ../../website/optimize/seo.rst:416
msgid "color: #777;"
msgstr "color: #777;"
#: ../../website/optimize/seo.rst:416
msgid "background: yellow"
msgstr "background: yellow"
#: ../../website/optimize/seo.rst:417
msgid "background: yellow;"
msgstr "background: yellow;"
#: ../../website/optimize/seo.rst:417 ../../website/optimize/seo.rst:418
#: ../../website/optimize/seo.rst:423 ../../website/optimize/seo.rst:449
msgid "}"
msgstr "}"
#: ../../website/optimize/seo.rst:420
msgid "/\\* From my-theme.css \\*/"
msgstr "/\\* Van my-theme.css \\*/"
#: ../../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 ""
"De CSS verzonden door Odoo bevat alle CSS / Less / Sass bestanden van alle "
"pagina's / modules. Door dit te doen moeten andere pagina weergaven van "
"dezelfde weergave geen nieuw CSS bestand inladen. Maar sommige modules "
"kunnen grote CSS/JavaScript bronnen bevatten die u niet op voorhand wilt "
"ophalen op de eerste pagina omdat ze te groot zijn. In dit geval splitst "
"Odoo de bronnen in een tweede bundel die geladen wordt wanneer de pagina die"
" het gebruikt het aanvraagt. Een voorbeeld hiervan is de back-end die enkel "
"ingeladen wordt wanneer de bezoekers aanmelden en de back-end opendoen "
"(/web)."
#: ../../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 ""
#: ../../website/optimize/seo.rst:440
msgid ""
"**Minified:** After being pre-processed and concatenated, the resulting CSS "
"is minified to reduce its size."
msgstr ""
"**Minified:** Na het pre-processen en concateneren zal de resulterende CSS "
"geminificeerd worden om de grootte te verkleinen."
#: ../../website/optimize/seo.rst:444
msgid "**Before minification**"
msgstr "**Voor minificatie**"
#: ../../website/optimize/seo.rst:444
msgid "**After minification**"
msgstr "**Na minificatie**"
#: ../../website/optimize/seo.rst:446
msgid "/\\* some comments \\*/"
msgstr "/\\* sommige commentaren \\*/"
#: ../../website/optimize/seo.rst:446
msgid ".text-muted {color: #666}"
msgstr ".text-muted {color: #666}"
#: ../../website/optimize/seo.rst:452
msgid ""
"The final result is then compressed, before being delivered to the browser."
msgstr ""
"Het uiteindelijke resultaat is dan gecomprimeerd, voordat het aan de browser"
" wordt aangeleverd."
#: ../../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 ""
#: ../../website/optimize/seo.rst:461
msgid "Static Resources: Javascript"
msgstr ""
#: ../../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 ""
#: ../../website/optimize/seo.rst:466
msgid "Odoo creates three Javascript bundles:"
msgstr "Odoo maakt drie JavaScript bundels aan:"
#: ../../website/optimize/seo.rst:468
msgid ""
"One for all pages of the website (including code for parallax effects, form "
"validation, etc.)"
msgstr ""
#: ../../website/optimize/seo.rst:471
msgid ""
"One for common Javascript code shared among frontend and backend (Bootstrap)"
msgstr ""
#: ../../website/optimize/seo.rst:474
msgid ""
"One for backend specific Javascript code (Odoo Web Client interface for your"
" employees using Odoo)"
msgstr ""
"Een voor back-end specifieke JavaScript code (Odoo Web Client interface voor"
" uw werknemers die Odoo gebruiken)"
#: ../../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 ""
#: ../../website/optimize/seo.rst:483
msgid ""
"If you work on :doc:`Developer mode "
"<../../general/developer_mode/activate>`, 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 ""
#: ../../website/optimize/seo.rst:489
msgid "CDN"
msgstr "CDN"
#: ../../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 ""
"Indien u de CDN optie activeert in Odoo worden statische bronnen "
"(JavaScript, CSS, afbeeldingen) geladen van het Content Delivery Netwerk. "
"Een Content Delivery Netwerk heeft drie voordelen:"
#: ../../website/optimize/seo.rst:495
msgid ""
"Load resources from a nearby server (most CDN have servers in main countries"
" around the globe)"
msgstr ""
"Laad bronnen van een dichtbij zijnde server (meeste CDN's hebben servers in "
"de belangrijkste landen over de wereld)"
#: ../../website/optimize/seo.rst:498
msgid ""
"Cache resources efficiently (no computation resources usage on your own "
"server)"
msgstr ""
"Cache bronnen efficiënt (er worden geen resources gebruikt op uw eigen "
"server voor de berekening)"
#: ../../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 ""
"Verdeel de bronnen die geladen worden over verschillende diensten zodat u "
"meerdere bronnen parallel kan laden (Sinds de Chrome limiet van 6 parallelle"
" aanvragen op domeinniveau is)"
#: ../../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 ""
"U kan uw CDN opties configureren vanuit de **Website Admin** app, met behulp"
" van het configuratie menu. Hier is een voorbeeld van een configuratie die u"
" kan gebruiken:"
#: ../../website/optimize/seo.rst:512
msgid "HTML Pages"
msgstr "HTML pagina's"
#: ../../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 ""
"De HTML pagina's kunnen gecomprimeerd worden, maar dit wordt meestal "
"afgehandeld door uw webserver (NGINX of Apache)."
#: ../../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 ""
#: ../../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 ""
"Als een voorbeeld, als u de kleurenprikker gebruikt om de kleur van een "
"paragraaf te wijzigen naar de primaire kleur van uw website, zal Odoo de "
"volgende code genereren:"
#: ../../website/optimize/seo.rst:525
msgid "``<p class=\"text-primary\">My Text</p>``"
msgstr "``<p class=\"text-primary\">Mijn tekst</p>``"
#: ../../website/optimize/seo.rst:527
msgid ""
"Whereas most HTML editors (such as CKEditor) will produce the following "
"code:"
msgstr ""
"Waar de meeste HTML editors (zoals een CKEditor) de volgende code "
"produceert:"
#: ../../website/optimize/seo.rst:530
msgid "``<p style=\"color: #AB0201\">My Text</p>``"
msgstr "``<p style=\"color: #AB0201\">Mijn tekst</p>``"
#: ../../website/optimize/seo.rst:533
msgid "Responsive Design"
msgstr "Responsief design"
#: ../../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 ""
#: ../../website/optimize/seo.rst:542
msgid ""
"As all Odoo modules share the same technology, absolutely all pages in your "
"website are mobile friendly."
msgstr ""
#: ../../website/optimize/seo.rst:546
msgid "Browser Caching"
msgstr ""
#: ../../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: `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 ""
#: ../../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 ""
"Dit laat Odoo toe om een heel lange cache vertraging in te stellen (XXX) op "
"deze bronnen: XXX seconden, terwijl deze direct wordt geüpdatet als u de "
"bron update."
#: ../../website/optimize/seo.rst:560
msgid "Scalability"
msgstr "Schaalbaarheid"
#: ../../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 ""
#: ../../website/optimize/seo.rst:571
msgid ""
"Here is the slide that summarizes the scalability of Odoo Website & "
"eCommerce."
msgstr ""
#: ../../website/optimize/seo.rst:577
msgid "Search Engines Files"
msgstr ""
#: ../../website/optimize/seo.rst:580
msgid "Sitemap"
msgstr "Sitemap"
#: ../../website/optimize/seo.rst:582
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 ""
#: ../../website/optimize/seo.rst:586
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 ""
"Standaard zijn alle URL's één ``/sitemap.xml`` bestand, maar als u veel "
"pagina's heeft zal Odoo automatisch een Sitemap index bestand aanmaakt dat "
"het `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ "
"protocol respecteert om sitemap URL's te groeperen in 45000 stukken per "
"bestand."
#: ../../website/optimize/seo.rst:592
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr "Elke sitemap heeft 4 attributen die automatisch berekend worden:"
#: ../../website/optimize/seo.rst:594
msgid "``<loc>`` : the URL of a page"
msgstr "``<loc>`` : de URL van een pagina"
#: ../../website/optimize/seo.rst:596
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 ""
#: ../../website/optimize/seo.rst:601
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 ""
#: ../../website/optimize/seo.rst:608
msgid "Structured Data Markup"
msgstr "Gestructureerde Gegevens Markup"
#: ../../website/optimize/seo.rst:610
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 ""
#: ../../website/optimize/seo.rst:615
msgid ""
"Google supports a number of rich snippets for content types, including: "
"Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""
"Google ondersteunt een aantal rijke snippets voor inhoudstypes, inclusief: "
"Beoordelingen, Mensen, Producten, Zaken, Evenementen en Organisaties."
#: ../../website/optimize/seo.rst:618
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 implementeert micro data zoals gedefinieerd in de `schema.org "
"<http://schema.org>`__ specificaties voor gebeurtenissen, e-commerce "
"producten, forum berichten en contactadressen. Dit staat uw productpagina's "
"toe om getoond te worden in Google en om extra informatie te gebruiken zoals"
" de prijs en beoordeling van een product:"
#: ../../website/optimize/seo.rst:628
msgid "robots.txt"
msgstr "robots.txt"
#: ../../website/optimize/seo.rst:630
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 ""
#: ../../website/optimize/seo.rst:634
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr ""
#: ../../website/optimize/seo.rst:637
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 ""
#: ../../website/optimize/seo.rst:641
msgid ""
"You can customize the file *robots* in :doc:`Developer mode "
"<../../general/developer_mode/activate>` 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 ""
#: ../../website/publish.rst:3
msgid "Publish"
msgstr "Publiceer"
#: ../../website/publish/domain_name.rst:3
msgid "How to use my own domain name"
msgstr "Hoe mijn eigen domeinnaam gebruiken"
#: ../../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 ""
"Standaard heeft uw Odoo online instantie en website een *.odoo.com* "
"domeinnaam, voor beide de URL en de e-mails. U kan dit wijzigen naar een "
"eigen domein (bijvoorbeeld www.uwbedrijf.com)."
#: ../../website/publish/domain_name.rst:10
msgid "What is a good domain name"
msgstr "Wat is een goede domeinnaam"
#: ../../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 ""
"Uw websiteadres is net zo belangrijk voor uw branding als de naam van uw "
"bedrijf of organisatie, dus doet u er goed aan om deze mogelijks te wijzigen"
" naar een meer gepaste domeinnaam. Hier zijn een paar tips:"
#: ../../website/publish/domain_name.rst:15
msgid "Simple and obvious"
msgstr "Simpel en duidelijk"
#: ../../website/publish/domain_name.rst:16
msgid "Easy to remember and spell"
msgstr "Gemakkelijk te onthouden en spellen"
#: ../../website/publish/domain_name.rst:17
msgid "The shorter the better"
msgstr "Hoe korter hoe beter"
#: ../../website/publish/domain_name.rst:18
msgid "Avoid special characters"
msgstr "Vermijd speciale karakters"
#: ../../website/publish/domain_name.rst:19
msgid "Aim for a .com and/or your country extension"
msgstr "Mik op een .com en/of andere land extensie"
#: ../../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 ""
"Lees meer: `Hoe een domeinnaam te kiezen voor optimale SEO "
"<https://www.searchenginejournal.com/choose-a-domain-name-maximum-"
"seo/158951/>`__"
#: ../../website/publish/domain_name.rst:24
msgid "How to buy a domain name"
msgstr "Hoe een domeinnaam kopen"
#: ../../website/publish/domain_name.rst:25
msgid "Buy your domain name at a popular registrar:"
msgstr "Koop uw domein bij een populaire registrator:"
#: ../../website/publish/domain_name.rst:27
msgid "`GoDaddy <https://www.godaddy.com>`__"
msgstr "`GoDaddy <https://www.godaddy.com>`__"
#: ../../website/publish/domain_name.rst:28
msgid "`Namecheap <https://www.namecheap.com>`__"
msgstr "`Namecheap <https://www.namecheap.com>`__"
#: ../../website/publish/domain_name.rst:29
msgid "`OVH <https://www.ovh.com>`__"
msgstr "`OVH <https://www.ovh.com>`__"
#: ../../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 ""
"Stappen om een domeinnaam te kopen zijn vrijwel ongecompliceerd. Bekijk deze"
" eenvoudige tutorials:"
#: ../../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>`__"
#: ../../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//>`__"
#: ../../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 ""
"Aarzel niet om een e-mailserver te kopen om e-mailadressen te hebben die uw "
"domeinnaam gebruiken. Koop echter geen extra service om uw website te maken "
"of te hosten. Dit is de taak van Odoo!"
#: ../../website/publish/domain_name.rst:45
msgid "How to apply my domain name to my Odoo instance"
msgstr "Hoe mijn domeinnaam koppelen aan mijn Odoo instantie"
#: ../../website/publish/domain_name.rst:46
msgid ""
"First let's authorize the redirection (yourcompany.com -> "
"yourcompany.odoo.com):"
msgstr ""
"Laten we eerste de doorverwijzing authoriseren (uwbedrijf.com -> "
"uwbedrijf.odoo.com):"
#: ../../website/publish/domain_name.rst:48
msgid "Open your Odoo.com account from your homepage."
msgstr "Open uw Odoo.com account vanuit uw homepage."
#: ../../website/publish/domain_name.rst:53
msgid "Go to the *Manage Databases* page."
msgstr "Ga naar de *Beheer databases** pagina."
#: ../../website/publish/domain_name.rst:58
msgid ""
"Click on *Domains* to the right of the database you would like to redirect."
msgstr "Klik op *Domeinen* rechts van de database die u wilt doorverwijzen."
#: ../../website/publish/domain_name.rst:63
msgid ""
"A database domain prompt will appear. Enter your custom domain (e.g. "
"www.yourcompany.com)."
msgstr ""
"Een database domein dialoog verschijnt. Geef uw persoonlijk domein in "
"(bijvoorbeeld www.uwbedrijf.com)."
#: ../../website/publish/domain_name.rst:70
msgid ""
"We can now apply the redirection from your domain name's manager account:"
msgstr ""
"We kunnen nu de doorverwijzing toepassen vanuit uw domeinnaam zijn "
"beheerders account:"
#: ../../website/publish/domain_name.rst:72
msgid "Log in to your account and search for the DNS Zones management page."
msgstr "Log in op uw account en zoek voor de DNS zones beheer pagina."
#: ../../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 ""
"Maak een CNAME record *www.uwdomein.com* wijzend naar *mywebsite.odoo.com*. "
"Als u een domeinnaam zonder www-voorvoegsel wil inschakelen (bijvoorbeeld "
"uwdomein.com), moet u *uwdomein.com* doorverwijzen naar *www.uwdomein.com*."
#: ../../website/publish/domain_name.rst:78
msgid "Here are some specific guidelines to create a CNAME record:"
msgstr ""
"Hier zijn een paar specifieke richtlijnen om een CNAME record aan te maken:"
#: ../../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>`__"
#: ../../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>`__"
#: ../../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>`__"
#: ../../website/publish/domain_name.rst:85
msgid "How to enable SSL (HTTPS) for my Odoo instance"
msgstr "Hoe SSL inschakelen (HTTPS) voor mijn Odoo instantie"
#: ../../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 ""
#: ../../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 ""
#: ../../website/publish/domain_name.rst:93
msgid "**Please note that the certificate generation may take up to 24h.**"
msgstr ""
#: ../../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 ""
#: ../../website/publish/domain_name.rst:99
msgid "How to make sure that all my URLs use my custom domain?"
msgstr ""
#: ../../website/publish/domain_name.rst:101
msgid ""
"To set up the root URL of your website and of all the links sent in emails, "
"you can ask an administrator of your database (any user in the *Settings* "
"group) to perform a login from the login screen. It's as simple as that!"
msgstr ""
#: ../../website/publish/domain_name.rst:103
msgid ""
"If you want to do it manually, you can go to :menuselection:`Settings --> "
"Technical --> System Parameters` . Find the entry called ``web.base.url`` "
"(you can create it if it does not exist) and enter the full URL of your "
"website, like ``https://www.myodoowebsite.com``."
msgstr ""
#: ../../website/publish/domain_name.rst:107
msgid ""
"The URL must include the protocol (``https://`` or ``http://``) and must not"
" end by a slash (``/``)."
msgstr ""
#: ../../website/publish/domain_name.rst:109
msgid ""
"If you want to block the root URL update when an administrator logs in, you "
"can add a System Parameter called ``web.base.url.freeze`` with its value "
"set to ``True``."
msgstr ""
#: ../../website/publish/domain_name.rst:113
msgid "My website is indexed twice by Google"
msgstr ""
#: ../../website/publish/domain_name.rst:115
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 ""
#: ../../website/publish/domain_name.rst:120
msgid ":doc:`../../discuss/email_servers`"
msgstr ":doc:`../../discuss/email_servers`"
#: ../../website/publish/multi_website.rst:3
msgid "Manage Multi Websites"
msgstr ""
#: ../../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 ""
#: ../../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 ""
#: ../../website/publish/multi_website.rst:18
msgid "Setup"
msgstr "Instellingen"
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../website/publish/multi_website.rst:48
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. See "
":doc:`domain_name`."
msgstr ""
#: ../../website/publish/multi_website.rst:52
msgid "Create the menu"
msgstr ""
#: ../../website/publish/multi_website.rst:54
msgid ""
"The new website has a default menu with all the installed applications. To "
"edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only"
" edit the menu of the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:59
msgid "Switch from one website to another"
msgstr ""
#: ../../website/publish/multi_website.rst:62
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 ""
#: ../../website/publish/multi_website.rst:71
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 prompted to create a new page from there."
msgstr ""
#: ../../website/publish/multi_website.rst:76
msgid "Add features"
msgstr "Opties toevoegen"
#: ../../website/publish/multi_website.rst:78
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 ""
#: ../../website/publish/multi_website.rst:82
msgid ""
"Each website comes with a high range of specific options in the settings. "
"First, select the website to configure."
msgstr ""
#: ../../website/publish/multi_website.rst:88
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 ""
#: ../../website/publish/multi_website.rst:94
msgid "You can, for instance, set specific :"
msgstr ""
#: ../../website/publish/multi_website.rst:96
msgid "languages,"
msgstr ""
#: ../../website/publish/multi_website.rst:98
msgid "domain names,"
msgstr ""
#: ../../website/publish/multi_website.rst:100
msgid "social media links,"
msgstr ""
#: ../../website/publish/multi_website.rst:102
msgid "customer portal mode (B2C vs. B2B),"
msgstr ""
#: ../../website/publish/multi_website.rst:104
msgid "dedicated live chat channels,"
msgstr ""
#: ../../website/publish/multi_website.rst:106
msgid "etc."
msgstr "etc."
#: ../../website/publish/multi_website.rst:108
msgid "The other options are global and apply to all your websites."
msgstr ""
#: ../../website/publish/multi_website.rst:111
msgid "Manage domain names"
msgstr ""
#: ../../website/publish/multi_website.rst:113
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 GeoIP."
msgstr ""
#: ../../website/publish/multi_website.rst:122
msgid ""
"Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, "
"dont forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-"
"installation`"
msgstr ""
#: ../../website/publish/multi_website.rst:127
msgid ":doc:`domain_name`"
msgstr ""
#: ../../website/publish/multi_website.rst:130
msgid "Customize the visitor experience"
msgstr ""
#: ../../website/publish/multi_website.rst:133
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 ""
#: ../../website/publish/multi_website.rst:143
msgid "Publish specific content per website"
msgstr ""
#: ../../website/publish/multi_website.rst:146
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 ""
#: ../../website/publish/multi_website.rst:154
msgid ""
"Here are all the objects that you can link to *either one or all the "
"websites*:"
msgstr ""
#: ../../website/publish/multi_website.rst:157
msgid "Products"
msgstr "Producten"
#: ../../website/publish/multi_website.rst:159
msgid "Product Categories for eCommerce"
msgstr ""
#: ../../website/publish/multi_website.rst:161
msgid "Blogs"
msgstr "Blogs"
#: ../../website/publish/multi_website.rst:163
msgid "Slide Channels"
msgstr ""
#: ../../website/publish/multi_website.rst:165
msgid "Forums"
msgstr "Forums"
#: ../../website/publish/multi_website.rst:167
msgid "Events"
msgstr "Evenementen"
#: ../../website/publish/multi_website.rst:169
msgid "Job Positions"
msgstr "Functies"
#: ../../website/publish/multi_website.rst:172
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 ""
#: ../../website/publish/multi_website.rst:176
msgid "Publish a page in all websites"
msgstr ""
#: ../../website/publish/multi_website.rst:178
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 ""
#: ../../website/publish/multi_website.rst:182
msgid ""
"If you want to duplicate it in just one other website, duplicate the page "
"and set the new website."
msgstr ""
#: ../../website/publish/multi_website.rst:188
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 ""
#: ../../website/publish/multi_website.rst:193
msgid ""
"By grouping pages by URL in the page manager, you quickly find the original "
"page behind each edited page."
msgstr ""
#: ../../website/publish/multi_website.rst:200
msgid "Multi-companies"
msgstr "Multi-bedrijven"
#: ../../website/publish/multi_website.rst:202
msgid ""
"Each website can be linked to a specific company of your system, in a multi-"
"companies environment."
msgstr ""
#: ../../website/publish/multi_website.rst:208
msgid ""
"With such a configuration, only company-related data appear on the website "
"(products, jobs, events, etc.)."
msgstr ""
#: ../../website/publish/multi_website.rst:211
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 ""
#: ../../website/publish/multi_website.rst:217
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 ""
#: ../../website/publish/multi_website.rst:223
msgid "Configure your eCommerce website"
msgstr ""
#: ../../website/publish/multi_website.rst:225
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 ""
#: ../../website/publish/multi_website.rst:230
msgid "Products only available on one website"
msgstr ""
#: ../../website/publish/multi_website.rst:232
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 ""
#: ../../website/publish/multi_website.rst:240
msgid "Products available on *some* websites"
msgstr ""
#: ../../website/publish/multi_website.rst:242
msgid ""
"To make a product available on some websites, but not all of them, you "
"should duplicate the product for each website."
msgstr ""
#: ../../website/publish/multi_website.rst:245
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 ""
#: ../../website/publish/multi_website.rst:252
msgid "Pricelists"
msgstr "Prijslijsten"
#: ../../website/publish/multi_website.rst:254
msgid ""
"To manage specific prices by websites, you can activate *Multiple Sales "
"Prices per Product* in Website settings."
msgstr ""
#: ../../website/publish/multi_website.rst:257
msgid ""
"Then, go to :menuselection:`Website --> Products --> Pricelists` to create "
"additional pricelists. See "
":doc:`../../ecommerce/maximizing_revenue/pricing`."
msgstr ""
#: ../../website/publish/multi_website.rst:260
msgid ""
"If you need help. Select a website to make a pricelist only available on "
"this website."
msgstr ""
#: ../../website/publish/multi_website.rst:266
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 ""
#: ../../website/publish/multi_website.rst:271
msgid "Payment Acquirers and Delivery Methods"
msgstr ""
#: ../../website/publish/multi_website.rst:273
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 ""
#: ../../website/publish/multi_website.rst:279
msgid "Customer accounts"
msgstr ""
#: ../../website/publish/multi_website.rst:281
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 ""
#: ../../website/publish/multi_website.rst:291
msgid "Technical hints for customization"
msgstr ""
#: ../../website/publish/multi_website.rst:293
msgid ""
"If you want to publish custom objects on the website, here are a few tips to"
" make it work with multi websites:"
msgstr ""
#: ../../website/publish/multi_website.rst:297
msgid "Sitemap: dont forget the domain in the route to only publish"
msgstr ""
#: ../../website/publish/multi_website.rst:297
msgid "available records in each websites sitemap."
msgstr ""
#: ../../website/publish/multi_website.rst:301
msgid "Access: you should call the method"
msgstr ""
#: ../../website/publish/multi_website.rst:300
msgid ""
"*can_access_from_current_website* in the controller to make sure the visitor"
" can see a record in the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:305
msgid "Search: when a list of records is displayed, dont forget to specify"
msgstr ""
#: ../../website/publish/multi_website.rst:304
msgid "the domain to only display records available for the current website."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:3
msgid "Geo IP installation (on-premises database)"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:6
msgid "Installation"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:8
msgid ""
"Please note that the installation depends on your computer operating system "
"and distribution. We will assume here that a Linux operating system is used."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:13
msgid "Install `geoip2 <https://pypi.org/project/geoip2/>`__ Python library"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:15
msgid ""
"Download the `GeoLite2 City database "
"<https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with a"
" file called ``GeoLite2-City.mmdb``"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:19
msgid "Move the file to the folder ``/usr/share/GeoIP/``"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:21
msgid "Restart the server"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:23
msgid ""
"If you can't/don't want to locate the geoip database in "
"``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo "
"command line interface. This option takes the absolute path to the GeoIP "
"database file and will use it as the GeoIP database. For example:"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:32
msgid ""
"`CLI documentation "
"<https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:34
msgid ""
"``GeoIP`` Python library can also be used. However this version is "
"discontinued since January 2019. See `GeoLite Legacy databases are now "
"discontinued <https://support.maxmind.com/geolite-legacy-discontinuation-"
"notice/>`_"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:37
msgid "How to test GeoIP geolocation in your Odoo website?"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:38
msgid ""
"Go into your website. Open the web page on which you want to test ``GeoIP``."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:39
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:40
msgid "Add the following piece of XML in the page :"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:46
msgid ""
"You should end up with a dictionary indicating the location of the ip "
"address."
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:51
msgid ""
"If the curly braces are empty ``{}``, it can be for any of the following "
"reason :"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:53
msgid ""
"The browsing IP address is the localhost (``127.0.0.1``) or a local area "
"network one (``192.168.*.*``)"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:54
msgid ""
"If a reversed proxy is used, make sure to configure it correctly. See "
"`--proxy-mode "
"<https://www.odoo.com/documentation/13.0/reference/cmdline.html#cmdoption-"
"odoo-bin-proxy-mode>`__"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:55
msgid "``geoip2`` is not installed or the GeoIP database file wasn't found"
msgstr ""
#: ../../website/publish/on-premise_geo-ip-installation.rst:56
msgid "The GeoIP database was unable to resolve the given IP address"
msgstr ""
#: ../../website/publish/translate.rst:3
msgid "How to translate my website"
msgstr "Hoe mijn website vertalen"
#: ../../website/publish/translate.rst:6
msgid "Overview"
msgstr "Overzicht"
#: ../../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 ""
"In aanvulling op het aanmaken van geweldige moderne websites geeft Odoo de "
"mogelijkheid om de website in meerdere talen te vertalen."
#: ../../website/publish/translate.rst:12
msgid "Process"
msgstr "Verwerken"
#: ../../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 ""
"Eenmaal uw website is aangemaakt heeft u de mogelijkheid om ze te vertalen "
"in zoveel talen als u wenst."
#: ../../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 ""
"Er zijn twee manieren om uw website te vertalen, u kan het manueel doen of "
"automatisch met de Gengo App. Indien u het automatisch wilt doen gaat u naar"
" de **App** module en installeert u **Automatische vertalingen via de Gengo "
"API** en **Website Gengo Vertaler**. Indien u dit manueel wilt doen "
"installeert u niets en volgt u de volgende stap."
#: ../../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 ""
"Ga nu naar uw website. In de rechter onderhoek van de pagina klikt u op "
"**Een taal toevoegen**."
#: ../../website/publish/translate.rst:29
msgid ""
"Choose the language in which you want to translate your website and then "
"click on **Load.**"
msgstr ""
"Kies de taal waarin u uw website wilt vertalen en klik vervolgens op "
"**Laden**."
#: ../../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 ""
"U zal zien dat er nu naast Engels ook Frans is, wat betekend dat de pagina "
"voor de vertaling is aangemaakt. U kan ook zien dat sommige delen van de "
"tekst automatisch vertaald zijn."
#: ../../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 ""
"Om de inhoud van uw website te vertalen klikt u op **Vertalen** (hier "
"**Traduire** aangezien we de website in het Frans willen vertalen)."
#: ../../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, follow `this "
"link <https://gengo.com/auth/form/login/>`_ in order to create one. You need"
" to ask for a public key and a private key."
msgstr ""
#: ../../website/publish/translate.rst:53
msgid ""
"The content you wish to translate will then be translated automatically."
msgstr "De inhoud die u wilt vertalen wordt vervolgens automatisch vertaald."
#: ../../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 u zien dat de meeste inhoud geel of groen is gearceerd. Het geel "
"staat voor de inhoud die u zelf moet vertalen. Het groen staat voor de "
"inhoud die al automatisch vertaald is."