On Thu, Apr 25, 2019 at 2:59 AM Ivan Zhakov wrote:
> [X] Please drop 8-bit and focus only on utf-8 resource names on Win32.
>
> The only problem I see that it would harder to backport fixes to
> stable branches. What about release apr 1.8 without ANSI logic?
>
That isn't possible by my reading
On Wed, Apr 24, 2019 at 9:31 PM William A Rowe Jr wrote:
>
> Committers and community both, please choose one below,
[X] Please drop 8-bit and focus only on utf-8 resource names on Win32.
I have found the problem and its in the way I setup CFLAGS and LDFLAGS.
In the past it was necessary to setup the env like this so that the build use
the Mac OSX SDK so that you can target older Mac OSX releases:
export
On Thu, Apr 25, 2019 at 06:31:50PM +0100, Barry Scott wrote:
> > On 25 Apr 2019, at 10:19, Stefan Sperling wrote:
> > On Wed, Apr 24, 2019 at 08:31:12PM -0500, A. Wilcox wrote:
> >> On 04/24/19 13:39, William A Rowe Jr wrote:
> >>> On Wed, Apr 24, 2019 at 1:04 PM Barry Scott >>>
On 04/24/2019 09:31 PM, William A Rowe Jr wrote:
> Some 17 years later we are at a crossroads, because the win32 code
> is somewhat illegible and harder to maintain due to the ANSI-vs-UTF8,
> Win9x-vs-NT code paths.
>
> NT won. The only remaining question is how many apr consumers are
>
