- 13 Jan, 2024 30 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
also str representation of unicode character is different.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Arnaud Fontaine authored
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
- the test was using wrong attribute and it was using DummyLocalizer, which breaks the site configuration. Fix the test and use mock - fix ods style not to translate untranslatable columns
-
Jérome Perrin authored
Page templates have a builtin translation system (with i18n:) and an "unicode conflict resolver", so it was not necessary to explicitly convert to unicode on python2 and this simplifies the transition to python3
-
Jérome Perrin authored
-
Jérome Perrin authored
This list was to cast the tuple, it can cause an AttributeError("'tuple' object has no attribute 'append'",) error when this branch is used. This is really an error code path, so that was unnoticed.
-
Jérome Perrin authored
introduce number:date-style for each of the "input_order" supported by DateTimeField, so that when exported to ODS we have the same input order as in html.
-
Jérome Perrin authored
so that we can test date time fields in listbox columns and listbox stat method easily.
-
Jérome Perrin authored
-
Jérome Perrin authored
With libreoffice5, float fields with input style 12.3% were correctly rendered as percentages without the need of an explicit number:percentage-style style, but with libreoffice7 it seems required, without this, a value of 2.05 is rendered as "2" instead of the expected "205%"
-
Jérome Perrin authored
Instead of duplicating the code for the case where a field value is rendered from a group (left, right etc) of the form and when the field value is rendered from a listbox editable field, reuse the macro also for fields from the form groups. Because fields from the form groups have top and bottom border, we introduce a new style prefix for these fields: "with_border_". Implementation note: We don't declare this new field in Base_getODSSupportedStylePrefixList, because we need to define the cell properties each time, so defining this dynamically is not really interesting.
-
Jérome Perrin authored
remove useless `field python: editable_fields.get(column_id, None)` tal:defines, the macro always documented `field` as required and all callers pass it. document that `style_prefix` is required
-
Jérome Perrin authored
This was set to 1.234,5 but erp5_ods_style does not support this style for now, so set it to a supported value for now so that we can progress with the testing of erp5_ods_style.
-
Jérome Perrin authored
Add a listbox with a figure editable field and a percentage editable field. These fields all have TALES to set precision from "precision" request key.
-
Jérome Perrin authored
See merge request nexedi/erp5!1863
-
- 12 Jan, 2024 1 commit
-
-
Xiaowu Zhang authored
-
- 05 Jan, 2024 3 commits
-
-
Jérome Perrin authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
- 29 Dec, 2023 2 commits
-
-
Roque authored
See merge request nexedi/erp5!1848
-
Roque authored
- landing page - dispatch uses opml-sync parameters - keeps backward compatibility
-
- 28 Dec, 2023 4 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
py2/py3: import InstanceDict from DocumentTemplate._DocumentTemplate instead of deprecated DocumentTemplate.DT_Util.
-