[x3d-public] [x3d] Spec Comment by on 19775-1: X3D Architecture - V4.0

[Brutzman, Donald (Don) (CIV)]

Thanks for this issue report Doug.  Not finding this reported in Mantis
previously.  Added comment and analysis as follows.

 

* Mantis 1396: ScreenFontStyle default value for justify field

* https://www.web3d.org/member-only/mantis/view.php?id=1396

 

	
36.4.4 ScreenFontStyle
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
components/layout.html#ScreenFontStyle
-----------------
MFString justify "BEGIN"
- should the default be ["BEGIN","BEGIN"] ?
-----------------
Field signature is specifically listed as

  MFString [in,out] justify "BEGIN"
["BEGIN"|"END"|"FIRST"|"MIDDLE"|""],["BEGIN"|"END"|"FIRST"|"MIDDLE"|""]

 

Corresponding justify field signature in FontStyle matches, recently
modified by Mantis 975.

* 15.4.1 FontStyle
*
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
components/text.html#FontStyle

  MFString [in,out] justify "BEGIN"
["BEGIN"|"END"|"FIRST"|"MIDDLE"|""],["BEGIN"|"END"|"FIRST"|"MIDDLE"|""]

The listing of allowed values matches, as expected.

Next, FontStyle includes prose which should similarly be applied to
ScreenFontStyle:

"The FontStyle node defines the size, family, and style used for Text nodes
(see 15.2.2 Text formatting)"

For clarity and ready reference, following addition appended
ScreenFontStyle:   "and 15.2.2 Text formatting"

 

15.2.2 definitions for justify field note that

* Thus, justify values of "", "BEGIN", and ["BEGIN" "FIRST"] are equivalent.
* An empty justify value ("") is equivalent to the default value.
* If the second string, minor alignment, is not specified, minor alignment
defaults to the value "FIRST".
* Thus, justify values of "", "BEGIN", and ["BEGIN" "FIRST"] are equivalent.

One could make a case that explicit default values for justify ought to be
used, namely ["BEGIN" "FIRST"] instead. This looks quite different, but is
actually the same.

Since the spec is quite explicit about these cases and no functional
changes, suggest leaving defaults the same so that no unexpected side
effects are provoked in legacy models or legacy code.

 

What do you think?

 

all the best, Don

-- 

Don Brutzman  Naval Postgraduate School, Code USW/Br        brutzman at nps.edu

Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA    +1.831.656.2149

X3D graphics, virtual worlds, Navy robotics https://
faculty.nps.edu/brutzman

 

-----Original Message-----
From: x3d <x3d-bounces at web3d.org> On Behalf Of Spec Feedback
Sent: Saturday, May 7, 2022 2:32 PM
To: x3d at web3d.org
Subject: [x3d] Spec Comment by on 19775-1: X3D Architecture - V4.0

 

-- Submitter indicates that this comment may be public: *Yes* --

 

Comment on 19775-1: X3D Architecture - V4.0

36.4.4

 
<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01
/components/layout.html#ScreenFontStyle>
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
components/layout.html#ScreenFontStyle

 

-----------------

MFString justify "BEGIN"

- should the default be ["BEGIN","BEGIN"] ?

-----------------

 

Submitted on Saturday, 2022,  May 7 - 2:31pm by  (Doug Sanden )

IP: 23.17.48.28

 

See:  <https://www.web3d.org/node/1694/submission/5778>
https://www.web3d.org/node/1694/submission/5778

 

 

_______________________________________________

x3d mailing list

 <mailto:x3d at web3d.org> x3d at web3d.org

 <http://web3d.org/mailman/listinfo/x3d_web3d.org>
http://web3d.org/mailman/listinfo/x3d_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220508/20e5a9fe/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5353 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220508/20e5a9fe/attachment.p7s>