- 15 Mar, 2023 40 commits
-
-
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
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
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
-
Aurel authored
-
Rafael Monnerat authored
See merge request !1754
-
Jérome Perrin authored
This fixes some regressions introduced by !1545 when searching the catalog for non ascii text See merge request !1752
-
Jérome Perrin authored
Using unicode with a catalog key or related key got broken in the merge of zope4 support, but using unicode on a translated key (such as translated_portal_type or translated_validation_state_title) was not working before.
-
Jérome Perrin authored
-
Jérome Perrin authored
it supports text, but unless they have non-ASCI characters, so it's better to always pass bytes.
-
Jérome Perrin authored
In original Products.ZSQLMethods, this is text, we want to keep the same semantics and encode only at a lower level.
-