Mikael Kalms Posted November 23, 2021 Report Share Posted November 23, 2021 Hi, I have only used PlasticX for a few minutes. Would like to point out that the fonts used - and perhaps the alignment strategy for these - makes text smudged. Left side is text from Plastic. Right side is text from PlasticX. I have screenshotted both applications and zoomed results to 400% using nearest neighbor interpolation. I perceive text in views where each letter is important - for example, filename column in the Workspace Explorer - as more difficult to read with the new font. Link to comment Share on other sites More sharing options...
Mikael Kalms Posted November 23, 2021 Author Report Share Posted November 23, 2021 Side note; I find the new font easier to read with the Dark theme, compared to new font + Light theme. Link to comment Share on other sites More sharing options...
Xarbrough Posted November 23, 2021 Report Share Posted November 23, 2021 The new font looks a little blurry for me (full HD monitor) as well, but on the other hand, old plastic may look a tiny bit too sharp-pixelated. Fonts are tough. But the blurriness is most noticeable with bold text, look at the letter 'e' in this screenshot, for example: This is original size and you can see how the e is almost a blob, as if the normal font was artificially bolded in code instead of having its own type face. Larger size: Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted November 24, 2021 Report Share Posted November 24, 2021 Hi @Mikael Kalms @Xarbrough thank you for your feedback. The old Windows GUI used the native Segoe UI. Segoe UI is optimized for ClearType, which is on by default in Windows. This is why you may find the font somewhat more readable in the old GUI. New GUI uses Inter font, that is a pretty standard font in new UI designs. The choice of the font is to follow the Unity App Framework font guidelines, and to maintain a consistent visual style between the supported platforms (macOS, Linux and Windows). We use that font in the three platforms. @Xarbrough you're right. Fonts are tough. Depending on the DPI resolution, the monitor, and the contrast you're using, sometimes fonts are more (or less) readable. We rely an Avalonia framework, that uses Skia font rendering (the same 2D drawing engine that uses Chrome) so I'm afraid there is little we can do in this matter. That said, maybe we can improve readability in the light theme by giving a little more contrast to the text with respect to the background. I'll do that for future releases. 1 Link to comment Share on other sites More sharing options...
FpffUVROGDdATCp Posted November 30, 2021 Report Share Posted November 30, 2021 Hi i think that light color schema need to be adjusted little bit to make it more contrast. May be it is only for me but quite hard for eyes to read text in workspace explorer . Text too light grey. i think need to make bit more dark. It is on Linux Link to comment Share on other sites More sharing options...
mdel Posted December 5, 2021 Report Share Posted December 5, 2021 Hello, I had the same experience than @Mikael Kalms as soon as I launch PlasticX GUI the font rendering gave me a very bad impression. It looks poor compared to user GUI I am using on Windows, and it look poor compared to the regular Plastic GUI. It feels very blurry. @Daniel Peñalba I do not think it is related to Skia renderering because Chrome does have better font rendering than PlasticX on Windows too. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted December 13, 2021 Report Share Posted December 13, 2021 @mdel Thank you for your feedback. Left font (Chrome) it's "Segoe UI" and right font (Plasticx) is "Inter". The rendering of each font is different (Chrome uses ClearType antialiasing), so it makes sense there is a difference. So thank you for the report. We are going to: 1) Make the text darker to improve readability. 2) Try to enable ClearType font rendering in our app. Link to comment Share on other sites More sharing options...
mdel Posted December 16, 2021 Report Share Posted December 16, 2021 @Daniel Peñalba in your example we can see the font are different but also Chrome - Segoe UI is using subpixel rendering (we can see different color) which is not the case of PlasticX. Also I am curious, why not to use the default system font? It looks to me the default design choice for mainstream crossplatform application (like Internet Browser) Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted December 16, 2021 Report Share Posted December 16, 2021 We're trying to bring the ClearType (subpixel) font drawing to PlasticX. Regarding the font chosen, we use Inter font, that is a pretty standard font in new UI designs. The choice of the font is to follow the Unity App Framework font guidelines, and to maintain a consistent visual style between the supported platforms (macOS, Linux and Windows). Believe me that the font is much more readable on mac than on windows (in macOS the subpixel drawing is correctly done). Once we fix subpixel drawing in windows it will look much better. In any case, we may setup some options to allow to change customize the font just in case users feel more comfortable using the system font. 1 Link to comment Share on other sites More sharing options...
mdel Posted December 16, 2021 Report Share Posted December 16, 2021 great, I am looking forward it! 😀 Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted January 10, 2022 Report Share Posted January 10, 2022 We're on the right way! Avalonia guys already implemented ClearType support in windows: https://github.com/AvaloniaUI/Avalonia/pull/7336 That means it will available for PlasticX once Avalonia create a new version with those changes, and we update the Avalonia framework version. 1 Link to comment Share on other sites More sharing options...
yonggyun Posted January 11, 2022 Report Share Posted January 11, 2022 Not a visibility issue, but another font issue. There is also a problem with the Korean notation. (It is impossible to change the language because it rollback to ko even if the client.conf file is changed.) It's not an encoding issue. If you copy and paste the "Properties" section in the lower right corner, it will be printed normally. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted January 11, 2022 Report Share Posted January 11, 2022 @yonggyun, thank you for the report. As you already may noticed, unicode chars are not fully supported yet. As you can see there are some issues rendering them in Avalonia (just for textboxes, the textblocks work fine). So in short, there is no support for double byte languages yet, but it should come soon. Avalonia is on it's way of supporting IME and rendering, but it's not ready yet. In the meantime we will review the client.conf issue just you to be able to use it in english. Just to clarify the issue: what you're reporting is that you're trying to setup EN language, but it is always reverted to KO. Is that right? (I'm assuming that KO is your OS language). And could you also clarify this one? Quote It's not an encoding issue. If you copy and paste the "Properties" section in the lower right corner, it will be printed normally. What do you mean by "the lower right corner"? Thanks! Link to comment Share on other sites More sharing options...
yonggyun Posted January 13, 2022 Report Share Posted January 13, 2022 Quote In the meantime we will review the client.conf issue just you to be able to use it in english. Just to clarify the issue: what you're reporting is that you're trying to setup EN language, but it is always reverted to KO. Is that right? (I'm assuming that KO is your OS language). right. After I excute plastic scm, the config file in that file goes back to "ko" Quote What do you mean by "the lower right corner"? I was talking about the broken text in the lower right part of the screenshot. nevermind. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted January 13, 2022 Report Share Posted January 13, 2022 @yonggyun, You need to set the language to "force_en". You can find more defaults here! 1 Link to comment Share on other sites More sharing options...
dylz Posted March 30, 2022 Report Share Posted March 30, 2022 hi @Daniel Peñalba, I am running in the same issue about the broken text(turned into unreadable code) like the lower right part of the screenshot that @yonggyun posted above. In my situation, the broken text are on the checkin text box. I am using a quite latest version plastic client cloud edition, and I am sure the config file's language setting is matching with my OS language, is that a support font issue? anyone have idea about how to fix this? thanks. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted March 30, 2022 Report Share Posted March 30, 2022 Hi @dylz thank you for reporting this. The version of Avalonia UI (the UI framework we use to build Plastic) we're using, doesn't support double byte chars yet. Good news is that Avalonia already implemented double byte support, so we just need to upgrade so Plastic will support it really soon. Thanks you for your patient, we'll try to get it ready as soon as possible 😉 Link to comment Share on other sites More sharing options...
dylz Posted March 31, 2022 Report Share Posted March 31, 2022 hi @Daniel Peñalba thanks for your prompt response, appreciate! may I know when the updated version will be released? thanks Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted March 31, 2022 Report Share Posted March 31, 2022 3 hours ago, dylz said: hi @Daniel Peñalba thanks for your prompt response, appreciate! may I know when the updated version will be released? thanks Not sure yet. We need Avalonia to release their major version with double-byte support, and then we can upgrade (2-3 months I guess). Link to comment Share on other sites More sharing options...
dylz Posted March 31, 2022 Report Share Posted March 31, 2022 great, great, thanks a lot for the always efficiency 1 Link to comment Share on other sites More sharing options...
yonggyun Posted September 8, 2022 Report Share Posted September 8, 2022 Any more news about the Avalonia UI update? Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted September 8, 2022 Report Share Posted September 8, 2022 We were told that this is is purely a limitation of the Skia milestone used by SkiaSharp. The out of the box Windows Skia build has dysfunctional ClearType even with Avalonia custom Skia build that uses a up to date milestone. So at the moment the only available solution is using a downgraded Version of SkiaSharp on Windows. The developer who is working on a native skia bindings.. which is almost working… has returned from holiday and is resuming this today. So hopefully they can find a way to make clear type work with the latest skia version. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted September 8, 2022 Report Share Posted September 8, 2022 @yonggyun about the support for double byte language support we already have a beta version supporting it. Please let us know if you want to access to the beta program and want to test it. cc/ @vsanchezm Link to comment Share on other sites More sharing options...
yonggyun Posted September 14, 2022 Report Share Posted September 14, 2022 On 9/8/2022 at 5:44 PM, Daniel Peñalba said: @yonggyun about the support for double byte language support we already have a beta version supporting it. Please let us know if you want to access to the beta program and want to test it. cc/ @vsanchezm i want join beta program. Link to comment Share on other sites More sharing options...
Daniel Peñalba Posted February 28, 2023 Report Share Posted February 28, 2023 Just you to know, ClearType support is coming in soon. Currently in dev... The difference is more noticeable zooming in: Link to comment Share on other sites More sharing options...
Recommended Posts