[oXygen-user] Master files?

[Imsieke, Gerrit, le-tex]

Of course I don’t know exactly how this is implemented; I’m sure the 
oXygen people will shed light on it. If the info still isn’t available 
after saving a.xsl and after saving the newly created file, I’d restart 
oXygen or switch to another project and then switch back in order to 
make sure that everything will be read anew.

There used to be similar issues when XML catalog entries were added 
after the catalog(s) have been read upon opening a project and/or upon 
starting oXygen, but catalog change event handling seems to have 
improved in recent versions. Which version do you use?

Gerrit

On 08.11.2020 18:57, David Birnbaum wrote:
> Dear oxygen-user list,
> 
> I've configured an XSLT transformation using master-file support, where 
> there is one master XSLT file (a.xsl), which imports (with <xsl:import>) 
> a file of functions (lib.xsl) and a set of files that contain only 
> templates (b.xsl, c.xsl, etc.). The imported template files use 
> functions defined in lib.xsl but don't import those functions directly. 
> Since the imported template files are never run on their own, and used 
> only by being imported into a.xsl, the functions from lib.xsl are 
> available to the imported template files when they are used, and the 
> transformation runs successfully.
> 
> I have specified a.xsl as a master file, and <oXygen/> validates it 
> successfully. For the most part (the four scariest words in debugging!) 
> the imported template files do not raise real-time validation errors 
> about unknown functions, even though they would have access to the 
> functions they use only because both they and those functions are 
> imported into a.xsl together. So far, so good.
> 
> My issue is that when I create a new template file to be imported into 
> a.xsl, <oXygen/> doesn't seem to know that it should be validated with 
> the understanding that it is being imported into a.xsl, which is also 
> importing lib.xsl. This means that when I create a new template file, 
> <oXygen/> raises real-time validation errors about unknown functions, 
> even though it does not raise those errors for other imported template 
> files that use similar function calls.
> 
> At some point <oXygen/> seems to learn that the new imported template 
> files should be checked with access to master-file information, that is, 
> that they will have access to the functions in question when they are 
> used, at which point the imported template files no longer raise 
> validation errors when I have them open in <oXygen/>. I have not, 
> however, been able to identify what exactly enables <oXygen/> to learn 
> this about new imported files as I am creating them, or how to notify 
> <oXygen/> explicitly about them when I first begin to author them. Can 
> someone please advise?
> 
> Thanks,
> 
> David
> djbpitt at gmail.com <mailto:djbpitt at gmail.com>
> 
>