feat: resource charset support#2440
Conversation
311604e to
e6d3860
Compare
|
@klopfdreh could you add some documentation for this? |
|
Sure 👍- beside the java doc where do I have to add it? |
|
Somewhere in here. Not sure if you think there is a good spot to mention this new feature. Let me know what you think. We could add a new page as well. |
|
I am going to add some documentation as soon as possible in this ticket. Main reason for the feature is that if you use other characters not covered by UTF-8 you can configure the client that a given charset is set for requests and the server is reading and delivering the resource with that charset. |
|
Thanks! It would be a good one to add to our 2024 release! |
e6d3860 to
959797e
Compare
959797e to
9f46331
Compare
|
As I remember from the previous PR I provided 2024 is 4.1.x, so I changed the base of the PR to this branch. I added some documentation into the ascii doc pages. The file |
|
I want to keep this in main as it is new functionality. |
|
Thanks for merging this feature. |

Fixes: #2115
Edit: In the web-view git shows the foo_enc.properties in a wrong way. In the IDE however it is encoded as intended. I added a hint in the
.gitattributesso thatUTF-8is used. Lets see if the build is working and the fetch is using the proper encoding.