I've created a PDF using CFDOCUMENT, using a barcode font in the stylesheet for certain elements. When the resulting barcode contains a single quote (') or ampersand (&), that character is replaced with a blank space when printing with CFPRINT, but the PDF displays and prints fine from Adobe Acrobat Reader.
Printers affected Zebra TLP 2844, LabelTac 4 (Creative). Drivers provided by Seagull Scientific.
Does anyone have any thoughts on what might be happening?
We have isolated the issue to the specific printer driver we're using to print. The printer is a LabelTac 4. Others experiencing similar issues will want to check for driver updates for their printers.
I'm working with their team to determine a resolution.
Updates to the latest driver from Seagull Scientific resulted in no change to the output. Seagull Scientific does not provide support for their drivers without the purchase of their BarTender software.
Related
I am about to use Weka for processing a dataset that contains numeric and nominal values. As Persian and Arabic are the secondary languages I am using in my Windows 7 operating system, I assumed that this might be the reason that when I am trying to save a loaded CSV data file in Weka as an ARFF file format, the numbers are all saved as question (?) marks! However, even by removing these languages from the Control Panel setting, nothing changed.
Moreover, I have upgraded my Java version from 8 to 9 recently. I am not sure if this could be the reason for this.
I searched for a probable reason on the internet, though could not find any solution. Thanks, everybody in advance.
I found the solution, and it was easy!
In the Control Panel, I selected the Region and Language option. Then in the Formats tab, I changed the Format option from Persian to English (United States), and everything turned out to be working alright in Weka!
Moreover, in the Administrative tab, for the Language for non-Unicode programs option, it is better to set the language in use as English (United States).
Cheers ...
I have a product on Microsoft store (PowerBI Tiles), that use the api powerbi.js from Microsoft to get visuals from logged-in user.
When I try to open the application using PowerPoint online on Firefox, we got some problems.
"The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature."
My team try to solve the problem on our side, but we detect that the problems doesn't come from our code, but from powerbi.js (Microsoft code). Even the demos from Microsoft doesn't work on Firefox.
We create two animated gifs reproducing the problem (on our application and also on the demos from Microsoft)
Microsoft Demos - Running on Firefox
PowerBI Tiles - Running on Firefox
Anyone with this kind of problem? Any solution to this problem.
Many thanks.
João
My application allows users to customize UI by selecting a user preferred language. It usually works great, except that on Windows 10, say, if a user locale is picked as, say, Cambodian in Windows Control Panel:
But then if the user in my app's UI picks US English, I can't seem to find a way to render it with "US English numbers." On Windows 8.1 it used to end up looking as such, no matter what locale is picked:
As my assumption was that one doesn't need to translate numbers. But on Windows 10, that same control ends up looking as such:
Note that its text is set up using just this call:
::SetWindowText(m_hWnd, L"1000");
So I am curious, is there any way to keep numbers rendered as the arabic numerals:
This issue goes much deeper than basic controls, it happens inside GDI and also affects DrawText and TextOut. The only documented way around it is to call ExtTextOut with the ETO_NUMERICSLATIN flag (or use Uniscribe to render text).
This behavior is completely by design
these flags only modify U+0030 -- U+0039, as needed
Becsause the truth is that GDI doesn't give a crap about formatting or really anything related to locales, with one signle exception: Digit Substitution
Any time you go to render text it will grab those digit substitution settings in the user locale (including the user override information) and use the info to decide how to display numbers.
Another thing that seems to work is to force a custom font with the GREEK_CHARSET charset. That charset triggers a font association magic feature. (EE_CHARSET also seems to work for English text). You would probably have to try to pick the best charset for each of your languages if you are going to do this but you cannot use ANSI_CHARSET nor DEFAULT_CHARSET.
If don't know why this only happens in Windows 10 but it really seems like a bug in certain places. In Explorer for example it will display "7-Zip" as "៧-Zip" etc.
I am recently trying to change our company's old program. One of the huge rocks in my way is that the old program was made with Borland C++, and it had its own way of connecting to the SQL Server 2000 database.
After 8 years, I'm trying to retire this program. But when I looked at the database, I got freaked out!
The whole database was in a vague language that was supposed to be Persian.
I'll give you a portion of the database converted to SQL Server 2005, so you can see it for yourself. I've spent many days trying to figure out how to decode this data. But so far no results has come out of it.
Link to the sample Database File
So please if you can tell me how to use them in Microsoft C#.net it will be much appreciated.
These are the datatypes used for them:
And this is how it looks:
Thanks a lot.
1) Analyse existing program and original database
Try to figure out how the C++ program stored Persian text in the database. What are the collations defined on the original server, database, and on column level.
Does the C++ program convert the data to be stored and retrieved from the database? If so, find out how.
It may well be that the program displays data in Persian, but does not store it in a compatible way. Or it uses a custom font that supports custom encoding. All this needs to be analyzed.
2) The screen shots looks as if everything Persian is encoded as ASCII characters higher than CHAR(128).
If this a standardized encoding or custom created?
3) To migrate the database, you most likely will need to convert the data mapping original characters to Unicode characters.
First recreate the tables using Unicode-enabled columns (NVARCHAR, NVARCHAR(MAX)) rather than CHAR and VARCHAR, which only support Latin or Extended Latin.
4) Even if you successfully migrated your data, SSMS may not correctly display the stored data due to font settings or OS support.
I summarized the difficulties of displaying Unicode in SSMS on my blog.
But first, you need to investigate the original database and application.
I am working on a translation application in which users are allowed to give English input and I need to convert to a target language and display on a text box. I am facing problems in displaying unicode characters.
Complex characters are not rendering correctly. I know windows uses Uniscribe for rendering complex characters. So do I need to use that explicitly to get the correct rendering? What is the equivalent of Uniscribe in LINUX and MAC?
I am using C++ with wxWidgets framework and trying to display unicode characters on a text box. Any help would be great!
Considering that Uniscribe support in wxWidgets was merely a Google Summer of code idea this year, it seems unlikely that it's working today.
There's no trivial Linux or Mac equivalent for Uniscribe
Read up on Pango. It's the library that supports full OpenType rendering on Linux. Mac's another story.