Using GetPrivateProfileString to read unicode strings
singurd
write unicode strings from a file ?
Goran
> Can i use GetPrivateProfileString/WritePrivateProfileString to read/
> write unicode strings from a file ?
If you have unicode app and "unicode" file (in Windows parlance,
that's UTF-16 encoding), yes. UTF-8-encoded file didn't work last time
I tried.
Goran.
Joseph M. Newcomer
GetPrivateProfileStringW/WritePrivateProfileStringW.
joe
On Fri, 21 Aug 2009 01:13:22 -0700 (PDT), singurd <sin...@yahoo.com> wrote:
>Can i use GetPrivateProfileString/WritePrivateProfileString to read/
>write unicode strings from a file ?
Joseph M. Newcomer [MVP]
email: newc...@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
Mihai N.
> write unicode strings from a file ?
Trick: if the file does not exist, or exists but it is not Unicode, then
the functions will convert everything to ANSI.
If you want to be unicode, then create an empty file with a BOM only
(FE FF) and then everything you write will be Unicode.
http://blogs.msdn.com/michkap/archive/2006/09/15/754992.aspx
--
Mihai Nita [Microsoft MVP, Visual C++]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
Serge Wautier
haven't had problems.
--
Serge.
http://www.apptranslator.com - Localization tool for your MFC applications
"Goran" <goran...@gmail.com> wrote in message
news:fd7257b6-8139-429d...@e27g2000yqm.googlegroups.com...
Joseph M. Newcomer
a hyperlink to your document?
joe
On Sat, 22 Aug 2009 01:04:10 -0700, "Mihai N." <nmihai_y...@yahoo.com> wrote:
>> Can i use GetPrivateProfileString/WritePrivateProfileString to read/
>> write unicode strings from a file ?
>
>Trick: if the file does not exist, or exists but it is not Unicode, then
>the functions will convert everything to ANSI.
>If you want to be unicode, then create an empty file with a BOM only
>(FE FF) and then everything you write will be Unicode.
>
>http://blogs.msdn.com/michkap/archive/2006/09/15/754992.aspx
Scot T Brennecke
only for compatibility with 16-bit versions of Windows. Applications should store initialization information in the registry." back
in 16-bit days, we didn't even have Unicode.
Mihai N.
> document, with a hyperlink to your document?
> joe
That is not my blog, it belongs to Michael Kaplan (MS)
Joseph M. Newcomer
with the design, but it needs to say that. According to the cited article, this fact is
not documented.
Note that I primarily am reporting errors of documentation. Sometimes I point out that
the design is flawed. But mostly, it is the omission of crtical information that should
have been written down.
The issue of "carrying settings around" sometimes suggests .INI files, so more people use
them than Microsoft intended. So the reality is that this behavior needs to be
documented, and the failure to provide clear documentation of this interesting behavior is
the "error" I want to cite.
joe
Joseph M. Newcomer
in the URL and thought it was yours, until I went back to re-read it. So I'll just put a
pointer in my page that references the blog value.
joe
On Sat, 22 Aug 2009 14:49:47 -0700, "Mihai N." <nmihai_y...@yahoo.com> wrote:
>> Fascinating! Could I incorporate parts of that article into my MSDN Errors
>> document, with a hyperlink to your document?
>> joe
>
>That is not my blog, it belongs to Michael Kaplan (MS)
Scot T Brennecke
the file. Otherwise, the function creates a file using ANSI characters."
WritePrivateProfileString Function (Windows):
http://msdn.microsoft.com/en-us/library/ms725501.aspx
WritePrivateProfileSection Function (Windows):
http://msdn.microsoft.com/en-us/library/ms725500.aspx
Joseph M. Newcomer
WritePrivateProfileString. For example, I had assumed if I called
WritePrivateProfileStringW, I would get a Unicode version of the file, but the article
makes it clear that this really only deals with the input arguments, not the file format.
The fact that the file *cannot* be created as Unicode solely by the APIs is not at all
obvious from those statements.
joe
Scot T Brennecke
portable settings files, XML format is a much more useful choice.
Goran
> I've used UTF-8 encoded values in ANSI ini files a couple of times and
> haven't had problems.
>
> --
>
> "Goran" <goran.pu...@gmail.com> wrote in message
>
> news:fd7257b6-8139-429d...@e27g2000yqm.googlegroups.com...
> On Aug 21, 10:13 am, singurd <sing...@yahoo.com> wrote:
>
> > Can i use GetPrivateProfileString/WritePrivateProfileString to read/
> > write unicode strings from a file ?
>
> If you have unicode app and "unicode" file (in Windows parlance,
> that's UTF-16 encoding), yes. UTF-8-encoded file didn't work last time
> I tried.
>
> Goran.
I saved my text with Notepad as UTF-8 (so, with BOM), tried reading
back, and didn't get what I expected. I just re-tried, it's the same.
How did you do it?
Goran.
Mihai N.
Must be UTF-16
singurd
Thanks to all
Its all in the file actualy, so i created the unicode file using the
code from the codeproject site.
_TCHAR bom = (_TCHAR)0xFEFF;
CFile* pFile = new CFile();
pFile->Open( strFile, CFile::modeCreate | CFile::modeWrite );
pFile->Write( &bom, sizeof(_TCHAR) );
pFile->Write( LPCTSTR(m_Text), m_Text.GetLength()*sizeof(_TCHAR) );
pFile->Close();
now the strFile file can contain unicode characters
David Ching
news:001e298e-884e-4b47...@l35g2000pra.googlegroups.com...
> Thanks to all
> Its all in the file actualy, so i created the unicode file using the
> code from the codeproject site.
>
> _TCHAR bom = (_TCHAR)0xFEFF;
>
> CFile* pFile = new CFile();
> pFile->Open( strFile, CFile::modeCreate | CFile::modeWrite );
> pFile->Write( &bom, sizeof(_TCHAR) );
> pFile->Write( LPCTSTR(m_Text), m_Text.GetLength()*sizeof(_TCHAR) );
> pFile->Close();
>
> now the strFile file can contain unicode characters
>
>
Didn't Joe say you could just use the 'W' version of e.g.
WritePrivateProfileString --> WritePrivateProfileStringW, and it would
create a UTF-16 .ini file if it didn't already exist? That sounds much
easier.
-- David
Joseph M. Newcomer
joe