On 05.09.20 14:50, Gustaf Neumann wrote:
I did not have time yet to dig into TCLHTTP_USE_EXTERNALTOUTF the
other test cases depending on that. My gut feeling says "this is
necessary", but my brain says "why this was no problem so far" and
"what will be the collateral damage" if we do so.
The flag TCLHTTP_USE_EXTERNALTOUTF is still in the code but needs
further investigation. However, i am going mid of next week on holiday
(boat), where i will not be reachable ... until then many things are
piled up on my side, so i have no chance to look into this deeper
right now.
My plan would be as follows: Prepare a release for the near future (i'll
be at 10 days offline, maybe i can work on change summary etc.). For
this release, leave the TCLHTTP_USE_EXTERNALTOUTF for the time being in
the code (deactivated by default), and address the encoding issue in
detail after that.
Users depending on releases will get a long list of new features with
4.99.20 and they will not be afraid of changed encodings etc. Other
users with complex encoding/recoding requirements can use the new
"-binary" flag of ns_http.
all the best
-g
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
