Hi Tsherr,

You have already done what you have to do - lower the resolution to make things bigger and adjusting DPI.

For your information, do not increase DPI more than 125% or you will have to Sage 50 cut off.

You may want to use Magnifier (Control Panel\All Control Panel Items\Ease of Access Center) from Windows as an alternative

So Sage isn't going to do something about the fonts?  Lowering the resolution to increase the font size is ridiculous - plus it means the monitor isn't in native resolution and therefore doesn't look as good.

I think Sage needs to either give the ability to make the fonts larger (better option), or just make them larger (might be simpler programming).

Does Sage support read these forums, or is it just end-users - if not, is there a way to submit a suggestion to Sage?

Hi Tsherr,

Please go to Help, in the menu bar, Contact Sage, Give us your Feedback to submit your idea.

Hi Tsherr

Here is the link to the website to post your concern and how important it is to you to have this change made. You will discover too that you are not the only one asking for this change. It ranks in the top 10. Please voice your concern and the more people give feedback the sooner or more likely the change will happen

sage50canadian.ideascale.com

Thanks Jo Anne, I'll do that.  Rather funny that it's a top ten issue, but it hasn't been fixed yet, but based on my experience with Ideascale for other applications, this seems par for the course.

Keith, there is lots of posted feedback regarding the need to resolve this issue

could you contact Sage 50 developers for a date as to when this will be resolved, or even if it will be resolved

and I will presume that the lack of a yes (with date) / no answer with 2 weeks as to the resolution of this problem, will signify the Sage developers have no plan to resolve the issue

Two weeks from now?  The change from 2007 to 2008 included a new invoice screen interface, with these 8 point fonts, and some funky behaviour when inserting or deleting rows.

Assuming that was changed Oct 1, 2007, CRBookKeeping is giving Sage 360 weeks to put it back to at least as good as 2007?

(QuickBooks appears to use 10 point fonts.  They're not scalable either, they're just a sort of common-sense size to begin with. )

So... yeah.

I'm not giving Sage 50, two weeks for a fix... I'm giving them two weeks to respond yes/no to providing the fix, otherwise I will presume the answer to be no fix....

and if yes, I need a release date - to keep the development team accountable

Sage needs to indicate if they plan on updating the product going forward - to say 'provide feedback', with no one closing the feedback loop is proving pointless

I think that the 9 month delay between submitting a 'feedback' note, and it being displayed for voting, should be answer enough.  As an excuse, "we're real busy doing important stuff" wears thin even before a year goes by.

Also doubt there's going to be any future change that isn't a new Sage 'Revenue Stream'.  

Sage obviously knows about making big, readable fonts:

I used to work for a small, probably far less beaurocratic software development.  Exchanges like this weren't unusual:

Sales Manager:  "I've got a customer on the phone, wanting to know if (new product) will do loan amortisations?"

President / head of Development, after a moment "Yes!....  Tell him yes, it will!"

It changed, I left.

Our Research & Development team is well aware of this issue.  We apologize that we are unable to provide a definite timeline of tackling this problem.  We will disclose more information once we get updated

since the R&D team is already working on the 2015 release, probably testing it now - can they disclose if the font issue is resolved in the 2015 release (to be available in four months) ?

'profesionals'?? and no one caught this?

Where is that posted, by the way?

current feedback link, from an email I got today

sage50canadian.ideascale.com/.../491420-19157

Merge these files into your registry. The fonts required by Sage are not the same in newer versions of Windows. These are files from Windows 7 that allow for the correct Font to be displayed.

FONTS.reg

FONTMAPPER.reg

Download the files. Right click on them and select Merge.

As always, before messing with your registry do a backup.

Sythe

Because Sage 50 is a 32 bit program, importing those registry keys may have no effect.  Sage 50 could be using fonts in:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Fonts

and

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\FontMapper

and doing substitutions from:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\FontSubstitutes

If anyone is getting REALLY tiny fonts, please open the sample file, take a screenshot with Alt-print-screen, paste it into Paint, and post the relevant parts in this forum. 

Or... contact Sage software for support on this issue.  This forum is for peer support, and as such those of us not with Sage have limited access to technical information and none to support case history.

Thank-you. That fixed my problem! I wish SAGE would post something in their FAQ to make our lives easier!

same issue, 6 years later. 

not may reply...

www.sagecity.com/.../sage-50-premium-accounting-2021-1-font-smaller-than-before-and-blur-in-settings

Those two files are no longer there. 

Do you still have a backup somewhere?

The original post is over 6 years old.

problem is still the same. 

don't have to get the font from the windows 7. 

copy the following key from another working windows 10 and merge. problems were solved. 

Thanks. 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Fonts

and

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\FontMapper

and doing substitutions from:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\FontSubstitutes

Official support for the issue: https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=78052&sliceId=1&cmd=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&noCount=true

Use option #2 simple and easy