Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: ODF 1.2 Part 1 CD 4
    • Fix Version/s: ODF-Later
    • Component/s: Schema and Datatypes
    • Labels:
      None
    • Proposal:
      • Broaden the scope of 10.4.5 office:binary-data, to allow any binary data (not only image data)
      • Use the office:binary-data inside office:script to store the compiled version
    • Resolution:
      Hide

      The purpose of the <office:script> element is to store inline scripts, but there is indeed also the option to store them separately in the package. This alternative is widely used. Future versions of the ODF specification may provide some guidance how scripts may be stored. In this context enhancements to the <office:script> element or a possible deprecation may be discussed.

      Show
      The purpose of the <office:script> element is to store inline scripts, but there is indeed also the option to store them separately in the package. This alternative is widely used. Future versions of the ODF specification may provide some guidance how scripts may be stored. In this context enhancements to the <office:script> element or a possible deprecation may be discussed.

      Description

      The note says:

      "In most situations, the element contains the source code of the script, but it may also contain a compiled version of the script or a link to external script code."

      I assume the compiled (binary) version would be BASE64 encoded ?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bart.hanssens Bart Hanssens (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: