New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken characters in the Welcome Page and the Contribution Manager #4747

Closed
lisandroperalta opened this Issue Nov 19, 2016 · 33 comments

Comments

Projects
None yet
9 participants
@lisandroperalta

lisandroperalta commented Nov 19, 2016

Hi everyone.
When I run Processing the Welcome page shows with broken characters instead of text. Same happens with the contribution manager.
Version 3.1.1 was the last one without this issue, since then every other version I've downloaded (including 3.2.3) presents this problem.
I'm using Windows 10 64bits and I have java v8 upd 101 if its any help. My Languaje is Spanish (Argentina)
Thanks!
I've atttached a screenshot to make myself more clear

captura de pantalla 2016-11-19 15 10 13

@Cubit-Games

This comment has been minimized.

Show comment
Hide comment
@Cubit-Games

Cubit-Games Nov 20, 2016

Same issue here, really really annoying.

Cubit-Games commented Nov 20, 2016

Same issue here, really really annoying.

@jeremydouglass

This comment has been minimized.

Show comment
Hide comment
@jeremydouglass

jeremydouglass Nov 20, 2016

Contributor

@Cubit-Games -- what operating system and OS version are you on, what version of Processing are you using, and is your OS configured for a language other than English?

Contributor

jeremydouglass commented Nov 20, 2016

@Cubit-Games -- what operating system and OS version are you on, what version of Processing are you using, and is your OS configured for a language other than English?

@Cubit-Games

This comment has been minimized.

Show comment
Hide comment
@Cubit-Games

Cubit-Games Nov 21, 2016

I am on Windows 10 and the latest version of processing 3 i downloaded yesterday. My OS is configured for English.

Cubit-Games commented Nov 21, 2016

I am on Windows 10 and the latest version of processing 3 i downloaded yesterday. My OS is configured for English.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 21, 2016

Member

@gohai could this be a regression from the font loading changes?

Member

benfry commented Nov 21, 2016

@gohai could this be a regression from the font loading changes?

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 21, 2016

Member

@lisandroperalta Thanks for letting us know about it—we've (obviously) not seen this problem before.

Member

benfry commented Nov 21, 2016

@lisandroperalta Thanks for letting us know about it—we've (obviously) not seen this problem before.

@benfry benfry added the high label Nov 21, 2016

@gohai

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Nov 21, 2016

Contributor

@lisandroperalta You write that every version after 3.1.1 didn't work for you, is this correct? Asking because we did a change in 3.2.2, which could have been the culprit, but if e.g. 3.2.1 also doesn't work, that would rule it out.

Contributor

gohai commented Nov 21, 2016

@lisandroperalta You write that every version after 3.1.1 didn't work for you, is this correct? Asking because we did a change in 3.2.2, which could have been the culprit, but if e.g. 3.2.1 also doesn't work, that would rule it out.

@lisandroperalta lisandroperalta changed the title from Borken characters in the Welcome Page and the Contribution Manager to Broken characters in the Welcome Page and the Contribution Manager Nov 21, 2016

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Nov 21, 2016

@gohai Indeed, I have 3.1.1 running without problems right now, but all the newer versions I've tried presented this issue. (I may have overlooked some, but I'm pretty sure it must be present in everyone)

lisandroperalta commented Nov 21, 2016

@gohai Indeed, I have 3.1.1 running without problems right now, but all the newer versions I've tried presented this issue. (I may have overlooked some, but I'm pretty sure it must be present in everyone)

@gohai

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Nov 21, 2016

Contributor

@lisandroperalta Thank you for confirming.
@benfry The JRE update in 3.1.2 maybe?

Contributor

gohai commented Nov 21, 2016

@lisandroperalta Thank you for confirming.
@benfry The JRE update in 3.1.2 maybe?

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 22, 2016

Member

@gohai good idea…

@lisandroperalta Try the following:

  • Make sure Processing is not already running
  • Rename the java folder in the processing-3.2.3 directory to something else java2 or java.bad or ihopethisworks
  • Copy the java folder from 3.1.1 to the 3.2.3 directory
  • Try running the 3.2.3 version of processing.exe

Does that fix it?

Member

benfry commented Nov 22, 2016

@gohai good idea…

@lisandroperalta Try the following:

  • Make sure Processing is not already running
  • Rename the java folder in the processing-3.2.3 directory to something else java2 or java.bad or ihopethisworks
  • Copy the java folder from 3.1.1 to the 3.2.3 directory
  • Try running the 3.2.3 version of processing.exe

Does that fix it?

@matteolegna

This comment has been minimized.

Show comment
Hide comment
@matteolegna

matteolegna Nov 23, 2016

Same issue here. Where would we find version 3.1.1 to download?

matteolegna commented Nov 23, 2016

Same issue here. Where would we find version 3.1.1 to download?

@gohai

This comment has been minimized.

Show comment
Hide comment
@matteolegna

This comment has been minimized.

Show comment
Hide comment
@matteolegna

matteolegna Nov 23, 2016

@gohai Thank you very much. I'm not too much used to GitHub.
@benfry Yes! Replacing the Java folder in the way you said makes it work as it should. Thanks!

matteolegna commented Nov 23, 2016

@gohai Thank you very much. I'm not too much used to GitHub.
@benfry Yes! Replacing the Java folder in the way you said makes it work as it should. Thanks!

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Nov 23, 2016

@benfry: the same as @matteolegna , replacing the java folder made it work!
Is it safe to run it like this?

lisandroperalta commented Nov 23, 2016

@benfry: the same as @matteolegna , replacing the java folder made it work!
Is it safe to run it like this?

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 23, 2016

Member

Yes, safe to run like that.

Do you have the font “Source Sans” installed on your system? Trying to figure out why this would be causing trouble… Unfortunately it's not our bug, but we need to figure out how to get around it.

Member

benfry commented Nov 23, 2016

Yes, safe to run like that.

Do you have the font “Source Sans” installed on your system? Trying to figure out why this would be causing trouble… Unfortunately it's not our bug, but we need to figure out how to get around it.

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Nov 23, 2016

Checking.... "source sans pro" (!?)
Is the same?

lisandroperalta commented Nov 23, 2016

Checking.... "source sans pro" (!?)
Is the same?

@gohai

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Nov 24, 2016

Contributor

@lisandroperalta Not exactly, but that could perhaps explain the issue - could you temporarily delete the Source Sans Pro font from your system and see if this changes things? (You can download the font later here.)

Could you also attach a screenshot of the Welcome page (Help > Welcome...)? Thanks.

@benfry
I found this change to font rendering on Windows that was introduced with 8u102. There's another one for 8u112, but I believe this only makes a difference for bold & italic. (Both are triggered by a particular font on certain systems fyi.)

Contributor

gohai commented Nov 24, 2016

@lisandroperalta Not exactly, but that could perhaps explain the issue - could you temporarily delete the Source Sans Pro font from your system and see if this changes things? (You can download the font later here.)

Could you also attach a screenshot of the Welcome page (Help > Welcome...)? Thanks.

@benfry
I found this change to font rendering on Windows that was introduced with 8u102. There's another one for 8u112, but I believe this only makes a difference for bold & italic. (Both are triggered by a particular font on certain systems fyi.)

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Nov 24, 2016

Hey! As soon as I get to my computer I'll try it. In the meantime, I've tried the following with the computer at work (just in case it is any help)
Windows 7 64 without java installed
Downloaded the 3.2.3 It works just fine :-P

lisandroperalta commented Nov 24, 2016

Hey! As soon as I get to my computer I'll try it. In the meantime, I've tried the following with the computer at work (just in case it is any help)
Windows 7 64 without java installed
Downloaded the 3.2.3 It works just fine :-P

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Nov 25, 2016

@gohai Once in my computer tried it. Deleting Source Sans Pro seems to solve it. Reinstalled Source Sans Pro just to see what happens and the issue reapeared.

captura de pantalla 2016-11-24 21 55 20

lisandroperalta commented Nov 25, 2016

@gohai Once in my computer tried it. Deleting Source Sans Pro seems to solve it. Reinstalled Source Sans Pro just to see what happens and the issue reapeared.

captura de pantalla 2016-11-24 21 55 20

@DollarAkshay

This comment has been minimized.

Show comment
Hide comment
@DollarAkshay

DollarAkshay Dec 7, 2016

Hey I just downloaded Processing and launched it and had the same problem

Screenshot :

Screenshot Processing Bug

After deleting Source Sans Pro it is working fine.

User Details

  • OS : Windows 10 64 Bit
  • Processing Version : 3.2.3 64-Bit

DollarAkshay commented Dec 7, 2016

Hey I just downloaded Processing and launched it and had the same problem

Screenshot :

Screenshot Processing Bug

After deleting Source Sans Pro it is working fine.

User Details

  • OS : Windows 10 64 Bit
  • Processing Version : 3.2.3 64-Bit
@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Dec 9, 2016

Member

For someone having this problem, can you compare the Source Sans file that's included with Processing and the version installed on your system to see if they're identical?

Member

benfry commented Dec 9, 2016

For someone having this problem, can you compare the Source Sans file that's included with Processing and the version installed on your system to see if they're identical?

@InfInt

This comment has been minimized.

Show comment
Hide comment
@InfInt

InfInt Dec 10, 2016

I compared both Fonts and they are not identical Byte wise.
image

But Glyph wise they seem to be identical:
image
While looking at both versions I found out that their type varies from otf to ttf. However, both are registered as OpenType

InfInt commented Dec 10, 2016

I compared both Fonts and they are not identical Byte wise.
image

But Glyph wise they seem to be identical:
image
While looking at both versions I found out that their type varies from otf to ttf. However, both are registered as OpenType

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Dec 11, 2016

Member

Ouch, I suspected that might be the case… I'm a little concerned that it's using the lookup tables for glyphs and dimensions from the installed version, but the glyph data from the version embedded with Processing (or vice versa).

Do you know where your copy of Source Sans came from? Did you install it? Did another application install it? Could you post it somewhere?

Member

benfry commented Dec 11, 2016

Ouch, I suspected that might be the case… I'm a little concerned that it's using the lookup tables for glyphs and dimensions from the installed version, but the glyph data from the version embedded with Processing (or vice versa).

Do you know where your copy of Source Sans came from? Did you install it? Did another application install it? Could you post it somewhere?

@InfInt

This comment has been minimized.

Show comment
Hide comment
@InfInt

InfInt Dec 14, 2016

I obtained my Version from Typekit It is tied into my installation of Adobe CC. As far as my knowledge goes, Adobe released that font as open source. At least a paragraph on the Typekit site says so.
I put a zip of those fonts here

InfInt commented Dec 14, 2016

I obtained my Version from Typekit It is tied into my installation of Adobe CC. As far as my knowledge goes, Adobe released that font as open source. At least a paragraph on the Typekit site says so.
I put a zip of those fonts here

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Dec 15, 2016

Member

Yeah, the open source version is the one that's included with the software. I suspect that Typekit must be subsetting it in some way (given the drastic size differences in the files) and the differences in the character lookup tables are conflicting with one another.

It seems to be something that Oracle broke in recent Java releases, unfortunately, so it's a "new" bug in Processing.

Member

benfry commented Dec 15, 2016

Yeah, the open source version is the one that's included with the software. I suspect that Typekit must be subsetting it in some way (given the drastic size differences in the files) and the differences in the character lookup tables are conflicting with one another.

It seems to be something that Oracle broke in recent Java releases, unfortunately, so it's a "new" bug in Processing.

@InfInt

This comment has been minimized.

Show comment
Hide comment
@InfInt

InfInt Dec 15, 2016

Is there anything I can do to help resolve this bug/issue?

InfInt commented Dec 15, 2016

Is there anything I can do to help resolve this bug/issue?

@gohai

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Dec 16, 2016

Contributor

@benfry Curious whether Processing could ship a modified version of the font using a custom name?

http://superuser.com/questions/120593/how-do-you-change-a-ttf-font-name

Contributor

gohai commented Dec 16, 2016

@benfry Curious whether Processing could ship a modified version of the font using a custom name?

http://superuser.com/questions/120593/how-do-you-change-a-ttf-font-name

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Dec 17, 2016

Member

Yeah, that's one possible solution… Not sure if that violates the license, though, and I'd hate to introduce other unintended consequences.

Could also try reporting the bug to Oracle and see if they—oh, ha! Never mind, not sure what happened to me there.

Since it seems limited to some Windows machines, the best option is to check whether the font is installed and if so, not loading the font from the disk. Since Java doesn't actually have a way to test if a font is loaded, you instead try to load the font and then call getPSName() to see if it's the expected font. Example:

import java.awt.Font;

Font f1 = new Font("Source Sans Pro", Font.PLAIN, 12);
Font f2 = new Font("Source Sans Pro Semibold", Font.PLAIN, 12);

println(f1.getPSName() + " ... " + f2.getPSName());

When the font is installed, it'll print SourceSansPro-Regular ... SourceSansPro-Semibold. When not installed, it'll print Dialog.plain ... Dialog.plain.

So inside a Base.isWindows() block, the code should check whether the fonts are installed, and if so, use those Font objects and not load them from the .otf files that we supply.

Member

benfry commented Dec 17, 2016

Yeah, that's one possible solution… Not sure if that violates the license, though, and I'd hate to introduce other unintended consequences.

Could also try reporting the bug to Oracle and see if they—oh, ha! Never mind, not sure what happened to me there.

Since it seems limited to some Windows machines, the best option is to check whether the font is installed and if so, not loading the font from the disk. Since Java doesn't actually have a way to test if a font is loaded, you instead try to load the font and then call getPSName() to see if it's the expected font. Example:

import java.awt.Font;

Font f1 = new Font("Source Sans Pro", Font.PLAIN, 12);
Font f2 = new Font("Source Sans Pro Semibold", Font.PLAIN, 12);

println(f1.getPSName() + " ... " + f2.getPSName());

When the font is installed, it'll print SourceSansPro-Regular ... SourceSansPro-Semibold. When not installed, it'll print Dialog.plain ... Dialog.plain.

So inside a Base.isWindows() block, the code should check whether the fonts are installed, and if so, use those Font objects and not load them from the .otf files that we supply.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Dec 21, 2016

Member

No takers, so just checked in a fix.

For anyone having this problem, are you running a version from the source? Or do I need to post a test version to see if it's fixed?

Member

benfry commented Dec 21, 2016

No takers, so just checked in a fix.

For anyone having this problem, are you running a version from the source? Or do I need to post a test version to see if it's fixed?

@DavidPitcher

This comment has been minimized.

Show comment
Hide comment
@DavidPitcher

DavidPitcher Dec 26, 2016

I am having the same issue as reported with the Welcome screen. I did a build with the latest sources and that did not resolve the problem for me.

image

DavidPitcher commented Dec 26, 2016

I am having the same issue as reported with the Welcome screen. I did a build with the latest sources and that did not resolve the problem for me.

image

@benfry benfry referenced this issue Feb 3, 2017

Closed

UI Problems #4874

@benfry benfry closed this in 93749da Feb 12, 2017

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 12, 2017

Member

Going with the renamed font to fix it for 3.3.

Member

benfry commented Feb 12, 2017

Going with the renamed font to fix it for 3.3.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 13, 2017

Member

For anyone who was having this problem, can you please try with 3.3 and report back?

Member

benfry commented Feb 13, 2017

For anyone who was having this problem, can you please try with 3.3 and report back?

@lisandroperalta

This comment has been minimized.

Show comment
Hide comment
@lisandroperalta

lisandroperalta Feb 13, 2017

Hey!
just downloaded 3.3 it and it works as it should!
:-) 👍

lisandroperalta commented Feb 13, 2017

Hey!
just downloaded 3.3 it and it works as it should!
:-) 👍

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 13, 2017

Member

Great, thanks for letting me know.

Member

benfry commented Feb 13, 2017

Great, thanks for letting me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment