oXygen Editor Content Completion Assistant suggestions - question
Oxygen general issues.
oXygen Editor Content Completion Assistant suggestions - question
Hello,
I was recently asked a question about the autocomplete suggestions in oXygen Editor text mode:
- where does oXygen take the suggestions for languages for xml:lang definition from?
I read that DITA-OT is not case sensitive - why is there option de-DE and not de-de?
Is there any way to edit that language list?
Can anyone give me some more information about this?
regards,
Justyna
I was recently asked a question about the autocomplete suggestions in oXygen Editor text mode:
- where does oXygen take the suggestions for languages for xml:lang definition from?
- dita_question.png (11.91 KiB) Viewed 568 times
Is there any way to edit that language list?
Can anyone give me some more information about this?
regards,
Justyna
Re: oXygen Editor Content Completion Assistant suggestions - question
Hi Justyna,
The DITA 1.3 standard does not specify a hardcoded set of values for xml:lang:
https://www.oxygenxml.com/dita/1.3/spec ... llang.html
Those particular values you get in the content completion window are provided by an Oxygen specific DITA framework customization file located in:
OXYGEN_INSTALL_DIR/frameworks/dita/resources/cc_config.xml
Usually such configuration files are not edited directly, someone could for example create an extension of the DITA framework customization which provides their own version of the cc_config.xml which would suit their team better:
https://www.oxygenxml.com/doc/versions/ ... etion.html
About this question you had:
There are various standards like:
https://www.rfc-editor.org/rfc/bcp/bcp47.txt
which seem to treat "Language-Region" by capitalizing the region name and this is from what I encountered common.
But indeed, in the specs above it says:
Radu
The DITA 1.3 standard does not specify a hardcoded set of values for xml:lang:
https://www.oxygenxml.com/dita/1.3/spec ... llang.html
Those particular values you get in the content completion window are provided by an Oxygen specific DITA framework customization file located in:
OXYGEN_INSTALL_DIR/frameworks/dita/resources/cc_config.xml
Usually such configuration files are not edited directly, someone could for example create an extension of the DITA framework customization which provides their own version of the cc_config.xml which would suit their team better:
https://www.oxygenxml.com/doc/versions/ ... etion.html
About this question you had:
Yes, the publishing engine should not interpret the values in a case sensitive manner.I read that DITA-OT is not case sensitive - why is there option de-DE and not de-de?
There are various standards like:
https://www.rfc-editor.org/rfc/bcp/bcp47.txt
which seem to treat "Language-Region" by capitalizing the region name and this is from what I encountered common.
But indeed, in the specs above it says:
Regards,At all times, language tags and their subtags, including private use
and extensions, are to be treated as case insensitive: there exist
conventions for the capitalization of some of the subtags, but these
MUST NOT be taken to carry meaning.
Thus, the tag "mn-Cyrl-MN" is not distinct from "MN-cYRL-mn" or "mN-
cYrL-Mn" (or any other combination), and each of these variations
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service