<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
The current design-phase draft prose assumes that </div>
<ul data-editing-info="{"applyListStyleFromLevel":false,"unorderedStyleType":1}" style="list-style-type: disc;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">FontLibrary loads font files and has them available for use by FontStyle and ScreenFontStyle,</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">FontStyle does not load any files,</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">FontStyle definition of 'family' field will look through all of the available fonts to find the correctly matching family.</div>
</li></ul>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
If that is not possible, then it would seem we need another design (perhaps the cyan text) that can closely couple a single perhaps-no-name font file with a corresponding FontStyle.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
My understanding is that a font file can contain multiple fonts, and optionally multiple styles for each font. If so, then some kind of disambiguation by name must be possible, correct?</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
From this perspective, does it seem that two types of font files are possible?</div>
<ul data-editing-info="{"applyListStyleFromLevel":false,"unorderedStyleType":1}" style="list-style-type: disc;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">Those containing a single perhaps-no-name font family, or</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">Those containing multiple named font families.</div>
</li></ul>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Perhaps we need to look at multiple font specifications in detail? Here is the primary specification, WOFF2:</div>
<ul data-editing-info="{"applyListStyleFromLevel":false,"unorderedStyleType":1}" style="list-style-type: disc;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">W3C WOFF File Format 2.0, section 3. Overall file structure and basic data types</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">"<span style="background-color: rgb(255, 255, 0);">The structure of WOFF2 files is similar to that of SFNT and WOFF 1.0 font files, in that there is a header followed by a table directory, followed by the data for those tables. The
SFNT structure is described fully in the TrueType [TrueType], OpenType [OpenType], and ISO "Open Font Format" [OFF] specifications.</span>"</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">"A complete WOFF2 file consists of several blocks of data: a 48-byte header, immediately followed (in this order) by a variable-size Table Directory, an optional Collection Directory (present only if the input font file is a font
collection), a compressed font data block, an optional block of Extended Metadata, and an optional block of Private Data."</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">"WOFF2 File</div>
</li><ul data-editing-info="{"applyListStyleFromLevel":true}" style="list-style-type: circle;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof"><span style="background-color: rgb(255, 255, 0);">WOFF2Header
</span>      <span style="background-color: rgb(255, 255, 0);">File header with basic font type and version</span>, along with offsets to metadata and private data blocks.</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof">TableDirectory    Directory of font tables, containing size and other info. "</div>
</li></ul>
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="elementToProof"><a href="https://www.w3.org/TR/WOFF2/#FileStructure" id="LPlnk" class="OWAAutoLink">https://www.w3.org/TR/WOFF2/#FileStructure</a></div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1">
<div id="LPBorder_GTaHR0cHM6Ly93d3cudzMub3JnL1RSL1dPRkYyLyNGaWxlU3RydWN0dXJl" class="LPBorder613833" style="width: 100%; margin-top: 16px; margin-bottom: 16px; position: relative; max-width: 800px; min-width: 424px;">
<table id="LPContainer613833" role="presentation" style="padding: 12px 36px 12px 12px; width: 100%; border-width: 1px; border-style: solid; border-color: rgb(200, 200, 200); border-radius: 2px;">
<tbody>
<tr valign="top" style="border-spacing: 0px;">
<td style="width: 100%;">
<div id="LPTitle613833" style="font-size: 21px; font-weight: 300; margin-right: 8px; font-family: wf_segoe-ui_light, "Segoe UI Light", "Segoe WP Light", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px;">
<a target="_blank" id="LPUrlAnchor613833" href="https://www.w3.org/TR/WOFF2/#FileStructure" style="text-decoration: none; color: var(--themePrimary);">WOFF File Format 2.0 - World Wide Web Consortium (W3C)</a></div>
<div id="LPDescription613833" style="font-size: 14px; max-height: 100px; color: rgb(102, 102, 102); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px; margin-right: 8px; overflow: hidden;">
3. Overall file structure and basic data types. The structure of WOFF2 files is similar to that of SFNT and WOFF 1.0 font files, in that there is a header followed by a table directory, followed by the data for those tables.</div>
<div id="LPMetadata613833" style="font-size: 14px; font-weight: 400; color: rgb(166, 166, 166); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif;">
www.w3.org</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="elementToProof"><br>
</div>
</li></ul>
<div class="elementToProof" style="font-family: "Courier New"; font-size: 9pt; color: rgb(0, 0, 0);">
all the best, Don</div>
<div class="elementToProof" id="Signature">
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Courier New"; font-size: 9pt;">--</span></p>
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Courier New"; font-size: 9pt;">Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</span></p>
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Courier New"; font-size: 9pt;">Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span></p>
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Courier New"; font-size: 9pt;">X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman</span></p>
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Courier New"; font-size: 9pt;"> </span></p>
</div>
<div id="appendonsend"></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> x3d-public <x3d-public-bounces@web3d.org> on behalf of Holger Seelig via x3d-public <x3d-public@web3d.org><br>
<b>Sent:</b> Saturday, March 1, 2025 2:12 PM<br>
<b>To:</b> X3D <x3d-public@web3d.org><br>
<b>Cc:</b> Holger Seelig <holger.seelig@yahoo.de><br>
<b>Subject:</b> Re: [x3d-public] draft X3D 4.1 prose for font files and libraries</font>
<div> </div>
</div>
<div style="line-break:after-white-space">
<div>I would also like to point out once again that a font file (WOFF, OTF, TTF) does not automatically contain the name or family name of the font. A name can therefore only be extracted from the URL. Which is certainly not desirable. </div>
<div><br>
</div>
<div>It is therefore not clear how to deduce a font file from the field `FontStyle.family`.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Holger</div>
<div><br>
</div>
<div>
<div dir="auto" style="color:rgb(0,0,0); letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; line-break:after-white-space">
<div dir="auto" style="color:rgb(0,0,0); letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; line-break:after-white-space">
<div dir="auto" style="color:rgb(0,0,0); letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; line-break:after-white-space">
<div dir="auto" style="color:rgb(0,0,0); letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; line-break:after-white-space">
<div dir="auto" style="color:rgb(0,0,0); letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; line-break:after-white-space">
<div dir="auto" style="text-align:start; text-indent:0px; line-break:after-white-space">
<div style="color:rgb(0,0,0); letter-spacing:normal; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
--</div>
<div style="color:rgb(0,0,0); letter-spacing:normal; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
Holger Seelig</div>
<div style="color:rgb(0,0,0); letter-spacing:normal; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
Leipzig, Germany</div>
<div style="color:rgb(0,0,0); letter-spacing:normal; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
<br>
</div>
<div style="color:rgb(0,0,0); letter-spacing:normal; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
holger.seelig@yahoo.de</div>
<div>https://create3000.github.io/x_ite/</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
<blockquote type="cite">
<div>Am 27.02.2025 um 13:26 schrieb Andreas Plesch via x3d-public <x3d-public@web3d.org>:</div>
<br class="x_Apple-interchange-newline">
<div>
<div dir="auto">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Since I wanted to do this for some time as it really makes webfonts much more usable with x3dom, I came up with a first implementation of the url field:
<div><br>
</div>
<div><a href="https://andreasplesch.github.io/Library/Viewer/index.html?url=https://gist.githubusercontent.com/andreasplesch/dc9111dcd106f1a69d567ceca8f52701/raw/8cdf9764f11e08b5f541dee487fc0811bb0cf927/FontHaveFunWithX3D.x3d" data-auth="NotApplicable" originalsrc="https://andreasplesch.github.io/Library/Viewer/index.html?url=https://gist.githubusercontent.com/andreasplesch/dc9111dcd106f1a69d567ceca8f52701/raw/8cdf9764f11e08b5f541dee487fc0811bb0cf927/FontHaveFunWithX3D.x3d">https://andreasplesch.github.io/Library/Viewer/index.html?url=https://gist.githubusercontent.com/andreasplesch/dc9111dcd106f1a69d567ceca8f52701/raw/8cdf9764f11e08b5f541dee487fc0811bb0cf927/FontHaveFunWithX3D.x3d</a></div>
<div><br>
</div>
<div>This is experimental and only for the viewer.</div>
<div><br>
</div>
<div>All loading can be done now by x3dom. Both the style and family fields are essentially ignored if a url MFString is available. Multiple urls can be provided as fallbacks. The url field accepts input and can be changed dynamically.</div>
<div><br>
</div>
<div>Here are other examples which show how css in the html can be used for webfont loading.</div>
<div><br>
</div>
<div><a href="https://andreasplesch.github.io/x3dom/test/functional/text_fonts.html" data-auth="NotApplicable" originalsrc="https://andreasplesch.github.io/x3dom/test/functional/text_fonts.html">https://andreasplesch.github.io/x3dom/test/functional/text_fonts.html</a></div>
<div><br>
</div>
<div>That can have advantages as this then provides all of the very many css options to x3d. For example, it is straightforward to copy and paste the css provided by google fonts. The link between css and x3d becomes the font-family name plus style plus weight.
No changes to the spec. are needed.</div>
<div><br>
</div>
<div>The simplest solution other than a url field I can think of is a new Font node which can only represent one font file with a single font and overrides family and style fields. That node can then be DEF/USEd between Text nodes. Perhaps there could be an
additional FontLibray node which can hold multiple Font nodes but I am not sure if this is necessary.</div>
<div><br>
</div>
<div>In theory, it would be possible to add style (normal, italic) and weight (quite a few classes, and numeric) fields to such a Font node. These would define what the font provides. Then the FontStyle fields could be used to either select the closest match
for rendering, or do synthesis which can be useful as some fonts do not have bold or italic versions. But all this is really the responsibility of the author anyways, and not necessary. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Andreas</div>
<div dir="auto"><br>
</div>
</div>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Wed, Feb 26, 2025 at 10:51 PM Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com">michalis.kambi@gmail.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
Andreas Plesch wrote:<br>
> <a href="https://www.w3.org/TR/WOFF2/" data-auth="NotApplicable" originalsrc="https://www.w3.org/TR/WOFF2/">
https://www.w3.org/TR/WOFF2/</a> is a compressed version of WOFF which seems popular on the web due to smaller file sizes. For example, it is used by the Google free Font service. I do not know if there are js/pascal/c etc. loading libraries for woff2 but it
should at least be recommended.<br>
<br>
CGE (Pascal) just uses FreeType for font reading, so we should support<br>
everything that FreeType handles :) And it does support WOFF 2<br>
according to <a href="https://www.phoronix.com/news/FreeType-2.10.2-Released" data-auth="NotApplicable" originalsrc="https://www.phoronix.com/news/FreeType-2.10.2-Released">
https://www.phoronix.com/news/FreeType-2.10.2-Released</a> .<br>
<br>
><br>
> From what I can tell WOFF and WOFF2 do not need to include font family name information inside the file. So I think that means if such a file is provided it will take precedence over the family field. Holger's overloading suggestion implicitly did this.<br>
><br>
> A web browser will synthesize bold and italic versions from a normal font version. Should this become a requirement for x3d as well ? Probably not. If authors want to use a bold version for certain, they need to provide corresponding font files.<br>
<br>
I see Andres comments align nicely with mine, posted 5 mins ago :)<br>
<br>
I also don't think X3D browsers should have the requirement to<br>
synthesize bold and italic versions from a normal font version. If<br>
FreeType doesn't do this (and I don't think it can) then it's not<br>
something I would ever implement, frankly. I'm not even sure how good<br>
are WWW browsers at doing this "synthesizing". The recommendation for<br>
using fonts, that I always seen followed, is that you need 4 font<br>
files (regular, bold, italic, bold+italic) if you want to provide all<br>
the options. The font authors seems to generally agree -- most fonts<br>
come with 4 such files.<br>
<br>
And as Andreas said, the spec should say that "url" overrides "family".<br>
<br>
Regards,<br>
Michalis<br>
</blockquote>
</div>
<div><br clear="all">
</div>
<div><br>
</div>
</div>
</div>
</div>
_______________________________________________<br>
x3d-public mailing list<br>
x3d-public@web3d.org<br>
http://web3d.org/mailman/listinfo/x3d-public_web3d.org<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>