~sansfontieres

Bordeaux, France

https://sansfontieres.com

Design studio: typeface & book design.

Code pushed on dev.sansfontieres.com

Recent activity

[PATCH] filetype: add .glif to xml 8 months ago

From Romain Hervier to ~martanne/devel

---
.glif files are used in type design development. From the current
specification[0]:
> The Glyph Interchange Format (GLIF) is a simple and clear XML representation
> of a single glyph. GLIF files typically have a .glif extension.
[0]: https://unifiedfontobject.org/versions/ufo3/glyphs/glif/

 lua/plugins/filetype.lua | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/lua/plugins/filetype.lua b/lua/plugins/filetype.lua
index 3cd234e..6116b9a 100644
--- a/lua/plugins/filetype.lua
+++ b/lua/plugins/filetype.lua
[message trimmed]

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Romain Hervier to ~sircmpwn/sr.ht-discuss

Quoth Thomasorus <oss@thomasorus.com>:
> The current fonts are already sans-serif and monospace fonts, that are on
> your system, so this part is already done.

My bad, the sans-serif is indeed the only body font defined on sr.ht,
but it’s not the case for the monospaced font declaration.
 
> Allowing to use custom fonts would be a very different project in itself as 
> each user would need to use the cascade to overwrite the default font
> family entries. That could be done with an input/textarea in your meta
> section, but I have no idea of the technical aspects of this. Drew can maybe
> tell you a bit more about this than I do.

Oh yeah, I know. That’s why I’m suggesting to only use bare sans-serif

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Romain Hervier to ~sircmpwn/sr.ht-discuss

Quoth Humm <hummsmith42@gmail.com>:
> I never understood why there are long lists of type faces that might be
> installed in the CSS; is there any reason for that?  I’d rather use the type
> face I configured as default throughout my system than one the designer
> thought was common or something.

They have their use for general public websites and whatnot (defining a
coherent fallback stategy to have a consistent layout, or if an hosted
font doesn’t load), but I’m not so sure about their usage on a technical
websites like sr.ht :^)

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Romain Hervier to ~sircmpwn/sr.ht-discuss

Quoth Thomasorus <oss@thomasorus.com>:
> Let me know what you think.

It’s quite a good recreation of the original design. I’m not a fan of
the large variation, it’s less efficient and readable than the original
spacing.

While we are discussing the matter: what about font preferences? I think
that setting the font-family to sans-serif and monospace would lead to a
random direction but may allow better accessibility for dyslexic persons
for example. Or even allow people to set the programming font they are
used to in their browser preference. Just chiming in.

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Romain Hervier to ~sircmpwn/sr.ht-discuss

I think that it would also be an improvement to allow people who host
a sourcehut instance to customize the CSS or do some light templating
modifications in an easy way.

Right now, such customizations would need the user of to provide a
modified copy of the frontend, which is arguably useless/overkill. I
may be wrong on the licensing situation, though, I didn’t really
check.

Working on a new frontend with such details in mind would be
appreciated I think.