On 4 February 2017 at 21:23, Hendrik Leppkes wrote:
> On Sat, Feb 4, 2017 at 10:29 AM, Carl Eugen Hoyos
> wrote:
> > 2017-02-04 10:25 GMT+01:00 Hendrik Leppkes :
> >
> >> Another MSVC workaround is an undocumented compiler pragma,
On Sat, Feb 4, 2017 at 10:29 AM, Carl Eugen Hoyos wrote:
> 2017-02-04 10:25 GMT+01:00 Hendrik Leppkes :
>
>> Another MSVC workaround is an undocumented compiler pragma, which
>> works in 2013, but not in 2012 (#pragma
>> execution_character_set("utf-8")),
2017-02-04 10:25 GMT+01:00 Hendrik Leppkes :
> Another MSVC workaround is an undocumented compiler pragma, which
> works in 2013, but not in 2012 (#pragma
> execution_character_set("utf-8")), but adding pragmas to files is also
> not something you can just easily hide away
On Sat, Feb 4, 2017 at 10:25 AM, Hendrik Leppkes wrote:
> On Sat, Feb 4, 2017 at 5:50 AM, Matt Oliver wrote:
>> On 4 February 2017 at 02:32, Hendrik Leppkes wrote:
>>
>>> On Fri, Feb 3, 2017 at 3:05 PM, James Almer
On Sat, Feb 4, 2017 at 5:50 AM, Matt Oliver wrote:
> On 4 February 2017 at 02:32, Hendrik Leppkes wrote:
>
>> On Fri, Feb 3, 2017 at 3:05 PM, James Almer wrote:
>> > On 2/3/2017 5:41 AM, Hendrik Leppkes wrote:
>> >> Without the
On 4 February 2017 at 02:32, Hendrik Leppkes wrote:
> On Fri, Feb 3, 2017 at 3:05 PM, James Almer wrote:
> > On 2/3/2017 5:41 AM, Hendrik Leppkes wrote:
> >> Without the /UTF-8 switch, the MSVC compiler treats all files as in the
> >> system codepage,
On Fri, Feb 3, 2017 at 3:05 PM, James Almer wrote:
> On 2/3/2017 5:41 AM, Hendrik Leppkes wrote:
>> Without the /UTF-8 switch, the MSVC compiler treats all files as in the
>> system codepage, instead of in UTF-8, which causes UTF-8 string literals
>> to be interpreted wrong.
>>
On 2/3/2017 5:41 AM, Hendrik Leppkes wrote:
> Without the /UTF-8 switch, the MSVC compiler treats all files as in the
> system codepage, instead of in UTF-8, which causes UTF-8 string literals
> to be interpreted wrong.
>
> This switch was only introduced in VS2015 Update 2, and any earlier
>
Without the /UTF-8 switch, the MSVC compiler treats all files as in the
system codepage, instead of in UTF-8, which causes UTF-8 string literals
to be interpreted wrong.
This switch was only introduced in VS2015 Update 2, and any earlier
versions do not have an equivalent solution.
Fixes