Hi Stefan, We want to avoid checking for updates to often so we'll check once in four application launches. So the user will get notified, but not always as soon as the update is uploaded. The user can always use "Help->Check for add-ons updates..." to manually check for any updates. Do yo...

Hi Stefan, 2) You are right, all these $framework variables, when used outside of a document type will expand to the defaults. But I understand the need to refer from outside of a document type a certain framework location. I will add an improvement request to provide a new variable like ${framework...

Hello Stefan, 1) Please check if the add-on archive contains the root directory of the framework. The behavior you describe can happen if instead of archiving the framework's root directory you've archived the containing files. If the archive has the correct structure you don't have to set anything ...

Hi,

The latest TEI framework build available for download is compatible only with Oxygen v14 that will be released very soon. Unfortunately we forgot to specify this. I've marked the build accordingly and I've also uploaded a new build that is compatible with Oxygen v13.

Best regards,
Alex

Hello, As an alternative, you could enter a shorter link description inside the XREF element. Instead of an empty element, just use : <xref href="http://www.oxygenxml.com/forum/topic6490.html" format="html" scope="external">topic6490.html</xref> . Regards, Alex

Hello, I was under the impression that your question referred to displaying the XML in oXygen Author page so I gave an answer for that. My mistake. You are actually referring to the html output of an WebHelp transformation? If that is the case, you should probably intervene inside the XSL stylesheet...

Hello, You can edit the CSS so that a shorter path is displayed for links. For DITA the CSS where you should intervene is {oxygenInstallDir}/frameworks/dita/css_classed/topic.css . For an XREF element the rule that should be modified is: *[class~="topic/link"][href]:before, *[class~="...

Hello, Thanks to the files you sent, we managed to identify this as a Saxon problem that relates to the catalog use. Basically Saxon checks if a module has already been loaded by comparing the module's unresolved URI with the catalog resolved URIs of the already loaded modules. Because of that it wi...

Hello, The fact that your library module gets imported multiple times shouldn't be a problem. The XQuery processor will try to resolve the imported module and should recognize that it has already been imported. The problem you described can arise if the resolved module doesn't match with the one alr...

Hello, I've attached a modified version of your stylesheet in which all of your requirements are working. XML sample: <root> <list type="bulleted"> <item id="appB">An anchor</item> <item>Another item</item> <item>Third item</item> </list> <link idref="appB">Link to the ...

Hello Maik,

Thank you for reporting these issues. We've made the necessary changes and they will be available in the next release.
Do not hesitate to contact us if you have more questions or suggestions.

Regards,
Alex

Hello, The <seeAlso> tags is just an idea we thought about (not yet implemented). The benefits are that we could automatically generate the links depending on the predefined output format (html, docbook, pdf). But unfortunately they wont appear inline in documentation, just before or after it. Best ...

Hello,

Currently, facets documentation cannot be edited in 'Schema' page and don't appear in the generated schema documentation. We added an issue on our internal bug tracking system to resolve these problems as soon as possible.

Best regards,
Alex

Hello,

Will it be helpful if we also add support for handling a 'seeAlso' element in appInfo? You will have to specify the namespace, local name and component type and we will automatically replace it in the documentation with a link to the actual location of that component.

Best regards,
Alex

Hello, Indeed, there are 2 problems. First, the ids used to identify the components are generated using a counter. Second, if you are using a split method (by namespace, location or component), the name of the html files are generated using the name of the given output file + another counter. Basica...

Hello, When executing an eXist XQuery in oXygen, the collection URI must be given relative, like this : for $book in collection("/db/myCollection")//book Also before running an XQuery against eXist you must create an eXist connection and use that connection as the XQuery processor. A detai...

Hello, In order to provide information about cell spanning you will have to create a Table Cell Span Provider. In method AuthorTableCellSpanProvider.getColSpan(AuthorElement cellElement) you will have to check if the given cellElement is the optional element (you can use AuthorElement.getLocalName()...

Hello, Concerning your question about the saxon serialization parameters, Oxygen uses its own serialization of the output of the transformation, so these params are not curently used. We will think of a way of integrating them in the next version of Oxygen (after 7.0). We are aware of the problem yo...

Hello, All items in the argument of the max() function must be numeric or derived from a single base type. So the items from "$workers//q2:bdate" are being converted to numeric type but something like {1975-02-20} cannot be converted to a number. You can try the following code : declare na...