 |
Where in the docs does it say that you can use anything non-ascii for a resource name? If it is documented like that it is simply wrong and we would have to update the documentation. |
|
|
I have read this documentation: https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html Under the section "Character Sets" https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html#character-sets is written, that bareos will use UTF-8 encodings. And in the section of the name resource there is only spoken of alphanumeric characters. So for example an 'ä' is an normal character. So then there must be an hint here, that only asciii chars, are allowed here. Because for options that accept an string, utf-8 chars are working. |
|
|
In the data-type section at https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html#data-types there is the following description: """ A keyword or name consisting of alphanumeric characters, including the hyphen, underscore, and dollar characters. The first character of a name must be a letter. A name has a maximum length currently set to 127 bytes. Please note that Bareos resource names as well as certain other names (e.g. Volume names) must contain only letters (including ISO accented letters), numbers, and a few special characters (space, underscore, …). All other characters and punctuation are invalid. """ We can improve the documentation for that quite a lot. However, I'm not sure it is sufficient to do it here. Do you think we should add another hint somewhere else? |
|
|
I think it will be better, general say, that only ascii chars are allowed under the general section. Or when possible modify the parser, so that it will accept utf-8 strings on all settings. |
|
|
no changes will occurs without community proposal (PR) or sponsored code. |
- Anonymous
