tandem
/
camper
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
camper/po/fr.po

2977 lines
87 KiB
Plaintext
Raw Normal View History

Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
# French translations for camper package
# Traductions françaises du paquet camper.
# Copyright (C) 2023 THE camper'S COPYRIGHT HOLDER
# This file is distributed under the same license as the camper package.
# jordi fita mas <jordi@tandem.blog>, 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: camper\n"
"Report-Msgid-Bugs-To: jordi@tandem.blog\n"
Translate footer links
2024-02-26 18:13:17 +00:00
"POT-Creation-Date: 2024-02-26 19:11+0100\n"
Change “Discover the environment” to “Discover”
2024-02-06 09:55:29 +00:00
"PO-Revision-Date: 2024-02-06 10:05+0100\n"
Add French translations
2023-12-20 12:01:52 +00:00
"Last-Translator: Oriol Carbonell <info@oriolcarbonell.cat>\n"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
"Language-Team: French <traduc@traduc.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
Change “Discover the environment” to “Discover”
2024-02-06 09:55:29 +00:00
"X-Generator: Poedit 3.4.2\n"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add a controlled layer group for the zones on the map It seems that we have to highlight the map zones too. On the previous website, they had a mouseover effect that displayed a tooltip, but here we can not do that because we use the mouse to select accommodations. This is just a test to see whether Oriol likes how it is shown, thus the red is likely to change to something else more pleasant to look at.
2024-01-31 14:12:11 +00:00
#: web/templates/campground_map.svg:1598
msgctxt "title"
msgid "Zones"
msgstr "Zones"
#: web/templates/campground_map.svg:1599
msgctxt "tooltip"
msgid "Zone 7"
msgstr "Zone 7"
#: web/templates/campground_map.svg:1600
msgctxt "tooltip"
msgid "Zone 6"
msgstr "Zone 6"
#: web/templates/campground_map.svg:1601
msgctxt "tooltip"
msgid "Zone 5"
msgstr "Zone 5"
#: web/templates/campground_map.svg:1602
msgctxt "tooltip"
msgid "Zone 4"
msgstr "Zone 4"
#: web/templates/campground_map.svg:1603
msgctxt "tooltip"
msgid "Zone 3"
msgstr "Zone 3"
#: web/templates/campground_map.svg:1604
msgctxt "tooltip"
msgid "Zone 2"
msgstr "Zone 2"
#: web/templates/campground_map.svg:1605
msgctxt "tooltip"
msgid "Zone 1"
msgstr "Zone 1"
Send an email on notification of success payment To send the actual mail with sendmail, i have stolen the code from go-mail[0] and removed everything i did not need. This is because there is no Go package to send email in Debian 12, and this was easier than to build the DEB for go-mail. Once i have the time…. [0]: https://go-mail.dev/
2024-02-13 04:20:35 +00:00
#: web/templates/mail/payment/body.gohtml:6
msgctxt "title"
msgid "Booking Payment Notification"
msgstr "Notification de paiement de réservation"
#: web/templates/mail/payment/body.gohtml:33
#: web/templates/mail/payment/body.gotxt:1
msgid "Hi %s,"
msgstr "Salut %s,"
#: web/templates/mail/payment/body.gohtml:35
#: web/templates/mail/payment/body.gotxt:3
msgid "We have successfully received the payment for the booking with the following details:"
msgstr "Nous avons reçu avec succès le paiement de la réservation avec les détails suivants :"
#: web/templates/mail/payment/body.gohtml:37
msgid "Payment reference: <strong>%s</strong>"
msgstr "Référence de paiement : <strong>%s</strong>."
#: web/templates/mail/payment/body.gohtml:39
msgid "Accommodation: <strong>%s</strong>"
msgstr "Hébergement : < strong>%s</strong>"
#: web/templates/mail/payment/body.gohtml:41
msgid "Arrival Date: <strong>%s</strong>"
msgstr "Date d’arrivée : <strong>%s</strong>"
#: web/templates/mail/payment/body.gohtml:43
msgid "Departure Date: <strong>%s</strong>"
msgstr "Date de depart : <strong>%s</strong>"
#: web/templates/mail/payment/body.gohtml:45
msgid "Total: <strong>%s</strong>"
msgstr "Totale : <strong>%s</strong>"
#: web/templates/mail/payment/body.gohtml:48
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
msgid "Down payment: <strong>%s</strong>"
msgstr "Acompte : <strong>%s</strong>"
#: web/templates/mail/payment/body.gohtml:52
#: web/templates/mail/payment/body.gotxt:12
Send an email on notification of success payment To send the actual mail with sendmail, i have stolen the code from go-mail[0] and removed everything i did not need. This is because there is no Go package to send email in Debian 12, and this was easier than to build the DEB for go-mail. Once i have the time…. [0]: https://go-mail.dev/
2024-02-13 04:20:35 +00:00
msgid "Thank you for your booking, and see you soon!"
msgstr "Merci pour votre réservation et à bientôt !"
#: web/templates/mail/payment/body.gotxt:5
msgid "Payment reference: **%s**"
msgstr "Référence de paiement : **%s**"
#: web/templates/mail/payment/body.gotxt:6
msgid "Accommodation: **%s**"
msgstr "Hébergement : **%s**"
#: web/templates/mail/payment/body.gotxt:7
msgid "Arrival Date: **%s**"
msgstr "Date d’arrivée : **%s**"
#: web/templates/mail/payment/body.gotxt:8
msgid "Departure Date: **%s**"
msgstr "Date de depart : **%s**"
#: web/templates/mail/payment/body.gotxt:9
msgid "Total: **%s**"
msgstr "Totale : **%s**"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/mail/payment/body.gotxt:10
msgid "Down payment: **%s**"
msgstr "Acompte : **%s**"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/payment/success.gohtml:6
msgctxt "title"
msgid "Payment Successful"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Paiement réussi"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
#: web/templates/public/payment/success.gohtml:12
msgid "We have received the payment. Thank you."
msgstr "Nous avons reçu le paiement. Merci."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/payment/request.gohtml:6
msgctxt "title"
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
msgid "Booking Payment"
msgstr "Paiement de la réservation"
#: web/templates/public/payment/request.gohtml:18
msgid "Thank you for your booking. Please, click the button below to pay with a credit card via Servired/Redsys."
msgstr "Merci pour votre réservation. Veuillez cliquer sur le bouton ci-dessous pour payer avec une carte de crédit via Servired/Redsys."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
#: web/templates/public/payment/request.gohtml:27
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
msgid "Pay with credit card"
msgstr "Payez avec une carte de crédit"
#: web/templates/public/payment/request.gohtml:30
msgid "Please, wait until we redirect you to the payment page."
msgstr "Veuillez attendre que nous vous redirigeons vers la page de paiement."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/payment/failure.gohtml:6
msgctxt "title"
msgid "Payment Failed"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le paiement a échoué"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
#: web/templates/public/payment/failure.gohtml:12
msgid "We could not process the payment. Please, contact us for support."
msgstr "Nous n’avons pas pu traiter le paiement. S’il vous plaît, contactez-nous pour obtenir de l’aide."
#: web/templates/public/payment/details.gohtml:4
msgctxt "title"
msgid "Order Number"
msgstr "Numéro de commande"
#: web/templates/public/payment/details.gohtml:8
msgctxt "title"
msgid "Date"
msgstr "Date"
#: web/templates/public/payment/details.gohtml:12
msgctxt "title"
msgid "Total"
msgstr "Totale"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/payment/details.gohtml:17
msgctxt "title"
msgid "Down Payment"
msgstr "Acompte"
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/services.gohtml:7
#: web/templates/public/services.gohtml:16
#: web/templates/public/layout.gohtml:67 web/templates/public/layout.gohtml:95
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:59
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Services"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Services"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/services.gohtml:19
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "The campsite offers many different services."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le camping propose de nombreux services différents."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/public/amenity.gohtml:39
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:114
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/public/campsite/page.gohtml:39
msgctxt "title"
msgid "Features"
msgstr "Caractéristiques"
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/location.gohtml:7
#: web/templates/public/location.gohtml:13
#: web/templates/public/layout.gohtml:69 web/templates/public/layout.gohtml:97
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:64
Replace contact page with location Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
2023-12-21 20:17:04 +00:00
msgctxt "title"
msgid "Location"
msgstr "Comment nous rejoindre"
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/home.gohtml:7 web/templates/public/layout.gohtml:53
#: web/templates/public/layout.gohtml:93
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Home"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Accueil"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:25
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "link"
msgid "Booking"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Réservation"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:28
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
msgid "The pleasure of camping in the middle of nature…"
msgstr "Le plaisir de camper en pleine nature…"
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:40
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Our services"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nos services"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:44
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/surroundings.gohtml:7
#: web/templates/public/surroundings.gohtml:12
#: web/templates/public/layout.gohtml:68 web/templates/public/layout.gohtml:96
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:15
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:67
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Surroundings"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Entourage"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:47
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "Located in <strong>Alta Garrotxa</strong>, between the <strong>Pyrenees</strong> and the <strong>Costa Brava</strong>."
msgstr "Situé dans <strong>l’Alta Garrotxa</strong>, entre les <strong>Pyrénées</strong> et la <strong>Costa Brava</strong>."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:48
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "Nearby there are the <strong>gorges of Sadernes</strong>, <strong>volcanoes</strong>, <strong>La Fageda d’en Jordà</strong>, the Jewish quarter of <strong>Besalú</strong>, the basaltic cliff of <strong>Castellfollit de la Roca</strong>… much to see and much to do."
msgstr "A proximité il y a les <strong>gorges de Sadernes</strong>, les <strong>volcans</strong>, <strong>La Fageda dâen Jordã </strong>, le quartier juif de <strong>Besalú</strong>, la falaise basaltique de <strong>Castellfollit de la Roca</strong>… beaucoup à voir et beaucoup à faire."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:49
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "Less than an hour from <strong>Girona</strong>, one from <strong>La Bisbal d’Empordà</strong>, and two from <strong>Barcelona</strong>."
msgstr "À moins d’une heure de <strong>Gérone</strong>, un de <strong>La Bisbal d’Empordà</strong>et deux de <strong>Barcelone</strong>."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: web/templates/public/home.gohtml:50
Change “Discover the environment” to “Discover”
2024-02-06 09:55:29 +00:00
msgid "Discover"
msgstr "Découvrir"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#: web/templates/public/campsite/type.gohtml:49
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:268
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Book"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Réserver"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#: web/templates/public/campsite/type.gohtml:57
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/index.gohtml:54
Updated translations
2023-12-22 02:32:40 +00:00
msgctxt "title"
msgid "Calendar"
msgstr "Calendrier"
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#: web/templates/public/campsite/type.gohtml:68
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:153
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:70
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Prices"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Prix"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:82
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "%s: %s/night"
msgstr "%s : %s/nuit"
Updated translations
2023-12-22 02:32:40 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:84
msgid "%s: %s"
msgstr "%s : %s"
#: web/templates/public/campsite/type.gohtml:88
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "%s/night"
msgstr "%s/nuit"
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:96
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "*Minimum %d nights per stay"
msgstr "*Minimum %d nuits par séjour"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:101
Add VAT and tourist tax information Since i need the number of decimals to format the price in the template, i added them to the company, and used them in the call to price_parse().
2024-01-15 00:45:58 +00:00
msgid "10 % VAT included."
msgstr "10 % TVA incluse."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:102
Fix the age of touristic tax It is for people aged 17 or olded, not 16. I was confused by the expression “over 16”, that **seems** to mean 17 or older, but actually includes people aged 16, too.
2024-01-18 14:27:46 +00:00
msgid "Tourist tax: %s/night per person aged 17 or older."
msgstr "Taxe touristique: %s/nuit par personne de plus de 16 ans."
Add VAT and tourist tax information Since i need the number of decimals to format the price in the template, i added them to the company, and used them in the call to price_parse().
2024-01-15 00:45:58 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:104
Added note about dogs to the campsite type page The pets icon is just the same as the notpet but without the diagonal bar. The price is hardcoded in the query for now, as there is no field in the campsite type.
2024-01-15 01:07:32 +00:00
msgid "Dogs: %s/night, tied, accompanied, and minimal barking."
msgstr "Chiens : %s/nuit, attachés, accompagnés et aboiements minimes."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:106
Added note about dogs to the campsite type page The pets icon is just the same as the notpet but without the diagonal bar. The price is hardcoded in the query for now, as there is no field in the campsite type.
2024-01-15 01:07:32 +00:00
msgid "No dogs allowed."
msgstr "Chiens interdits."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:125
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Info"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Info"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:129
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Facilities"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Installations"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:133
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Description"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Description"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:137
Add additional information field to campsite types This is actually just to have a fourth column in order to “balance” lists for types that have a long descriptions.
2024-01-14 23:28:34 +00:00
msgctxt "title"
msgid "Additional Information"
msgstr "Informations Complémentaires"
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:140
Add check-in and check-out time information to campsite type’s page
2024-01-15 00:02:50 +00:00
msgctxt "time"
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgid "Check-in"
Add check-in and check-out time information to campsite type’s page
2024-01-15 00:02:50 +00:00
msgstr "Arrivée"
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: web/templates/public/campsite/type.gohtml:144
Add check-in and check-out time information to campsite type’s page
2024-01-15 00:02:50 +00:00
msgctxt "time"
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgid "Check-out"
Add check-in and check-out time information to campsite type’s page
2024-01-15 00:02:50 +00:00
msgstr "Départ"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:18
#: web/templates/admin/season/calendar.gohtml:16
msgctxt "day"
msgid "Mon"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Lun"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:19
#: web/templates/admin/season/calendar.gohtml:17
msgctxt "day"
msgid "Tue"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mar."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:20
#: web/templates/admin/season/calendar.gohtml:18
msgctxt "day"
msgid "Wed"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mer."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:21
#: web/templates/admin/season/calendar.gohtml:19
msgctxt "day"
msgid "Thu"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Jeu."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:22
#: web/templates/admin/season/calendar.gohtml:20
msgctxt "day"
msgid "Fri"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ven."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:23
#: web/templates/admin/season/calendar.gohtml:21
msgctxt "day"
msgid "Sat"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Sam."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/public/campsite/calendar.gohtml:24
#: web/templates/admin/season/calendar.gohtml:22
msgctxt "day"
msgid "Sun"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Dim."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#: web/templates/public/campsite/dates.gohtml:4
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:29
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:52
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgctxt "input"
msgid "Arrival date"
msgstr "Date d’arrivée"
#: web/templates/public/campsite/dates.gohtml:15
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:40
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:56
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgctxt "input"
msgid "Departure date"
msgstr "Date de depart"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:30
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "What to Do Outside the Campsite?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Que faire à l’extérieur du camping ?"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:50
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "Once at the Campsite, We Can Inform You about What Activities are Available"
msgstr "Une fois au camping, nous pourrons vous informer sur les activités disponibles"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:53
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Cycle routes"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Pistes cyclables"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:54
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "There are many bicycle rental companies in Olot."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Il existe de nombreuses sociétés de location de vélos à Olot."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:58
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Routes"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Itinéraires"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:59
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Routes of all kinds, climbing, mountain passes, for all levels."
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgstr "Itinéraires de toutes sortes, escalade, cols de montagne, pour tous les niveaux."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:63
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Family outing"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Sortie en famille"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:64
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Many outing possibilities, for all ages."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nombreuses possibilités de sorties, pour tous les âges."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:68
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Kayak"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Kayak"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/public/surroundings.gohtml:69
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgid "There are several points where you can go by kayak, from sections of the Ter river as well as on the coast…."
msgstr "Il y a plusieurs points où vous pouvez aller en kayak, à partir de sections de la rivière Ter ainsi que sur la côte…."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/campground.gohtml:7
#: web/templates/public/campground.gohtml:16
#: web/templates/public/layout.gohtml:54 web/templates/public/layout.gohtml:94
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Campground"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Translate map’s legend
2024-01-29 13:37:27 +00:00
#: web/templates/public/campground.gohtml:20
msgctxt "title"
msgid "Legend"
msgstr "Légende"
#: web/templates/public/campground.gohtml:21
msgctxt "title"
msgid "Entrance"
msgstr "Entrée"
#: web/templates/public/campground.gohtml:23
msgctxt "legend"
msgid "Information"
msgstr "Information"
#: web/templates/public/campground.gohtml:24
msgctxt "legend"
msgid "Shop"
msgstr "Boutique"
#: web/templates/public/campground.gohtml:25
msgctxt "legend"
msgid "Restaurant"
msgstr "Restaurant"
#: web/templates/public/campground.gohtml:26
msgctxt "legend"
msgid "Bar"
msgstr "Bar"
#: web/templates/public/campground.gohtml:27
msgctxt "legend"
msgid "TV room"
msgstr "Salle de télévision"
#: web/templates/public/campground.gohtml:28
msgctxt "legend"
msgid "Game room"
msgstr "Salle de jeux"
#: web/templates/public/campground.gohtml:29
msgctxt "legend"
msgid "Recycling"
msgstr "Recyclage"
#: web/templates/public/campground.gohtml:30
msgctxt "legend"
msgid "Waste"
msgstr "Poubelle"
#: web/templates/public/campground.gohtml:31
msgctxt "legend"
msgid "Service station"
msgstr "Station-service"
#: web/templates/public/campground.gohtml:33
msgctxt "title"
msgid "Playtime"
msgstr "Récréation"
#: web/templates/public/campground.gohtml:35
msgctxt "legend"
msgid "Pool"
msgstr "Piscine"
#: web/templates/public/campground.gohtml:36
msgctxt "legend"
msgid "Playground"
msgstr "Cour de récréation"
#: web/templates/public/campground.gohtml:37
msgctxt "legend"
msgid "Sports field"
msgstr "Terrain de sport"
#: web/templates/public/campground.gohtml:39
msgctxt "title"
msgid "Accomodations"
msgstr "Hébergement"
#: web/templates/public/campground.gohtml:41
msgctxt "legend"
msgid "Wooden lodge"
msgstr "Chalet"
#: web/templates/public/campground.gohtml:42
msgctxt "legend"
msgid "Bungalow"
msgstr "Bungalow"
#: web/templates/public/campground.gohtml:43
msgctxt "legend"
msgid "Safari tent"
msgstr "Safari tent"
#: web/templates/public/campground.gohtml:45
msgctxt "title"
msgid "Main Building"
msgstr "Bâtiment principal"
#: web/templates/public/campground.gohtml:47
msgctxt "legend"
msgid "Restroom"
msgstr "Toilettes"
#: web/templates/public/campground.gohtml:48
msgctxt "legend"
msgid "Shower"
msgstr "Douche"
#: web/templates/public/campground.gohtml:49
msgctxt "legend"
msgid "Baby bath"
msgstr "Bain pour bébé"
#: web/templates/public/campground.gohtml:50
msgctxt "legend"
msgid "Washing machine"
msgstr "Machine à laver"
#: web/templates/public/campground.gohtml:51
msgctxt "legend"
msgid "Clothesline"
msgstr "Corde à linge"
#: web/templates/public/campground.gohtml:52
msgctxt "legend"
msgid "Barbecue"
msgstr "Barbecue"
#: web/templates/public/campground.gohtml:53
msgctxt "legend"
msgid "Chemical waste disposal"
msgstr "Élimination des déchets chimiques"
#: web/templates/public/campground.gohtml:55
msgctxt "title"
msgid "Throughout the Campground"
msgstr "Dans tout le camping"
#: web/templates/public/campground.gohtml:57
msgctxt "legend"
msgid "Fire extinguisher"
msgstr "Extincteur d’incendie"
#: web/templates/public/campground.gohtml:58
msgctxt "legend"
msgid "Faucet"
msgstr "Robinet"
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
#: web/templates/public/layout.gohtml:12 web/templates/public/layout.gohtml:48
msgid "Campsite Montagut"
msgstr "Camping Montagut"
#: web/templates/public/layout.gohtml:24 web/templates/admin/layout.gohtml:21
msgid "Skip to main content"
msgstr "Passer au contenu principal"
#: web/templates/public/layout.gohtml:50
msgid "Menu"
msgstr "Menu"
#: web/templates/public/layout.gohtml:58 web/templates/public/layout.gohtml:104
#: web/templates/admin/campsite/feature/form.gohtml:16
#: web/templates/admin/campsite/feature/index.gohtml:10
#: web/templates/admin/campsite/carousel/form.gohtml:16
#: web/templates/admin/campsite/carousel/index.gohtml:10
#: web/templates/admin/campsite/form.gohtml:15
#: web/templates/admin/campsite/index.gohtml:6
#: web/templates/admin/campsite/index.gohtml:15
#: web/templates/admin/campsite/type/feature/form.gohtml:16
#: web/templates/admin/campsite/type/feature/index.gohtml:10
#: web/templates/admin/campsite/type/carousel/form.gohtml:16
#: web/templates/admin/campsite/type/carousel/index.gohtml:10
#: web/templates/admin/campsite/type/form.gohtml:15
#: web/templates/admin/campsite/type/option/form.gohtml:16
#: web/templates/admin/campsite/type/option/index.gohtml:10
#: web/templates/admin/campsite/type/index.gohtml:10
#: web/templates/admin/layout.gohtml:46 web/templates/admin/layout.gohtml:95
msgctxt "title"
msgid "Campsites"
msgstr "Locatifs"
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
#: web/templates/public/layout.gohtml:70
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#: web/templates/public/booking/page.gohtml:7
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:41
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Booking"
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgstr "Réservation"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
#: web/templates/public/layout.gohtml:91
msgctxt "title"
msgid "Sections"
msgstr "Sections"
#: web/templates/public/layout.gohtml:115
msgctxt "title"
msgid "Opening"
msgstr "Ouverture"
#: web/templates/public/layout.gohtml:122
msgid "<abbr title=\"Catalonia Tourism Registry\">RTC</abbr> <abbr title=\"Number\">#</abbr>%s"
msgstr "<abbr title=\"Registre du tourisme de Catalogne\"># RTC</abbr> %s"
Translate footer links
2024-02-26 18:13:17 +00:00
#: web/templates/public/layout.gohtml:131
msgctxt "title"
msgid "Credits"
msgstr "Crédits"
#: web/templates/public/layout.gohtml:131
msgctxt "title"
msgid "Terms and Conditions"
msgstr "Termes et conditions"
#: web/templates/public/layout.gohtml:131
msgctxt "title"
msgid "Reservation Conditions"
msgstr "Conditions de réservation"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/page.gohtml:15
msgid "Sorry, there was a problem. You’ll find more details highlighted below."
msgstr "Il y avait un problème. Vous trouverez plus de détails ci-dessous."
Add a warning on the booking page when payment is using test environment Apparently, the bank has to validate the fucking thing on the actual domain, because of reasons, so we have to replace the current web in production with this version in test mode, meaning that users **will** believe they have paid, when in fact they have not. The warning is for these few people that actually read such notices.
2024-02-26 15:00:29 +00:00
#: web/templates/public/booking/page.gohtml:20
msgid "Payment is in test mode. You can make the booking regardless, but no money will be charged. We will send you an additional email with instructions on how to perform the payment."
msgstr "Le paiement est en mode test. Malgré tout, vous pouvez effectuer la réservation, mais aucun argent ne sera facturé. Nous vous enverrons un e-mail supplémentaire avec des instructions sur la manière d’effectuer le paiement."
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:14
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:44
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "title"
msgid "Accommodation"
msgstr "Hébergement"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:26
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "title"
msgid "Booking Period"
msgstr "Période de réservation"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:55
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "title"
msgid "Guests"
msgstr "Personnes logeant"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:59
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:64
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Adults aged 17 or older"
msgstr "Adultes âgés 17 ans ou plus"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:70
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:68
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Teenagers from 11 to 16 years old"
msgstr "Adolescents de 11 à 16 ans"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:81
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:72
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Children from 2 to 10 years old"
msgstr "Enfants de 2 à 10 ans"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:91
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
msgid "Note: Due to guest capacity, we have added more accomodations to the booking, but we <strong>cannot</strong> guarantee that they will be next to each other."
msgstr "Remarque : En raison de la capacité d’accueils, nous avons ajouté d’autres hébergements à la réservation, mais nous <strong>ne pouvons</strong> garantir qu’ils seront côte à côte."
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:99
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:76
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Dogs"
msgstr "Chiens"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:108
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "Note: This accommodation does <strong>not</strong> allow dogs."
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
msgstr "Remarque : Dans cet hébergement les chiens <strong>ne</strong> sont pas acceptés."
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:120
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Area preferences (optional)"
msgstr "Préférences de zone (facultatif)"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:122
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Campground map"
msgstr "Plan du camping"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:145
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:106
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Customer Details"
msgstr "Détails du client"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:148
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:109
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Full name"
msgstr "Nom et prénom"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:157
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/admin/payment/details.gohtml:113
#: web/templates/admin/taxDetails.gohtml:69
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
msgid "Address"
msgstr "Adresse"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:166
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/admin/payment/details.gohtml:117
#: web/templates/admin/taxDetails.gohtml:93
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
msgid "Postcode"
msgstr "Code postal"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:175
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
msgid "Town or village"
msgstr "Ville"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:184
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:125
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:101
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Country"
msgstr "Pays"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:187
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Choose a country"
msgstr "Choisissez un pays"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:195
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:129
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
#: web/templates/admin/login.gohtml:27 web/templates/admin/profile.gohtml:38
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:53
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Email"
msgstr "E-mail"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:204
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:133
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:45
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Phone"
msgstr "Téléphone"
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
#: web/templates/public/booking/fields.gohtml:215
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "ACSI card? (optional)"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Carte ACSI ? (Facultatif)"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:223
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Add rel="terms-of-service" to booking form’s link to conditions I also changed the translatable link to not include any HTML, because it meant that i had to retranslate them just to add a new attribute, that does not make much sense—the attribute is not even translatable, thus all translations must include it verbatim.
2024-01-22 02:41:54 +00:00
msgid "I have read and I accept %[1]sthe reservation conditions%[2]s"
msgstr "J’ai lu et j’accepte %[1]sles conditions de réservation%[2]s"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:241
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "cart"
msgid "Total"
msgstr "Totale"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:246
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/details.gohtml:84
Add down payment Customer wants to require a down payment of 30 % for bookings made one week or more before the actual date, and to make the full payment otherwise. This would require yet another relation to keep these values. Fuck it; i added them to the function, as they are very unlikely to change. That forced me to change the test for draft_payment to use relative dates, otherwise there is no way i can have stable results in the future.
2024-02-13 22:45:25 +00:00
msgctxt "cart"
msgid "Down payment"
msgstr "Acompte"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:260
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
msgid "By down paying the %d %% of the total, you are pre-booking your preferences. We will respond within 24 hours and this percentage will be charged if accepted."
msgstr "En En effectuant le paiement de %d %% du total vous pré-réservez vos préférences. Nous vous répondrons dans les 24 heures et ce pourcentage sera facturé en cas d’acceptation."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:262
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
msgid "By paying the total you are pre-booking your preferences. We will respond within 24 hours and this amount will be charged if accepted."
msgstr "En procédant au paiement du montant total vous pré-réservez vos préférences. Nous vous répondrons dans les 24 heures et ce montant sera facturé en cas d’acceptation."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: web/templates/public/booking/fields.gohtml:266
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
msgid "See <%s>our conditions</%s> for more information."
msgstr "Consultez <%s>nos conditions</%s> pour plus d’informations."
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: web/templates/admin/payment/settings.gohtml:6
#: web/templates/admin/payment/index.gohtml:14
msgctxt "title"
msgid "Payment Settings"
msgstr "Paramètres de paiement"
#: web/templates/admin/payment/settings.gohtml:10
#: web/templates/admin/payment/index.gohtml:6
#: web/templates/admin/payment/details.gohtml:11
#: web/templates/admin/layout.gohtml:40
msgctxt "title"
msgid "Payments"
msgstr "Paiements"
#: web/templates/admin/payment/settings.gohtml:21
msgctxt "input"
msgid "Merchant Code"
msgstr "Code Marchant"
#: web/templates/admin/payment/settings.gohtml:30
msgctxt "input"
msgid "Terminal Number"
msgstr "Numéro de terminal"
#: web/templates/admin/payment/settings.gohtml:40
msgctxt "input"
msgid "Merchant Key (only if must change it)"
msgstr "Clé marchande (uniquement si vous devez la changer)"
#: web/templates/admin/payment/settings.gohtml:42
msgctxt "input"
msgid "Merchant Key"
msgstr "Clé Marchant"
#: web/templates/admin/payment/settings.gohtml:52
msgctxt "title"
msgid "Environment"
msgstr "Environnement"
#: web/templates/admin/payment/settings.gohtml:59
msgctxt "title"
msgid "Integration"
msgstr "Intégration"
#: web/templates/admin/payment/settings.gohtml:66
#: web/templates/admin/location.gohtml:53 web/templates/admin/profile.gohtml:78
#: web/templates/admin/taxDetails.gohtml:170
msgctxt "action"
msgid "Save changes"
msgstr "Enregistrer les changements"
#: web/templates/admin/payment/index.gohtml:20
#: web/templates/admin/user/login-attempts.gohtml:19
msgctxt "header"
msgid "Date"
msgstr "Date"
#: web/templates/admin/payment/index.gohtml:21
#: web/templates/admin/payment/details.gohtml:22
#: web/templates/admin/booking/index.gohtml:21
msgctxt "header"
msgid "Reference"
msgstr "Référence"
#: web/templates/admin/payment/index.gohtml:22
#: web/templates/admin/payment/details.gohtml:26
#: web/templates/admin/booking/index.gohtml:25
msgctxt "header"
msgid "Status"
msgstr "Statut"
#: web/templates/admin/payment/index.gohtml:23
msgctxt "header"
msgid "Down payment"
msgstr "Acompte"
#: web/templates/admin/payment/index.gohtml:24
msgctxt "header"
msgid "Total"
msgstr "Totale"
#: web/templates/admin/payment/index.gohtml:40
msgid "No payments found."
msgstr "Aucun paiement trouvée."
#: web/templates/admin/payment/details.gohtml:7
msgctxt "title"
msgid "Payment %s"
msgstr "Paiement %s"
#: web/templates/admin/payment/details.gohtml:19
msgctxt "title"
msgid "Payment"
msgstr "Paiement"
#: web/templates/admin/payment/details.gohtml:30
msgctxt "payment header"
msgid "Created at"
msgstr "Créé à"
#: web/templates/admin/payment/details.gohtml:34
msgctxt "payment header"
msgid "Last updated at"
msgstr "Dernière mise à jour à"
#: web/templates/admin/payment/details.gohtml:48
msgctxt "header"
msgid "Area preferences"
msgstr "Préférences de zone"
#: web/templates/admin/payment/details.gohtml:60
msgctxt "cart"
msgid "Nights"
msgstr "Nuits"
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: web/templates/admin/payment/details.gohtml:80 pkg/booking/cart.go:191
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgctxt "cart"
msgid "Tourist tax"
msgstr "Taxe touristique"
#: web/templates/admin/payment/details.gohtml:92
#: web/templates/admin/campsite/type/option/form.gohtml:18
#: web/templates/admin/campsite/type/option/index.gohtml:6
#: web/templates/admin/campsite/type/option/index.gohtml:17
msgctxt "title"
msgid "Campsite Type Options"
msgstr "Options de type d’emplacement de camping"
#: web/templates/admin/payment/details.gohtml:121
#: web/templates/admin/taxDetails.gohtml:77
msgctxt "input"
msgid "City"
msgstr "Ville"
#: web/templates/admin/payment/details.gohtml:137
#: web/templates/admin/profile.gohtml:68
msgctxt "input"
msgid "Language"
msgstr "Langue"
#: web/templates/admin/payment/details.gohtml:141
msgctxt "input"
msgid "ACSI card?"
msgstr "Carte ACSI ?"
#: web/templates/admin/payment/details.gohtml:142
#: web/templates/admin/campsite/index.gohtml:41
#: web/templates/admin/campsite/type/index.gohtml:53
#: web/templates/admin/season/index.gohtml:44
#: web/templates/admin/user/login-attempts.gohtml:31
#: web/templates/admin/amenity/index.gohtml:40
msgid "Yes"
msgstr "Oui"
#: web/templates/admin/payment/details.gohtml:142
#: web/templates/admin/campsite/index.gohtml:41
#: web/templates/admin/campsite/type/index.gohtml:53
#: web/templates/admin/season/index.gohtml:44
#: web/templates/admin/user/login-attempts.gohtml:31
#: web/templates/admin/amenity/index.gohtml:40
msgid "No"
msgstr "Non"
Add management of legal texts
2023-12-22 01:23:18 +00:00
#: web/templates/admin/legal/form.gohtml:8
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:29
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "Edit Legal Text"
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Modifier le texte juridique"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of legal texts
2023-12-22 01:23:18 +00:00
#: web/templates/admin/legal/form.gohtml:10
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:31
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "New Legal Text"
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Nouveau texte juridique"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:15
#: web/templates/admin/legal/index.gohtml:6
#: web/templates/admin/legal/index.gohtml:15
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:70
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgctxt "title"
msgid "Legal Texts"
msgstr "Textes juridiques"
#: web/templates/admin/legal/form.gohtml:41
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "Slug"
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Slug"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:50
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:50
#: web/templates/admin/campsite/type/feature/form.gohtml:59
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/form.gohtml:51
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:41
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:50
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:53
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/profile.gohtml:29
#: web/templates/admin/surroundings/form.gohtml:41
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:50
#: web/templates/admin/amenity/form.gohtml:50
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "input"
msgid "Name"
msgstr "Nom"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:68
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "input"
msgid "Content"
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Contenu"
Add management of legal texts
2023-12-22 01:23:18 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:88
#: web/templates/admin/carousel/form.gohtml:55
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:65
#: web/templates/admin/campsite/carousel/form.gohtml:50
#: web/templates/admin/campsite/form.gohtml:92
#: web/templates/admin/campsite/type/feature/form.gohtml:74
#: web/templates/admin/campsite/type/carousel/form.gohtml:59
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:287
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:98
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:73
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:81
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:69
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:58
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:65
#: web/templates/admin/amenity/carousel/form.gohtml:50
#: web/templates/admin/amenity/form.gohtml:91
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:34
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:39
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Update"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mettre à jour"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/form.gohtml:90
#: web/templates/admin/carousel/form.gohtml:57
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:67
#: web/templates/admin/campsite/carousel/form.gohtml:52
#: web/templates/admin/campsite/form.gohtml:94
#: web/templates/admin/campsite/type/feature/form.gohtml:76
#: web/templates/admin/campsite/type/carousel/form.gohtml:61
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:289
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:100
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:75
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:83
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:71
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:67
#: web/templates/admin/amenity/carousel/form.gohtml:52
#: web/templates/admin/amenity/form.gohtml:93
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/index.gohtml:14
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "action"
msgid "Add Legal Text"
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Ajouter un texte juridique"
Add management of legal texts
2023-12-22 01:23:18 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/index.gohtml:20
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/index.gohtml:30
#: web/templates/admin/campsite/type/feature/index.gohtml:31
#: web/templates/admin/campsite/type/option/index.gohtml:30
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/index.gohtml:29
#: web/templates/admin/season/index.gohtml:29
#: web/templates/admin/user/index.gohtml:20
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:83
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/index.gohtml:30
#: web/templates/admin/amenity/index.gohtml:21
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "header"
msgid "Name"
msgstr "Nom"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/legal/index.gohtml:32
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "No legal texts added yet."
Add “Menu” next to the trigram symbol (“hamburger”)
2024-01-10 18:41:57 +00:00
msgstr "Aucune texte juridique n’a encore été ajoutée."
Add management of legal texts
2023-12-22 01:23:18 +00:00
#: web/templates/admin/carousel/form.gohtml:8
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/carousel/form.gohtml:28
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "title"
msgid "Edit Carousel Slide"
msgstr "Modifier la diapositive du carrousel"
#: web/templates/admin/carousel/form.gohtml:10
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/carousel/form.gohtml:30
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "title"
msgid "New Carousel Slide"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgstr "Nouveau diapositive carrousel"
Add management of legal texts
2023-12-22 01:23:18 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/carousel/form.gohtml:40
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/form.gohtml:35
#: web/templates/admin/campsite/type/carousel/form.gohtml:44
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/form.gohtml:35
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgctxt "input"
msgid "Caption"
msgstr "Légende"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/location.gohtml:6 web/templates/admin/location.gohtml:15
Replace contact page with location Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
2023-12-21 20:17:04 +00:00
msgctxt "title"
msgid "Location Settings"
msgstr "Paramètres de comment nous rejoindre"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/location.gohtml:20
Replace contact page with location Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
2023-12-21 20:17:04 +00:00
msgctxt "input"
msgid "Directions"
msgstr "Directions"
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/location.gohtml:33
Replace contact page with location Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
2023-12-21 20:17:04 +00:00
msgctxt "input"
msgid "Opening Dates"
msgstr "Dates d’ouverture"
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/location.gohtml:46
Replace contact page with location Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
2023-12-21 20:17:04 +00:00
msgctxt "input"
msgid "Map Embed"
msgstr "Carte intégrée"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:8
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Edit Campsite Feature"
msgstr "Modifier l’entité de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:10
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "New Campsite Feature"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Nouvelle caractéristique de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:17
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/feature/index.gohtml:6
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Campsite Features"
msgstr "Caractéristiques de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/form.gohtml:32
#: web/templates/admin/campsite/type/feature/form.gohtml:41
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:35
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:32
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgctxt "input"
msgid "Icon"
msgstr "Icône"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/index.gohtml:15
#: web/templates/admin/campsite/type/feature/index.gohtml:16
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/index.gohtml:15
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add Feature"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Ajouter une caractéristique"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/index.gohtml:31
#: web/templates/admin/campsite/carousel/index.gohtml:31
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: web/templates/admin/campsite/type/feature/index.gohtml:32
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/carousel/index.gohtml:32
#: web/templates/admin/campsite/type/option/index.gohtml:31
#: web/templates/admin/services/index.gohtml:30
#: web/templates/admin/services/index.gohtml:75
#: web/templates/admin/user/index.gohtml:23
#: web/templates/admin/surroundings/index.gohtml:84
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/index.gohtml:31
#: web/templates/admin/amenity/carousel/index.gohtml:31
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:25
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/home/index.gohtml:54
#: web/templates/admin/home/index.gohtml:99
msgctxt "header"
msgid "Actions"
msgstr "Actions"
#: web/templates/admin/campsite/feature/index.gohtml:35
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: web/templates/admin/campsite/type/feature/index.gohtml:36
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/index.gohtml:35
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgid "Are you sure you wish to delete this feature?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer cette caractéristique ?"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/feature/index.gohtml:47
#: web/templates/admin/campsite/carousel/index.gohtml:49
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: web/templates/admin/campsite/type/feature/index.gohtml:48
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/carousel/index.gohtml:50
#: web/templates/admin/campsite/type/option/index.gohtml:47
#: web/templates/admin/services/index.gohtml:47
#: web/templates/admin/services/index.gohtml:91
#: web/templates/admin/user/index.gohtml:37
#: web/templates/admin/surroundings/index.gohtml:63
#: web/templates/admin/surroundings/index.gohtml:101
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/index.gohtml:47
#: web/templates/admin/amenity/carousel/index.gohtml:49
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:45
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/home/index.gohtml:71
#: web/templates/admin/home/index.gohtml:116
msgctxt "action"
msgid "Delete"
msgstr "Supprimer"
#: web/templates/admin/campsite/feature/index.gohtml:56
msgid "No campsite features added yet."
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Aucune caractéristique de camping n’a encore été ajoutée."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/carousel/form.gohtml:8
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Edit Campsite Carousel Slide"
msgstr "Modifier la diapositive du carrousel de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/carousel/form.gohtml:10
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "New Campsite Carousel Slide"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgstr "Nouveau diapositive de carrousel de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/form.gohtml:17
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:6
msgctxt "title"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Campsite Carousel"
msgstr "Camping Carrousel"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:16
#: web/templates/admin/campsite/type/carousel/index.gohtml:17
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:15
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/index.gohtml:16
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:84
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add slide"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter la diapositive"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:29
#: web/templates/admin/campsite/type/carousel/index.gohtml:30
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:28
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:82
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/index.gohtml:29
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:52
#: web/templates/admin/home/index.gohtml:97
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Image"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Image"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:30
#: web/templates/admin/campsite/type/carousel/index.gohtml:31
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:29
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/index.gohtml:30
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:53
#: web/templates/admin/home/index.gohtml:98
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Caption"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Légende"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:35
#: web/templates/admin/campsite/type/carousel/index.gohtml:36
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:34
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/index.gohtml:35
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:103
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Are you sure you wish to delete this slide?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer cette diapositive ?"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/carousel/index.gohtml:58
#: web/templates/admin/campsite/type/carousel/index.gohtml:59
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:56
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/carousel/index.gohtml:58
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:125
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No slides added yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucune diapositive n’a encore été ajoutée."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/form.gohtml:8
msgctxt "title"
msgid "Edit Campsite"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Modifier le camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/form.gohtml:10
msgctxt "title"
msgid "New Campsite"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nouveau camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:33
#: web/templates/admin/campsite/index.gohtml:27
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "campsite"
msgid "Active"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Actif"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:42
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Campsite Type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Type d’emplacement de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:47
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Select campsite type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Sélectionnez le type d’emplacement"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:56
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/form.gohtml:42
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Label"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Label"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:64
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/form.gohtml:63
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Info (First Column)"
msgstr "Info (première colonne)"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/form.gohtml:77
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/form.gohtml:76
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "Info (Second Column)"
msgstr "Info (deuxième colonne)"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/index.gohtml:14
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add Campsite"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter un camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/index.gohtml:23
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/index.gohtml:20
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Label"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Label"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/index.gohtml:24
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Type"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/index.gohtml:25
#: web/templates/admin/campsite/type/index.gohtml:30
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/index.gohtml:22
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "header"
msgid "Features"
msgstr "Caractéristiques"
#: web/templates/admin/campsite/index.gohtml:26
#: web/templates/admin/campsite/type/index.gohtml:32
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/index.gohtml:23
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "header"
msgid "Carousel"
msgstr "Carrousel"
#: web/templates/admin/campsite/index.gohtml:36
#: web/templates/admin/campsite/type/index.gohtml:45
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:35
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "action"
msgid "Edit Features"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Edit caractéristiques"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/index.gohtml:39
#: web/templates/admin/campsite/type/index.gohtml:51
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:38
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "action"
msgid "Edit Carousel"
msgstr "Modifier le carrousel"
#: web/templates/admin/campsite/index.gohtml:47
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No campsites added yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucun camping n’a encore été ajouté."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/feature/form.gohtml:8
#: web/templates/admin/campsite/type/feature/form.gohtml:32
msgctxt "title"
msgid "Edit Campsite Type Feature"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Modifier la caractéristique de type de camping"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/feature/form.gohtml:10
#: web/templates/admin/campsite/type/feature/form.gohtml:34
msgctxt "title"
msgid "New Campsite Type Feature"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Nouvelle caractéristique de type de camping"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/feature/form.gohtml:17
#: web/templates/admin/campsite/type/feature/index.gohtml:11
#: web/templates/admin/campsite/type/carousel/form.gohtml:17
#: web/templates/admin/campsite/type/carousel/index.gohtml:11
#: web/templates/admin/campsite/type/form.gohtml:16
#: web/templates/admin/campsite/type/option/form.gohtml:17
#: web/templates/admin/campsite/type/option/index.gohtml:11
#: web/templates/admin/campsite/type/index.gohtml:6
#: web/templates/admin/campsite/type/index.gohtml:16
#: web/templates/admin/layout.gohtml:43
msgctxt "title"
msgid "Campsite Types"
msgstr "Types d’emplacements de camping"
#: web/templates/admin/campsite/type/feature/form.gohtml:18
#: web/templates/admin/campsite/type/feature/index.gohtml:6
#: web/templates/admin/campsite/type/feature/index.gohtml:17
msgctxt "title"
msgid "Campsite Type Features"
msgstr "Caractéristiques du type d’emplacement de camping"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: web/templates/admin/campsite/type/feature/index.gohtml:57
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgid "No campsite type features added yet."
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
msgstr "Aucune caractéristique de type camping n’a encore été ajoutée."
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/carousel/form.gohtml:8
#: web/templates/admin/campsite/type/carousel/form.gohtml:32
msgctxt "title"
msgid "Edit Campsite Type Carousel Slide"
msgstr "Modifier la diapositive du carrousel de type camping"
#: web/templates/admin/campsite/type/carousel/form.gohtml:10
#: web/templates/admin/campsite/type/carousel/form.gohtml:34
msgctxt "title"
msgid "New Campsite Type Carousel Slide"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgstr "Nouveau diapositive de carrousel de type camping"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/carousel/form.gohtml:18
#: web/templates/admin/campsite/type/carousel/index.gohtml:6
#: web/templates/admin/campsite/type/carousel/index.gohtml:16
msgctxt "title"
msgid "Campsite Type Carousel"
msgstr "Type de camping Carrousel"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/type/form.gohtml:8
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/form.gohtml:30
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Edit Campsite Type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Modifier le type d’emplacement"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/campsite/type/form.gohtml:10
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/form.gohtml:32
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "New Campsite Type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nouveau type d’emplacement de camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/form.gohtml:42
#: web/templates/admin/campsite/type/index.gohtml:33
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "campsite type"
msgid "Active"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Actif"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/form.gohtml:67
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgid "Check-in"
msgstr "Arrivée"
#: web/templates/admin/campsite/type/form.gohtml:80
msgctxt "input"
msgid "Check-out"
msgstr "Départ"
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
#: web/templates/admin/campsite/type/form.gohtml:93
msgctxt "input"
msgid "Minimum number of nights"
msgstr "Nombre minimum de nuits"
#: web/templates/admin/campsite/type/form.gohtml:101
msgctxt "input"
msgid "Maximum number of nights"
msgstr "Nombre maximale de nuits"
#: web/templates/admin/campsite/type/form.gohtml:110
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgctxt "input"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum number of campers"
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
msgstr "Nombre maximum de personnes"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
#: web/templates/admin/campsite/type/form.gohtml:120
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
msgctxt "input"
msgid "Allow overflowing guests to neighbouring campsites"
msgstr "Autoriser la réservation d’un hébergement voisin si le nombre maximum de personnes est dépassé"
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
#: web/templates/admin/campsite/type/form.gohtml:129
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
msgctxt "input"
msgid "Ask for zone preferences when booking"
msgstr "Demandez la préférence de zone lors de la réservation"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:139
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Dogs allowed"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Chiens acceptés"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:144
msgctxt "input"
msgid "Dogs price"
msgstr "Prix des chiens"
#: web/templates/admin/campsite/type/form.gohtml:157
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Season"
msgstr "Saison"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:158
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Price per night"
msgstr "Prix par nuit"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:159
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Price per adult (> 16)"
msgstr "Prix per adulte (> 16)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:160
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Price per teenager (11–16)"
msgstr "Prix per adolescent (11–16)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:161
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Price per child (2–10)"
msgstr "Prix per enfant (2–10)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:171
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "input"
msgid "Price per night"
msgstr "Prix par nuit"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:182
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Price per adult (> 16)"
msgstr "Prix per adulte (> 16)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:193
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Price per teenager (11–16)"
msgstr "Prix per adolescent (11–16)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:204
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "input"
msgid "Price per child (2–10)"
msgstr "Prix per enfant (2–10)"
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:220
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Spiel"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Boniment"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:233
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Info"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Info"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:246
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Facilities"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Installations"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:259
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:66
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:54
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Description"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Description"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: web/templates/admin/campsite/type/form.gohtml:272
Add additional information field to campsite types This is actually just to have a fourth column in order to “balance” lists for types that have a long descriptions.
2024-01-14 23:28:34 +00:00
msgctxt "input"
msgid "Additional Information"
msgstr "Informations Complémentaires"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:8
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:32
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "title"
msgid "Edit Campsite Type Option"
msgstr "Modifier l’option Type d’emplacement de camping"
#: web/templates/admin/campsite/type/option/form.gohtml:10
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:34
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "title"
msgid "New Campsite Type Option"
msgstr "Nouvelle option de type d’emplacement de camping"
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:54
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "input"
msgid "Minimum"
msgstr "Minimum"
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:62
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
msgctxt "input"
msgid "Maximum"
msgstr "Maximum"
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:75
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
msgctxt "campsite type"
msgid "Per night"
msgstr "Par nuit"
Add a small note to the booking form when there is overflow Customer wants to warn customers that plots are not guaranteed to be next to each other.
2024-02-11 21:06:00 +00:00
#: web/templates/admin/campsite/type/option/form.gohtml:84
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
msgctxt "input"
msgid "Price"
msgstr "Prix"
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/option/index.gohtml:16
msgctxt "action"
msgid "Add Option"
msgstr "Ajouter une option"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: web/templates/admin/campsite/type/option/index.gohtml:35
msgid "Are you sure you wish to delete this option?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer cette option ?"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: web/templates/admin/campsite/type/option/index.gohtml:56
msgid "No campsite type options added yet."
msgstr "Aucune option de type de camping n’a encore été ajoutée."
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/index.gohtml:15
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add Type"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter un type"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/index.gohtml:31
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Options"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Options"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/index.gohtml:48
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Edit Options"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Modifier les options"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/campsite/type/index.gohtml:60
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No campsite types added yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucun type d’emplacement n’a encore été ajouté."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/season/form.gohtml:8
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:29
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Edit Season"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Éditer la saison"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/season/form.gohtml:10
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:31
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "New Season"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nouvelle saison"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:15
Add rel="terms-of-service" to booking form’s link to conditions I also changed the translatable link to not include any HTML, because it meant that i had to retranslate them just to add a new attribute, that does not make much sense—the attribute is not even translatable, thus all translations must include it verbatim.
2024-01-22 02:41:54 +00:00
#: web/templates/admin/season/index.gohtml:6
#: web/templates/admin/season/index.gohtml:15
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:52
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgctxt "title"
Add rel="terms-of-service" to booking form’s link to conditions I also changed the translatable link to not include any HTML, because it meant that i had to retranslate them just to add a new attribute, that does not make much sense—the attribute is not even translatable, thus all translations must include it verbatim.
2024-01-22 02:41:54 +00:00
msgid "Seasons"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgstr "Saisons"
#: web/templates/admin/season/form.gohtml:41
#: web/templates/admin/season/index.gohtml:30
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "season"
msgid "Active"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Actif"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/form.gohtml:63
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Color"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Couleur"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/index.gohtml:14
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add Season"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter une saison"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/index.gohtml:28
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Color"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Couleur"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/season/index.gohtml:51
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No seasons added yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucune saison n’a encore été ajoutée."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/season/calendar.gohtml:49
#: web/templates/admin/media/picker.gohtml:61
msgctxt "action"
msgid "Cancel"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Annuler"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
#: web/templates/admin/dashboard.gohtml:6
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/dashboard.gohtml:13 web/templates/admin/layout.gohtml:89
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Dashboard"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Tableau de bord"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/login.gohtml:6 web/templates/admin/login.gohtml:18
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Login"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Connexion"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/login.gohtml:36 web/templates/admin/profile.gohtml:49
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Password"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mot de passe"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/login.gohtml:45
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Login"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Connexion"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/services/form.gohtml:8
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:26
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Edit Service"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Modifier le service"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/services/form.gohtml:10
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:28
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "New Service"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nouveau service"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Remove the required attribute from service’s name input It is virtually impossible to see when such a field fails prior to submit the form, unless you happen to have the correct language selected at the time. Leave it to the backend’s validation for now.
2024-01-24 10:13:39 +00:00
#: web/templates/admin/services/form.gohtml:15
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/services/index.gohtml:6
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:61
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Services Page"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La page des services"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:14
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:83
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Carousel"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Carrousel"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:60
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Add service"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ajouter un service"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:73
Add position to services to be able to manually sort by admins
2024-01-13 00:15:24 +00:00
msgctxt "header"
msgid "Order"
msgstr "Ordre"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:74
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "header"
msgid "Service"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Service"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:79
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Are you sure you wish to delete this service?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer ce service ?"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/services/index.gohtml:100
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No services added yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucun service n’a encore été ajouté."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/profile.gohtml:6 web/templates/admin/profile.gohtml:15
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: web/templates/admin/layout.gohtml:33
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Profile"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Profil"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/profile.gohtml:20
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "inut"
msgid "Profile Image"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Image de profil"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/profile.gohtml:46
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "legend"
msgid "Change password"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Changer le mot de passe"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/profile.gohtml:58
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Password Confirmation"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Confirmation du mot de passe"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
#: web/templates/admin/user/login-attempts.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/login-attempts.gohtml:15
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
msgctxt "title"
msgid "Login Attempts"
msgstr "Tentatives de connexion"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/login-attempts.gohtml:10
#: web/templates/admin/user/index.gohtml:6
#: web/templates/admin/user/index.gohtml:16
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:73
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgctxt "title"
msgid "Users"
msgstr "Utilisateurs"
#: web/templates/admin/user/login-attempts.gohtml:20
#: web/templates/admin/user/index.gohtml:21
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
msgctxt "header"
msgid "Email"
msgstr "E-mail"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/login-attempts.gohtml:21
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
msgctxt "header"
msgid "IP Address"
msgstr "Adresse IP"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/login-attempts.gohtml:22
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
msgctxt "header"
msgid "Success"
msgstr "Succès"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/index.gohtml:14
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
msgctxt "action"
msgid "Add User"
msgstr "Ajouter un utilisateur"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/index.gohtml:15
Add page to see login attempts for a company
2024-01-17 19:28:42 +00:00
msgctxt "action"
msgid "Logs"
msgstr "Journaux"
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/index.gohtml:22
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
msgctxt "header"
msgid "Role"
msgstr "Rôle"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/user/index.gohtml:27
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
msgid "Are you sure you wish to delete this user?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer ce utilisateur ?"
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/taxDetails.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:15
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Tax Details"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Détails de la taxe"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:20
#: web/templates/admin/taxDetails.gohtml:61
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Business Name"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgstr "Nom de l’entreprise"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:29
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "VAT Number"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Numéro de TVA"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:37
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Trade Name"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nom commercial"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:85
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Province"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Province"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:111
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Currency"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Devise"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:121
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Default Language"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Langue par défaut"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:130
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
msgctxt "title"
msgid "Tourism"
msgstr "Tourisme"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:133
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
msgctxt "input"
msgid "RTC number"
msgstr "Numéro RTC"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:141
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
msgctxt "input"
msgid "Tourist Tax"
msgstr "Taxe touristique"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:150
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
msgctxt "title"
msgid "Invoicing"
msgstr "Facturation"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:153
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Invoice Number Format"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Format de numéro de facture"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/taxDetails.gohtml:161
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Legal Disclaimer"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Avertissement juridique"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: web/templates/admin/surroundings/form.gohtml:8
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:29
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "title"
msgid "Edit Highlight"
msgstr "Modifier un point d’intérêt"
#: web/templates/admin/surroundings/form.gohtml:10
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/form.gohtml:31
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "title"
msgid "New Highlight"
msgstr "Nouveau point d’intérêt"
#: web/templates/admin/surroundings/index.gohtml:6
msgctxt "title"
msgid "Surroundings Page"
msgstr "Page de l’entourage"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/surroundings/index.gohtml:14
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "title"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
msgid "Ad"
msgstr "Annonce"
#: web/templates/admin/surroundings/index.gohtml:21
msgctxt "input"
msgid "Title"
msgstr "Titre"
#: web/templates/admin/surroundings/index.gohtml:37
msgctxt "input"
msgid "Link Text"
msgstr "Texte du lien"
#: web/templates/admin/surroundings/index.gohtml:50
msgctxt "input"
msgid "Link URL"
msgstr "Address du lien"
#: web/templates/admin/surroundings/index.gohtml:59
msgid "Are you sure you wish to delete the ad?"
msgstr "Êtes-vous sûr de vouloir supprimer cette annonce ?"
#: web/templates/admin/surroundings/index.gohtml:68
msgctxt "title"
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgid "Highlights"
msgstr "Points d’intérêt"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:69
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "action"
msgid "Add highlight"
msgstr "Ajouter un point d’intérêt"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:88
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgid "Are you sure you wish to delete this highlight?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer cette point d’intérêt ?"
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: web/templates/admin/surroundings/index.gohtml:110
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgid "No highlights added yet."
msgstr "Aucun point d’intérêt n’a encore été ajoutée."
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:8
msgctxt "title"
msgid "Edit Amenity Feature"
msgstr "Modifier l’entité de installation"
#: web/templates/admin/amenity/feature/form.gohtml:10
msgctxt "title"
msgid "New Amenity Feature"
msgstr "Nouvelle caractéristique de installation"
#: web/templates/admin/amenity/feature/form.gohtml:16
#: web/templates/admin/amenity/feature/index.gohtml:10
#: web/templates/admin/amenity/carousel/form.gohtml:16
#: web/templates/admin/amenity/carousel/index.gohtml:10
#: web/templates/admin/amenity/form.gohtml:15
#: web/templates/admin/amenity/index.gohtml:6
#: web/templates/admin/layout.gohtml:49
msgctxt "title"
msgid "Amenities"
Translate map’s legend
2024-01-29 13:37:27 +00:00
msgstr "Installations"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/amenity/feature/form.gohtml:17
#: web/templates/admin/amenity/feature/index.gohtml:6
msgctxt "title"
msgid "Amenity Features"
msgstr "Caractéristiques de installation"
#: web/templates/admin/amenity/feature/index.gohtml:56
msgid "No amenity features added yet."
msgstr "Aucune caractéristique de installation n’a encore été ajoutée."
#: web/templates/admin/amenity/carousel/form.gohtml:8
msgctxt "title"
msgid "Edit Amenity Carousel Slide"
msgstr "Modifier la diapositive du carrousel de installation"
#: web/templates/admin/amenity/carousel/form.gohtml:10
msgctxt "title"
msgid "New Amenity Carousel Slide"
msgstr "Nouveau diapositive de carrousel de installation"
#: web/templates/admin/amenity/carousel/form.gohtml:17
#: web/templates/admin/amenity/carousel/index.gohtml:6
msgctxt "title"
msgid "Amenity Carousel"
msgstr "Carrousel de installation"
#: web/templates/admin/amenity/form.gohtml:8
msgctxt "title"
msgid "Edit Amenity"
msgstr "Modifier l’installation"
#: web/templates/admin/amenity/form.gohtml:10
msgctxt "title"
msgid "New Amenity"
msgstr "Nouveau installation"
#: web/templates/admin/amenity/form.gohtml:33
#: web/templates/admin/amenity/index.gohtml:24
msgctxt "amenity"
msgid "Active"
msgstr "Actif"
#: web/templates/admin/amenity/index.gohtml:14
msgctxt "action"
msgid "Add Amenity"
msgstr "Ajouter un installation"
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:29
msgid "Are you sure you wish to delete this amenity?"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
msgstr "Êtes-vous sûr de vouloir supprimer ce installation ?"
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: web/templates/admin/amenity/index.gohtml:53
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgid "No amenities added yet."
msgstr "Aucun installation n’a encore été ajouté."
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: web/templates/admin/layout.gohtml:29
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "User Menu"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Menu utilisateur"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: web/templates/admin/layout.gohtml:37
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Company Settings"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
msgstr "Paramètres de l’entreprise"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:55
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:10
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
#: web/templates/admin/media/index.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/index.gohtml:14
#: web/templates/admin/media/upload.gohtml:10
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Média"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:58 web/templates/admin/home/index.gohtml:6
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Home Page"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Page d'accueil"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:78
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Logout"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Déconnexion"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:92
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
#: web/templates/admin/booking/index.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:16
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "title"
msgid "Bookings"
msgstr "Réservations"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:101
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
msgid "Breadcrumb"
msgstr "Fil d’Ariane"
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: web/templates/admin/layout.gohtml:113
Add the application’s version to the footer This is mostly because it is required for the “Digital Kit”, but it also works in our favor because now i can version the URL to the static resources. Go 1.18 adds the info from git if the package is build from a git repository, but this is not the case in OBS, so i instead relay on a constant for the version number. This constant is “updated” by Debian’s rules, mostly due to the discussion in [0]. [0]: https://github.com/golang/go/issues/22706
2024-01-21 19:50:04 +00:00
msgid "Camper Version: %s"
msgstr "Camper version: %s"
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:15
msgctxt "title"
msgid "Slogan"
msgstr "Slogan"
#: web/templates/admin/home/index.gohtml:21
msgctxt "input"
msgid "Slogan"
msgstr "Slogan"
#: web/templates/admin/home/index.gohtml:38
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
msgctxt "title"
msgid "Cover"
msgstr "Couverture"
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:39
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
msgctxt "action"
msgid "Add cover image"
msgstr "Ajouter une image de couverture"
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:58
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
msgid "Are you sure you wish to delete this cover image?"
msgstr "Êtes-vous sûr de vouloir supprimer cette image de couverture ?"
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: web/templates/admin/home/index.gohtml:80
Add home’s cover carousel This is a separate carousel from the one displayed at the bottom with location info; it is, i suppose, a carousel for the hero image. For the database, it works exactly as the home carousel, but on the front had to use AlpineJS instead of Slick because it needs to show a text popping up from the bottom when the slide is show, something i do not know how to do in Slick. It now makes no sense to have the carousel inside the “nature” section, because the heading is no longer in there, and moved it out into a new “hero” div. Since i now have two carousels in home, i had to add additional attributes to carousel.AdminHandler to know which URL to point to when POSTing, PUTting, or redirecting.
2024-01-16 20:05:52 +00:00
msgid "No images added to the cover yet."
msgstr "Aucune image de couverture n’a encore été ajoutée."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:8
msgctxt "title"
msgid "Media Picker"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Sélecteur de médias"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:19
msgctxt "title"
msgid "Upload New Media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Téléverser de nouveaux médias"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:22
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/upload.gohtml:21
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "File"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Fichier"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:26
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:26
#: web/templates/admin/media/upload.gohtml:25
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum upload file size: %s"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Taille maximale de téléversement : %s"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:31
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/upload.gohtml:30
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Upload"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Télécharger"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:47
msgctxt "title"
msgid "Choose Existing Media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Choisir un média existant"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/picker.gohtml:58
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/index.gohtml:23
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "No media uploaded yet."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Aucun média n’a encore été téléchargé."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/form.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:16
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Edit Media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Modifier un média"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:22
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Updated file"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Fichier mis à jour"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/form.gohtml:31
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Filename"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Nom du fichier"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/index.gohtml:15
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Upload media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Télécharger les médias"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: web/templates/admin/media/upload.gohtml:6
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/media/upload.gohtml:16
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "title"
msgid "Upload Media"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Envoyer un fichier"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:14
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "action"
msgid "Add Booking"
msgstr "Ajouter une réservation"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:15
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "action"
msgid "Export Bookings"
msgstr "Exporter les réservations"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:22
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "header"
msgid "Arrival Date"
msgstr "Date d’arrivée"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:23
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "header"
msgid "Departure Date"
msgstr "Date de depart"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:24
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "header"
msgid "Holder Name"
msgstr "Nom du titulaire"
Add breadcrumb to all admin pages I tried to use ../, and ../../ to make the routes relatives, but it would not work well because the same page would have two URLs, one ending with slash and another without, and the relative links would be different on each case.
2024-01-21 21:44:04 +00:00
#: web/templates/admin/booking/index.gohtml:41
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgid "No booking found."
msgstr "Aucune réservation trouvée."
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: pkg/payment/settings.go:37
msgctxt "redsys environment"
msgid "Test"
msgstr "Test"
#: pkg/payment/settings.go:41
msgctxt "redsys environment"
msgid "Live"
msgstr "Live"
#: pkg/payment/settings.go:50
msgctxt "redsys integration"
msgid "InSite"
msgstr "Insite"
#: pkg/payment/settings.go:54
msgctxt "redsys integration"
msgid "Redirect"
msgstr "Redirection"
#: pkg/payment/settings.go:98
msgid "Merchant code can not be empty."
msgstr "Le code marchand ne peut pas être vide."
#: pkg/payment/settings.go:99
msgid "Merchant code must be exactly nine digits long."
msgstr "Le code marchand doit comporter exactement neuf chiffres."
#: pkg/payment/settings.go:100
msgid "Merchant code must be a number."
msgstr "Le code du commerçant doit être un chiffre."
#: pkg/payment/settings.go:104
msgid "Terminal number can not be empty."
msgstr "Le numéro de terminal ne peut pas être vide."
#: pkg/payment/settings.go:105
msgid "Terminal number must be a number between 1 and 999."
msgstr "Le numéro de terminal doit être compris entre 1 et 999."
#: pkg/payment/settings.go:113
msgid "Selected environment is not valid."
msgstr "L’environnement sélectionné n’est pas valide."
#: pkg/payment/settings.go:114
msgid "Selected integration is not valid."
msgstr "L’intégration sélectionnée n’est pas valide."
#: pkg/payment/settings.go:117
msgid "The merchant key is not valid."
msgstr "La clé marchand n’est pas valide."
#: pkg/payment/public.go:110
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
msgctxt "order product name"
msgid "Campsite Booking"
msgstr "Réservation camping"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: pkg/payment/public.go:342
Send an email on notification of success payment To send the actual mail with sendmail, i have stolen the code from go-mail[0] and removed everything i did not need. This is because there is no Go package to send email in Debian 12, and this was easier than to build the DEB for go-mail. Once i have the time…. [0]: https://go-mail.dev/
2024-02-13 04:20:35 +00:00
msgctxt "subject"
msgid "Booking payment successfully received"
msgstr "Paiement de réservation reçu avec succès"
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/legal/admin.go:258 pkg/app/user.go:249 pkg/campsite/types/option.go:365
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/feature.go:272 pkg/campsite/types/admin.go:577
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: pkg/campsite/feature.go:269 pkg/season/admin.go:412
#: pkg/services/admin.go:316 pkg/surroundings/admin.go:340
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: pkg/amenity/feature.go:269 pkg/amenity/admin.go:283
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "Name can not be empty."
msgstr "Le nom ne peut pas être laissé vide."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/legal/admin.go:259 pkg/campsite/types/option.go:366
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/feature.go:273 pkg/campsite/types/admin.go:578
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/campsite/feature.go:270 pkg/amenity/feature.go:270
Add management of legal texts
2023-12-22 01:23:18 +00:00
msgid "Name must have at least one letter."
msgstr "Le nom doit comporter au moins une lettre."
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: pkg/carousel/admin.go:276 pkg/campsite/types/carousel.go:225
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/campsite/carousel.go:227 pkg/amenity/carousel.go:227
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Slide image"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Image du diaporama"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: pkg/carousel/admin.go:277 pkg/campsite/types/carousel.go:226
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/campsite/carousel.go:228 pkg/amenity/carousel.go:228
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Set slide image"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Définir l’image de la diapositive"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: pkg/carousel/admin.go:346 pkg/campsite/types/carousel.go:299
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: pkg/campsite/carousel.go:302 pkg/surroundings/admin.go:335
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/amenity/carousel.go:302
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Slide image can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’image de la diapositive ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make the slogan user-editable and translatable Because God forbid we have any performance; everything —**everything**— must be user editable.
2024-01-23 10:52:39 +00:00
#: pkg/carousel/admin.go:347 pkg/campsite/types/carousel.go:300
Add public pages for each individual accommodation A small page with a brief description, carousel, and feature list of each individual accommodation. Most of the relations and functions for carousel and features are like the ones for campsite types, but i had to use the accommodation’s label to find them, because they do not have slugs; i did not even though these would be public, and they already have a label, although not unique for all companies, like UUID slugs are.
2024-01-26 21:27:54 +00:00
#: pkg/campsite/carousel.go:303 pkg/surroundings/admin.go:336
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/amenity/carousel.go:303
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Slide image must be an image media type."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’image de la diapositive doit être de type média d’image."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/app/login.go:56 pkg/app/user.go:246 pkg/company/admin.go:217
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:536
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Email can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’e-mail ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/app/login.go:57 pkg/app/user.go:247 pkg/company/admin.go:218
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:537
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "This email is not valid. It should be like name@domain.com."
Fix encoding issue in PO file for French
2023-12-18 20:23:03 +00:00
msgstr "Cette adresse e-mail n’est pas valide. Il devrait en être name@domain.com."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/app/login.go:59
msgid "Password can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le mot de passe ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/app/login.go:86
msgid "Invalid user or password."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Utilisateur ou mot de passe non valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/app/user.go:197
msgctxt "language option"
msgid "Automatic"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Automatique"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/app/user.go:250
msgid "Confirmation does not match password."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La confirmation ne correspond pas au mot de passe."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/app/user.go:251 pkg/company/admin.go:238
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Selected language is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La langue sélectionnée n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/app/user.go:253
msgid "File must be a valid PNG or JPEG image."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le fichier doit être une image PNG ou JPEG valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: pkg/app/admin.go:73
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Access forbidden"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Accès interdit"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:369
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le minimum ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:370
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum must be an integer number."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le minimum doit être un nombre entier."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:372
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum must be zero or greater."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le minimum doit être égal ou supérieur à zéro."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:375
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le maximum ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:376
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum must be an integer number."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le maximum doit être un nombre entier."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:378
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum must be equal or greater than minimum."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le maximum doit être égal ou supérieur au minimum."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:382
msgid "Price can not be empty."
msgstr "Le prix ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:383
msgid "Price must be a decimal number."
msgstr "Le prix doit être un nombre décimal."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/option.go:384
msgid "Price must be zero or greater."
msgstr "Le prix doit être égal ou supérieur à zéro."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#: pkg/campsite/types/feature.go:271 pkg/campsite/feature.go:268
Add amenities section and public page This is more or less the same as the campsites, as public information goes, but for buildings and other amenities that the camping provides that are not campsites.
2024-01-27 21:51:41 +00:00
#: pkg/services/admin.go:315 pkg/amenity/feature.go:268
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Selected icon is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’icône sélectionnée n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:328
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "input"
msgid "Cover image"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Image de couverture"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:329
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Set campsite type cover"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Définir une couverture type camping"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:580
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgid "Check-in can not be empty."
msgstr "L’arrivée ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:581
Add check_in and check_out fields to campsite_type Apparently, each campsite type could have different check-in and check-out times, thus i need them in the database. I thought about using an integer or a datetime field, but customer seems to want a text field to maybe add “before” and “after” there as well. Translatable text it is.
2024-01-22 19:19:19 +00:00
msgid "Check-out can not be empty."
msgstr "Le départ ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:582
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Cover image can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’image de couverture ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:583
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Cover image must be an image media type."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’image de couverture doit être de type média d’image."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:587
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum number of campers can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre maximum de campeurs ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:588
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum number of campers must be an integer number."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre maximum de campeurs doit être un nombre entier."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:589
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Maximum number of campers must be one or greater."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre maximum de campeurs doit être égal ou supérieur à un campeur."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:592
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum number of nights can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre minimum de nuits ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:593
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum number of nights must be an integer."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre minimum de nuits doit être un entier."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:594
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Minimum number of nights must be one or greater."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nombre minimum de nuits doit être supérieur ou égal à une nuit."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:597
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
msgid "Maximum number of nights can not be empty."
msgstr "Le nombre maximale de nuits ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:598
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
msgid "Maximum number of nights must be an integer."
msgstr "Le nombre maximale de nuits doit être un entier."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:599
Replace min_nights from campsite_type_costs to range in campsite_type Customer told us that the minimum number of nights is per campsite type, not per season. And he wants this, along with the maximum number of nights, in order to limit the range of departure dates that guests can choose when booking.
2024-01-31 22:06:45 +00:00
msgid "Maximum number of nights must be equal or greater than the minimum."
msgstr "Le nombre maximale de nuits doit être égal ou supérieur au minimum."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:603
msgid "Dogs price can not be empty when dogs are allowed."
msgstr "Le prix des chiens net peut pas être vide lorsqu’ils sont acceptés."
#: pkg/campsite/types/admin.go:604
msgid "Dogs price must be a decimal number."
msgstr "Le prix des chiens doit être un nombre décimal."
#: pkg/campsite/types/admin.go:605
msgid "Dogs price must be zero or greater."
msgstr "Le prix de chiens doit être égal ou supérieur à zéro."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/admin.go:610
msgid "Price per night can not be empty."
msgstr "Le prix par nuit ne peut pas être vide."
#: pkg/campsite/types/admin.go:611
msgid "Price per night must be a decimal number."
msgstr "Le prix par nuit doit être un nombre décimal."
#: pkg/campsite/types/admin.go:612
msgid "Price per night must be zero or greater."
msgstr "Le prix par nuit doit être égal ou supérieur."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:615
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per adult can not be empty."
msgstr "Le prix par adulte ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:616
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per adult must be a decimal number."
msgstr "Le prix par adulte doit être un nombre décimal."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:617
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per adult must be zero or greater."
msgstr "Le prix par adulte doit être égal ou supérieur."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:620
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per teenager can not be empty."
msgstr "Le prix par adolescent ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:621
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per teenager must be a decimal number."
msgstr "Le prix par adolescent doit être un nombre décimal."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:622
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per teenager must be zero or greater."
msgstr "Le prix par adolescent doit être égal ou supérieur."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:625
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per child can not be empty."
msgstr "Le prix par enfant ne peut pas être vide."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:626
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per child must be a decimal number."
msgstr "Le prix par enfant doit être un nombre décimal."
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
#: pkg/campsite/types/admin.go:627
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Price per child must be zero or greater."
msgstr "Le prix par enfant doit être égal ou supérieur."
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/public.go:247
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Adults"
msgstr "Adultes"
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/public.go:254
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Teenagers (aged 11 to 16)"
msgstr "Adolescents (de 11 à 16 anys)"
Allow campsite type option to be just per unit, not per unit per night Customer told us that there are some options, such as towels, that have a fixed price for the whole stay, not a per night price. Thus, had to add a boolean to know whether to use sum or max when computing the cart’s total for each option.
2024-02-11 20:45:00 +00:00
#: pkg/campsite/types/public.go:261
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "header"
msgid "Children (aged 2 to 10)"
msgstr "Enfants (de 2 à 10 anys)"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/campsite/admin.go:275 pkg/booking/public.go:172
#: pkg/booking/public.go:227
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Selected campsite type is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le type d’emplacement sélectionné n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add ask_zone_preferences and overflow_allowed to campsite_type The “overflow” is for when people want to book plots for more guests than is permitted, which the system would need to add a new plot to the “shopping cart”, as it were; not implemented yet. The ask zone preferences is to whether show the corresponding input on the booking form, that it was done implicitly when the campsite type had options, because up until now it was only for plots, but it is no longer the case, thus i need to know when to show it; now it is explicit.
2024-01-29 02:38:11 +00:00
#: pkg/campsite/admin.go:276 pkg/amenity/admin.go:282
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Label can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L'étiquette ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:183
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "January"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Janvier"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:184
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "February"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Février"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:185
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "March"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mars"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:186
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "April"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Avril"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:187
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "May"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Mai"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:188
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "June"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Juin"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:189
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "July"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Juillet"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:190
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "August"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Août"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:191
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "September"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Septembre"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:192
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "October"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Octobre"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:193
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "November"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Novembre"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:194
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "month"
msgid "December"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Décembre"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:413
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Color can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La couleur ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:414
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "This color is not valid. It must be like #123abc."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Cette couleur n’est pas valide. Il doit être comme #123abc."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:514
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgctxt "action"
msgid "Unset"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Unset"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:545
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Start date can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date de début ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:546
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Start date must be a valid date."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date de début doit être une date valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:548
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "End date can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date de fin ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/season/admin.go:549
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "End date must be a valid date."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date de fin doit être une date valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add admin page to list the users There is no way, for now, to add, edit or remove users, because currently we only need to list users. I can not give admins access to the user table, for security permissions, so i had to create a new view. I could name it also ‘user’ in ‘camper’ scheme, but then i was afraid i would have problems with unit tests and their search_path, so instead i called it ‘company_user_profile’, which is like ‘user_profile’ but for all users in ‘company_user’. I created a new Go package for it, rather than add the admin handler in ‘auth’, because ‘template’ depends on ‘auth’, and rendering from ‘auth’ would cause a dependency loop. I needed to have the roles in gettext to translate them, but there is no obvious place where to put the call to PgettextNoop. For now, there are in ‘NewAdminHandler’ because it is called once in the application’s lifetime and they actually do not matter much.
2024-01-17 18:42:47 +00:00
#: pkg/user/admin.go:18
msgctxt "role"
msgid "guest"
msgstr "invité"
#: pkg/user/admin.go:19
msgctxt "role"
msgid "employee"
msgstr "employé"
#: pkg/user/admin.go:20
msgctxt "role"
msgid "admin"
msgstr "administrateur"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: pkg/surroundings/admin.go:286
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "input"
msgid "Highlight image"
msgstr "Image du point d’intérêt"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: pkg/surroundings/admin.go:287
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
msgctxt "action"
msgid "Set highlight image"
msgstr "Définir l’image du point d’intérêt"
Add ad management for surroundings They only want a single ad (for now, i guess).
2024-01-23 13:53:15 +00:00
#: pkg/surroundings/admin.go:407
msgctxt "input"
msgid "Ad image"
msgstr "Image de l’annonce"
#: pkg/surroundings/admin.go:408
msgctxt "action"
msgid "Set ad image"
msgstr "Définir l’image de l’annonce"
#: pkg/surroundings/admin.go:459
msgid "Ad image can not be empty."
msgstr "L’image de l’annonce ne peut pas être vide."
#: pkg/surroundings/admin.go:460
msgid "Ad image must be an image media type."
msgstr "L’image de l’annonce doit être de type média d’image."
#: pkg/surroundings/admin.go:464
msgid "The title can not be empty."
msgstr "Le titre ne peut pas être vide."
#: pkg/surroundings/admin.go:465
msgid "The link text can not be empty."
msgstr "Le texte du lien ne peut pas être vide."
#: pkg/surroundings/admin.go:466
msgid "The ad URL can not be empty"
msgstr "L’addresse du lien ne peut pas être vide."
#: pkg/surroundings/admin.go:467 pkg/company/admin.go:221
msgid "This web address is not valid. It should be like https://domain.com/."
msgstr "Cette adresse web n’est pas valide. Il devrait en être https://domain.com/."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:200 pkg/booking/public.go:521
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Selected country is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le pays sélectionné n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:204
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Business name can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nom de l’entreprise ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:205
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Business name must have at least two letters."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nom de l’entreprise doit comporter au moins deux lettres."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:207
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "VAT number can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le numéro de TVA ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:208
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "This VAT number is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ce numéro de TVA n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:212 pkg/booking/public.go:539
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Phone can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le téléphone ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:213 pkg/booking/public.go:540
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "This phone number is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ce numéro de téléphone n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:223 pkg/booking/public.go:529
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Address can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "L’adresse ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:224
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "City can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La ville ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:225
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Province can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La province ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:226 pkg/booking/public.go:531
msgid "Postcode can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le code postal ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/company/admin.go:227 pkg/booking/public.go:532
msgid "This postcode is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Ce code postal n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:231
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "RTC number can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le numéro RTC ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:232
msgid "Tourist tax can not be empty."
msgstr "La taxe touristique ne peut pas être vide."
#: pkg/company/admin.go:233
msgid "Tourist tax must be a decimal number."
msgstr "La taxe touristique doit être un nombre décimal."
#: pkg/company/admin.go:234
msgid "Tourist tax must be zero or greater."
msgstr "La taxe touristique doit être égal ou supérieur à zéro."
#: pkg/company/admin.go:237
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Selected currency is not valid."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La devise sélectionnée n’est pas valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add tourist tax to company Not used anywhere yet, but i will need it when computing the booking’s total.
2024-01-14 01:09:17 +00:00
#: pkg/company/admin.go:239
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Invoice number format can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le format du numéro de facture ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#: pkg/auth/user.go:40
msgid "Cross-site request forgery detected."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Détection d’une falsification de requête intersites."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/media/admin.go:312
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Uploaded file can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le fichier téléchargé ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#: pkg/media/admin.go:371
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Filename can not be empty."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "Le nom de fichier ne peut pas être vide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: pkg/booking/cart.go:153
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "cart"
msgid "Night"
msgstr "Nuit"
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: pkg/booking/cart.go:154
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "cart"
msgid "Adult"
msgstr "Adulte"
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: pkg/booking/cart.go:155
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "cart"
msgid "Teenager"
msgstr "Adolescent"
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: pkg/booking/cart.go:156
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgctxt "cart"
msgid "Child"
msgstr "Enfant"
Show a disclaimer on top of book button that it is in fact a prebooking
2024-02-15 14:54:22 +00:00
#: pkg/booking/cart.go:157
Add campsite_type_pet_cost relation to hold price of dogs in campsites It is a separate relation, instead of having a field in campsite_type, because not all campsite types allow dogs. I could have added a new field to campsite_type, but then its values it would be meaningless for campsites that do not allow dogs, and a nullable field is not a valid solution because NULL means “unknown”, but we **do** know the price — none. A separate relation encodes the same information without ambiguities nor null values, and, in fact, removed the dogs_allowed field from campsite_type to prevent erroneous status, such as a campsite type that allows dogs without having a cost — even if the cost is zero, it has to be added to the new relation.
2024-02-10 05:18:30 +00:00
msgctxt "cart"
msgid "Dog"
msgstr "Chien"
Add the admin page to see payments Had to do a couple of changes to the database: add the currency_code to the payment relation, to format the price according to the payment’s currency instead of the company’s; and the reference SQL function, to replace the equivalent golang function, so that i can use it to index payments. The rest is mostly the same as any other page, except that the individual payment’s page is not a form, but a regular info dump. I also moved the payment settings as a sub-route of payments, as i believe this makes more sense than an additional user menu item.
2024-02-14 03:54:42 +00:00
#: pkg/booking/admin.go:126
Add “part” of the bookings’ management “Part”, because it is not possible to add or actually manage any booking yet, but it has the export feature that we need to validate the project.
2024-01-18 20:05:30 +00:00
msgctxt "filename"
msgid "bookings.ods"
msgstr "reservations.ods"
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:276 pkg/booking/public.go:305
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "Arrival date must be a valid date."
msgstr "La date d’arrivée doit être une date valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:290 pkg/booking/public.go:312
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "Departure date must be a valid date."
msgstr "La date de départ doit être une date valide."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:304
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Arrival date can not be empty"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date d’arrivée ne peut pas être vide"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:306
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#, c-format
msgid "Arrival date must be %s or after."
msgstr "La date d’arrivée doit être égale ou postérieure à %s."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:307
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#, c-format
msgid "Arrival date must be %s or before."
msgstr "La date d’arrivée doit être antérieure ou égale à %s."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:311
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
msgid "Departure date can not be empty"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "La date de départ ne peut pas être vide"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:313
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#, c-format
msgid "Departure date must be %s or after."
msgstr "La date de départ doit être égale ou postérieure à %s."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:314
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#, c-format
msgid "Departure date must be %s or before."
msgstr "La date de départ doit être antérieure ou égale à %s."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:356
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#, c-format
msgid "There can be at most %d guests in this accommodation."
msgstr "Il peut y avoir au plus %d invités dans cet hébergement."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:376
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of adults can not be empty"
msgstr "Le nombre d’adultes ne peut pas être vide."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:377
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of adults must be an integer."
msgstr "Le nombre d’adultes doit être un entier."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:378
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "There must be at least one adult."
msgstr "Il doit y avoir au moins un adulte."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:381
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of teenagers can not be empty"
msgstr "Le nombre d’adolescents ne peut pas être vide."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:382
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of teenagers must be an integer."
msgstr "Le nombre d’adolescents doit être un entier."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:383
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of teenagers can not be negative."
msgstr "Le nombre d’adolescents ne peut pas être négatif."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:386
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of children can not be empty"
msgstr "Le nombre d’enfants ne peut pas être vide."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:387
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of children must be an integer."
msgstr "Le nombre d’enfants doit être un entier."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:388
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of children can not be negative."
msgstr "Le nombre d’enfants ne peut pas être négatif."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:391
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of dogs can not be empty"
msgstr "Le nombre de chiens ne peut pas être vide."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:392
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of dogs must be an integer."
msgstr "Le nombre de chiens nuits être un entier."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:393
Compute and show the “cart” for the booking form I have to ask number and age ranges of hosts of guests for all campsite types, not only those that have price options for adults, children, etc. because i must compute the tourist tax for adults. These numbers will be used to generate de rows for guests when actually creating the booking, which is not done already. To satisfy the campsite types that do have a price per guest, not only per night, i had to add the prices for each range in the campsite_type_cost relation. If a campsite type does not have price per person, then that should be zero; the website then does not display the price. The minimal price for any campsite type is one adult for one night, thus to compute the price i need at least the campsite type, the dates, and the number of adults, that has a minimum of one. I changed the order of the form to ask for these values first, so i can compute the initial price as soon as possible. To help further, i show the <fieldset>s progressively when visitors select options.
2024-02-04 05:37:25 +00:00
msgid "Number of dogs can not be negative."
msgstr "Le nombre de chiens ne peut pas être négatif."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:464
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#, c-format
msgid "%s can not be empty"
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "%s ne peut pas être vide"
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:465
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#, c-format
msgid "%s must be an integer."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "%s doit être un entier."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:466
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#, c-format
msgid "%s must be %d or greater."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "%s doit être %d ou plus."
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:467
Add French’s Gettext file, with very little translations I do not know enough French to do the full translations, but i wanted to make sure that it would work.
2023-12-13 22:55:43 +00:00
#, c-format
msgid "%s must be at most %d."
Add French translations
2023-12-20 12:01:52 +00:00
msgstr "%s doit être tout au plus %d."
Updated translations
2023-12-22 02:32:40 +00:00
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:525
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "Full name can not be empty."
msgstr "Le nom complet ne peut pas être vide."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:526
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "Full name must have at least one letter."
msgstr "Le nom complet doit comporter au moins une lettre."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#: pkg/booking/public.go:530
msgid "Town or village can not be empty."
msgstr "La ville ne peut pas être vide."
#: pkg/booking/public.go:545
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
msgid "It is mandatory to agree to the reservation conditions."
msgstr "Il est obligatoire d’accepter les conditions de réservation."
Make address, postcode, and city require for booking Customer changed their mind.
2024-02-24 19:03:11 +00:00
#~ msgid "Postal code can not be empty."
#~ msgstr "Le code postal ne peut pas être vide."
#~ msgid "This postal code is not valid."
#~ msgstr "Ce code postal n’est pas valide."
#~ msgctxt "input"
#~ msgid "Address (optional)"
#~ msgstr "Adresse (Facultatif)"
#~ msgctxt "input"
#~ msgid "Postcode (optional)"
#~ msgstr "Code postal (Facultatif)"
Add ready_payment function and use their slug as URL Now that the payments have slug, i can use them in the URL to show the actual data of a payment, and kickstart the payment process with Redsys.
2024-02-12 17:06:17 +00:00
#~ msgctxt "action"
#~ msgid "Pay"
#~ msgstr "Payer"
Handle the booking cart entirely with HTMx Besides the dynamic final cart, that was already handled by HTMx, i had to check the maximum number of guests, whether the accommodation allows “overflow”, whether dogs are allowed, and that the booking dates were within the campground’s opening and closing dates. I could do all of this with AlpineJS, but then i would have to add the same validation to the backend, prior to accept the payment. Would not make more sense to have them in a single place, namely the backend? With HTMx i can do that. However, i now have to create the form “piecemeal”, because i may not have the whole information when the visitor arrives to the booking page, and i still had the same problem as in commit d2858302efa—parsing the whole form as is would leave guests and options field empty, rather than at their minimum values. One of the fieldsets in that booking form are the arrival and departure dates, that are the sames we use in the campsite type’s page to “preselect” these values. Since now are in a separate struct, i can reuse the same type and validation logic for both pages, making my JavaScript code useless, but requiring HTMx. I think this is a good tradeoff, in fact.
2024-02-10 02:49:44 +00:00
#~ msgctxt "input"
#~ msgid "Check-in Date"
#~ msgstr "Date d'arrivée"
#~ msgctxt "input"
#~ msgid "Check-out Date"
#~ msgstr "Date de départ"
#~ msgid "The departure date must be after the arrival date."
#~ msgstr "La date de départ doit être postérieure à la date d’arrivée."
Add management of surroundings’ highlights (points of interest) Customer does not want the new “masonry-like” design of the surroundings page, and wants the same style they already had: a regular list with text and photo, alternating the photo’s side. And, of course, they want to be able to add and edit them themselves. It is like another carousel, but with an additional rich-text description. The photos that we had in that page are no longer of use.
2024-01-16 00:25:25 +00:00
#~ msgid "Campsite Montagut is an ideal starting point for quiet outings, climbing, swimming in the river and gorges, volcanoes, the Fageda d’en Jordà, cycle tours for all ages…."
#~ msgstr "Le camping Montagut est un point de départ idéal pour des sorties tranquilles, de l’escalade, des baignades dans la rivière et les gorges, les volcans, la Fageda dâen Jordã, des randonnées à vélo pour tous les âges…."
#~ msgid "Get to the Costa Brava and enjoy the beaches, the gastronomy or go kayaking…."
#~ msgstr "Rendez-vous sur la Costa Brava et profitez des plages, de la gastronomie ou faites du kayak…."
#~ msgid "You will also find museums in Olot, Figures, Girona."
#~ msgstr "Vous trouverez également des musées à Olot, Figures, Gérone."
#~ msgid "As well as music festivals, dance, theater…."
#~ msgstr "Ainsi que des festivals de musique, de danse, de théâtre…."
Add position to services to be able to manually sort by admins
2024-01-13 00:15:24 +00:00
#~ msgctxt "header"
#~ msgid "Translations"
#~ msgstr "Traductions"
#~ msgctxt "title"
#~ msgid "Translate Season to %s"
#~ msgstr "Traduire Season en %s"
#~ msgid "Source:"
#~ msgstr "Source :"
#~ msgctxt "input"
#~ msgid "Translation:"
#~ msgstr "Traduction :"
#~ msgctxt "action"
#~ msgid "Translate"
#~ msgstr "Traduire"
#~ msgctxt "title"
#~ msgid "Translate Service to %s"
#~ msgstr "Traduire le service en %s"
Use I18nInput instead of L10nInput to translate carousels
2024-01-12 18:33:44 +00:00
#~ msgctxt "title"
#~ msgid "Translate Carousel Slide to %s"
#~ msgstr "Traduire la diapositive Carousel en %s"
Replace use of L10NInput with I18nInput for campsite
2024-01-10 20:52:49 +00:00
#~ msgctxt "title"
#~ msgid "Translate Campsite Type Feature to %s"
Add function to delete campsite type features
2024-01-26 21:54:19 +00:00
#~ msgstr "Traduire caractéristique de type de camping en %s"
Replace use of L10NInput with I18nInput for campsite
2024-01-10 20:52:49 +00:00
#~ msgctxt "title"
#~ msgid "Translate Campsite Type Carousel Slide to %s"
#~ msgstr "Convertir Glissière de carrousel de type camping en %s"
#~ msgctxt "title"
#~ msgid "Translate Campsite Type Option to %s"
#~ msgstr "Traduire l’option Type de camping en %s"
#~ msgctxt "title"
#~ msgid "Translate Campsite Type to %s"
#~ msgstr "Traduire Type de camping en %s"
Updated translations
2023-12-22 02:32:40 +00:00
#~ msgid "Starting from %s €/night"
#~ msgstr "À partir de %s €/nuit"
#~ msgctxt "season"
#~ msgid "Closed"
#~ msgstr "Fermé"