Adam Strzelecki wrote: > Yeah, but I how can I set my_fop_config.xml to be next to customize.xxe > (same folder)? Something like %A or %a pointing at path where > customize.xxe lays would be nice. > I just want to tell user... extract those 3 files into ~/.xxe/addon/ and > now you have customized FOP & DocBook, I don't want to place any files > into XMLMind installation folder.
Sure. > Pbm is that there's no system independent variable so I need to use > %H/.xxe/addon/fop-config.xml on Unix and %H/Application > Data/XMLmind/XMLEditor/addon/fop-config. > > Also I think there's a but in XXE itself in Windows. I have Polish > Windows and "Application Data" is called there "Dane Aplikacji", and > %APPDATA% env variable points properly to localized folder, but XXE > seems to create explicitly "Application Data" (English), specially just > for XXE. Can you use %APPDATA% folder exactly as it is set? > > That was supposed to be "bug", not "but" neither "butt" ;) --> If your customize.xxe contains: <cfg:parameter name="configuration">%C%Sfop-config.xml</cfg:parameter> Then you need to copy "fop-config.xml" in the directory containing customize.xxe. "%C%S" is intended to work whatever the OS you use. "%C" is the name of the directory containing the XXE configuration file (in your case customize.xxe) from which the *process* *command* has been loaded. The problem is that, in your case, <cfg:parameter name="configuration"> is found in a named parameter group referenced by a process command and not directly in a process command. --> If "%C%S" does not work for you, then we prefer to remove the above limitation rather than add "%A" or "%a" variables. Removing the limitation would mean: "%C" is the name of the directory containing the XXE configuration file (in your case customize.xxe) from which the process command *or* *the* *named* *parameter* *group* has been loaded. Therefore please try: <cfg:parameterGroup name="docb.toPS.FOPParameters"> <cfg:parameter name="configuration">%C%Sfop-config.xml</cfg:parameter> </cfg:parameterGroup> and tell us if it works, if it does not work just say so and we'll remove this limitation for next release.
