Fwd: WebCGM 2.0 and ISO/IEC 2022 switching

[Lofton Henderson <lofton@rockynet.com>]

Jeff asks me to forward this question to the TC list.  Please copy
him on any replies...

> Date: Fri, 24 Mar 2006 15:23:45
> -0800
> From: Jeff Wolkenhauer <jeffrey.wolkenhauer@ugs.com>
> To: lofton@rockynet.com
> Subject: WebCGM 2.0 and ISO/IEC 2022 switching
>
> Hello Lofton,
>
> [...] I tried the list and it bounced, telling me that I am not a
> subscriber, although I believe I was and have emailed it before. 
> And I couldn't find a way to resubscribe to the list on the Oasis Web
> site.
>
> I have a question below that I'm hoping I can get feedback on from the
> list.  Would you mind forwarding it to the list?  Or I could
> use a tip on getting resubscribed.
> [...]
> Best Regards,
> Jeff Wolkenhauer
> --
>
> =======================================
> Hello group,
>
> I am hoping I can get some clarification regarding the use of ISO/IEC
> 2022 switching within non-graphical strings in WebCGM 2.0.
>
> First, my understanding from the PPF is that
>   1) ISO/IEC 2022 switching is allowed within SF strings.
>   2) The only allowed encodings are ISO Latin1, UTF-8, and
> UTF-16.
> So a CGM generator may switch between any of those three
> encodings.
>
> Is this correct?
>
> I ask because the phrase in the section T.14.5 of the PPF:
>   "Otherwise, the use of ISO 2022 switching
>    is prohibited in non-graphical text string."
> confused me at first, but it's placement in the text and the other
> references to allowing 2022 switching imply the meaning of the phrase to
> be, "Use of character sets other than ISO Latin1, UTF-8, and UTF-16,
> are prohibited for ISO 2022 switching in non-graphical text
> strings".
>
> If the answer to my first question is "yes", my second question
> relates to the scope of the 2022 switch.  Is the character set
> invoked only for that string (my hope) or for all subsequent SF strings
> in the rest of the metafile?
>
> For example, if the default ISO Latin is in effect, and a screen tip is
> to be output in Japanese using UTF-8, I would prepend <ESC 2/5 2/15
> 4/9> to the string.  But I am hoping that subsequent SF strings
> can be specified in Latin again - especially since UTF-8 has no
> return.
>
> In clear text:
> BegAPS "Eng_Ja_Howdy" "grobject" StList;
> APSAttr 'name' "14 1 'Japanese Greetings'";
> APSAttr "screentip" "14 1 '<ESC 2/5 2/15
> 4/9>...UTF-8 for JP-Greetings'"; %
> (ö %
> APSAttr "region" "11 1
> 1            %--
> typ:idx, cnt:1, val:1(rect)   --%
>                  
> 16
> 4             
> %-- typ:vdc, cnt:4, val:(4-pts)   --%
>                  
> 520 859 708 914"; %-- Points defining a
> rect        --%
> BegAPSBody;
>     RestrText 187 55 (520 859) FINAL
>       "Hi";
> EndAPS;
>
> So APSAttr _type_ "screentip" is ISO Latin, the screentip
> itself is UTF-8, and the following APSAttr type "region" is ISO
> Latin.
>
> Thanks very much for your help with these two questions.
>
> Best Regards,
> Jeff Wolkenhauer
>
> UGS The PLM
> Company       
> (503.466.9401)
>                                       
> jeffrey.wolkenhauer@ugs.com
>                                       
> 15455 NW Greenbrier Pkwy, Suite 210 * Beaverton, OR 97006
> --