There is a shortcut option in the web-editor toolbar to let author insert the special characters already. The same can be seen in screenshot below:     These list of characters is configurable here. If you need to add more characters to this then follow the below steps:   Log into AEM and open the...

The toolbar in web-editor is completely customizable, there are many customizations that you can achieve, few use cases would be : Add/Remove toolbar options. Examples : Add a button to make the text bold or remove the insert multimedia option from the toolbar as it is not used frequently.Add a cust...

Problem Statement: Are you facing issue on author instance where preview of DITA asset is not rendering correctly and this happens on asset details page ? Do you see the html encoding rather than actual page UI - Refer the the screenshot below.     Precondition: Do you have dispatcher set up on you...

One additional change that content users will observe with 3.8 XML Documentation build on baselines tab is few more labels with images. This was not there in previous build.      With the new release, content users can also apply labels on indirect references like images etc. using the 'Add Labels'...

Easiest way is to make use of translation=no attribute. Authors can insert the additional attribute as 'translation=no' on the paragraphs that they do not want to translate. The translation vendor needs to be informed and they can do configuration at their end to ignore the text with this attribute....

Hi @DivrajSingh - Can you also share the high level steps to integrate the custom DITA-OT plugin with the product provided DITA-OT on local?

Hi @DivrajSingh ,  The most common use case - We should use keys and variables in cases where we have some text (maybe product name, company name, etc. ) that is used in many places and might change in the future. Also if there are topics that use different variable values in the context of some oth...

Step 1: Create a global map for storing your keys. Create a map and add the keyref element to it.     <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "technicalContent/dtd/map.dtd"> <map id="map.ditamap_ffbdbf06-8658-4311-ad84-1c631bba904f"> <title>global-k...

That is okay. But you should still be able to add that to your map.( Additional information - The authoring of the markdown file in the AEM system is in our roadmap)   If you drag/drop the markdown file into map from xml editor then it will automatically add format attribute also. Do let me know if ...

Hi, XML documentation uses DITA-OT internally to generate the different output. DITA-OT allows the markdown files generation from source dita content and it also lets the author use the raw markdown files for publishing. Please refer below for more details: Generating Markdown files from the source ...