Hello, The schema documentation process first generates an temporary XML file. This XML file contains all the schema components and their meta information (like the annotation). On this XML format we apply XSLTs to obtain either HTML or Docbook output. These stylesheets are available in {INSTALLATIO...

Hi, I'll send you the code on your email address. If you find the tags from the text mode more helpful than the markers from the author page then you can create a similar layout in author mode by adding these CSS rules: teiHeader *:before { content: "<" oxy_local-name() ">"; colo...

Hi, First thing to keep in mind is that oxy_xpath and oxy_replace are CSS functions while string-join is an XPath one. We use oxy_replace as a helper to build the final XPath expression that will be given to an oxy_xpath to execute. Combining these two functions (oxy_xpath and oxy_replace) can be qu...

Hello, All the built in form controls are designed to edit either an attribute value or the text content of an element. That's why the content you are entering in the text area is escaped before is inserted in the document. It's treated as plain text. If you want, you can create a custom form contro...

Hi, Using oxy_xpath and oxy_replace together should work just fine for your use case. If you try something like this do you get an error message? oxy_xpath(oxy_replace("string-join(doc('http://shared/config.xml')//family[name='$thisFamily']/product, ',')",'$thisFamily',oxy_xpath('../family...

Hello, If you are willing to help us investigate the problem, you can enable logging in Oxygen. I will send you the instructions by email. However, using such an expensive XPath query in the CSS does not result in a good user experience when editing the XML. While the query is executed the entire do...

Hi, The styles property was introduced in Oxygen version 15 so prior versions do not recognize it as a supported property. Fortunately there is a dedicated property for setting the color and it will work in both versions: content: oxy_label(text, "(Print): Replace **** with Product Code", ...

Hi,

The AutoCorrect options were indeed introduced in Oxygen v15.0. For version 14 you can still use the last approach (the one with AuthorDocumentFilter).

Best regards,
Alex

Hi, I believe that author actions can also be seen as "Dynamic abbreviations". The user presses ENTER then writes a part from the action's name (the abbreviation) and when executing the actions the expanded content is inserted. Another way would be through the Code templates support. You w...

Hi, There is a built-in auto correct support that replaces simple quotes with a character of your choice. Since you are working with the author component there are a couple of possible approaches: - Configure the auto correct in an Oxygen standalone preferences and then provide the option file as de...

Hi, The value for the imposedPage parameter is one of the constants from the ro.sync.exml.editor.EditorPageConstants interface. If you want to open the editor in the author mode then the right value is EditorPageConstants.PAGE_AUTHOR. Thank you for pointing it out. I'll also update the documentation...

Hi, I'm not sure how your CSS looks like but with the small CSS below the buttons are indeed placed higher than other form controls and the vertical-align property has no effect on them. para:before { content: "TEST" oxy_textfield(edit, '@bla') oxy_button(actionID, 'insert.table', transpar...

Hi, If you use PluginWorkspaceProvider.getPluginWorkspace().getUtilAccess() to get the UtilAccess the framework related editor variables are indeed not expanded. It's not an inherent limitation but just something we missed. Even more disturbing, the documentation states that these variables should b...

Hi, The StylesFilter is called many times because we don't cache it's results on our side and the styles for an element are requested a lot. So it's up to the implementation to do a caching if necessary. I suspect that you are using the node as the key in your cache. There might be a problem if this...

Hello, Unfortunately you can't copy static text in the Author mode. Even though the selection shows the static content as being selected, the copy action will skip the static content. Possible ways to get the value of the xml:id attribute: 1. you can use the Attributes View to select the xml:id attr...

Hello, This is indeed a common use case for Oxygen and we have several ways to achieve your goal. One of them is exactly the one you tried, namely by adding an combo box form control by using a StylesFilter. You are right, the documentation is a bit unclear about how to obtain the AuthorAccess insta...

Hello, From what I understand you would like to create Document Templates. The steps to create these templates are: - for each template you have to create a new file. The name of the file is the template's name. For example a file named Book.xml will generate a template named Book and the extension ...

Hello Patrik, This behavior is not possible right now for the built-in form controls. But this looks like a nice feature so I've added an issue to get it implemented. Until then, a possible workaround for you would be to create custom a form control. If you want I can send you the source code for th...

Hi Sebastien,

I'm just curious, why you need an AuthorAccess object in a StylesFilter? What's the use case?

Best regards,
Alex

Hi Sebastien, We are aware that the ExtensionsBundle gets instantiated twice on document load and we already have added an issue to fix it. We also have an issue registered to provide the StylesFilter with an AuthorAccess instance. Meanwhile, if you want an AuthorAccess instance in the StylesFilter ...

Hello,

We also have a topic about how to integrate a DITA Specialization: Integration of a DITA Specialization.

Best regards,
Alex

Hello, Normally Oxygen maps the DITA DTDs to copies from the local file system through catalogs. But you probably have a DITA specialization so the PUBLIC ID of the DTDs doesn't match and so the resources are not resolved. You should add some catalogs entries for those DTDs. A catalog is an XML file...

Hi, When inserting a table element Oxygen automatically generates an ID for it. So just remove the id attribute from the inserted fragment. This behavior is controlled by the ID Options... from the DITA menu. But if you want to be sure an ID is inserted no matter those options, you should explicitly...

Hi, You can't change the default values in the table wizard but what you can do is change the insert table action to always insert a table fragment with the specification you want. You should go to Preferences -> Document Type Associations and edit the DITA framework. On the Author/Actions tab ident...

Hi David, You will have to use the Java based API. You must extend DITAUniqueAttributesRecognizer and override the getDefaultOptions( ) method. You must return a GenerateIDElementsInfo object with only the class values for which you want to generate IDs. Next you must extend DITAExtensionsBundle and...

Hi, We already have an open issue to update the W3C CSS Validator that we use. I've added your vote to it and increase its priority. I've tried the following CSS rule in the CSS Validation Service but I'm also receiving the error you mentioned. Have I missed something? tr:hover td { background-color...

Hi, Your assumptions are correct. Just to make sure I've followed. The project is in the framework dir and the Additional frameworks directories option page is saved at project level and specifies the location like so: ${pd}/../ A possible issue that comes to mind is the fact that when the users mus...

Hi, It seams that the documentation is somewhat incomplete. Sorry about that... I'll add an issue to correct it but in the meantime here is what you must do: - the file must be named CustomProperties.xml and must looks like this: <?xml version="1.0" encoding="UTF-8"?> <css_keywor...

Hi, I've tried this scenario and setting -oxy-editable:false on an element will also make it's attributes read-only. In the code snapshots I've posted, the attributes are editable but as soon as you set attr2 to value a both attributes become READ-ONLY. If you want to output the attributes in a colu...

Hi, You can still use form controls, you just have to mark the element as READ_ONLY (using the -oxy-editable property). As a result the form controls will also be READ-ONLY: element:before { content: oxy_local-name() " " oxy_textfield(edit, '@attr1', columns, 10) " " oxy_textfiel...