Public account pages, plus the validation messages behind their forms.
| File |
Strings |
user/register.php |
~67 |
user/reset2.php |
~22 |
user/login.php |
~21 |
user/reset.php |
~14 |
librairies/Utils/Validateur.php |
~38 |
user/dashboard.php is out of scope: it is the entry point to the edit forms, which stay French, and translating it alone would produce a half-English path.
Validateur
The ~38 messages in Validateur.php (lines 72 through 288) are shared with the back-office forms, which stay French. Once they are catalogue keys, the back-office simply resolves them in fr — no branching needed.
If #213 has landed with the i18n constraint, this part is already done. That is why it is the highest-return constraint on the parent issue: the work is In Progress right now.
Watch-outs
A form field that is emptied posts nothing. The formulaire=ok marker is what must drive redisplay, not isset($_POST[$field]) — the "POST OR database" pattern. Any translated error message has to be reachable through that path, not only on first display.
The site suite is read-only, and several of its tests rely on a form rejecting invalid input. Loosening a validation to accommodate a translation would silently turn a read-only test into one that writes to the database. Mutate a rule to check a test still means something before trusting it.
user/reset2.php is reached from an emailed link whose token stays valid for 24 hours, and the redirect for the old user-reset2.php URL exists for that reason (htaccess/50-routage.conf, covered by RoutageTest). The language parameter must not break that path.
Emails themselves stay French — the templates in resources/templates/ are out of scope for this milestone.
Public account pages, plus the validation messages behind their forms.
user/register.phpuser/reset2.phpuser/login.phpuser/reset.phplibrairies/Utils/Validateur.phpuser/dashboard.phpis out of scope: it is the entry point to the edit forms, which stay French, and translating it alone would produce a half-English path.Validateur
The ~38 messages in
Validateur.php(lines 72 through 288) are shared with the back-office forms, which stay French. Once they are catalogue keys, the back-office simply resolves them infr— no branching needed.If #213 has landed with the i18n constraint, this part is already done. That is why it is the highest-return constraint on the parent issue: the work is In Progress right now.
Watch-outs
A form field that is emptied posts nothing. The
formulaire=okmarker is what must drive redisplay, notisset($_POST[$field])— the "POST OR database" pattern. Any translated error message has to be reachable through that path, not only on first display.The
sitesuite is read-only, and several of its tests rely on a form rejecting invalid input. Loosening a validation to accommodate a translation would silently turn a read-only test into one that writes to the database. Mutate a rule to check a test still means something before trusting it.user/reset2.phpis reached from an emailed link whose token stays valid for 24 hours, and the redirect for the olduser-reset2.phpURL exists for that reason (htaccess/50-routage.conf, covered byRoutageTest). The language parameter must not break that path.Emails themselves stay French — the templates in
resources/templates/are out of scope for this milestone.