[GH-ISSUE #537] Use font with wide scripts support #299

New issue

Open

opened 2026-02-25 23:33:54 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:33:54 +03:00

Owner

Originally created by @sergeevabc on GitHub (Nov 13, 2022).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/537

Shiori 1.5.3 on Windows 7 x64.

At present the app uses custom font with Latin script support only.
To be specific: /css/fonts/source-sans-pro-v13-latin-700.woff2
And what do others see when they use letters out of Latin scope? The eyesore.

Either use font with wide scripts support (e.g. Noto Sans) or let system/user decide.

Originally created by @sergeevabc on GitHub (Nov 13, 2022). Original GitHub issue: https://github.com/go-shiori/shiori/issues/537 Shiori 1.5.3 on Windows 7 x64. At present the app uses custom font with Latin script support only. To be specific: ```/css/fonts/source-sans-pro-v13-latin-700.woff2``` And what do others see when they use letters out of Latin scope? The eyesore. ![image](https://user-images.githubusercontent.com/373718/201513100-1cdbd151-a731-477e-8f20-86f6592dad97.png) Either use font with wide scripts support (e.g. Noto Sans) or let system/user decide.

kerem added the

type:bug

component:frontend

tag:help-wanted

labels

2026-02-25 23:33:54 +03:00

kerem commented

2026-02-25 23:33:54 +03:00

Author

Owner

@fmartingr commented on GitHub (Jan 21, 2023):

Hey @sergeevabc, I'm completely unfamiliar with this, I have some japanese bookmarks but I have not seen this issue on those. Are there built-in fonts on operating system that support wide-script support? So we could fallback to those or stop using custom fonts altogether.

@fmartingr commented on GitHub (Jan 21, 2023): Hey @sergeevabc, I'm completely unfamiliar with this, I have some japanese bookmarks but I have not seen this issue on those. Are there built-in fonts on operating system that support wide-script support? So we could fallback to those or stop using custom fonts altogether.

kerem commented

2026-02-25 23:33:54 +03:00

Author

Owner

@jansol commented on GitHub (Dec 27, 2024):

Simply using the serif/sans-serif/monospace aliases should yield a decent set of fonts and their corresponding fallback lists as determined by the browser/system.

@jansol commented on GitHub (Dec 27, 2024): Simply using the `serif`/`sans-serif`/`monospace` aliases should yield a decent set of fonts and their corresponding fallback lists as determined by the browser/system.

kerem commented

2026-02-25 23:33:54 +03:00

Author

Owner

@fmartingr commented on GitHub (Feb 15, 2025):

Simply using the serif/sans-serif/monospace aliases should yield a decent set of fonts and their corresponding fallback lists as determined by the browser/system.

By that you mean that we can use:

font-family: Arial, serif, sans-serif; // or monospace where applicable

(Where Arial can be any ohter font)

And that would work? I see we already have sans-serif set as fallback in most places:

$ ag "font-family" --file-search-regex '\.(less|html)$'
internal/view/assets/less/archive.less
46:                     font-family: "Source Sans Pro", sans-serif;

internal/view/assets/less/common.less
62:     font-family: "Source Sans Pro", sans-serif;
476:                    font-family: "Ubuntu Mono", "Courier New", Courier, monospace;

@fmartingr commented on GitHub (Feb 15, 2025): > Simply using the `serif`/`sans-serif`/`monospace` aliases should yield a decent set of fonts and their corresponding fallback lists as determined by the browser/system. By that you mean that we can use: ```less font-family: Arial, serif, sans-serif; // or monospace where applicable ``` (Where Arial can be any ohter font) And that would work? I see we already have `sans-serif` set as fallback in most places: ``` $ ag "font-family" --file-search-regex '\.(less|html)$' internal/view/assets/less/archive.less 46: font-family: "Source Sans Pro", sans-serif; internal/view/assets/less/common.less 62: font-family: "Source Sans Pro", sans-serif; 476: font-family: "Ubuntu Mono", "Courier New", Courier, monospace; ```

kerem commented

2026-02-25 23:33:54 +03:00

Author

Owner

@jansol commented on GitHub (Feb 15, 2025):

By that you mean that we can use:

Yes, although it shouldn't be necessary to specify both serif and sans-serif (and monospace for that matter), any one of the three should be enough as a fallback.

@jansol commented on GitHub (Feb 15, 2025): > By that you mean that we can use: Yes, although it shouldn't be necessary to specify both `serif` and `sans-serif` (and `monospace` for that matter), any one of the three should be enough as a fallback.