Highlighted

Toolsets referencing component name ids

New Here ,
May 26, 2016

Copy link to clipboard

Copied

Hi,

Hoping that someone might know the answer to a challenge I am having with a custom toolset I am trying to deploy to a number of users.

It basically comes down to the reference to non standard components, like custom actions, by their id and not their name value.  This id seems unique to a user.  In turn importing a toolset will be missing components for all users except the creator when you import toolsets.

To illustrate, look at one of the tool sets like 'Making accessible documents' on https://acrobatusers.com/tool-sets-exchange​ and if you download the .aaui file and open it with notepad, you will see some components are referenced by an ID (red text) and others by named values (Green text):

     <Component label="Add Accessible Features">

            <Component label="Specify the language used in encoding your document&apos;s information for assistive devices"/>

            <Component name="B14A020D071C90CB664FFD9B0D9B6C4"/>

            <Component name="Separator"/>

            <Component label="Add hidden tags to your document for use with accessible devices"/>

            <Component name="Adobe:MakeAccessible"/>

            <Component name="Separator"/>

            <Component label="Include descriptions of all images and graphics for use by reading devices"/>

            <Component name="SetAlternateText"/>

            <Component name="Separator"/>

            <Component label="Specify the path to read content on your pages"/>

            <Component name="TouchUpLayoutTool"/>

  </Component>

If you import this toolset you will find the non standard components that are referenced by an ID will not actually display because that ID was unique to the authors install and so many toolsets cannot be shared/published because they just don't show some of the components a user wants to put on a toolset.

I can tell where this ID is saved, it is within the HKCU path of the registry but I really don't want to mess with the registry for this.  I just want other users to be able to import the tool set and it show all components and ideally do that by referencing all components by a name value.  I am making sure the actions are on the users' machine, the toolset just breaks because of this ID issue.

What am I missing or is this an oversight by Adobe that whilst they support Export and Import in Acrobat 11.x they did not consider the impact of referencing ID values instead of named components.

Topics

Acrobat

Views

138

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Toolsets referencing component name ids

New Here ,
May 26, 2016

Copy link to clipboard

Copied

Hi,

Hoping that someone might know the answer to a challenge I am having with a custom toolset I am trying to deploy to a number of users.

It basically comes down to the reference to non standard components, like custom actions, by their id and not their name value.  This id seems unique to a user.  In turn importing a toolset will be missing components for all users except the creator when you import toolsets.

To illustrate, look at one of the tool sets like 'Making accessible documents' on https://acrobatusers.com/tool-sets-exchange​ and if you download the .aaui file and open it with notepad, you will see some components are referenced by an ID (red text) and others by named values (Green text):

     <Component label="Add Accessible Features">

            <Component label="Specify the language used in encoding your document&apos;s information for assistive devices"/>

            <Component name="B14A020D071C90CB664FFD9B0D9B6C4"/>

            <Component name="Separator"/>

            <Component label="Add hidden tags to your document for use with accessible devices"/>

            <Component name="Adobe:MakeAccessible"/>

            <Component name="Separator"/>

            <Component label="Include descriptions of all images and graphics for use by reading devices"/>

            <Component name="SetAlternateText"/>

            <Component name="Separator"/>

            <Component label="Specify the path to read content on your pages"/>

            <Component name="TouchUpLayoutTool"/>

  </Component>

If you import this toolset you will find the non standard components that are referenced by an ID will not actually display because that ID was unique to the authors install and so many toolsets cannot be shared/published because they just don't show some of the components a user wants to put on a toolset.

I can tell where this ID is saved, it is within the HKCU path of the registry but I really don't want to mess with the registry for this.  I just want other users to be able to import the tool set and it show all components and ideally do that by referencing all components by a name value.  I am making sure the actions are on the users' machine, the toolset just breaks because of this ID issue.

What am I missing or is this an oversight by Adobe that whilst they support Export and Import in Acrobat 11.x they did not consider the impact of referencing ID values instead of named components.

Topics

Acrobat

Views

139

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
May 26, 2016 1

Have something to add?

Join the conversation