<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">If I open a X3D scene with FontLibrary nodes in an editor like Castle or Sunrize, there is normally no knowledge about any parent scenes, thus FontLibrary should be scene scoped.<div><br></div><div>Best regards,</div><div>Holger</div><div><br></div><div><div>
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="text-align: start; text-indent: 0px; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px;">--</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px;">Holger Seelig</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px;">Leipzig, Germany</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px;"><br></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px;">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 01.03.2025 um 15:45 schrieb Andreas Plesch via x3d-public <x3d-public@web3d.org>:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div class="gmail_quote gmail_quote_container"><div>I basically had the same questions as Michalis.</div><div><br></div><div>Comments below.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Date: Sat, 1 Mar 2025 05:52:24 +0100<br>
From: Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>><br><br>
As for FontLibrary,<br>
<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary</a><br>
: I admit I don't understand this proposal (yet).<br>
<br>
1. Where is the FontLibrary actually used? It doesn't seem you can refer to<br>
a FontLibrary node in any way. It's also not X3DChildNode, so you cannot<br>
just place it in groups.<br></blockquote><div><br></div><div>This is a big missing piece.</div><div>After some thought, I think the idea is to give the X3D browser information on how to render fonts which are referenced in a FontStyle.family field. </div><div>One option is to think of it not as a Node but as a Statement describing a resource available to the X3D browser in general.</div><div>Another option is to make it part of WorldInfo as a value for a new WorldInfo.fonts field ?</div><div>The idea came up as an alternative to a FontStyle.url field, so see below.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2. The sentence """If present, only the first active font library retrieved<br>
from the url list shall be used."""" --- What is the meaning of word "used"<br>
in this sentence? Used for what?<br></blockquote><div><br></div><div>What is 'active' ? Probably accessible</div><div><br></div><div>"Used": ?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
3. """Individual font library files can be used by multiple FontStyle nodes<br>
in a scene.""" -- How? FontStyle does not refer to FontLibrary. And I<br>
understand in this version, FontStyle would not have its own FontStyle.url<br>
field.<br>
<br>
Did you maybe want to add a field like "SFNode FontLibrary<br>
fontLibrary" to FontStyle or Text? Or make FontLibrary a X3DChildNode?<br></blockquote><div><br></div><div>That was my first thought as well but see above.</div><div>A simple way to make a FontLibrary url available to multiple FontStyle nodes is by DEF/USE.</div><div>A FontStyle.fontLibrary field is preferred over a global scope since it clearly associates a font to a FontStyle/Text.</div><div>It is better not to have to rely on the family name to identify a font. Having to rely on the family name is more error prone for both the author and the browser.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
4. A testcase, preferably many testcase(s), explaining the FontLibrary<br>
usage (X3D files + intended rendering) would very helpful. (Same goes for<br>
the previous proposal actually.) Please provide testcases along with spec<br>
prose -- they make the intention more obvious.<br></blockquote><div><br></div><div>Including edge cases if possible.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Overall, so far, I admit FontLibrary is confusing to me, I don't know what<br>
it means. The previous proposal (extending FontStyle) seems more<br>
straightforward -- a few people (including me) had feedback, but it seems<br>
that we all "got the intention" of FontStyle.url correctly, we just pointed<br>
some things to improve in wording.<br></blockquote><div><br></div><div>One advantage of a FontLibrary (or perhaps just 'Font') node would be DEF/USE.</div><div><br></div><div>As mentioned multiple times, the spec. should include language that the FontStyle.style field may be ignored if a FontLibrary url is accessible as in most cases that url will only provide data for one specific style..</div><div><br></div><div>Regards, -Andreas</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
pt., 28 lut 2025 o 19:56 Brutzman, Donald (Don) (CIV) via x3d-public <<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>> napisa?(a):<br>
<br>
> Thanks everyone for responses, implementation improvements, technical<br>
> details, and many insights.<br>
><br>
> First positive takeaway: WOFF File Format 2.0 is the clear preference to<br>
> WOFF 1.0.<br>
><br>
> WOFF File Format 2.0, W3C Recommendation, 08 August 2024<br>
><br>
> - "Abstract. Based on experience with WOFF 1.0, which is widely<br>
> deployed, this specification was developed to provide improved compression<br>
> and thus lower use of network bandwidth, while still allowing fast<br>
> decompression even on mobile devices. This is achieved by combining a<br>
> content-aware preprocessing step and improved entropy coding, compared to<br>
> the Flate compression used in WOFF 1.0."<br>
> - <a href="https://www.w3.org/TR/WOFF2" rel="noreferrer" target="_blank">https://www.w3.org/TR/WOFF2</a><br>
><br>
> Clearly, from recent excellent emails, there are many implementer-specific<br>
> issues and interactions when adding font files that are good to know about,<br>
> but don't necessarily need to be expressed in an X3D model (or the X3D<br>
> Architecture specification).<br>
><br>
> Dick and I worked further today to assess whether separation of font files<br>
> from FontStyle node into a FontLibrary node was the preferred to represent<br>
> this information in an X3D model. We also repeated WOFF Recommendation's<br>
> use of term "collection" as part of a *FontLibrary *definition.<br>
><br>
> - The FontLibrary node specifies a collection of one or more font<br>
> family definitions. A font family may include one or more related font<br>
> style definitions. FontLibrary provides the ability to selectively load<br>
> font files for use by FontStyle<br>
> <<a href="https://outlook.office.com/mail/id/AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AN5ikByHYYkeveIfklhUi1gAG%2Blh21AAA?nativeVersion=1.2025.219.400#FontStyle" rel="noreferrer" target="_blank">https://outlook.office.com/mail/id/AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AN5ikByHYYkeveIfklhUi1gAG%2Blh21AAA?nativeVersion=1.2025.219.400#FontStyle</a>> and<br>
> ScreenFontStyle<br>
> <<a href="https://outlook.office.com/mail/id/layout.html#ScreenFontStyle" rel="noreferrer" target="_blank">https://outlook.office.com/mail/id/layout.html#ScreenFontStyle</a>> nodes.<br>
><br>
> FontLibrary node pros (meaning separation of font files from FontStyle<br>
> node):<br>
><br>
> - Keeps existing (and fairly complex) FontStyle implementations<br>
> unchanged<br>
> - Separation of loading and presentation functionality between two<br>
> nodes<br>
> - FontLibrary simply adds to the selection of fonts available, and<br>
> retains emphasis of *family *and *style *fields within a given<br>
> FontStyle node.<br>
> - If separate font files redefine a given family (with the same name),<br>
> then addition of *enabled *field might allow authors to determine<br>
> which of them is relevant. However *enabled *field can be considered<br>
> redundant (since changing url has same effect).<br>
> - Alternative approach to use of an *enabled *field, we might also<br>
> need to add a sentence such as<br>
> - "If a font family is redefined by multiple FontLibrary nodes, then<br>
> the first defined family is used."<br>
> - (or we can remain silent and let browser implementations sort<br>
> that out)<br>
><br>
> FontLibrary node cons (meaning bundle all url functionality in FontStyle):<br>
><br>
> - Closer coupling of *family *field and font files themselves, recent<br>
> email dialog indicates that sometimes the font file simply overrides the<br>
> family field...<br>
> - We do not want to change any defined functionality for *family* and *style<br>
> *fields, they still seem correct in X3D Architecture and no suitable<br>
> changes yet seen.<br>
> - No need for *enabled *field.<br>
><br>
> Our current opinion is that FontLibrary provides a superior approach to<br>
> continued growth of FontStyle node. To facilitate comparison and review,<br>
> current draft has proposed FontLibrary prose in yellow, and alternate<br>
> (not accepted) FontStyle alternative in cyan.<br>
><br>
> - X3D 4.1 (draft) Architecture, clause 15 Text component, 15.4.1<br>
> FontLibrary<br>
> -<br>
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary</a><br>
> X3D Architecture 4.1 draft ? ISO/IEC 19775-1:202x ? 15 Text component<br>
> <<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/text.html#FontLibrary</a>><br>
> 15.2.2.4 Language. The language field specifies the context of the<br>
> language for the text string in the form of a language and a country in<br>
> which that language is used. Both the language and the country are<br>
> specified using the language tags defined in which may specify only a<br>
> country (using the three-character codes defined in ISO 3166) or both a<br>
> language (using the two-character codes ...<br>
> <a href="http://www.web3d.org/" rel="noreferrer" target="_blank">www.web3d.org</a><br>
><br>
><br>
> Additional questions to ponder, further insights welcome:<br>
><br>
> - Our impression of the term 'webfont' is that it is simply a generic<br>
> term, not a standard or specification per se, and often employed to<br>
> reference WOFF. Is that correct?<br>
><br>
> - Font files tend to be large. Might there ever be a use case where<br>
> an author chooses to define a font as source text in the url field? We<br>
> have some precedent for this in Script url and (sorta) PixelTexture.<br>
> Nevertheless font definitions are also convoluted and (perhaps notoriously)<br>
> difficult to parse. Of note is that WOFF2 specifically is designed for<br>
> effective binary compression. Our inclination so far is to not describe<br>
> (or encourage) definition of the font within an X3D model. YMMV (though we<br>
> doubt it). Much better authoring approach is to use any of many conversion<br>
> tools that might credibly update a legacy font into WOFF2.<br>
><br>
> Thanks everyone for leaning forward on this, looking ahead to continuing<br>
> discussion.<br>
><br>
> Have fun with font library collections for X3D models! ?<br>
><br>
><br>
> all the best, Don<br>
><br>
> --<br>
><br>
> Don Brutzman Naval Postgraduate School, Code USW/Br<br>
> <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
><br>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA<br>
> +1.831.656.2149<br>
><br>
> X3D graphics, virtual worlds, navy robotics<br>
> <a href="https://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">https://faculty.nps.edu/brutzman</a><br>
><br>
><br>
><br>
> ------------------------------<br>
> *From:* x3d-public <<a href="mailto:x3d-public-bounces@web3d.org" target="_blank">x3d-public-bounces@web3d.org</a>> on behalf of Brutzman,<br>
> Donald (Don) (CIV) via x3d-public <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Sent:* Wednesday, February 26, 2025 5:39 PM<br>
> *To:* X3D <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Cc:* Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br>
> *Subject:* Re: [x3d-public] draft X3D 4.1 prose for font files and<br>
> libraries<br>
><br>
> Dick and I worked on suggested prose for X3D 4.1 with details continuing<br>
> in Mantis 1490 below.<br>
><br>
> Review request:<br>
><br>
> - X3D 4.1 Architecture (draft), 15 Text component, 15.4.1 FontStyle<br>
> -<br>
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/components/text.html#FontStyle" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/components/text.html#FontStyle</a><br>
><br>
> Improvements:<br>
><br>
> - Include all X3DURLObject fields,<br>
><br>
> SFTime [in,out] autoRefresh 0.0 [0,?)<br>
> SFTime [in,out] autoRefreshTimeLimit 3600.0 [0,?)<br>
> SFString [in,out] description ""<br>
> SFBool [in,out] load TRUE<br>
> MFString [in,out] url [] [URI]<br>
><br>
> - Decided to NOT overload functionality of *family * field by adding<br>
> file names (sorry Holger! adjusting your implementation will likely be<br>
> simple in comparison)<br>
><br>
> - New prose:<br>
><br>
> The *url* field is optional and can refer to a relative or online address<br>
> for a font library that contains one or more font definitions. An empty<br>
> *url* list indicates that the default set of fonts provided by the<br>
> browser are used. If present, only the first active font library retrieved<br>
> from the *url* list shall be used. Individual font library files can be<br>
> used by multiple FontStyle nodes in a scene. Each font file only needs to<br>
> be loaded once per session.<br>
> X3D browsers shall support WOFF (MIME type application/x-font-woff) (see W3C<br>
> WOFF File Format<br>
> <<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/references.html#W3C_WOFF" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/references.html#W3C_WOFF</a>>).<br>
> Support for the OpenType file format (MIME type<br>
> application/x-font-opentype) (see OpenType Specification<br>
> <<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/bibliography.html#OPENTYPE" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/bibliography.html#OPENTYPE</a>>)<br>
> and TrueType file format (MIME type application/x-font-truetype) (see ISO/IEC<br>
> 14496-22 Open Font Format<br>
> <<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/references.html#I14496_22" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/references.html#I14496_22</a>>)<br>
> is also recommended.<br>
> Security, licensing, and copyright/usage permissions are handled via the<br>
> exposure of a font file itself.<br>
> Support for the *autoRefresh*, *autoRefreshTimeLimit*, and *load* fields is<br>
> optional.<br>
> More details on the *autoRefresh*, *autoRefreshTimeLimit*, *description*,<br>
> *load*, and *url* fields are contained in 9.2.1 URLs, URNs and URIs<br>
> <<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/components/networking.html#URLs" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/components/networking.html#URLs</a>><br>
> .<br>
> Looking it over, adding more functionality to FontStyle node seems to be<br>
> unwise. Dick has an excellent proposal:<br>
> TODO alternative approach: move all new functionality into a separate<br>
> *FontLibrary* node to avoid complicating FontStyle further. This also<br>
> offers the ability to succinctly load multiple font libraries in a given<br>
> scene. The expense of defining a new node for X3D is offset by clearer<br>
> distinction between X3D 4.0 and 4.1, also simplifying model content<br>
> significantly.<br>
> Feedback is welcome.<br>
> Leaving existing FontStyle implementations alone probably avoids many<br>
> unintended side effects. First law of engineering: "If it ain't broke,<br>
> don't fix it."<br>
><br>
> Thanks for all review. It feels like we are finally converging on a<br>
> straightforward approach to valuable future capabilities.<br>
><br>
> Have fun with X3D fonts! ?<br>
><br>
><br>
> all the best, Don<br>
><br>
> --<br>
><br>
> Don Brutzman Naval Postgraduate School, Code USW/Br<br>
> <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
><br>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA<br>
> +1.831.656.2149<br>
><br>
> X3D graphics, virtual worlds, navy robotics<br>
> <a href="https://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">https://faculty.nps.edu/brutzman</a><br>
><br>
><br>
><br>
> ------------------------------<br>
> *From:* Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br>
> *Sent:* Monday, February 24, 2025 9:32 AM<br>
> *To:* X3D <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Cc:* Holger Seelig <<a href="mailto:holger.seelig@yahoo.de" target="_blank">holger.seelig@yahoo.de</a>><br>
> *Subject:* Re: [x3d-public] Open dyslexic and/or (unfortunately)<br>
> comicsans fonts; draft X3D 4.1 prose for font files and libraries<br>
><br>
> Wow, really super Holger! ?<br>
><br>
> There was a conversation about this on x3d-public a few years back... We<br>
> committed to adding it in X3D 4.1 and (if I recall correctly) also noted<br>
> that adding a url field might enable usage of larger font files.<br>
><br>
> I've attempted to capture this candidate specification change in a Mantis<br>
> issue. All review, feedback, and improvements are always welcome.<br>
><br>
> - Mantis 1490 FontStyle handling of font files and font libraries<br>
> - <a href="https://mantis.web3d.org/view.php?id=1490" rel="noreferrer" target="_blank">https://mantis.web3d.org/view.php?id=1490</a><br>
><br>
> Description.<br>
> A goal for X3D 4.1 is use of font files in FontStyle (see Mantis 0001464<br>
> <<a href="https://mantis.web3d.org/view.php?id=1464" rel="noreferrer" target="_blank">https://mantis.web3d.org/view.php?id=1464</a>>).<br>
><br>
> Addition of individual-font files might be accomplished by listing the<br>
> font file name in the FontStyle 'family' field.<br>
><br>
> Referencing different fonts in a single combined font library file may<br>
> require an additional field, for example 'url'. In general the use of a<br>
> font library may be preferred, but repeatedly run-time retrieval of a font<br>
> library is not desirable, since the file might be quite large and rarely<br>
> changing. This might be noted in the specification prose, e.g.<br>
><br>
> - "MFString [in,out] url [] [URI]"<br>
> - "The family field may list a specific font file. A font listed in the<br>
> family field may be provided by a corresponding font library."<br>
> - "The url field may refer to a font library. Font libraries can be used<br>
> by multiple FontStyle nodes in a scene and need only be loaded once per<br>
> session."<br>
><br>
> Support levels: add "Level 2, FontStyle, support for font files in family<br>
> field and support for font libraries via url field ."<br>
><br>
> Security, licensing, and copyright/usage issues are handled via the<br>
> exposure of the font file itself. If retrievable (locally or online) then<br>
> proper access is presumably handled separately.<br>
><br>
> Additional information.<br>
> - X3D 4.1 (draft) Architecture, 15 Text component, 15.4.1 FontStyle<br>
> -<br>
> <a href="https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#FontStyle" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#FontStyle</a><br>
><br>
> - X3D 4.1 (draft) Architecture, 15 Text component, 15.4.2 Text<br>
> -<br>
> <a href="https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#Text" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#Text</a><br>
><br>
> - X3D 4.1 (draft) Architecture, 15 Text component, 15.5 Support levels<br>
> -<br>
> <a href="https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#SupportlLevels" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/text.html#SupportlLevels</a><br>
><br>
> Have fun with X3D Text! :)<br>
><br>
><br>
> all the best, Don<br>
><br>
> --<br>
><br>
> Don Brutzman Naval Postgraduate School, Code USW/Br<br>
> <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
><br>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA<br>
> +1.831.656.2149<br>
><br>
> X3D graphics, virtual worlds, navy robotics<br>
> <a href="https://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">https://faculty.nps.edu/brutzman</a><br>
><br>
><br>
><br>
> ------------------------------<br>
> *From:* x3d-public <<a href="mailto:x3d-public-bounces@web3d.org" target="_blank">x3d-public-bounces@web3d.org</a>> on behalf of Holger<br>
> Seelig via x3d-public <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Sent:* Monday, February 24, 2025 2:48 AM<br>
> *To:* X3D <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Cc:* Holger Seelig <<a href="mailto:holger.seelig@yahoo.de" target="_blank">holger.seelig@yahoo.de</a>><br>
> *Subject:* Re: [x3d-public] Open dyslexic and/or (unfortunately)<br>
> comicsans fonts<br>
><br>
> With X_ITE you can use a URL in the family field of a FontStyle node to<br>
> specify a path to a custom font file. Provided you have one of these fonts,<br>
> it should be very easy:<br>
><br>
> <?xml version="1.0" encoding="UTF-8"?><br>
> <!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 4.0//EN" "<br>
> <a href="https://www.web3d.org/specifications/x3d-4.0.dtd" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/x3d-4.0.dtd</a>"><br>
> <X3D profile='Interchange' version='4.0' xmlns:xsd='<br>
> <a href="http://www.w3.org/2001/XMLSchema-instance" rel="noreferrer" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>' xsd:noNamespaceSchemaLocation='<br>
> <a href="https://www.web3d.org/specifications/x3d-4.0.xsd" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/x3d-4.0.xsd</a>'><br>
> <head><br>
> <component name='Text' level='1'/><br>
> </head><br>
> <Scene><br>
> <Transform DEF='Text'><br>
> <Shape><br>
> <Appearance><br>
> <Material/><br>
> </Appearance><br>
> <Text<br>
> string='"3D Text"'><br>
> <FontStyle<br>
> family='"path/to/your/font.otf", "SERIF"'/><br>
> </Text><br>
> </Shape><br>
> </Transform><br>
> </Scene><br>
> </X3D><br>
><br>
> Supported File Formats:<br>
><br>
> <a href="https://create3000.github.io/x_ite/components/text/fontstyle/#supported-file-formats" rel="noreferrer" target="_blank">https://create3000.github.io/x_ite/components/text/fontstyle/#supported-file-formats</a><br>
><br>
> Best regards,<br>
> Holger<br>
><br>
> --<br>
> Holger Seelig<br>
> Leipzig, Germany<br>
><br>
> <a href="mailto:holger.seelig@yahoo.de" target="_blank">holger.seelig@yahoo.de</a><br>
> <a href="https://create3000.github.io/x_ite/" rel="noreferrer" target="_blank">https://create3000.github.io/x_ite/</a><br>
><br>
> Am 24.02.2025 um 11:09 schrieb John Carlson via x3d-public <<br>
> <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>>:<br>
><br>
> If someone knows how change the fonts of the standards to OpenDyslexic or<br>
> ComicSans, that might be a great accessibility experiment.<br>
> _______________________________________________<br>
> x3d-public mailing list<br>
> <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
><br>
><br>
> _______________________________________________<br>
> x3d-public mailing list<br>
> <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250301/db01b350/attachment.html" rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250301/db01b350/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of x3d-public Digest, Vol 191, Issue 133<br>
********************************************<br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Andreas Plesch<br>Waltham, MA 02453</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>