[J3] [SC22WG5.6428] F2023 DIS ballot results and comments

[Nathan Sircombe]

…there’s also the issue of a licence to consider – I’m pretty sure you get Cambria and such as part of the Office EULA, I don’t think that’ll cover it being lifted and embedded in LaTeX docs… one for the ISO lawyers!?

From: Nathan Sircombe <Nathan.Sircombe at arm.com>
Date: Thursday, 2 February 2023 at 10:58 pm
To: General J3 interest list <j3 at mailman.j3-fortran.org>
Cc: Malcolm Cohen <malcolm at nag-j.co.jp>
Subject: Re: [J3] [SC22WG5.6428] F2023 DIS ballot results and comments
Hi Malcolm,

Apparently so, I did find a few references to using XeLaTeX and LuaLaTex, I’ve never come across them before...

…looks like the C++ std. is set in default LaTeX serif, well as of 2020, but the ISO/IEC cover pages are all in Cambria.

Nathan.

From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Malcolm Cohen via J3 <j3 at mailman.j3-fortran.org>
Date: Thursday, 2 February 2023 at 5:29 am
To: 'General J3 interest list' <j3 at mailman.j3-fortran.org>
Cc: Malcolm Cohen <malcolm at nag-j.co.jp>
Subject: Re: [J3] [SC22WG5.6428] F2023 DIS ballot results and comments
Hi Nathan,

Cambria is supported by xelatex and lualatex. (Strangely, with the ones I have, lualatex does not do bold – it’s just regular weight; xelatex seems to work though.)

Whether the whole document will work is another matter. Likely not.

Cheers,
--
..............Malcolm Cohen, NAG Oxford/Tokyo.

From: J3 <j3-bounces at mailman.j3-fortran.org> On Behalf Of Nathan Sircombe via J3
Sent: Thursday, February 2, 2023 7:18 AM
To: General J3 interest list <j3 at mailman.j3-fortran.org>
Cc: Nathan Sircombe <Nathan.Sircombe at arm.com>
Subject: Re: [J3] [SC22WG5.6428] F2023 DIS ballot results and comments

Hi,

>> Unlike line numbers paragraph numbers remain invariant with different font sizes (mentioned by ITTF in the DIS comments), page sizes and page margins as well as in any translation.  I vote to keep paragraph numbers and not to have line numbers in the versions going outside the Fortran committees.
> I agree with David.

Me also. Paragraph numbering is sufficient granularity I think and doesn’t bring complications with translations and re-numbering between relatively minor revisions.

> Cambria is a Microsoft product, one would think that ISO would use a more independent font
Yes, it’s rather Microsoft-centric. But the real problem is the different font systems. Even if ISO dictated an opensource font, that would likely be OpenType (or TrueType like Cambria et al.) and (as far as I know) LaTeX doesn’t support these, and there’s no easy way to build a LaTeX font from a TrueType. Other flavours of TeX do support Open/TrueType though I think.
I don’t see it’s possible to _actually_ set the whole thing in Cambria. Can we just say ‘no’ on the grounds of ‘cost’.
…has this ever come up before? Does it impact other standards, like C++ (I can’t imagine they’re using Word…)?

Talking of Microsoft – what are all the retro Windows 3 style OLE icons peppered through the document with .txt filename underneath.

Cheers,
Nathan.

From: J3 <j3-bounces at mailman.j3-fortran.org<mailto:j3-bounces at mailman.j3-fortran.org>> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org<mailto:j3 at mailman.j3-fortran.org>>
Date: Wednesday, 1 February 2023 at 9:15 pm
To: David Muxworthy <d.muxworthy at bcs.org.uk<mailto:d.muxworthy at bcs.org.uk>>, sc22wg5 at open-std.org<mailto:sc22wg5 at open-std.org> <sc22wg5 at open-std.org<mailto:sc22wg5 at open-std.org>>, General J3 interest list <j3 at mailman.j3-fortran.org<mailto:j3 at mailman.j3-fortran.org>>
Cc: Gary Klimowicz <gak at dancingbear.dev<mailto:gak at dancingbear.dev>>, David Muxworthy <d.muxworthy at icloud.com<mailto:d.muxworthy at icloud.com>>
Subject: [J3] [SC22WG5.6428] F2023 DIS ballot results and comments

> On Feb 1, 2023, at 09:37, d.muxworthy--- via J3 <j3 at mailman.j3-fortran.org<mailto:j3 at mailman.j3-fortran.org>> wrote:
>
>> The argument against line numbers is that, especially when the document is translated, they can change. Does anyone have strong opinions about whether we should put line numbers back in the official standard? I'd like to keep the paragraph numbers and don't care about line numbers.
>
> Unlike line numbers paragraph numbers remain invariant with different font sizes (mentioned by ITTF in the DIS comments), page sizes and page margins as well as in any translation.  I vote to keep paragraph numbers and not to have line numbers in the versions going outside the Fortran committees.
> David

I agree with David.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230206/6b11bb52/attachment.htm>