i recently installed fresh win 7 pro OS on brand new DELL i5 desktop machine. while trying to use word 2013, i noticed that text written in Monotype Hadassah font is displayed using Times new roman font.
is anybody noticed such an issue?
thanks.
after some experiments:
the fonts works OK in notepad - which means that probably the problem is in office 2013 and not in the OS itself.
since the font is registered as restricted with respect to the "embedding" ability i thought that it may be due to this restriction, but nevertheless, removing the restriction ( i recommend on TTFPatch utility didn't change the behaviour.
interestingly, i found that saving the document as PDF resulted in correct rendering of the
font - which is pretty satisfactory to me.
Related
I've got a VB.Net Windows Form application containing several controls (labels, groupboxes, comboboxes, etc.) This application is deployed to several PCs running Windows 10. There are also Win10 tablets connecting to these PCs via Remote Desktop. The issue is that the text on the form sometimes gets resized and overlaps onto other controls when viewed on the tablet. In other words, the text becomes too big.
I thought this was only happening when using Remote Desktop but today I saw it happen on a PC too. This is the first time this has happened. One difference is that the PC was re-imaged in the field instead of being brought back to the office first. The monitors used between the two locations are different, and I'm suspecting this has something to do with it. I know there are DPI and resolution factors to consider but don't fully understand how to rectify them in this case, or if they're even applicable.
Here's how it looks as designed and running on my dev PC:
And here's how it looks when running on the production PC (sorry for the grainy image):
Of note is that some text doesn't appear to get oversized, for example the "Currently: 6 ft/min". All fonts are Microsoft Sans Serif.
Suggestions?
The answer provided here worked for me by changing the compatibility settings for the executable. Another method is provided here but I haven't had a chance to test it yet.
So we've recently had our dev machines replaced with 4k laptops and windows 10. I've got visual studio set up, the DPI scaling has worked for the most part to make things usable. The only problem is errors / dialog boxes.
I can't find a way to make them scale up to something readable. Instead I'm getting unintelligable errors written for ants.
Has anyone had any experience of this issue on high DPI screens? And if so did you find a way to fix the problem?
As an example of what I'm talking about, content is scaled, but the options to the left are not. If I get an error popup (exceptions, build failed etc) then everything is in that tiny text, making it unreadable.
I'm working on a legacy VB6 application in Windows 10. I'm currently trying to get the application to run seamlessly in Windows 10 and I'm coming across some issues. One of them is the SSTab control. See Image below:
Style, Tab Orientation, All the properties are identical, but as can be seen the text in Windows 7 looks proper vs Win 10. It seems to float left and when selected, one of the S's seems to get cut off the top and added in the 2nd line.
Anyone have any idea?
Try choosing Win 7 in the version part of compatibility. There is the App Compat Kit from MS that allows you to set thousands of compat settings rather than just a few common ones in that compatibility dialog https://www.microsoft.com/en-au/download/details.aspx?id=7352
Hi I got a lil problem with a mobile handheld computer (Motorola MC9200) running Windows CE 7.0.
Within the browser (Internet Explorer + software like Naurtech CETerm) there is some font-smoothing or cleartype. Problem about that is that , and font with a css style of font-weight 900 for example look exactly the same as normal font. So you can't tell the difference.
Another problem would be the panning. I'm running a fullscreen web application and the user shouldn't be able to pan the whole screen 1 cm out. Funny thing is while the user is panning the whole picture the font-smoothing/cleartype is disabled and you can tell the difference between font-weights.
Anyone no a solution to that? I already searched the registry for cleartype and font but didn't find anything helpful. I don't have other WinCE 7.0 devices so I don't know if that problem is WinCE 7.0 related or related to the device.
I don't have a device at hand, but WEC 7.0 offers the SystemParametersInfo function that sounds a bit like what you're after.
Call it with uiAction set to SPI_SETFONTSMOOTHING to disable ClearType on a system-wide basis:
SystemParametersInfo(SPI_SETFONTSMOOTHING, FALSE, NULL, SPIF_SENDCHANGE);
Earlier versions of Windows CE had a registry setting to allow OEM's to disable ClearType, but I've been unable to locate this setting in WEC 7.0, so my guess is it's no longer supported and ClearType is always enabled by default.
My team has used the same Install Shield 12 project for years. Several weeks ago Windows Explorer in Vista and Win7 stopped displaying icon sizes above 16x16 for the installer. So List, Details, and Small views show the 16x icon but Tile, Thumbnail, Medium and Large views are just text.
This is true for new installers, but also for 3 years of archived installers. We have not tried systems older than Vista, but we have tried it on multiple machines. We use a normal 32x32 32bit ICO file. In IrfanView it has two pages with a blank first page. In InstallShield it has one Icon to choose from at index 0. None of this has changed in the last three years.
I've dug around on the Flexera forums, here, and in various Google results but I haven't discovered anything except that quite a few people still use Install Shield 12.
Does anyone know what happened or how to fix it?
I suspect that there has been a recent windows update that changed the rules. Do we need to include an ICO containing different sizes? Does windows now restrict something that the older versions of Install Shield does?
I changed tactics. Instead of trying to understand why our old ICO suddenly stopped working I just created a new ICO. I made an effort to create exactly what Windows would expect in an ICO.
A quick and dirty search for application icon editors turned up IcoFX (this link goes to an free older version). Even Stack Overflow contributors recommended it. I fed it a pristine 256x256 png and told it to "Create Windows Icon From Image" using its default settings:
- 4bit # 16x16, 32x32
- 8bit # 16x16, 32x32, 48x48
- 32bit # 16x16, 32x32, 48x48, 256x256
This new ICO worked, although I had to rebuild my Windows icon cache to see the change.
I'm disappointed that I don't know what changed in the OSes. However, this solved the problem and also dramatically improved our old 32x32 pixel by 32bit ICO.