|
Try the following:
_locale_t locale = _create_locale(LC_CTYPE, "Arabic");
errno_t ret = _wcstombs_s_l(&convertedChars, pToFill, maxCharLen, pWideCharBuf, maxCharLen, locale);
Use the best guess
|
|
|
|
|
Thank you so much sir
It solved my problem.
|
|
|
|
|
Hello Sir,
The solution which you have given is working fine for me in windows machine But now I need to implement the same thing (utf-8 to ascii conversion) in a POS terminal which neither has 'locale.h' nor _wcstombs_s_l in the stdlib.
The POS terminal has linux kernal.My quries are :
1)Instead of using the function _wcstombs_s_l and create_locale can I replace it with the function definition itself.
2)If I can then please if possible provide me the link where I can find the proper definition of these two functions.
3)If i can not then is there any other way to implement utf8 to ascii conversion.
Please help.
Thanks
|
|
|
|
|
|
You should be aware that all solutions involving wcstombs and related depend on the locale and the typical encoding might not be what you call 'ascii'.
Actually, what is called ASCII does not contain any Arabic characters whatsoever. Probably, you are referring to a specific codepage that uses ASCII + some Arabic characters?
In that case, it's probably a good idea to set the proper locale before conversion (see Richard MacCutchans post for info), so you get the correct codepage and not, as you probably get with the code given so far, UTF-8 encoding, which means that the text file will contain multiple bytes per character.
For instance, see http://stackoverflow.com/questions/2190190/wcstombs-character-encoding[^]. Probably something like setlocale( LC_ALL, "ar.1256" ); will do what you need; it should set the codepage to windows 1256 (which is used for arabic) and use the (generic) Arabic locale.
Locales and encoding are a quite complicated issue, so you should be careful and precise when using them. Also, by C++ definition the locale employ system-dependent strings for locale, so if should cater to the platform you are coding for.
|
|
|
|
|
Thanks Sir for your reply.
It solved my problem.
|
|
|
|
|
I want to implement T13 ATA Secure Erase and can not find any documentation. Is something available?
I found this http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml[^]
36. When you surround an army, leave an outlet free.
...
Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
There are other factors to consider besides secure erasure.
Like data remanance, correctly implemented PC BIOS (ie. it hasn't been compromised), PCI cards with onboard BIOS etc. Plus there's the thorny issue of SSD data remanance.
If at all possible the HDD should be encrypted, but not so good with SSD.
harddisk_ata_security_v1.1-1.pdf
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
Thanks for answering to my problem, but I have a simple task and I can`t find documentation on T13 Secure Erase 
36. When you surround an army, leave an outlet free.
...
Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
I had a look at the t13.org website and they allow you download documents if you register and login.
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
Thanks again. I searched the site before. Actually I need something like an API or SDK. 
VII. 36. When you surround an army, leave an outlet free. Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
|
Thanks a lot
VII. 36. When you surround an army, leave an outlet free. Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
David's pointing you to the spec is an excellent answer.
A few things I will add to the mix:
* You will need multiple commands ( SECURITY ERASE PREPARE, SECURITY ERASE UNIT, and possibly other SECURITY commands ) from the spec in order to accomplish a secure erase.
* Sending (single-sector) ATA passthru commands from uesr mode applications is possible on Windows (XP SP2 and newer, IIRC), assuming you have Admin privileges on the system. You will need do some Googling on IOCTL_ATA_PASSTHRU_DIRECT in order to find relevant information.
* That being said, you will still be at the mercy of the system BIOS and possibly the O/S. Once a SECURITY FREEZE LOCK is sent to the drive, it is *generally* difficult or impossible to send SECURITY ERASE to the drive. Some motherboard BIOSs send the SECURITY FREEZE LOCK prior to start of boot just to ensure a drive is not accidentally or maliciously erased.
All of this is from my memory, which is several years old at this point.
|
|
|
|
|
Hello All,
I have a MFC app thats being developed in VS 6.0
If the app is idle for more than 5 mins it should lock automatically.
i.e., the next time when user tries to click anywhere on app, it should ask for user name and password.
Is there any good examples for that?
The closest example i can think of is the screen saver lock in Windows operating system.
Any sample code will help.
Thanks in advance.
|
|
|
|
|
Have a look at this article HOWTO track a user's idle time[^]; it seems to have a good implementation on how to detect the idle time.
When the idle time (five minutes) has been reached you could show a modal dialog that requires the user to specify his/her user name and password.
0100000101101110011001000111001011101001
|
|
|
|
|
|
I have an application that can also run as a service via srvany. It performs a monitoring task and uses the PlaySound method defined in mmsystem.h to play a .wav notification on certain events. It runs fine under XP as an app or as a service.
Under Win7, the app runs fine. But when running as a service under Win7, I get no sound. The "allow service to interact with desktop" option is available but ignored under Win7 as part of Session 0 isolation. I expect this is somehow related.
I'm looking for verification or alternate approaches.
Thanks.
modified 5-Apr-13 13:28pm.
|
|
|
|
|
You are most likely right in your conclusion. I think the session 0 isolation prevents such interactions.
A possible work-around is to have your Service start or interact with a non-service component that runs in the user session.
|
|
|
|
|
I have weird bug: in a MDI aplication, if I mapped OnFileOpen in follow way:
ON_COMMAND(ID_FILE_OPEN, OnFileOpen)
after the document file has opened, the application crashes with follow message:
(KERNELBASE.DLL): 0xC0000005: Access Violation.
but only in Release mode ... in Debug mode, everything is going well ...
if I mapped OnFileOpen in follow way:
ON_COMMAND(ID_FILE_OPEN, CWinApp::OnFileOpen)
again, everything is going well ... did you meet with this behaviour ? Perhaps you give some hint ... Thank you.
|
|
|
|
|
In a Debug build the compiler performs additional tasks, for instance it zeroes variables you haven't initialized (e.g. WinAPI structs) (in Release build the unitialized data contains garbage).
Have a look at the following CodeProject article: "Surviving the Release Version"[^].
Veni, vidi, vici.
|
|
|
|
|
Check your CMyApp::OnFileOpen() code and the functions that are called from there. Comment all lines in that function except the base class CWinApp::OnFileOpen() call and uncomment step by step until the violation occurs. Then you should know which part of your code is responsible.
|
|
|
|
|
Inside of CMyApp::OnFileOpen I didn't call CWinApp:OnFileOpen .. here is the buggy code:
void CMyApp::OnFileOpen(void)
{
CFileDialog dlgFile(TRUE);
dlgFile.DoModal();
return;
}
and in release mode, the application crashes ...
|
|
|
|
|
Even if I used:
void CMyApp::OnFileOpen(void)
{
CFileDialog dlgFile(TRUE);
return;
}
and the application is crashing down ...
|
|
|
|
|
Crashes it in this function or later?
If you did not call CWinApp::OnFileOpen(), no document is created. So the reason for the crash is probably somewhere in your document creation. Did you call OnFileNew() or use ProcessShellCommands() to create a document?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
