I have a VB 6.0 application in which one of the windows needs to display Arabic characters. When it used VSFlexgrid 7 it worked fine, but since upgrading to VSFlexgrid 8 it displays question marks and other "junk" characters. I have references to vsflex8.ocx, vsflex8l.ocx, vsflex8n.ocx and vsflex8u.ocx in the project. Is there something else I need to download, or a setting I need to set somewhere?
Related
In my Visual Studio 2012 application, I just wrote the following:
_snprintf_s(page[row++], NUM_COLS, _TRUNCATE, " Lat: %-11s (\x0b1 %3.1fm)",
lat_string, lat_precision_meters);
The \xb1 is the escape code for the "+/-" symbol, 177 in extended ASCII, ISO 8859.
I read that this was originally a Windows feature with some other name.
This works for me - it shows the correct symbol next to the precision, in my default font.
My question is: have I just introduced an issue for users who override the default font? Are all Microsoft-provisioned fonts ISO 8859-1 compliant?
In xcode it's possible to have characters like "💊" in code. If I paste it to Android Studio it shows me another 2 unicode characters, which don't have anything in common with "💊".
Both editors use UTF-8 encoding AFAIK.
So where is the difference?
Android Studio uses windows-1252 as default and you can use the unicode equivalent:
\uD83D\uDC8A
for example using a TextView:
myTextView.setText("\uD83D\uDC8A");
will create something like (in my device two pills are showed):
Here you can find the equivalent "Java Escape" code :
http://www.charbase.com/1f48a-unicode-pill
After I have moved from Windows Server 2003 to Windows Server 2008 R2, the PDF font issue was encountered.
The description of the issue:
Using Window Server 2003, crystal report is used to export the report to PDF. Using the object tool option in PDF to select the string, we can see the string below contains in one box. (*not enough reputation to post images)
'abcde'
However when Window Server 2008 is used, a different string is produced.
'abcd' 'e'
As you can see, the string is separated into 3 boxes when windows server 2008 is used. Hence, I am unable to use a simple java program to read the string due to the added spaces (about one pixel difference).
The crystal report engine has not been changed. Hence, I susupect that it is due to the window server font issue, but have no idea how to rectifty this issue.
Hope someone has a solution to this problem.
Any help will be appreciated!
I maintain a PowerBuilder Classic 12.5 application which has functionality to print checks on a Source Technologies MICR printer. The application has been running fine in a Windows XP environment. We are trying to move to a Windows-7 operating system and the check printing no longer works.
Here is the issue. PowerBuilder issues a PrintOpen followed by several Print commands to send command strings to the printer to unlock MICR mode and various secure fonts:
il_job = PrintOpen( )
Print(il_job,'&%STF[password]$')
Print(il_job,'&%SMCPFFFF$')
Print(il_job,'&%STP10003$')
Print(il_job,'&%STP10002$')
Print(il_job,'&%STP10001$')
Print(il_job,'&%1B$&u600D')
Print(il_job,'&%1B$*t600R')
This works fine on XP, and if you redirect the printer to "print to file", you can see the command strings right there in the file.
In Windows-7, the printer does not recognize the command strings, and in fact, just prints the commands on the check stock. If you do the same "print to file", you can see the commands in there, but each character in the command string is separated by other characters.
The following is a sample taken from the "print to" file, and you can see the string '&%SMCPFFFF$' by looking at each character that precedes an asterisk (*).
*p171Y&*p50X%*p100XS*p150XM*p200XC*p250XP*p300XF*p350XF*p400XF*p450XF*p500X$
This would seem to be a print driver issue, and in fact, Source Technologies now provides a "Universal Print Driver" which we have been told to use. Our PC support person was able to get the check printing working temporarily by re-installing the old print driver that we used on Windows XP, but as soon as the printer is turned off and on again, it resets to the new universal driver.
I tried using PrintDefineFont and PrintSetFont, to set the font to Courier Regular 8pt (which is what the Tech Support guy at Source Technologies told us we needed), but that didn't help:
PrintDefineFont(il_job, 1, "Courier", -8, 400, Fixed!, AnyFont!, FALSE, FALSE)
PrintSetFont(il_job, 1)
Can anyone help me with this issue? Or suggest where I might get help.
Thanks.
Try this: Add a new printer. Select the port your printer is connected to. Select Manufacturer: Generic, Printer: Generic/Text only. When you print to this printer it should send exactly what's in your Print statements to the printer.
Thanks Hugh, I tried your suggestion which sounded good, but unfortunately it had no effect.
As it happens, as of yesterday I did resolve the last of the printing issues. I had to address each of the special fonts (micr line, signature, check amount etc.) individually, and used a combination of using PrintDefineFont/PrintSetFont, embedded printer command strings to reset the font, and changing a Column control in the datawindow to a Text control (a printer command string is moved into this field as well as the data, and the one worked, the other didn't).
Appreciate your help.
Les
Please right click on your software and go to compatibility mode and select "Windows XP with SP3" in it, click APPLY and OK.
Confirm if the software now send print commands perfectly?
I'm using PHPExcel to generate a very simple .xls file (PHPExcel_IOFactory::createWriter($PHPExcel, 'Excel5')). Whenever that file is opened on Windows 7 using Excel 2010 or 2007, I get the following error:
Excel found unreadable content in 'XXXXXXX.xls'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click Yes.
When I open the same file in Excel 2010 in Windows XP it works fine. If I open the same file in OpenOffice, it works regardless of the OS.
Windows 7 / Excel 2010: Error
Windows 7 / Excel 2007: Error
Windows XP / Excel 2010: Works
Windows XP / Excel 2007: Works
Any / OpenOffice: Works
When I tell PHPExcel to generate an .xlsx file (PHPExcel_IOFactory::createWriter($PHPExcel, 'Excel2007')), it works fine with all the above combinaisons.
I found countless threads on the MS forums, and it seems to affect only Windows 7 files with Excel files generated by third party libraries (not just PHPExcel). But no one has a solution.
I also found the following MS KB article, but I'm not familiar with the underlying Excel specifications: http://support.microsoft.com/kb/2411912
Has anyone else experienced this?
If it is the problem you've highlighted from the MS Support site, then it's locked somewhere in the innards of PHP_OLE, probably in the PHPExcel_Shared_OLE_PPS_File class. I've raised this as Issue 15508 on the PHPExcel site, and will try to run some debugging over the weekend on a Windows 7 box.
No guarantees of a quick fix: but you've given me a pointer on how to try and recreate the problem, and where to look.
For me it was fixed when I used proper UTF-8 encoded strings instead of ISO-8859-1. Maybe PHPExcel can hint about bad encodings?
You have to write with UTF-8 the title, creator, LastModifiedby etc... fields. This was my solution.