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 CRXDE Lite mode. create symbols.json file at the
following location:/apps/fmdita/xmleditor/ (You can copy the default
from - /libs/fmdita/clientlibs/clientlibs/xmleditor/symbols.json
location) Add the specia...
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 custom button in toolbar to define a custom action.
Customize toolbar for map and topic separately. The XML Documentation
Solution provides an easy way to customize the web editor toolbar. Below
are the ...
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 your author instance? If yes, the below solution can help you in
resolving this issue. Remedy: It could be because of the missing
configuration. You should need to enable the mime type for DITA files.
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' option on the baselines tab. Earlier these labels
were only limited to the direct references and it was difficult to
choose the correct versions of images while creating the baseline using
labels. With thi...
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. The OOTB machine translation (with trial Microsoft
Translation connector) showcase the same behavior. Here are few
screenshots and steps that would help in better understanding: Testing
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 other publication then also it would be helpful.
Regards, Kiran Mohan
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 you want a short demonstration of this. Thanks & Regards,