Interoperability.blob.core.windows.net
[MS-CTDOC]: Word Custom Toolbar Binary File FormatIntellectual Property Rights Notice for Open Specifications DocumentationTechnical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit trademarks. Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.Revision SummaryDateRevision HistoryRevision ClassComments6/27/20081.0First release11/14/20081.01Revised and edited the technical content1/16/20091.02Updated the Intellectual Property Rights Notice7/13/20091.03MajorRevised and edited the technical content8/28/20091.04EditorialRevised and edited the technical content11/6/20091.05EditorialRevised and edited the technical content2/19/20102.0EditorialRevised and edited the technical content3/31/20102.01EditorialRevised and edited the technical content4/30/20102.02EditorialRevised and edited the technical content6/7/20102.03EditorialRevised and edited the technical content6/29/20102.04EditorialChanged language and formatting in the technical content.7/23/20102.04No ChangeNo changes to the meaning, language, or formatting of the technical content.9/27/20102.04No ChangeNo changes to the meaning, language, or formatting of the technical content.11/15/20102.04No ChangeNo changes to the meaning, language, or formatting of the technical content.12/17/20102.04No ChangeNo changes to the meaning, language, or formatting of the technical content.3/18/20112.04No ChangeNo changes to the meaning, language, or formatting of the technical content.6/10/20112.04No ChangeNo changes to the meaning, language, or formatting of the technical content.1/20/20122.5MinorClarified the meaning of the technical content.4/11/20122.5No ChangeNo changes to the meaning, language, or formatting of the technical content.7/16/20122.5No ChangeNo changes to the meaning, language, or formatting of the technical content.10/8/20122.5No ChangeNo changes to the meaning, language, or formatting of the technical content.2/11/20132.5No ChangeNo changes to the meaning, language, or formatting of the technical content.7/30/20132.5No ChangeNo changes to the meaning, language, or formatting of the technical content.11/18/20132.5No ChangeNo changes to the meaning, language, or formatting of the technical content.2/10/20142.5No ChangeNo changes to the meaning, language, or formatting of the technical content.4/30/20142.6MinorClarified the meaning of the technical content.7/31/20142.7MinorClarified the meaning of the technical content.10/30/20142.7No ChangeNo changes to the meaning, language, or formatting of the technical content.9/4/20152.7No ChangeNo changes to the meaning, language, or formatting of the technical content.Table of ContentsTOC \o "1-9" \h \z1Introduction PAGEREF _Toc429053687 \h 51.1Glossary PAGEREF _Toc429053688 \h 51.2References PAGEREF _Toc429053689 \h 51.2.1Normative References PAGEREF _Toc429053690 \h 51.2.2Informative References PAGEREF _Toc429053691 \h 61.3Overview PAGEREF _Toc429053692 \h 61.4Relationship to Protocols and Other Structures PAGEREF _Toc429053693 \h 61.5Applicability Statement PAGEREF _Toc429053694 \h 61.6Versioning and Localization PAGEREF _Toc429053695 \h 61.7Vendor-Extensible Fields PAGEREF _Toc429053696 \h 62Structures PAGEREF _Toc429053697 \h 72.1Toolbar Data PAGEREF _Toc429053698 \h 72.2Toolbar Control Data PAGEREF _Toc429053699 \h 73Structure Examples PAGEREF _Toc429053700 \h 84Security Considerations PAGEREF _Toc429053701 \h 95Appendix A: Product Behavior PAGEREF _Toc429053702 \h 106Change Tracking PAGEREF _Toc429053703 \h 117Index PAGEREF _Toc429053704 \h 12Introduction XE "Introduction" This document specifies the Word Custom Toolbar Binary File Format Structure data used by the toolbar customization structures specified in [MS-DOC] and [MS-OSHARED]. Toolbar customization structures provide a run-time solution for the creation and deployment of toolbar customizations that are specific to the content of a file. Sections 1.7 and 2 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in [RFC2119]. All other sections and examples in this specification are informative.Glossary XE "Glossary" The following terms are specific to this document:custom toolbar: A type of toolbar that contains a user-defined set of controls and is not included in an application by default. A custom toolbar has a toolbar identifier value of "1".custom toolbar control: A user-defined control that can be added to a toolbar. A custom toolbar control has a toolbar control identifier (TCID) value of "1" and can be one of the following types of controls: ActiveX, Button, ComboBox, DropDown, Edit, or Popup.toolbar: A row, column, or block of controls that represent tasks or commands within an application. A toolbar can be either a menu toolbar, which provides access to menu commands, or a basic toolbar, which contains buttons that provide shortcuts to tasks that are frequently accessed from menus.toolbar control: An object that appears on a toolbar and enables user interaction or input, typically to initiate an action, display information, or set values.toolbar control identifier (TCID): An integer that identifies a specific control on a toolbar.toolbar delta: A file component that stores a modification that a user made to a built-in toolbar. Stored modifications include adding, changing, or removing a control from a built-in toolbar.MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.References XE "References" Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata. Normative References XE "References:normative" XE "Normative references" We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact dochelp@. We will assist you in finding the relevant information. [MS-DOC] Microsoft Corporation, "Word Binary File Format (.doc) Structure Specification".[MS-OSHARED] Microsoft Corporation, "Office Common Data Types and Objects Structures".[MSDN-TBID/Word] Microsoft Corporation, "Word Toolbar IDs Table", Excerpted from MS-CTDOC, [MSDN-TCID/Word] Microsoft Corporation, "Word Toolbar Control IDs Table", Excerpted from MS-CTDOC, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, References XE "References:informative" XE "Informative references" None.Overview XE "Overview (synopsis)" This document specifies the Toolbar Data table and the Toolbar Control Data table which are defined in [MSDN-TBID/Word] and [MSDN-TCID/Word]. The Toolbar Data table and the Toolbar Control Data table are used by the Toolbar Customization structures specified in [MS-DOC] and [MS-OSHARED].Relationship to Protocols and Other Structures XE "Relationship to protocols and other structures" The toolbar data presented in section 2.1 of this document is used by the TBCMenuSpecific structure, as described in [MS-OSHARED] section 2.3.1.21 and by the Customization structure, as described in [MS-DOC] section 2.9.50.The toolbar control data presented in section 2.2 of this document is used by the TBCHeader and TBCSFlags structures, as described in [MS-OSHARED] section 2.3.1.Applicability Statement XE "Applicability" The toolbar information presented in section 2.1 of this document is intended to be used in conjunction with the toolbar customization structures, as described in [MS-DOC] and [MS-OSHARED]. It provides the association between a built-in toolbar, a toolbar control, a custom toolbar, and a toolbar delta.The toolbar control information presented in section 2.2 of this document is intended to be used in conjunction with the toolbar customization structures, as described in [MS-OSHARED] section 2.3.1. It provides the values for the tcid field of the TBCHeader structure, as described in [MS-OSHARED] section 2.3.1.10 and the values for several fields of the TBCSFlags structure, as described in [MS-OSHARED] section 2.3.1.12, which are used by built-in toolbar controls with a specific toolbar control identifier (TCID).Versioning and Localization XE "Versioning" XE "Localization" None.Vendor-Extensible Fields XE "Vendor-extensible fields" XE "Fields - vendor-extensible" None.StructuresToolbar Data XE "Details:Toolbar Data table" XE "Toolbar Data table" XE "Structures:Toolbar Data table" The Toolbar Data table [MSDN-TBID/Word] contains toolbar data used by the TBCMenuSpecific structure, as specified in [MS-OSHARED] section 2.3.1.21 and by the Customization structure, as specified in [MS-DOC] section 2.9.50.The TBID column of the Toolbar Data table contains a list of values for the tbid field of the TBCMenuSpecific structure, as specified in [MS-OSHARED] section 2.3.1.21 and for the tbidForTBD field of the Customization structure, as specified in [MS-DOC] section 2.9.50. The Meaning column contains a short description of the toolbar associated to a specific toolbar identifier.Toolbar Control Data XE "Details:Toolbar Control Data table" XE "Toolbar Control Data table" XE "Structures:Toolbar Control Data table" The Toolbar Control Data table [MSDN-TCID/Word] contains toolbar control data used by the TBCHeader and TBCSFlags structures, as specified in [MS-OSHARED] section 2.3.1.The TCID column of the Toolbar Control Data table specifies the list of values that the tcid field of the TBCHeader structure specified in [MS-OSHARED] section 2.3.1 MUST have if the toolbar control is not a custom toolbar control. The value of the tcid field of the TBCHeader structure specified in [MS-OSHARED] section 2.3.1 MAY also equal 4177. The TCT column specifies the toolbar control type as specified by the tct field of the TBCHeader structure, as specified in [MS-OSHARED] section 2.3.1.10 for the tcid. The Meaning column contains a short description for the tcid.Structure Examples XE "Examples" XE "Example" None.Security Considerations XE "Security - implementer considerations" XE "Implementer - security considerations" None.Appendix A: Product Behavior XE "Product behavior" The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.Microsoft Word 97Microsoft Word 2000Microsoft Word 2002Microsoft Office Word 2003Microsoft Office Word 2007Microsoft Word 2010Microsoft Word 2013Microsoft Word 2016Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.Change Tracking XE "Change tracking" XE "Tracking changes" No table of changes is available. The document is either new or has had no changes since its last release.IndexAApplicability PAGEREF section_c177530bb8bb49cba302fd91d7e30d9c6CChange tracking PAGEREF section_5655f371ddf4483a8789d21cea73d8e311DDetails Toolbar Control Data table PAGEREF section_fffaf1e71fb541c686a8bb54337a43b87 Toolbar Data table PAGEREF section_72fa5caeba79459caa8f3e2f772761727EExample PAGEREF section_1f1b70f1cf314edb840c4d36d4d4fedc8Examples PAGEREF section_1f1b70f1cf314edb840c4d36d4d4fedc8FFields - vendor-extensible PAGEREF section_217609fed0d2496cb1e5b37354f6801c6GGlossary PAGEREF section_66f9cf947f7b4beb86957d5804e919835IImplementer - security considerations PAGEREF section_2b0a830c328149ae96aa7ef27a0a914b9Informative references PAGEREF section_4d8a0b84f57443afb7331ace19f068166Introduction PAGEREF section_ea4395ddae3f444cabc13c20a81e66105LLocalization PAGEREF section_77ea3479520240bda5e4041a20bca3ca6NNormative references PAGEREF section_9df17874376c41ec984ca16754621d645OOverview (synopsis) PAGEREF section_15938d0af3a7479184ac78ac7e0688096PProduct behavior PAGEREF section_344992967a2840e0a6627ee0eabda71110RReferences PAGEREF section_aeb51a202fe74312abc6da8dbddbf85d5 informative PAGEREF section_4d8a0b84f57443afb7331ace19f068166 normative PAGEREF section_9df17874376c41ec984ca16754621d645Relationship to protocols and other structures PAGEREF section_eedb1106e30644ca8932350d2f78e5ac6SSecurity - implementer considerations PAGEREF section_2b0a830c328149ae96aa7ef27a0a914b9Structures Toolbar Control Data table PAGEREF section_fffaf1e71fb541c686a8bb54337a43b87 Toolbar Data table PAGEREF section_72fa5caeba79459caa8f3e2f772761727TToolbar Control Data table PAGEREF section_fffaf1e71fb541c686a8bb54337a43b87Toolbar Data table PAGEREF section_72fa5caeba79459caa8f3e2f772761727Tracking changes PAGEREF section_5655f371ddf4483a8789d21cea73d8e311VVendor-extensible fields PAGEREF section_217609fed0d2496cb1e5b37354f6801c6Versioning PAGEREF section_77ea3479520240bda5e4041a20bca3ca6 ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- net profit vs net revenue
- net profit vs net income
- net revenue vs net profit
- blob to string converter online
- net user set password windows 10
- net revenue vs net income
- cms promoting interoperability program
- convert blob to string oracle
- oracle convert blob to text
- js convert blob to string
- sql convert blob to string
- oracle blob to char