Re: [naviserver-devel] NaviServer/4.99.16 vs NaviServer/4.99.25
You are a magician !
On Sun, Jun 18, 2023 at 1:44 PM Gustaf Neumann wrote:
> On 17.06.23 19:08, Sassy Natan wrote:
>
> Is there any way to keep it as it was?
> So encoding convertfrom utf-8 will work like in the past?
>
> The "encoding convertfrom" has not changed, but its output is now properly
> encoded.
>
> The following will probably work for you: add the following section to your
> configuration file (and for other extensions, when you need this).
>
>ns_section ns/encodings {
>ns_param .adp iso8859-1
>}
>
> I am not sure, what this will mean for Tcl9 though.
>
> all the best
>
> -g
>
> ___
> naviserver-devel mailing list
> naviserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>
--
Regards,
Sassy Natan
972-(0)54-2203702
___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] NaviServer/4.99.16 vs NaviServer/4.99.25
On 17.06.23 19:08, Sassy Natan wrote:
Is there any way to keep it as it was?
So encoding convertfrom utf-8 will work like in the past?
The "encoding convertfrom" has not changed, but its output is now
properly encoded.
The following will probably work for you: add the following section to your
configuration file (and for other extensions, when you need this).
ns_section ns/encodings {
ns_param .adp iso8859-1
}
I am not sure, what this will mean for Tcl9 though.
all the best
-g
___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] NaviServer/4.99.16 vs NaviServer/4.99.25
Thank you! The problem is that in my code I was using the encoding convertfrom utf-8 in many places and since I'm in the process of upgrading my system to the new version of NaviSever I will need to maintain two versions of the code. One for the old server and one for the new server. It is not trivial as it sounds as the development cycle of my product is running in parallel in both versions. Is there any way to keep it as it was? So encoding convertfrom utf-8 will work like in the past? even if there is a security bridge? Thank You On Sat, Jun 17, 2023 at 7:27 PM Gustaf Neumann wrote: > Dear Sassy, > > Why do you say that the output right next to text utf-8 is broken? > > You simply do not need the extra [encoding convertfrom utf-8 ... ] in > versions after 4.99.23 in text pages.The UTF-8 handling in earlier > versions was broken. > > The changes in 4.99.23 were triggered by requests of full emoji support > (in UTF-8 multi-byte characters, up to 4 bytes). The changes effect > also the DB-Interface, such that now such multi-byte characters are > fully supported in display and storing. Look e.g.: > https://openacs.org/xowiki/text-with-hebrew > > > One more thing to note is that the log file which also has UTF-8 > characters is not translated. I see the escape characters instead of the > data. > > This is exactly the same answer as in you earlier question. There are > several known attacks based on Unicode, which can as well be used to > trick the person reading the log-file. > > If you do not care about the log file sanitizing and you prefer the old > behavior, turn sanitizing off. > > all the best > > -gn > > > > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Regards, Sassy Natan 972-(0)54-2203702 ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] NaviServer/4.99.16 vs NaviServer/4.99.25
Dear Sassy, Why do you say that the output right next to text utf-8 is broken? You simply do not need the extra [encoding convertfrom utf-8 ... ] in versions after 4.99.23 in text pages.The UTF-8 handling in earlier versions was broken. The changes in 4.99.23 were triggered by requests of full emoji support (in UTF-8 multi-byte characters, up to 4 bytes). The changes effect also the DB-Interface, such that now such multi-byte characters are fully supported in display and storing. Look e.g.: https://openacs.org/xowiki/text-with-hebrew > One more thing to note is that the log file which also has UTF-8 characters is not translated. I see the escape characters instead of the data. This is exactly the same answer as in you earlier question. There are several known attacks based on Unicode, which can as well be used to trick the person reading the log-file. If you do not care about the log file sanitizing and you prefer the old behavior, turn sanitizing off. all the best -gn ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
