[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Was OOXML's problem that it should have used JSON not XML?
Sounds good. Sorting out what a character is --when using old pre-unicode non-ascii fonts-- must be tricky. I am not asking for any "gotcha" reasons, but I think there is a "public interest" in understanding the general interaction between the ISO working group and Microsoft (I don't know it), and seeing what the longer-term benefits of the ISO project has been. (As distinct from institution interaction of them showing up to meeting, sponsoring the editor, etc.) When OOXML was adopted as a standard at ISO, it was on the proviso that there would be an ongoing maintenance process: you have given the example of the I18n, but has it been much use elsewhere. My subjective and distant impression is that the influence has been mainly on the value-add areas of interest to governments, such as signatures, rather than say the text processing core (though your mention of fonts is evidence to the contrary...): is that right? On Wed, Jan 24, 2018 at 2:22 PM, MURATA Makoto <eb2m-mrt@asahi-net.or.jp> wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|