- oXygen-user - www.oxygenxml.com

Expand/Collapse all with one cliock
by Frank Dissinger 14 Feb '23

14 Feb '23

Hi list, Is it possible to expand/collapse all items at the same level with just one click? I tried all combinations such as Ctrl-click, Alt-click, Shift-Ctrl-click etc., but to know avail. I refer to the Project window, DITA Maps Manager and Outline view. This would be a useful feature. FrameMaker can do it! 😉 Regards, Frank -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)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>

2 1

Hyphenation in Author mode?
by Frank Dissinger 14 Feb '23

14 Feb '23

Can words be hyphenated automatically in Author mode? -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)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>

2 1

Image and table width in Author mode
by Frank Dissinger 14 Feb '23

14 Feb '23

Hi list, I publish DITA content as online help and PDF. In oXygen's Author mode I would like to make sure that images do not exceed the width of the A4-sized PDF pages. Sometimes I also place two or more inline images side by side in a paragraph and want to make sure if all of them fit on the line or if there is a line break between them. All my images have PNG format and an "otherprops="fmdpi:xxx" attribute where xxx is usually 150, in some cases 140, 160 or similar. FrameMaker, my previous XML editor, honors this attribute and scales the images appropriately. I notice that oXygen displays images bigger in its editor compared to 150 dpi images in FrameMaker. I would need to reduce all images to about 66% of their size (= by factor 1.5). Unfortunately I do not know of any CSS style which scales images based on their own pixel size. Percentage values in CSS apply to the widht or height of the viewport. Likewise, I would like to make sure that table columns are not too narrow on the PDF pages. What can I do? Any ideas are welcome. Regards, Frank -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)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>

4 5

DITA footnotes in Author mode
by Frank Dissinger 09 Feb '23

09 Feb '23

Hi list, oXygen does not seem to have any special styling for DITA footnotes in Author mode. They are just shown as inline elements in italics. Has anybody managed to style footnots with CSS in a way similar to how they would like on a page, i.e. on the bottom of the page with ascending numbers and a superscript number at the location where the footnote is referenced? I made some attempts with "fn {position: absolute; bottom: -2em}", but was not CSS-skilled enough to prevent the footnotes all being placed on top of each other. And I don't know how to implement a counter for elements that are scattered over the element tree (not children of the same element). Any ideas? Regards, Frank -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)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>

2 1

Re: [oXygen-user] Conkeyrefs not rendered on map-level
by Sascha Nothofer 02 Feb '23

02 Feb '23

Hi Radu, thanks for your analysis of my issue! Your questions and thoughts helped me to track down the problem. If you try to publish a map containing a title (or data element) with a conkeyref like this <map><title><ph conkeyref="key/productName"/></title>...</map> and if the reused element contains another element with an id attribute like this <ph id="productName"><ph id="otherId">...</ph>...</ph> then the DITA OT 3.7.3 (Oxygen 25.0 build in) is not able to resolve the reference on map level. For example the pdf front page title does not contain the referenced content. If you use conref instead, everything is fine. Conkeyrefs from topic to topic are also resolved as expected. It looks like a OT bug. Thx! Sascha > 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? yes, html or pdf. We have no problems in Oxygen/Author. All references are displayed fine. > > 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? No problem in Maps Manager. The problem is only in preprocessing output and following. > > 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? yes > 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 [https://reinmedical.com/en/node/1499/view-as-image] [cid:image690462.png@57dd3af6.4dab699c] <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(a)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 [https://reinmedical.com/en/node/1498/view-as-image] 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. ________________________________ Von: oXygen-user <oxygen-user-bounces(a)oxygenxml.com> im Auftrag von oxygen-user-request(a)oxygenxml.com <oxygen-user-request(a)oxygenxml.com> Gesendet: Mittwoch, 25. Januar 2023 19:00 An: oxygen-user(a)oxygenxml.com Betreff: oXygen-user Digest, Vol 139, Issue 17 Send oXygen-user mailing list submissions to oxygen-user(a)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(a)oxygenxml.com You can reach the person managing the list at oxygen-user-owner(a)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(a)oxygenxml.com> To: oxygen-user(a)oxygenxml.com Subject: Re: [oXygen-user] Inserting child elements automatically Message-ID: <a269f912-194c-7099-e127-ef95da07c5e4(a)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 "". 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-i… 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 element. I would like > oXygen to automatically insert 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(a)cgs-oris.com | *Web* www.cgs-oris.com<http://www.cgs-oris.com> > <http://www.cgs-oris.com/> CGS ORIS - Homepage<http://www.cgs-oris.com/> www.cgs-oris.com Smart software solutions & media for the printing and packaging industry. Simple to use, for all of your needs related to color management, proofing, prototyping and certification. > > *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.png] <https://www.cgs-oris.com/signatur> [https://www.cgs-oris.com/media/k2/items/cache/b689fad0280b286c898256c8d3b6e…]<https://www.cgs-oris.com/signatur> CGS ORIS - Signatur<https://www.cgs-oris.com/signatur> www.cgs-oris.com Hainburg, Germany (December 13, 2022) – Last week CGS ORIS already released new versions of its proofing and prototyping solutions: Now the updates of the color management applications for four- and multi-color printing are available, too. PRESS MATCHER 4.2 and X GAMUT 4.2 contain a great amount of... > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)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/5ee65dd…> ------------------------------ Message: 2 Date: Wed, 25 Jan 2023 11:38:18 +0200 From: "Oxygen XML Editor Support (Radu Coravu)" <support(a)oxygenxml.com> To: oxygen-user(a)oxygenxml.com Subject: Re: [oXygen-user] Conkeyrefs not rendered on map-level Message-ID: <b72cb011-17c0-2682-aea5-0d9adc6e548f(a)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(a)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(a)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/b2b77bc…> -------------- 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/b2b77bc… [http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230125/b2b77bc…] > ------------------------------ Subject: Digest Footer _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user ------------------------------ End of oXygen-user Digest, Vol 139, Issue 17 ********************************************

2 1

[Ann] New maintenance build available for oXygen 25.0 (2023013006)
by Oxygen XML Editor Support (Adrian Buza) 01 Feb '23

01 Feb '23

Dear oXygen users, We announce the release of a new maintenance build (2023013006) for oXygen 25.0 (XML Editor, XML Developer, XML Author, XML WebHelp, PDF Chemistry, Publishing Engine). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2023013006 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support

1 0

[ANN] The Oxygen Live Tutorials add-on has been released!
by Alin Belu 31 Jan '23

31 Jan '23

Hello, We are excited to announce the release of our newest add-on – *Live Tutorials*! Now, end users can access live tutorials and learn how to utilize Oxygen right from the application by using this latest entry in our add-on library. The Live Tutorials add-on comes bundled with a set of tutorials for learning to work with the DITA XML standard and it also gives you the ability to create your own tutorials. Each tutorial contains one or more missions. A mission consists of a set of instructions and helpful tips in addition to the initial file content that is opened in the application. After you modify the original content to get the desired outcome, the mission is considered successful. To manually install the add-on, follow this procedure: 1. Go to *Help > Install new add-ons* to open an add-on selection dialog box. Enter or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml in the *Show add-ons from* field or select it from the drop-down menu. 2. Select the *Live Tutorials* add-on and click *Next*. 3 Read the end-user license agreement. Then select the *I accept all terms of the end-user license agreement* option and click *Finish*. 4 Restart the application. Result: The *Tutorials* view is now available. To open the view, select *Tutorials* from the *Window > Show View* menu. For more information on this newest release, see the details for the Live Tutorials add-on on the page below: https://www.oxygenxml.com/doc/ug-editor/topics/live-tutorials-addon.html We hope you will find this new tool useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

FM/OXY: Different DITA code for "conkeyref"
by Frank Dissinger 27 Jan '23

27 Jan '23

Hi list, As some of you know, I have just switched from FrameMaker to oXygen. I discovered that the two programs create different DITA code for "<dlentry conkeyref="...">. oXygen creates an empty * *tag before the closing </dlentry> tag. Are both codes equally correct? Or is one better than the other? oXygen code: <dlentry conkeyref="lib_ref/search"> <dt/> <dd>**</dd> </dlentry> FrameMaker code: <dlentry conkeyref="lib_ref/search"> <dt/> <dd/> </dlentry> Referenced dita topic: <dlentry id="search"> <dt><uicontrol keyref="color_search_box"/></dt> <dd>Use this option to quickly find a specific color if many colors are loaded.Enter the first few letters or any part of the color name. This will select the first color the name of which is matched by these characters.If your input matches multiple colors, click on the small arrow to select a color from the list. This list contains only colors with names that contain the characters you have entered.</dd> </dlentry> BTW: This difference became obvious after defining a Schematron rule which outputs an error for <dd> elements which do not have any child elements. I have defined this rule and many similar ones because I want to wrap every paragraph in wherever is valid. The FM-generated code (<dd/>) is marked up as invalid by this rule. It would be a nightmare to change all these hundreds of "conkeyref"s in all my projects. Or should I just do without this check (i.e. the second "assert")? <sch:pattern id="Check_DD"> <sch:rule context="dd"> <sch:assert test="not(text()[normalize-space()])">DD element must not contain any text.</sch:assert> <sch:assert test="*">DD does not contain any child elements</sch:assert> </sch:rule> </sch:pattern> Regards, Frank -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)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>

2 1

After Fluenta update the context menu action disappeared
by Franz-Josef Knelangen 26 Jan '23

26 Jan '23

Hello, the Fluenta context menu action in the DITA Maps Manager view disappeared after updating to Fluenta 3.3. Reinstalling the plug-in didn't help, reinstalling Oxygen didn't help either. Is there some temporary config file I have to change/delete to get this working again? Please, advice. Greetings, Franz-Josef Franz-Josef Knelangen Leiter Dokumentation Direct: Main: Mobile: +49 7634 5612-0 +49 7634 5612-0 - Facebook<https://www.facebook.com/akgsoftware/> | Xing<https://www.xing.com/pages/akgsoftware> | LinkedIn<https://www.linkedin.com/company/18590571> | YouTube<https://www.youtube.com/c/AKGSoftware-infrastructure> [cid:image002_01fef2d4-1f7d-4ea5-9727-748ef31e8852.png] AKG Software Consulting GmbH Uhlandstr. 12 D-79423 Heitersheim www.akgsoftware.de<https://www.akgsoftware.de/> Gesch?ftsf?hrer: Dipl.-Ing. Artur K. G?nther, Dipl.-Ing. Arno Br?ggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens G?nther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg i. Br.)

3 3

Conkeyrefs not rendered on map-level
by Sascha Nothofer 25 Jan '23

25 Jan '23

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 todo with the custom pdf plugin: 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://reinmedical.com/en/node/1499/view-as-image] [cid:image7e18df.png@242e64c4.45866f07] <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(a)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 [https://reinmedical.com/en/node/1498/view-as-image] 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.

2 1