Reviewers
Request review
No reviewers
Labels
Clear labels
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Apply labels
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
No Label
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#787
Reference in New Issue
There is no content yet.
Delete Branch 'theMasix'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
I added the Vazir Font based on a request from #783
👀
as long as the lines don't get excessively long, why not keep this inline?
@ -4,3 +3,1 @@
@import url('./fonts/Route159/Route159.css');
@import url('./fonts/Lora/Lora.css');
@import url('./fonts/Playfair_Display/PlayfairDisplay.css');
@import url("./feather.css");
what's the license are these files?
Codecov Report
VSCode Prettier extension did this.
@ -4,3 +3,1 @@
@import url('./fonts/Route159/Route159.css');
@import url('./fonts/Lora/Lora.css');
@import url('./fonts/Playfair_Display/PlayfairDisplay.css');
@import url("./feather.css");
License added.
since i'm not sure it's that much "prettier", or more readable for that matter, could we put this back into one line each?
after that it should be good to merge
fixed.
Thank you for your PR! 😊 I still have a small change request, and then we should be good to merge!
This font is for the interface. Maybe you could also import the Shabnam font as suggested in #783 instead of Vizir for this one? This can be done in another PR, but if you don't want to do it in this one, could you at least restore Route159? It looks like there are some margin issues with this font on some buttons (but not in other places strangely).
(it is quite subtle, but the text is not perfectly centered vertically)
could we do what was suggested and only enable this for certain Unicode ranges?
🙋♀️
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
we could add
unicode-range
hereunfortunately, those being the same as Arabic, might break Arabic texts.
@DearRude, what do you think?
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
Just like English and German, Persian and Arabic have common characters. We would not be able to cut down Arabic by
unicode-range
.However, I suggest using Vazir and Shamim fonts for Arabic too. Since those fonts fully support Arabic and have been used in other projects in Arabic, I won't be a bad idea if we support both.
I can provide range of unicode in Persian and Arabic together if needed.
I believe using non-Latin one would have the same effect. If we prioritize it, only Persian and Arabic chars will be effected.
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
the ranges are well documented, https://en.m.wikipedia.org/wiki/Arabic_script_in_Unicode but excessive
so i think we should use the non-Latin variants of the scripts.
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
This
Vazir-WOL
is a non-latin package. But as @dearrude said, Persian and Arabic has some common characters.@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
WOL ➡️ Without Latin
so how come @elegaanz noticed those issues with the centering of the text? what's going on?
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
As @elegaanz said, It's an strange issue and I don't know if
Shabnam
could fix it or not!@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
let's try!
@ -0,0 +6,4 @@
url('Vazir-WOL.woff') format('woff'),
url('Vazir-WOL.ttf') format('truetype');
font-weight: normal;
font-style: normal;
Shabnam-WOL
Added. @igalic @elegaanzPerfect! Thank you!
Reviewers
28576c1fa3
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Forgejo.