Send oXygen-user mailing list submissions to
        oxygen-user@oxygenxml.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.oxygenxml.com/mailman/listinfo/oxygen-user
or, via email, send a message with subject or body 'help' to
        oxygen-user-request@oxygenxml.com

You can reach the person managing the list at
        oxygen-user-owner@oxygenxml.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of oXygen-user digest..."


Today's Topics:

   1. Re: Inserting child elements automatically
      (Oxygen XML Editor Support (Radu Coravu))
   2. Re: Conkeyrefs not rendered on map-level
      (Oxygen XML Editor Support (Radu Coravu))


----------------------------------------------------------------------

Message: 1
Date: Wed, 25 Jan 2023 08:06:34 +0200
From: "Oxygen XML Editor Support (Radu Coravu)"
        <support@oxygenxml.com>
To: oxygen-user@oxygenxml.com
Subject: Re: [oXygen-user] Inserting child elements automatically
Message-ID: <a269f912-194c-7099-e127-ef95da07c5e4@oxygenxml.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi Frank,


Let's split your use cases in two:

1) Inserting elements using Oxygen's actions (toolbars, menus)

2) Inserting elements using the content completion window.


1)


Let's take table insertion for example:


If you edit your DITA framework extension that is defined in the
Preferences->"Document Type Association" page, it has an
"Author=>Actions" tab.

If you edit the action "insert.table", it calls an operation named
"ro.sync.ecss.extensions.dita.topic.table.InsertTableOperation" with
certain parameters. One of the parameters is named "cellFragment", you
can set its value to "<p/>".

There are other ways to change a table, for example insert a new column,
insert a new row. So actions like "insert.table.row.below" or
"insert.table.column.after" which also need to be changed accordingly.


2) Inserting elements like <info> using the content completion window.

Your DITA extension framework customization can contain a
"cc_config.xml" file which defines that for certain elements, if they
are inserted, another element should be inserted inside them as well:

https://www.oxygenxml.com/doc/ug-editor/topics/configure-elements-attr-cc-individually.html#configure-elements-attr-cc-individually__examples_configuring_elements


Hope this helps.


Regards,

Radu


Radu Coravu
Oxygen XML Editor

On 1/24/23 11:49, Frank Dissinger wrote:
>
> Hi list,
>
>
> Whenever this is valid, I wrap text in a <p> element. I would like
> oXygen to automatically insert <p> as a child element when inserting
> <table>, <simpletable> (for the table cells of course), <info>,
> <stepresult>, <stepxmp>... and many more. How do I do this?
>
>
> Regards,
>
> Frank
>
> --
>
> *Frank Dissinger*
>
> Documentation Manager
>
> ....................................................................
>
> *CGS Publishing Technologies International GmbH*
>
> *Email *frank.dissinger@cgs-oris.com | *Web* www.cgs-oris.com
> <http://www.cgs-oris.com/>
>
> *Address* Kettelerstr. 24 | D-63512 Hainburg | Germany
>
> *Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99
>
> *Commercial register* Offenbach, HRB no. 21495
>
> *Managing directors* Bernd R?ckert, Christoph Thommessen
>
>
> https://www.cgs-oris.com/Signatur.png

<https://www.cgs-oris.com/signatur>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user@oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230125/5ee65dde/attachment-0001.htm>

------------------------------

Message: 2
Date: Wed, 25 Jan 2023 11:38:18 +0200
From: "Oxygen XML Editor Support (Radu Coravu)"
        <support@oxygenxml.com>
To: oxygen-user@oxygenxml.com
Subject: Re: [oXygen-user] Conkeyrefs not rendered on map-level
Message-ID: <b72cb011-17c0-2682-aea5-0d9adc6e548f@oxygenxml.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi Sasha,


Usually problems can be either editing problems or publishing problems
or problems which affect both editing and publishing.


> Currently I want to switch from Oxygen 23 to 25.0 including an
> extracted build-in DITA-OT3.x with custom pdf2 plugin but In the
> updated?environment we have the following effect:
>
>
> In almost all DITAVAL contexts (we have a lot) the variable texts are
> not rendered into the DITA Map anymore without error messages.
>
This looks like an editing problem, in such cases we are interested in
knowing what those particular error messages state. Ideally we would
also have a small sample DITA project to reproduce the problem on our
side. You can do this with a separate off list email.
>
> Just a few DITAVAL contexts produce output as before.
>
By output do you mean publishing?
>
> In published content topics/chapters everything is fine -> conkeyrefs
> are resolved.
>
So the publishing is fine? Only the DITA Maps Manager has problems
displaying the keyrefs?
>
> Also Oxygen Author WYSIWYG resolves all conkeyrefs as expected in
> topics and in the map.
>
Ok, so the main editor area seems to work.
>
>
> In the pre-processing output (?_MERGED.xml) the specific map elements
> do not contain the variable text but conref attributes with wrong
> transformed links:
> The conrefs contain ?path/topic.dita#ElementID? instead of
> ?path/ditatopic.dita#topicID/ElementID?
>
> In correct output contexts there are no conref attrubtes rendered into
> output, just the elements with resolved text.
>
So there is also a publishing problem as well? Oxygen 25.0 comes bundled
with DITA OT 3.7 from what I remember, maybe there is some
incompatibility between your custom PDF plugin and DITA OT 3.7.

Do you have also a DITA DTD specialization plugin? If so did you install
it in the DITA OT bundled with Oxygen 25.0?

> I guess, there could be many different reasons for this. I tried a lot
> and couldn?t reproduced the problem in a simple test project. I also
> did?nt manage to simplify our project to a working state.
>
I somehow suspect you may have some DITA specialization for certain
topics. I'm not sure. If you can reproduce about the same problem when
editing and when publishing, the problem is usually somewhere in the
DITA Open Toolkit publishing engine, some plugin which may not be installed.


Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 1/23/23 17:19, Sascha Nothofer wrote:
>
> Hi DITA & Oxygen Users,
>
> Currently I want to switch from Oxygen 23 to 25.0 including an
> extracted build-in DITA-OT3.x with custom pdf2 plugin but In the
> updated?environment we have the following effect:
>
>
> In almost all DITAVAL contexts (we have a lot) the variable texts are
> not rendered into the DITA Map anymore without error messages. Just a
> few DITAVAL contexts produce output as before.
>
> In published content topics/chapters everything is fine -> conkeyrefs
> are resolved. Also Oxygen Author WYSIWYG resolves all conkeyrefs as
> expected in topics and in the map.
>
> In the pre-processing output (?_MERGED.xml) the specific map elements
> do not contain the variable text but conref attributes with wrong
> transformed links:
> The conrefs contain ?path/topic.dita#ElementID? instead of
> ?path/ditatopic.dita#topicID/ElementID?
>
> In correct output contexts there are no conref attrubtes rendered into
> output, just the elements with resolved text.
>
> I guess, there could be many different reasons for this. I tried a lot
> and couldn?t reproduced the problem in a simple test project. I also
> did?nt manage to simplify our project to a working state.
>
>
> Maybe someone experienced a similar effect (conkeyrefs in topic
> content resolved but not in map title/data elements) and can provide
> hints for a possible cause and or solution.
>
> What I can say so far:
> - It has nothing todowith the custom pdfplugin: same problem with
> build-in pdf and html transformation scenarios.
> - We are using only standard pdf parameter settings.
> - It has nothing todo with filtering directly because I have deleted
> all filter atts in the conkeyref chain in scope of the problem. Also
> our props attribute specialization does not affect the problem.
> - We do not use:
>
> - ?- scoped keys and ditavalref in maps
>
> -? - push-replace
>
> -? Same problem with and without DITA project files.
>
> - Problem is not caused by DITA topic content structures (I have
> copied content from working to non-working context.
>
> I'm curious if someone has already seen something like this.
>
> Best Regards
>
> Sascha
>
>
>
>
>        <https://goo.gl/maps/g6BewH36cWS2>
> Kontakt | Contact      Rein Medical GmbH
> T:     +49 2161 6984 - 131      Monforts Quartier 23
> *M:*  
>        Schwalmstra?e 301
> *F:*   +49 2161 6984 - 231      41238 M?nchengladbach
> *E:*   sascha.nothofer@reinmedical.com  Germany
> *W:*   https://www.reinmedical.com      
> *S:*  
>       
>
>
> Rechtliches | Legal           
> Gesch?ftsf?hrer:       Dieter Cyganek, Stephan Rein, Thorsten Godulla,
> Hisakazu Harada, Akira Suzuki
> Registergericht:       Amtsgericht M?nchengladbach HRB 15810   
> Ust.-ID-Nr.:   DE811604837     
> WEE-Reg.-Nr.:  DE 59730470     
> Diese E-Mail ist ausschlie?lich f?r den angegebenen Empf?nger
> bestimmt. Sie kann Informationen enthalten, welche vertraulich sind
> und durch die Verschwiegenheit gesch?tzt werden. Diese E-Mail darf nur
> von diesem Empf?nger gelesen, ausgedruckt, aufbewahrt, kopiert und
> verbreitet werden. Sollten Sie diese Mitteilung irrt?mlich erhalten
> haben, bitten wir Sie, den Absender zu benachrichtigen, s?mtliche
> Ausdrucke zu vernichten und diese E-Mail zu l?schen.
> This message may contain confidential information and is intended only
> for the specified recipient. If you are not the specified recipient
> you should not disseminate, distribute or copy this e-mail. Please
> notify the specified sender immediately by e-mail if you have received
> this e-mail by mistake and delete this e-mail from your system.
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user@oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230125/b2b77bc7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image7e18df.png
Type: image/png
Size: 7476 bytes
Desc: not available
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230125/b2b77bc7/attachment-0001.png

>

------------------------------

Subject: Digest Footer

_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user


------------------------------

End of oXygen-user Digest, Vol 139, Issue 17
********************************************