Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #21001 > unrolled thread

Re: wcout issue

Started byDave Angel <d@davea.name>
First post2012-02-28 14:32 -0500
Last post2012-02-28 14:32 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: wcout issue Dave Angel <d@davea.name> - 2012-02-28 14:32 -0500

#21001 — Re: wcout issue

FromDave Angel <d@davea.name>
Date2012-02-28 14:32 -0500
SubjectRe: wcout issue
Message-ID<mailman.257.1330457550.3037.python-list@python.org>
On 02/27/2012 10:26 PM, Ben Held wrote:
> Hello,
>
> After upgrading from Python 2.6 to 3.2 in our application we noticed that after calling Py_Initialize, our output from std::wcout has extra spaces in it:
>
> wcout<<  L"Just a test\n";
>
> now prints out:
>
> J u s t  a  t e s t
>
> Any clue why?
>
>
> Ben Held
>
>

Have you tried capturing this output, and looking at it with a hex 
viewer?  Are the characters really space, or could they be nulls?  If 
the latter, perhaps it's outputting ucs2 for Unicode.  (I have no 
further ideas, just trying to provoke some experimentation)



-- 

DaveA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web