If user still has a cookie from a previous run this this will cause
problems.

This is a dirty workaround. Why configurator has to use cookies ?

https://www.erp5.com/erp5-HowTo.Create.Action.Dialogs
> The action must use an intermediate dialog, where the user can enter parameters.

Also allow to set a name for the business configuration that will be
created.

 * fix typo in column name
 * add editable field for correct display

I'm not sure this workflow is used, just fix the transition which were
using non existant dialog or wrong transitions names.

... otherwise when nothing is selected it looks like something is set.

Also translate and sort output.

Slapos build does not seem to support gif.

* it should be a *list* mode listbox (it was a view mode)
* listbox column title should be the portal type name ( no written rule for this apparently )
* listbox title should be plural of portal type https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#set-listbox-title-to-plural-of-portal-type-title-if-applicable

my_view_mode_listbox_configuration_save should use my_view_mode_listbox as target, not my_list_mode_listbox

https://www.erp5.com/documentation/developer/guideline/module/erp5-Guideline.Module.Creation/#place-simulation-and-validation-fields-at-bottom-of-right-group

backport nexedi/erp5!740

tests for booking in french language from https://lab.nexedi.com/nexedi/capago/merge_requests/363  needs it, probably on production it should not change anything as with "real zopes" we set the encoding in zope.conf.

66b4b55f did not apply, I just skipped this commit.

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

zope.conf default encoding is also used for responses and converters, so
for consistency we should also force default encoding there.
This is especially useful when running tests, because zope.conf is not
used and default values are used.

https://tools.ietf.org/html/rfc4329#section-7 states that text/javascript is obsolete.

Doesn't really matter in the end because WebPage_viewAsWeb forces the content type.

In HTTP/1.1 , when not specified , charset detault to ISO-8859-1

https://tools.ietf.org/html/rfc2616#section-3.7.1

> media subtypes of the "text"  type are defined to have a default charset value of "ISO-8859-1" when   received via HTTP

Zope adds a charset with default encoding (
https://github.com/zopefoundation/Zope/blob/2.13/src/ZPublisher/HTTPResponse.py#L512-L515 ) but does this only for text/ type, but we serve our javascript as application/javascript

backport nexedi/erp5!825/ for test
failure at
https://lab.nexedi.com/nexedi/capago/merge_requests/360/diffs#note_73137

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

According to pep-0263, python scripts can define encoding magic on
first or second line.
If we use for example such a script:

```python
  # coding: utf-8
  return "héhé"
```

then using .read() was wrong, because it return the script with headers,
ie:

```python
  ## Script (Python) "test_coding"
  ##bind container=container
  ##bind context=context
  ##bind namespace=
  ##bind script=script
  ##bind subpath=traverse_subpath
  ##parameters=
  ##title=
  ##
  # coding: utf-8
  return "héhé"
```

so the coding magic is no longer in first line and pylint complains
with error like:

Cannot decode using encoding "ascii", unexpected byte at position 11 (invalid-encoded-data)]

backport nexedi/erp5!796

mentioned in [Re: Create Bt5 with list of all accounting accounts
?](https://www.erp5.com/project_section/capago-project/forum/Create-Bt5-with-list-of-all-accounting-accounts-HLBp84CyNR/view?list_start=9&reset=1#2019138697)

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

Using a cache cookie that is incremented each time an account is added or modified,
we can keep an (almost) up to date list of accounts in the UI.

Fixes #20170221-1812E21

/reviewed-on nexedi/erp5!796
(cherry picked from commit bbbe264a)

missing in https://lab.nexedi.com/nexedi/erp5-capago/merge_requests/30

Backport nexedi/erp5!799

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

https://microsoft.github.io/monaco-editor/ as an ERP5 source code editor.

Backport nexedi/erp5!687

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

Just set indentation rules for now

Because typescript is a subset of javascript, running typescript
compiler on javascript files can already report several issues.

https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html

This is triggered by using "Format document" from context menu.

Include prettier 1.14.0 Copyright 2017-2018 James Long
https://github.com/prettier/prettier/

So that we can edit web pages & web scripts with monaco

So that javascript editor provides hints for code using these libraries.

Some pointers for type scripts definitions:
https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html
https://definitelytyped.org/

In the previous approach, several "useless" request were still made
during edition.

https://microsoft.github.io/monaco-editor/ as an ERP5 source code editor

this commit is only a build of the vendor code.

It was built using https://lab.nexedi.com/jerome/monaco-editor-erp5/ at
revision 9d7f8b5 and uploaded to ERP5 following this procedure:

First enable webdav by adding in zope conf:
```
<webdav-source-server>
  address 127.0.0.1:12200
  force-connection-close off
</webdav-source-server>
```

This was built and uploaded to ERP5 with:
```bash
git clone https://lab.nexedi.com/jerome/monaco-editor-erp5.git/
cd monaco-editor-erp5
npm
npm run build
lftp http://login:pwd@127.0.0.1:12200/erp5/portal_skins/erp5_monaco_editor/monaco-editor/ -e 'mput dist/*'
```

instead of building HTML in python, it's cleaner and prevent problems when attachments names are HTML entities.

because storing as document depends on erp5_ingestion & erp5_dms

So that conversion is done by a zope activity node and not on a front
node.