tandem
/
numerus
2
0
Fork 0
Code Issues 37 Pull Requests Packages Projects 1 Releases 1 Wiki Activity
numerus/po/es.po

978 lines
24 KiB
Plaintext
Raw Normal View History

Add Catalan and Spanish translation with gotext[3] I had to choose between [1], [2], and [3]. As far as i could find, [1] is not easy to work with templates[4] and at the moment is not maintained[5]. Both [2] and [3] use the same approach to be used from within templates: you have to define a FuncMap with template functions that call the message catalog. Also, both libraries seems to be reasonably maintained, and have packages in Debian’s repository. However, [2] repeats the same mistakes that POSIX did with its catalogs—using identifiers that are not the strings in the source language—, however this time the catalogs are written in JSON or YAML! This, somehow, makes things worse…. [3], the one i settled with, is fine and decently maintained. There are some surprising things, such as to be able to use directly the PO file, and that it has higher priority over the corresponding MO, or that the order of parameters is reversed in respect to gettext. However, it uses a saner format, and is a lot easier to work with than [3]. The problem, of course, is that xgettext does not know how to find translatable strings inside the template. [3] includes a CLI tool similar to xgettext, but is not a drop-in replacement[6] and does not process templates. The proper way to handle this would be to add a parser to xgettext, but for now i found out that if i surround the call to the translation functions from within the template with parentheses, i can trick xgettext into believing it is parsing Scheme code, and extracts the strings successfully—at least, for what i have tried. Had to add the keyword for pgettext, because Schemed does not have it, but at least i can do that with command line parameters. For now i left only Spanish and Catalan as the two available languages, even though the source text is written in English, because that way i can make sure i do not leave strings untranslated. [1]: https://golang.org/x/text [2]: https://github.com/nicksnyder/go-i18n [3]: https://github.com/leonelquinteros/gotext [4]: https://github.com/golang/go/issues/39954 [5]: https://github.com/golang/go/issues/12750 [6]: https://github.com/leonelquinteros/gotext/issues/38
2023-01-18 18:07:42 +00:00
# Spanish translations for numerus package.
# Copyright (C) 2023 jordi fita mas
# This file is distributed under the same license as the numerus package.
# jordi fita mas <jordi@tandem.blog>, 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: numerus\n"
"Report-Msgid-Bugs-To: jordi@tandem.blog\n"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
"POT-Creation-Date: 2023-05-11 23:31+0200\n"
Add Catalan and Spanish translation with gotext[3] I had to choose between [1], [2], and [3]. As far as i could find, [1] is not easy to work with templates[4] and at the moment is not maintained[5]. Both [2] and [3] use the same approach to be used from within templates: you have to define a FuncMap with template functions that call the message catalog. Also, both libraries seems to be reasonably maintained, and have packages in Debian’s repository. However, [2] repeats the same mistakes that POSIX did with its catalogs—using identifiers that are not the strings in the source language—, however this time the catalogs are written in JSON or YAML! This, somehow, makes things worse…. [3], the one i settled with, is fine and decently maintained. There are some surprising things, such as to be able to use directly the PO file, and that it has higher priority over the corresponding MO, or that the order of parameters is reversed in respect to gettext. However, it uses a saner format, and is a lot easier to work with than [3]. The problem, of course, is that xgettext does not know how to find translatable strings inside the template. [3] includes a CLI tool similar to xgettext, but is not a drop-in replacement[6] and does not process templates. The proper way to handle this would be to add a parser to xgettext, but for now i found out that if i surround the call to the translation functions from within the template with parentheses, i can trick xgettext into believing it is parsing Scheme code, and extracts the strings successfully—at least, for what i have tried. Had to add the keyword for pgettext, because Schemed does not have it, but at least i can do that with command line parameters. For now i left only Spanish and Catalan as the two available languages, even though the source text is written in English, because that way i can make sure i do not leave strings untranslated. [1]: https://golang.org/x/text [2]: https://github.com/nicksnyder/go-i18n [3]: https://github.com/leonelquinteros/gotext [4]: https://github.com/golang/go/issues/39954 [5]: https://github.com/golang/go/issues/12750 [6]: https://github.com/leonelquinteros/gotext/issues/38
2023-01-18 18:07:42 +00:00
"PO-Revision-Date: 2023-01-18 17:45+0100\n"
"Last-Translator: jordi fita mas <jordi@tandem.blog>\n"
"Language-Team: Spanish <es@tp.org.es>\n"
"Language: es\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"
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
#: web/template/invoices/products.gohtml:2
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/products.gohtml:23
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Add Products to Invoice"
msgstr "Añadir productos a la factura"
#: web/template/invoices/products.gohtml:9 web/template/invoices/new.gohtml:9
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/index.gohtml:9 web/template/invoices/view.gohtml:9
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
#: web/template/invoices/edit.gohtml:9 web/template/contacts/new.gohtml:9
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/contacts/index.gohtml:9 web/template/contacts/edit.gohtml:10
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: web/template/profile.gohtml:9 web/template/expenses/new.gohtml:10
#: web/template/expenses/index.gohtml:10 web/template/expenses/edit.gohtml:10
#: web/template/tax-details.gohtml:9 web/template/products/new.gohtml:9
#: web/template/products/index.gohtml:9 web/template/products/edit.gohtml:10
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Home"
msgstr "Inicio"
#: web/template/invoices/products.gohtml:10 web/template/invoices/new.gohtml:10
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/index.gohtml:2 web/template/invoices/index.gohtml:10
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
#: web/template/invoices/view.gohtml:10 web/template/invoices/edit.gohtml:10
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Invoices"
msgstr "Facturas"
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
#: web/template/invoices/products.gohtml:12 web/template/invoices/new.gohtml:2
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/new.gohtml:11 web/template/invoices/new.gohtml:19
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "New Invoice"
msgstr "Nueva factura"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/products.gohtml:48
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: web/template/products/index.gohtml:38
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "product"
msgid "All"
msgstr "Todos"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/products.gohtml:49
#: web/template/products/index.gohtml:39
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Name"
msgstr "Nombre"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/products.gohtml:50
#: web/template/invoices/view.gohtml:62 web/template/products/index.gohtml:41
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Price"
msgstr "Precio"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/products.gohtml:64
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/products/index.gohtml:81
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "No products added yet."
msgstr "No hay productos."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/products.gohtml:72 web/template/invoices/new.gohtml:62
#: web/template/invoices/edit.gohtml:62
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "action"
msgid "Add products"
msgstr "Añadir productos"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/new.gohtml:39 web/template/invoices/view.gohtml:67
#: web/template/invoices/edit.gohtml:39
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
msgctxt "title"
msgid "Subtotal"
msgstr "Subtotal"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/new.gohtml:49 web/template/invoices/view.gohtml:71
#: web/template/invoices/view.gohtml:111 web/template/invoices/edit.gohtml:49
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
msgctxt "title"
msgid "Total"
msgstr "Total"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/new.gohtml:66 web/template/invoices/edit.gohtml:66
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "action"
msgid "Update"
msgstr "Actualizar"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/new.gohtml:68 web/template/invoices/index.gohtml:20
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "action"
msgid "New invoice"
msgstr "Nueva factura"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/index.gohtml:18
Add button to download many invoices as PDF in a ZIP archive
2023-03-09 11:11:53 +00:00
msgctxt "action"
msgid "Download invoices"
msgstr "Descargar facturas"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/invoices/index.gohtml:40 web/template/contacts/index.gohtml:32
#: web/template/expenses/index.gohtml:34 web/template/products/index.gohtml:32
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgctxt "action"
msgid "Filter"
msgstr "Filtrar"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:46
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "invoice"
msgid "All"
msgstr "Todas"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:47 web/template/invoices/view.gohtml:34
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Date"
msgstr "Fecha"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:48
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Invoice Num."
msgstr "Nº factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/invoices/index.gohtml:49 web/template/contacts/index.gohtml:39
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Customer"
msgstr "Cliente"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:50
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
msgid "Status"
msgstr "Estado"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/invoices/index.gohtml:51 web/template/contacts/index.gohtml:42
#: web/template/expenses/index.gohtml:44 web/template/products/index.gohtml:40
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
Add invoice tags I followed the same restrictions as Gitea’s topics, arbitrarily, because if it is enough for repositories it should be for invoices too, apparently.
2023-03-10 13:02:55 +00:00
msgid "Tags"
msgstr "Etiquetes"
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/invoices/index.gohtml:52 web/template/expenses/index.gohtml:45
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "title"
Add views to compute taxes and total amount of invoices They are not functions because i need to join them with the main invoice relation, and although possible is a bit more awkward with functions. The taxes have their own relation because i will need them grouped by their name in the PDF, so it will probably be a select for that relation.
2023-02-22 13:39:38 +00:00
msgid "Amount"
msgstr "Importe"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:53
Add views to compute taxes and total amount of invoices They are not functions because i need to join them with the main invoice relation, and although possible is a bit more awkward with functions. The taxes have their own relation because i will need them grouped by their name in the PDF, so it will probably be a select for that relation.
2023-02-22 13:39:38 +00:00
msgctxt "title"
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Download"
msgstr "Descargar"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/invoices/index.gohtml:54 web/template/contacts/index.gohtml:43
#: web/template/expenses/index.gohtml:46 web/template/products/index.gohtml:42
Add the context menu with the duplicate option As per the design document.
2023-03-08 10:54:06 +00:00
msgctxt "title"
msgid "Actions"
msgstr "Acciones"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:61
Add button to download many invoices as PDF in a ZIP archive
2023-03-09 11:11:53 +00:00
msgctxt "action"
msgid "Select invoice %v"
msgstr "Seleccionar factura %v"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:116 web/template/invoices/view.gohtml:19
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/contacts/index.gohtml:69 web/template/expenses/index.gohtml:77
#: web/template/products/index.gohtml:71
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgctxt "action"
msgid "Edit"
msgstr "Editar"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:124 web/template/invoices/view.gohtml:16
Add the context menu with the duplicate option As per the design document.
2023-03-08 10:54:06 +00:00
msgctxt "action"
msgid "Duplicate"
msgstr "Duplicar"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/index.gohtml:134
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "No invoices added yet."
msgstr "No hay facturas."
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:2 web/template/invoices/view.gohtml:33
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
msgctxt "title"
msgid "Invoice %s"
msgstr "Factura %s"
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:22
Convert invoices to PDF with WeasyPrint Although it is possible to just print the invoice from the browser, many people will not even try an assume that they can not create a PDF for the invoice. I thought of using Groff or TeX to create the PDF, but it would mean maintaining two templates in two different systems (HTML and whatever i would use), and would probably look very different, because i do not know Groff or TeX that well. I wish there was a way to tell the browser to print to PDF, and it can be done, but only with the Chrome Protocol to a server-side running Chrome instance. This works, but i would need a Chrome running as a daemon. I also wrote a Qt application that uses QWebEngine to print the PDF, much like wkhtmltopdf, but with support for more recent HTML and CSS standards. Unfortunately, Qt 6.4’s embedded Chromium does not follow break-page-inside as well as WeasyPrint does. To use WeasyPrint, at first i wanted to reach the same URL as the user, passing the cookie to WeasyPrint so that i can access the same invoice as the user, something that can be done with wkhtmltopdf, but WeasyPrint does not have such option. I did it with a custom Python script, but then i need to package and install that script, that is not that much work, but using the Debian-provided script is even less work, and less likely to drift when WeasyPrint changes API. Also, it is unnecessary to do a network round-trip from Go to Python back to Go, because i can already write the invoice HTML as is to WeasyPrint’s stdin.
2023-02-26 16:26:09 +00:00
msgctxt "action"
msgid "Download invoice"
msgstr "Descargar factura"
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:61
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
msgctxt "title"
msgid "Concept"
msgstr "Concepto"
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:64
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
msgctxt "title"
msgid "Discount"
msgstr "Descuento"
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:66
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
msgctxt "title"
msgid "Units"
msgstr "Unidades"
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#: web/template/invoices/view.gohtml:101
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
msgctxt "title"
msgid "Tax Base"
msgstr "Base imponible"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/invoices/edit.gohtml:2 web/template/invoices/edit.gohtml:19
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgctxt "title"
msgid "Edit Invoice “%s”"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgstr "Edición de la factura «%s»"
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/invoices/edit.gohtml:68
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgctxt "action"
msgid "Edit invoice"
msgstr "Editar factura"
Move page titles to their respective templates I have been thinking about that, and it does not make that much sense to have the titles in the Go source anymore: most of them are static text that i have to remember to set in the controller each time, and when the time come i have to face a dynamic title i am sure i will manage with only the template capabilities—worst comes worst, i can always define a function. On the other hand, there is no way i can define a template without its title and i know that everytime that template is used, no matter what controller rendered it, it will always have that title.
2023-01-31 12:07:17 +00:00
#: web/template/dashboard.gohtml:2
Add Catalan and Spanish translation with gotext[3] I had to choose between [1], [2], and [3]. As far as i could find, [1] is not easy to work with templates[4] and at the moment is not maintained[5]. Both [2] and [3] use the same approach to be used from within templates: you have to define a FuncMap with template functions that call the message catalog. Also, both libraries seems to be reasonably maintained, and have packages in Debian’s repository. However, [2] repeats the same mistakes that POSIX did with its catalogs—using identifiers that are not the strings in the source language—, however this time the catalogs are written in JSON or YAML! This, somehow, makes things worse…. [3], the one i settled with, is fine and decently maintained. There are some surprising things, such as to be able to use directly the PO file, and that it has higher priority over the corresponding MO, or that the order of parameters is reversed in respect to gettext. However, it uses a saner format, and is a lot easier to work with than [3]. The problem, of course, is that xgettext does not know how to find translatable strings inside the template. [3] includes a CLI tool similar to xgettext, but is not a drop-in replacement[6] and does not process templates. The proper way to handle this would be to add a parser to xgettext, but for now i found out that if i surround the call to the translation functions from within the template with parentheses, i can trick xgettext into believing it is parsing Scheme code, and extracts the strings successfully—at least, for what i have tried. Had to add the keyword for pgettext, because Schemed does not have it, but at least i can do that with command line parameters. For now i left only Spanish and Catalan as the two available languages, even though the source text is written in English, because that way i can make sure i do not leave strings untranslated. [1]: https://golang.org/x/text [2]: https://github.com/nicksnyder/go-i18n [3]: https://github.com/leonelquinteros/gotext [4]: https://github.com/golang/go/issues/39954 [5]: https://github.com/golang/go/issues/12750 [6]: https://github.com/leonelquinteros/gotext/issues/38
2023-01-18 18:07:42 +00:00
msgctxt "title"
Move page titles to their respective templates I have been thinking about that, and it does not make that much sense to have the titles in the Go source anymore: most of them are static text that i have to remember to set in the controller each time, and when the time come i have to face a dynamic title i am sure i will manage with only the template capabilities—worst comes worst, i can always define a function. On the other hand, there is no way i can define a template without its title and i know that everytime that template is used, no matter what controller rendered it, it will always have that title.
2023-01-31 12:07:17 +00:00
msgid "Dashboard"
msgstr "Panel"
Add Catalan and Spanish translation with gotext[3] I had to choose between [1], [2], and [3]. As far as i could find, [1] is not easy to work with templates[4] and at the moment is not maintained[5]. Both [2] and [3] use the same approach to be used from within templates: you have to define a FuncMap with template functions that call the message catalog. Also, both libraries seems to be reasonably maintained, and have packages in Debian’s repository. However, [2] repeats the same mistakes that POSIX did with its catalogs—using identifiers that are not the strings in the source language—, however this time the catalogs are written in JSON or YAML! This, somehow, makes things worse…. [3], the one i settled with, is fine and decently maintained. There are some surprising things, such as to be able to use directly the PO file, and that it has higher priority over the corresponding MO, or that the order of parameters is reversed in respect to gettext. However, it uses a saner format, and is a lot easier to work with than [3]. The problem, of course, is that xgettext does not know how to find translatable strings inside the template. [3] includes a CLI tool similar to xgettext, but is not a drop-in replacement[6] and does not process templates. The proper way to handle this would be to add a parser to xgettext, but for now i found out that if i surround the call to the translation functions from within the template with parentheses, i can trick xgettext into believing it is parsing Scheme code, and extracts the strings successfully—at least, for what i have tried. Had to add the keyword for pgettext, because Schemed does not have it, but at least i can do that with command line parameters. For now i left only Spanish and Catalan as the two available languages, even though the source text is written in English, because that way i can make sure i do not leave strings untranslated. [1]: https://golang.org/x/text [2]: https://github.com/nicksnyder/go-i18n [3]: https://github.com/leonelquinteros/gotext [4]: https://github.com/golang/go/issues/39954 [5]: https://github.com/golang/go/issues/12750 [6]: https://github.com/leonelquinteros/gotext/issues/38
2023-01-18 18:07:42 +00:00
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:23
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "menu"
msgid "Account"
msgstr "Cuenta"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:29
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "menu"
msgid "Tax Details"
msgstr "Configuración fiscal"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:37
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "action"
msgid "Logout"
msgstr "Salir"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:46
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "nav"
Add nav link to dashboard
2023-01-31 12:29:56 +00:00
msgid "Dashboard"
msgstr "Panel"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:47
Add nav link to dashboard
2023-01-31 12:29:56 +00:00
msgctxt "nav"
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Invoices"
msgstr "Facturas"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/app.gohtml:48
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "nav"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Expenses"
msgstr "Gastos"
#: web/template/app.gohtml:49
msgctxt "nav"
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "Products"
msgstr "Productos"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: web/template/app.gohtml:50
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "nav"
Rename Customer to Contact That section is intended for both customers and suppliers, collectively called “contacts”.
2023-02-01 09:14:26 +00:00
msgid "Contacts"
msgstr "Contactos"
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
#: web/template/contacts/new.gohtml:2 web/template/contacts/new.gohtml:11
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/contacts/new.gohtml:19
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "New Contact"
msgstr "Nuevo contacto"
#: web/template/contacts/new.gohtml:10 web/template/contacts/index.gohtml:2
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/contacts/index.gohtml:10 web/template/contacts/edit.gohtml:11
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Contacts"
msgstr "Contactos"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/contacts/new.gohtml:36 web/template/contacts/index.gohtml:14
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "action"
msgid "New contact"
msgstr "Nuevo contacto"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/contacts/index.gohtml:38
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "contact"
msgid "All"
msgstr "Todos"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/contacts/index.gohtml:40
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Email"
msgstr "Correo-e"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/contacts/index.gohtml:41
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Phone"
msgstr "Teléfono"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/contacts/index.gohtml:79
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "No contacts added yet."
msgstr "No hay contactos."
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/contacts/edit.gohtml:3 web/template/contacts/edit.gohtml:20
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Edit Contact “%s”"
msgstr "Edición del contacto «%s»"
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/contacts/edit.gohtml:41
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "action"
msgid "Update contact"
msgstr "Actualizar contacto"
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
#: web/template/login.gohtml:2 web/template/login.gohtml:15
Move page titles to their respective templates I have been thinking about that, and it does not make that much sense to have the titles in the Go source anymore: most of them are static text that i have to remember to set in the controller each time, and when the time come i have to face a dynamic title i am sure i will manage with only the template capabilities—worst comes worst, i can always define a function. On the other hand, there is no way i can define a template without its title and i know that everytime that template is used, no matter what controller rendered it, it will always have that title.
2023-01-31 12:07:17 +00:00
msgctxt "title"
msgid "Login"
msgstr "Entrada"
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
#: web/template/login.gohtml:19
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "action"
msgid "Login"
msgstr "Entrar"
Add breadcrumbs
2023-02-03 12:58:10 +00:00
#: web/template/profile.gohtml:2 web/template/profile.gohtml:10
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/profile.gohtml:18
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "title"
msgid "User Settings"
msgstr "Configuración usuario"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/profile.gohtml:22
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "title"
msgid "User Access Data"
msgstr "Datos acceso usuario"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/profile.gohtml:28
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "title"
msgid "Password Change"
msgstr "Cambio de contraseña"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/profile.gohtml:35
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgctxt "title"
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgid "Language"
msgstr "Idioma"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/profile.gohtml:39 web/template/tax-details.gohtml:172
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "action"
msgid "Save changes"
msgstr "Guardar cambios"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: web/template/expenses/new.gohtml:3 web/template/expenses/new.gohtml:12
#: web/template/expenses/new.gohtml:20
msgctxt "title"
msgid "New Expense"
msgstr "Nuevo gasto"
#: web/template/expenses/new.gohtml:11 web/template/expenses/index.gohtml:3
#: web/template/expenses/index.gohtml:11 web/template/expenses/edit.gohtml:11
msgctxt "title"
msgid "Expenses"
msgstr "Gastos"
#: web/template/expenses/new.gohtml:32 web/template/expenses/index.gohtml:15
msgctxt "action"
msgid "New expense"
msgstr "Nuevo gasto"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/expenses/index.gohtml:40
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
msgctxt "expense"
msgid "All"
msgstr "Todos"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/expenses/index.gohtml:41
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "title"
msgid "Contact"
msgstr "Contacto"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/expenses/index.gohtml:42
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "title"
msgid "Invoice Date"
msgstr "Fecha de factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/expenses/index.gohtml:43
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "title"
msgid "Invoice Number"
msgstr "Número de factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: web/template/expenses/index.gohtml:87
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "No expenses added yet."
msgstr "No hay gastos."
#: web/template/expenses/edit.gohtml:3 web/template/expenses/edit.gohtml:20
msgctxt "title"
msgid "Edit Expense “%s”"
msgstr "Edición del gasto «%s»"
#: web/template/expenses/edit.gohtml:35
msgctxt "action"
msgid "Update expense"
msgstr "Actualizar gasto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:2 web/template/tax-details.gohtml:10
#: web/template/tax-details.gohtml:18
Add missing Catalan and Spanish translations
2023-01-30 09:52:22 +00:00
msgctxt "title"
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgid "Tax Details"
msgstr "Configuración fiscal"
Add missing Catalan and Spanish translations
2023-01-30 09:52:22 +00:00
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:35
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "title"
Add fieldset for currency in tax details page
2023-01-28 11:24:52 +00:00
msgid "Currency"
msgstr "Moneda"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:41
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "title"
msgid "Invoicing"
Add company’s default payment method I had to use a deferrable foreign key because the payment methods have a reference to the company, and the company now a circular reference to payment method.
2023-03-04 21:15:52 +00:00
msgstr "Facturación"
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:53
msgid "Are you sure?"
msgstr "¿Estáis seguro?"
#: web/template/tax-details.gohtml:59
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
msgctxt "title"
msgid "Tax Name"
msgstr "Nombre impuesto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:60
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
msgctxt "title"
msgid "Rate (%)"
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgstr "Porcentaje"
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:61
Introduce the concept of tax class We want to show the percentage of the tax as columns in the invoice, but until now it was not possible to have a single VAT column when products have different VAT (e.g., 4 % and 10 %), because, as far as the application is concerned, these where ”different taxes”. We also think it would be hard later on to compute the tax due to the government. So, tax classes is just a taxonomy to be able to have different names and rates for the same type of tax, mostly VAT and retention in our case.
2023-02-28 11:02:27 +00:00
msgctxt "title"
msgid "Class"
msgstr "Clase"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:85
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
msgid "No taxes added yet."
msgstr "No hay impuestos."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:91 web/template/tax-details.gohtml:152
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
msgctxt "title"
msgid "New Line"
msgstr "Nueva línea"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:105
Add the tax relation with very rough form and handler
2023-01-28 13:18:58 +00:00
msgctxt "action"
msgid "Add new tax"
msgstr "Añadir nuevo impuesto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:121
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "title"
msgid "Payment Method"
msgstr "Método de pago"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:122
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "title"
msgid "Instructions"
msgstr "Instrucciones"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:146
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgid "No payment methods added yet."
msgstr "No hay métodos de pago."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/tax-details.gohtml:164
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "action"
msgid "Add new payment method"
msgstr "Añadir nuevo método de pago"
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
#: web/template/products/new.gohtml:2 web/template/products/new.gohtml:11
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: web/template/products/new.gohtml:19
Rename extension of templates to .gohtml Apparently, there are tools that only know how to use that extensions when referring to Go templates.
2023-01-30 15:48:21 +00:00
msgctxt "title"
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "New Product"
msgstr "Nuevo producto"
#: web/template/products/new.gohtml:10 web/template/products/index.gohtml:2
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/products/index.gohtml:10 web/template/products/edit.gohtml:11
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Products"
msgstr "Productos"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/products/new.gohtml:30 web/template/products/index.gohtml:14
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "action"
msgid "New product"
msgstr "Nuevo producto"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/products/search.gohtml:12
msgid "No products found."
msgstr "No se ha encontrado ningún producto."
Boost the products’ section links and forms Had to add the editProductPage because now i need to know the slug in order to build the form’s action link. I also added the `ProductName` field because it was less awkward than using `.Form.Name` everywhere.
2023-03-27 07:44:04 +00:00
#: web/template/products/edit.gohtml:3 web/template/products/edit.gohtml:20
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "title"
msgid "Edit Product “%s”"
msgstr "Edición del producto «%s»"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: web/template/products/edit.gohtml:34
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "action"
msgid "Update product"
msgstr "Actualizar producto"
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/login.go:36 pkg/profile.go:40 pkg/contacts.go:268
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Email"
msgstr "Correo-e"
#: pkg/login.go:47 pkg/profile.go:49
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
msgctxt "input"
msgid "Password"
msgstr "Contraseña"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/login.go:69 pkg/profile.go:89 pkg/contacts.go:365
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
msgid "Email can not be empty."
msgstr "No podéis dejar el correo-e en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/login.go:70 pkg/profile.go:90 pkg/contacts.go:366
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
msgid "This value is not a valid email. It should be like name@domain.com."
msgstr "Este valor no es un correo-e válido. Tiene que ser parecido a nombre@dominio.es."
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/login.go:72
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
msgid "Password can not be empty."
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgstr "No podéis dejar la contraseña en blanco."
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/login.go:108
Use a “proper” struct for the login form Similar to the profile form, the login form now parses and validates itself, with the InputField structs that the templates expect. I realized that i was doing more work than necessary when parsing fields fro the profile form because i was repeating the operation and the field name, so now it is a function of InputField. This time i needed extra attributes for the login form. I am not sure that the Go source code needs to know about HTML attributes, but it was the easiest way to pass them to the template.
2023-02-01 10:02:32 +00:00
msgid "Invalid user or password."
msgstr "Nombre de usuario o contraseña inválido."
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:164 pkg/products.go:263 pkg/invoices.go:776
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:135
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "input"
msgid "Name"
msgstr "Nombre"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:169 pkg/products.go:290 pkg/expenses.go:193
#: pkg/expenses.go:343 pkg/invoices.go:187 pkg/invoices.go:597
#: pkg/invoices.go:1044 pkg/contacts.go:140 pkg/contacts.go:325
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgctxt "input"
msgid "Tags"
msgstr "Etiquetes"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:173 pkg/expenses.go:347 pkg/invoices.go:191
#: pkg/contacts.go:144
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgctxt "input"
msgid "Tags Condition"
msgstr "Condición de las etiquetas"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:177 pkg/expenses.go:351 pkg/invoices.go:195
#: pkg/contacts.go:148
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgctxt "tag condition"
msgid "All"
msgstr "Todas"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:178 pkg/expenses.go:352 pkg/invoices.go:196
#: pkg/contacts.go:149
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgid "Invoices must have all the specified labels."
msgstr "Las facturas deben tener todas las etiquetas."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:182 pkg/expenses.go:356 pkg/invoices.go:200
#: pkg/contacts.go:153
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgctxt "tag condition"
msgid "Any"
msgstr "Cualquiera"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:183 pkg/expenses.go:357 pkg/invoices.go:201
#: pkg/contacts.go:154
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgid "Invoices must have at least one of the specified labels."
msgstr "Las facturas debent tener como mínimo una de las etiquetas."
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:269 pkg/invoices.go:790
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "input"
msgid "Description"
msgstr "Descripción"
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:274 pkg/invoices.go:794
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "input"
msgid "Price"
msgstr "Precio"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:284 pkg/expenses.go:177 pkg/invoices.go:823
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgctxt "input"
Allow multiple taxes, and even not tax, for products It seems that we do not agree en whether the IRPF tax should be something of the product or the contact, so we decided to make the product have multiple taxes, just in case, and if only one is needed, then users can just select one; no need to limit to one.
2023-02-08 12:47:36 +00:00
msgid "Taxes"
msgstr "Impuestos"
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:309 pkg/profile.go:92 pkg/invoices.go:867
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "Name can not be empty."
msgstr "No podéis dejar el nombre en blanco."
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:310 pkg/invoices.go:868
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "Price can not be empty."
msgstr "No podéis dejar el precio en blanco."
Moved the link to edit expense from the invoicer’s name to a menu This menu will also have options like delete, and whatever we like to do to expenses, like invoices do.
2023-05-06 09:08:21 +00:00
#: pkg/products.go:311 pkg/invoices.go:869
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "Price must be a number greater than zero."
msgstr "El precio tiene que ser un número mayor a cero."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:313 pkg/expenses.go:215 pkg/expenses.go:220
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:877
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
msgid "Selected tax is not valid."
msgstr "Habéis escogido un impuesto que no es válido."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/products.go:314 pkg/expenses.go:216 pkg/expenses.go:221
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:878
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
msgid "You can only select a tax of each class."
Add company’s default payment method I had to use a deferrable foreign key because the payment methods have a reference to the company, and the company now a circular reference to payment method.
2023-03-04 21:15:52 +00:00
msgstr "Solo podéis escoger un impuesto de cada clase."
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
#: pkg/company.go:98
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Currency"
msgstr "Moneda"
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
#: pkg/company.go:105
msgctxt "input"
msgid "Invoice number format"
msgstr "Formato del número de factura"
#: pkg/company.go:111
msgctxt "input"
msgid "Legal disclaimer"
msgstr "Nota legal"
#: pkg/company.go:129
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Selected currency is not valid."
msgstr "Habéis escogido una moneda que no es válida."
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
#: pkg/company.go:130
msgid "Invoice number format can not be empty."
msgstr "No podéis dejar el formato del número de factura en blanco."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:297
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Tax name"
msgstr "Nombre impuesto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:303
Introduce the concept of tax class We want to show the percentage of the tax as columns in the invoice, but until now it was not possible to have a single VAT column when products have different VAT (e.g., 4 % and 10 %), because, as far as the application is concerned, these where ”different taxes”. We also think it would be hard later on to compute the tax due to the government. So, tax classes is just a taxonomy to be able to have different names and rates for the same type of tax, mostly VAT and retention in our case.
2023-02-28 11:02:27 +00:00
msgctxt "input"
msgid "Tax Class"
msgstr "Clase de impuesto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:306
Introduce the concept of tax class We want to show the percentage of the tax as columns in the invoice, but until now it was not possible to have a single VAT column when products have different VAT (e.g., 4 % and 10 %), because, as far as the application is concerned, these where ”different taxes”. We also think it would be hard later on to compute the tax due to the government. So, tax classes is just a taxonomy to be able to have different names and rates for the same type of tax, mostly VAT and retention in our case.
2023-02-28 11:02:27 +00:00
msgid "Select a tax class"
msgstr "Escoged una clase de impuesto"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:310
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Rate (%)"
msgstr "Porcentaje"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:333
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Tax name can not be empty."
msgstr "No podéis dejar el nombre del impuesto en blanco."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:334
Introduce the concept of tax class We want to show the percentage of the tax as columns in the invoice, but until now it was not possible to have a single VAT column when products have different VAT (e.g., 4 % and 10 %), because, as far as the application is concerned, these where ”different taxes”. We also think it would be hard later on to compute the tax due to the government. So, tax classes is just a taxonomy to be able to have different names and rates for the same type of tax, mostly VAT and retention in our case.
2023-02-28 11:02:27 +00:00
msgid "Selected tax class is not valid."
msgstr "Habéis escogido una clase impuesto que no es válida."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:335
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Tax rate can not be empty."
msgstr "No podéis dejar el porcentaje en blanco."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:336
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Tax rate must be an integer between -99 and 99."
msgstr "El porcentaje tiene que estar entre -99 y 99."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:399
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "input"
msgid "Payment method name"
msgstr "Nombre del método de pago"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:405
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgctxt "input"
msgid "Instructions"
msgstr "Instrucciones"
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:423
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgid "Payment method name can not be empty."
msgstr "No podéis dejar el nombre del método de pago en blanco."
Show the tax details form in a dialog using HTMx
2023-03-21 10:58:54 +00:00
#: pkg/company.go:424
Add the payment method relation and corresponding form
2023-03-03 15:49:06 +00:00
msgid "Payment instructions can not be empty."
msgstr "No podéis dejar las instrucciones de pago en blanco."
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/profile.go:25
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgctxt "language option"
msgid "Automatic"
msgstr "Automático"
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/profile.go:31
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgctxt "input"
msgid "User name"
msgstr "Nombre de usuario"
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/profile.go:57
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgctxt "input"
msgid "Password Confirmation"
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgstr "Confirmación contraseña"
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
Add the edit contact page
2023-02-03 12:29:10 +00:00
#: pkg/profile.go:65
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgctxt "input"
msgid "Language"
msgstr "Idioma"
Allow optional select with empty label This is not yet necessary, but the empty label is because i do not want to select a default tax for products—at least, not without a setting for it. Since i need to add the required attribute now to select, because otherwise the browser would allow sending that empty value, i did not want to do it unconditionally, just in case.
2023-02-05 13:06:33 +00:00
#: pkg/profile.go:93
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgid "Confirmation does not match password."
msgstr "La confirmación no corresponde con la contraseña."
Allow optional select with empty label This is not yet necessary, but the empty label is because i do not want to select a default tax for products—at least, not without a setting for it. Since i need to add the required attribute now to select, because otherwise the browser would allow sending that empty value, i did not want to do it unconditionally, just in case.
2023-02-05 13:06:33 +00:00
#: pkg/profile.go:94
Validate profile form and use templates for fields Let’s start first with a non-fancy validation method with just if conditionals instead of bringing yet another complicated library. I hope i do not regret it. I wanted to move all the input field to a template because all that gobbledygook with the .input div and repeating the label in the placeholder was starting to annoy me. Now with error messages was even more concerning. I did not know whether the label should be a part of the input fields or something that the template should do. At the end i decided that it makes more sense to be part of the input field because in the error messages i use that same label, thus the template does not have a say in that, and, besides, it was just easier to write the template. The same with the error messages: i’ve seen frameworks that have a map with the field’s id/name to the error slice, but then it would be a bit harder to write the template. I added AddError functions instead of just using append inside the validator function, and have a local variable for whether it all went OK, because i was worried that i would leave out the `ok = false` in some conditions. I had started writing “constructors” functions for InputField and SelectField, but then had to add other methods to change the required field and who knows what else, and in the end it was easier to just construct the field inline.
2023-01-31 14:40:12 +00:00
msgid "Selected language is not valid."
msgstr "Habéis escogido un idioma que no es válido."
Rename Customer to Contact That section is intended for both customers and suppliers, collectively called “contacts”.
2023-02-01 09:14:26 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:126
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Select a contact."
msgstr "Escoged un contacto"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:160
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "input"
msgid "Contact"
msgstr "Contacto"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:166
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "input"
msgid "Invoice number"
msgstr "Número de factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:171 pkg/invoices.go:586
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "input"
msgid "Invoice Date"
msgstr "Fecha de factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:183
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgctxt "input"
msgid "Amount"
msgstr "Importe"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:213
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Selected contact is not valid."
msgstr "Habéis escogido un contacto que no es válido."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:214 pkg/invoices.go:641
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Invoice date must be a valid date."
msgstr "La fecha de factura debe ser válida."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:217
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Amount can not be empty."
msgstr "No podéis dejar el importe en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:218
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
msgid "Amount must be a number greater than zero."
msgstr "El importe tiene que ser un número mayor a cero."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:322 pkg/invoices.go:160 pkg/invoices.go:580
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgctxt "input"
msgid "Customer"
msgstr "Cliente"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:323 pkg/invoices.go:161
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgid "All customers"
msgstr "Todos los clientes"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:328 pkg/invoices.go:172
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgctxt "input"
msgid "Invoice Number"
msgstr "Número de factura"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:333 pkg/invoices.go:177
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgctxt "input"
msgid "From Date"
Improve translations to avoid from and to date confusion It turns out that “De la data/fecha” was understood to mean the invoice date, not the first date of a range—“at” instead of “from”.
2023-03-30 09:06:19 +00:00
msgstr "A partir de la fecha"
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/expenses.go:338 pkg/invoices.go:182
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
msgctxt "input"
msgid "To Date"
Improve translations to avoid from and to date confusion It turns out that “De la data/fecha” was understood to mean the invoice date, not the first date of a range—“at” instead of “from”.
2023-03-30 09:06:19 +00:00
msgstr "Hasta la fecha"
Add filters form for invoices Instead of using links in the invoice tags, that we will replace with a “click-to-edit field”, with Oriol agreed to add a form with filters that includes not only the tags but also dates, customer, status, and the invoice number. This means i now need dynamic SQL, and i do not think this belongs to the database (i.e., no PL/pgSQL function for that). I have looked at query builder libraries for Golang, and did not find anything that suited me: either they wanted to manage not only the SQL query but also all structs, or they managed to confuse Goland’s SQL analyzer. For now, at least, i am using a very simple approach with arrays, that still confuses Goland’s analyzer, but just in a very specific part, which i find tolerable—not that their analyzer is that great to begin with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/invoices.go:166 pkg/invoices.go:574
msgctxt "input"
msgid "Invoice Status"
msgstr "Estado de la factura"
#: pkg/invoices.go:167
msgid "All status"
msgstr "Todos los estados"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:423
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Select a customer to bill."
msgstr "Escoged un cliente a facturar."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:524
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgid "invoices.zip"
msgstr "facturas.zip"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:530 pkg/invoices.go:1028
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Invalid action"
msgstr "Acción inválida."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:592
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "input"
msgid "Notes"
msgstr "Notas"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:602
Add company’s default payment method I had to use a deferrable foreign key because the payment methods have a reference to the company, and the company now a circular reference to payment method.
2023-03-04 21:15:52 +00:00
msgctxt "input"
msgid "Payment Method"
msgstr "Método de pago"
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:638
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgid "Selected invoice status is not valid."
msgstr "Habéis escogido un estado de factura que no es válido."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:639
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
msgid "Selected customer is not valid."
msgstr "Habéis escogido un cliente que no es válido."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:640
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Invoice date can not be empty."
msgstr "No podéis dejar la fecha de la factura en blanco."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#: pkg/invoices.go:643
Add company’s default payment method I had to use a deferrable foreign key because the payment methods have a reference to the company, and the company now a circular reference to payment method.
2023-03-04 21:15:52 +00:00
msgid "Selected payment method is not valid."
msgstr "Habéis escogido un método de pago que no es válido."
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:766 pkg/invoices.go:771
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "input"
msgid "Id"
msgstr "Identificador"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:804
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "input"
msgid "Quantity"
msgstr "Cantidad"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:813
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgctxt "input"
msgid "Discount (%)"
msgstr "Descuento (%)"
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:865
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
msgid "Product ID must be a number greater than zero."
msgstr "El ID de producto tiene que ser un número mayor a cero."
Add the edit form for invoices I had to change the way /invoices/new and /invoices/batch are handled, because httprouter was not happy with the new POST /invoices/:slug/edit route, claiming that /invoices/:slug conflicts with the previously existing routes. I also could not make it work with the PATCH method, even though i correctly added the patchMethod override function, therefore editing invoices is also weird because i have to take into account the “quick” invoice status change. I use the same form for both new and edit invoices, because the only changes are that we can not edit the invoice date and number, by Oriol’s design, but must be able to change the status; very similar forms.
2023-03-13 14:00:35 +00:00
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:871
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Quantity can not be empty."
msgstr "No podéis dejar la cantidad en blanco."
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:872
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Quantity must be a number greater than zero."
msgstr "La cantidad tiene que ser un número mayor a cero."
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:874
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Discount can not be empty."
msgstr "No podéis dejar el descuento en blanco."
Add expenses’ index and add form
2023-05-03 10:46:25 +00:00
#: pkg/invoices.go:875
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
msgid "Discount must be a percentage between 0 and 100."
Add company’s default payment method I had to use a deferrable foreign key because the payment methods have a reference to the company, and the company now a circular reference to payment method.
2023-03-04 21:15:52 +00:00
msgstr "El descuento tiene que ser un porcentaje entre 0 y 100."
Add the form to add products to an invoice and create invoices too Still missing: the invoice number, that requires more tables and possibly a PL/pgSQL function to do it properly.
2023-02-12 20:06:48 +00:00
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:238
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Business name"
msgstr "Nombre y apellidos"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:248
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "VAT number"
msgstr "DNI / NIF"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:254
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Trade name"
msgstr "Nombre comercial"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:259
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Phone"
msgstr "Teléfono"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:277
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Web"
msgstr "Web"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:285
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Address"
msgstr "Dirección"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:294
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "City"
msgstr "Población"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:300
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Province"
msgstr "Provincia"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:306
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgctxt "input"
msgid "Postal code"
msgstr "Código postal"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:315
Allow multiple taxes, and even not tax, for products It seems that we do not agree en whether the IRPF tax should be something of the product or the contact, so we decided to make the product have multiple taxes, just in case, and if only one is needed, then users can just select one; no need to limit to one.
2023-02-08 12:47:36 +00:00
msgctxt "input"
msgid "Country"
msgstr "País"
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:353
Allow multiple taxes, and even not tax, for products It seems that we do not agree en whether the IRPF tax should be something of the product or the contact, so we decided to make the product have multiple taxes, just in case, and if only one is needed, then users can just select one; no need to limit to one.
2023-02-08 12:47:36 +00:00
msgid "Selected country is not valid."
msgstr "Habéis escogido un país que no es válido."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:357
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Business name can not be empty."
msgstr "No podéis dejar el nombre y los apellidos en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:358
Add validation for minimum length of contact’s name
2023-04-18 19:01:29 +00:00
msgid "Business name must have at least two letters."
msgstr "El nombre y los apellidos deben contener como mínimo dos letras."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:359
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "VAT number can not be empty."
msgstr "No podéis dejar el DNI o NIF en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:360
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "This value is not a valid VAT number."
msgstr "Este valor no es un DNI o NIF válido."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:362
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Phone can not be empty."
msgstr "No podéis dejar el teléfono en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:363
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "This value is not a valid phone number."
msgstr "Este valor no es un teléfono válido."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:369
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "This value is not a valid web address. It should be like https://domain.com/."
msgstr "Este valor no es una dirección web válida. Tiene que ser parecida a https://dominio.es/."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:371
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Address can not be empty."
msgstr "No podéis dejar la dirección en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:372
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "City can not be empty."
msgstr "No podéis dejar la población en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:373
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Province can not be empty."
msgstr "No podéis dejar la provincia en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:374
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "Postal code can not be empty."
msgstr "No podéis dejar el código postal en blanco."
Add the actions menu to products and contacts
2023-05-11 21:32:21 +00:00
#: pkg/contacts.go:375
Add the edit contact page
2023-02-03 12:29:10 +00:00
msgid "This value is not a valid postal code."
msgstr "Este valor no es un código postal válido válido."
Add keyboard controls for product search They are almost the same as for the multiselect, except that it “clicks” the option to “select” it, as this will trigger the replacement of the <fieldset> with the whole product.
2023-04-27 22:06:48 +00:00
#~ msgid "Product ID can not be empty."
#~ msgstr "No podéis dejar el identificador de producto en blanco."
Replace use of <select> for tags “and” and “or” with checkboxes I realized that using a select for just two, short, options is overkill: the select and its options use a lot more real state than the two radios, which can have tooltips (not yet, though). Since i am going to replace this field with a custom element that has a toggle-like aspect, i already added the is="numerus-toggle" attribute and use it for stying the non-JavaScript field.
2023-04-15 02:05:59 +00:00
#~ msgctxt "input"
#~ msgid "Number"
#~ msgstr "Número"
Add invoice tags I followed the same restrictions as Gitea’s topics, arbitrarily, because if it is enough for repositories it should be for invoices too, apparently.
2023-03-10 13:02:55 +00:00
#~ msgctxt "title"
#~ msgid "Label"
#~ msgstr "Etiqueta"
Allow multiple taxes, and even not tax, for products It seems that we do not agree en whether the IRPF tax should be something of the product or the contact, so we decided to make the product have multiple taxes, just in case, and if only one is needed, then users can just select one; no need to limit to one.
2023-02-08 12:47:36 +00:00
#~ msgid "Select a tax for this product."
#~ msgstr "Escoged un impuesto para este producto."
Add the edit contact page
2023-02-03 12:29:10 +00:00
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
#~ msgctxt "input"
Allow multiple taxes, and even not tax, for products It seems that we do not agree en whether the IRPF tax should be something of the product or the contact, so we decided to make the product have multiple taxes, just in case, and if only one is needed, then users can just select one; no need to limit to one.
2023-02-08 12:47:36 +00:00
#~ msgid "Tax"
#~ msgstr "Impuesto"
Add products section There is still some issues with the price field, because for now it is in cents, but do not have time now to fix that.
2023-02-04 10:32:39 +00:00
Rename Customer to Contact That section is intended for both customers and suppliers, collectively called “contacts”.
2023-02-01 09:14:26 +00:00
#~ msgctxt "title"
#~ msgid "Customers"
#~ msgstr "Clientes"
#~ msgid "No customers added yet."
#~ msgstr "No hay clientes."