proposal of non-normative regex and text for DR 09-0061, ST_Panose issue

[Chris Rae]

Hi Suzuki-san - many thanks for putting this together.

I agree that this information is useful, but it contains implementation details that aren't covered anywhere else in the standard so I don't think it ought to be informative. That said, I am not completely sure that it ought to be normative either. Typically in the standard have steered clear of describing what to do with invalid values, and the proposed text really just describes what Microsoft Office does with invalid Panose values. We could perhaps declare in IS 29500 that the value must contain a Panose-1 value, and then Microsoft should fully document in their implementer notes the process you outline in this text (along with any other detail or restrictions that we find).

Others on WG4 - what do you think of this approach? Suzuki-san, is the situation common enough that we really should document how to deal with invalid data?

Chris

-----Original Message-----
From: suzuki toshiya [mailto:mpsuzuki at hiroshima-u.ac.jp] 
Sent: 29 March 2011 11:44
To: Chris Rae
Cc: MURATA Makoto (FAMILY Given); e-SC34-WG4 at ecma-international.org
Subject: proposal of non-normative regex and text for DR 09-0061, ST_Panose issue

Dear Chris,

Here is my draft of non-normative regex and the description about how to fallback from invalid Panose-1 value, please comment if such text is suitable to ISO spec. This text is not normative, but I wish if OOXML can provide the info how to simulate existing implementation by Microsoft when it gets invalid Panose-1 value.

Regards,
suzuki toshiya, Hiroshima University