/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/27

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/26

backport nexedi/erp5!694

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/25

See 4bb5d32e

Do not rely on DateTime.strftime which does fails on dates <= 1900.
This simple case does not need all the features of strftime and can be
implemented inline.

It currently fails with such ValueError:
```
year=101 is before 1900; the datetime strftime() methods require year >= 1900
```

backport nexedi/erp5!680

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/24

Because at the moment we don't have SFTP integrated in ERP5 or testnode,
this test will only work if the URL of a running SFTP is set through
testSFTPConnection_SFTP_URL environment variable.

This allows sorting the list of filenames, by size ( sort_on="st_size" ),
by modification date ( sort_on="st_mdate" )

backport nexedi/erp5!666

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/23

All top level documents are not supposed to acquire local roles
https://www.erp5.com/erp5-Guideline.Unset.Acquire.Local.Roles.On.Document.Portal.Type.Configuration.If.Applicable

I believe this comes from the time where we were using images as
sub-documents of products or persons. We now use embedded files for
these cases, so no need to have an exception here.

backport nexedi/erp5!634

This is only a partial backport, we don't have Romain's gadget in this branch

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/22

https://codemirror.net/demo/matchtags.html

makes editions of web pages and xml easier

Backport nexedi/erp5!631

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/21

group_calendar_interaction_workflow introduce interaction on calendar
exception, we should take into account that these calendar exception
also exists in leave request and presence request.

Also rename the test to be more specific and remove useless
organisation.

The interaction should also be triggered if a Calendar Exception is changed.

Revert "erp5_calendar: Improve workflow interaction to update calendar if any sub-object is changed"

This reverts commit c49a7911.

revert just to apply
nexedi/erp5!631 easily

backport nexedi/erp5!630

There was conflicts, because we have already backported
nexedi/erp5!137/

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/19

TODO:

 * [ ] file as bug
 * [ ] unify implementation with Base_getAccountingPeriodStartDateForSectionCategory
 * [ ] MR for nexedi/erp5
 * [ ] capago: stop creating accounting period for durban in `ERP5Site_openCapagoAccountingPeriod`, this was just hiding the bug

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/20

This script was returning organisations in random order !

When organisation does not have accounting periods, but another organisation at the same level of the same group has, the result was undefined.

This fixes by considering all organisation from the same group.

Fix for [#20171205-E91759](https://nexedi.erp5.net/bug_module/20171205-E91759)

Basically extend the change from
24c836a7 to the case where there's an
exception, but the exception does not match and add tests to reproduce
the case.

Backport nexedi/erp5!611

To fix problem reported as [Reports in French even with English selected for the UI](https://www.erp5.com/project_section/capago-project/forum/Reports-in-French-even-with-English-selected-for-the-UI-2iRze6Od6s)


/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/18

Backport of nexedi/erp5!627

to fix test failures from https://lab.nexedi.com/nexedi/capago/merge_requests/302#note_58587

/reviewed-on https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/17

Report content and also notification subject must be translated.

The attachment filename at this point is not translated, but it would be
nice to have I feel.

by evaluating it in a translationContext

Some report sections may be using translation.

Localizer.get_selected_language is only functional in response to user
requests. Saving it in Base_computeReportSection was already too late
because it's already an activity request.