TRansformation scenarios: Where are they saved?
After some time working with the adapted scenario in a book project, I was very surprised today that the scenario got lost. The last time I could use it was eight days ago. I did not change anything in between. Can I retrieve this scenario? Oxygen 20.1 on win7-64 Bernhard
Check to see if you switched between the global and project selection.Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Bernhard Kleine <bernhard.kleine@gmx.net> Date: 10/23/19 4:30 AM (GMT-08:00) To: oxygen-user@oxygenxml.com Subject: [oXygen-user] TRansformation scenarios: Where are they saved? After some time working with the adapted scenario in a book project, Iwas very surprised today that the scenario got lost. The last time Icould use it was eight days ago. I did not change anything in between.Can I retrieve this scenario?Oxygen 20.1 on win7-64Bernhard_______________________________________________oXygen-user mailing listoXygen-user@oxygenxml.comhttps://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi, By default transformation scenarios are on a per project basis, so they are saved in the current project (.xpr) file. Check in the Project view (Window > Show View > Project), look at the very top at the root node, it's the actual .xpr file name. You may have inadvertently switched to a different project, so check in the history combo box from the Project view or in the main menu > Project > Reopen Project. Your scenario could be in one of the previously used projects. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support On 23.10.2019 14:30, Bernhard Kleine wrote:
After some time working with the adapted scenario in a book project, I was very surprised today that the scenario got lost. The last time I could use it was eight days ago. I did not change anything in between. Can I retrieve this scenario?
Oxygen 20.1 on win7-64
Bernhard
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
thanks, that was only temporary. Reloading the project brought the sceneario back. Regards Bernhard Am 23.10.2019 um 16:00 schrieb Oxygen XML Editor Support (Adrian Buza):
Hi,
By default transformation scenarios are on a per project basis, so they are saved in the current project (.xpr) file. Check in the Project view (Window > Show View > Project), look at the very top at the root node, it's the actual .xpr file name. You may have inadvertently switched to a different project, so check in the history combo box from the Project view or in the main menu > Project > Reopen Project. Your scenario could be in one of the previously used projects.
Regards, Adrian Adrian Buza oXygen XML Editor and Author Support On 23.10.2019 14:30, Bernhard Kleine wrote:
After some time working with the adapted scenario in a book project, I was very surprised today that the scenario got lost. The last time I could use it was eight days ago. I did not change anything in between. Can I retrieve this scenario?
Oxygen 20.1 on win7-64
Bernhard
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
I am cleaning up DITA source for a client. I am finding errors that are flagged by the "DITAmap Completeness Check" that are not caught by the standard DITA topic validation. In particular, if a topic contains a (broken) cross reference to another element within the same topic, the topic validation does not catch that error. Is there a way to set up a custom DITA topic validation that will catch this sort of error? Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype)
Hi Kristen, When automatic or manual validation is performed on a DITA topic, we have about 3 validation stages, a stage in which the DTD/schema is used to check for errors, a stage in which a custom Schematron schema is used to check for errors and a stage in which a DITA specific error scanner is used to check for more errors. Our DITA specific error scanner for topics only checks for broken table layouts and for references to missing topics but it could be improved to also check for broken references to IDs in the same topic. I will add an internal issue to do this. Hypothetically the error scanner could also be improved to report links to other topics which have missing IDs but this would mean that the validation would not be fast anymore, it would need to also load those referenced topics and look into them. But for IDs located in the same topic it's no problem. For now maybe you can create a custom Schematron schema to do this extra check: https://blog.oxygenxml.com/2017/02/sharing-schematron-validation-rules.html Some time ago we created this experimental Schematron schema:
OXYGEN_INSTALL_DIR\frameworks\dita\resources\dita-1.2-for-xslt2-links-checker.sch
which actually looks inside the referenced topics for the IDs. It might also work for references inside the current topic. Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com On 10/24/2019 7:41 PM, Kristen James Eberlein wrote:
I am cleaning up DITA source for a client.
I am finding errors that are flagged by the "DITAmap Completeness Check" that are not caught by the standard DITA topic validation.
In particular, if a topic contains a (broken) cross reference to another element within the same topic, the topic validation does not catch that error.
Is there a way to set up a custom DITA topic validation that will catch this sort of error?
Best, Kris
Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Thanks, Radu. I would not want the topic validation to go looking at links to other topics, but it would be good if it found problems with links within the topic. I like to train authors to always validate every topic that they modify -- and to trust that "all is well" if validation run without errors! Thanks for adding an internal issue, and for all your hard work in supporting oXygen users and delivering such an outstanding product. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) On 10/25/2019 2:49 AM, Oxygen XML Editor Support (Radu Coravu) wrote:
Hi Kristen,
When automatic or manual validation is performed on a DITA topic, we have about 3 validation stages, a stage in which the DTD/schema is used to check for errors, a stage in which a custom Schematron schema is used to check for errors and a stage in which a DITA specific error scanner is used to check for more errors. Our DITA specific error scanner for topics only checks for broken table layouts and for references to missing topics but it could be improved to also check for broken references to IDs in the same topic. I will add an internal issue to do this. Hypothetically the error scanner could also be improved to report links to other topics which have missing IDs but this would mean that the validation would not be fast anymore, it would need to also load those referenced topics and look into them. But for IDs located in the same topic it's no problem.
For now maybe you can create a custom Schematron schema to do this extra check:
https://blog.oxygenxml.com/2017/02/sharing-schematron-validation-rules.html
Some time ago we created this experimental Schematron schema:
OXYGEN_INSTALL_DIR\frameworks\dita\resources\dita-1.2-for-xslt2-links-checker.sch
which actually looks inside the referenced topics for the IDs. It might also work for references inside the current topic.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 10/24/2019 7:41 PM, Kristen James Eberlein wrote:
I am cleaning up DITA source for a client.
I am finding errors that are flagged by the "DITAmap Completeness Check" that are not caught by the standard DITA topic validation.
In particular, if a topic contains a (broken) cross reference to another element within the same topic, the topic validation does not catch that error.
Is there a way to set up a custom DITA topic validation that will catch this sort of error?
Best, Kris
Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (5)
-
Bernhard Kleine -
dvint -
Kristen James Eberlein -
Oxygen XML Editor Support (Adrian Buza) -
Oxygen XML Editor Support (Radu Coravu)