[request/session] refactor language handling: don't attempt to sync web/repo languages This decouple thing and make code easier to understand. Previous behaviour was fine w/ validation error that were translated on the server side, but isn't satisfying for notification and all. Now: * translations should be done on the ui side (see previous validation error refactoring) * consistent behaviour: each side (web/repo) is responsible to deal with its request/session of language, no weird interaction between them on this topic * drop on the way the 'session properties' api, used only for that matter. -> much simpler/cleaner/saner api The thing missing being a way for user to tell "My favorite language is xxx but I also want cw to consider my http language header)

     1

[MESSAGES CONTROL]

     2

disable-msg = C0301

     3

     4

[VARIABLES]

     5

# Enable / disable this checker

     6

enable-variables = yes

     7

additional-builtins = _, display_name

     8

     9

[BASIC]

    10

required-attributes=

    11

attr-rgx = (w|[a-z_][a-z0-9_]{2,30})

    12

variable-rgx = (w|[a-z_][a-z0-9_]{2,30})$

    13

argument-rgx = (w|[a-z_][a-z0-9_]{2,30})$

    14

    15

[TYPECHECK]

    16

generated-members=debug,info,notice,warning,error,critical,exception