[x3d-public] draft X3D 4.1 prose for font files and libraries

[John Carlson]

Or alternatively, provide a cssStyle attribute/field.  Another idea would
be to add a css class in the family field???

Maybe one could support both FontStyle.url and css support?

Hmm!

John


On Fri, Mar 14, 2025 at 10:12 AM John Carlson <yottzumm at gmail.com> wrote:

> I don’t have a clue on why FontStyle.url is insufficient, except that some
> font urls have more than one font.
>
> Perhaps all that is needed is providing more values to existing FontStyle
> fields, and gracefully hide most of the ugly, complicated stuff.   Perhaps
> it would be best to provide a registry of fonts separate from the
> standards?  Maybe even with component levels?
>
> Really, this conversation started with me asking about CSS fonts.  How
> about adding CSS styles to FontStyle???   That is, provide a way to include
> a CSS file, perhaps with Inline?  Or just use existing style attribute?
>
> Hmm!
>
> John
>
> On Fri, Mar 14, 2025 at 5:41 AM Michalis Kamburelis via x3d-public <
> x3d-public at web3d.org> wrote:
>
>>
>>     I still have not heard a convincing argument why a more
>> straightforward "FontStyle.url" was rejected. "FontStyle.url" seems
>> like a straightforward solution that avoids all the pitfalls of
>> "FontLibrary", because the association between FontStyle <-> font file
>> is just explicit.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250314/00d05bcf/attachment.html>