#idk why this template isn't working

23 messages · Page 1 of 1 (latest)

vale moss
#

The goal was to have the ability to use fonts without manually defining a global list of the uploaded fonts anywhere

( I'm using the css extension )

MediaWiki

The CSS extension allows CSS stylesheets to be included in specific articles. The CSS can be another article, a file or can be rules defined directly within the parser-function.

#

no I saw the post guidelines last second and then they disappeared

#

idk what it said 🥀

muted slate
#

that's not where the files are stored

vale moss
#

do I drop "/wiki/" or is that still wrong

muted slate
#

if you open the file page for the font, there'll be a link to the original location

#

e.g https://static.wikitide.net/fischwiki/3/3d/AccanthisADFStd.otf

vale moss
#

I think that changes per-file

muted slate
#

indeed it does

vale moss
#

idk how to automate getting that for the sake of not wanting to manually define every uploaded font file somewhere

muted slate
#

you could load in both fonts and only use the one you want

#

it would not have significant performance implications

vale moss
#

well both file formats don't exist at once, it's for the sake of not manually defining what file format {{{1}}} could be in

#

also I'd wanna use every font file I upload

muted slate
#

but unless you are using hundreds, you'll be fine

vale moss
#

I just thought it'd be inconvenient to have a manually-typed-in global list

muted slate
#

stick it in common.css and forget about it

#

it's not like the url is going to change after that

vale moss
muted slate
#

it's not like fonts get updates

#

i havent actually checked if/when the url changes tbh

#

if it did i feel like there'd be a lot more complaints tho