|
Creating navigational topicrefs to cross deliverables in a flat HTML structure
Hi Alicia, I don't know if you use Oxygen, but what you're describing sounds something like what Oxygen's WebHelp transformation can do. You can make a top-level help collection map: <map> <title>Onli
|
Hi Alicia, I don't know if you use Oxygen, but what you're describing sounds something like what Oxygen's WebHelp transformation can do. You can make a top-level help collection map: <map> <title>Onli
|
By
Chris Papademetrious
· #47309
·
|
|
Writing ditaval via XSLT process - is there a more intelligent solution?
Hi Mike, It's not quite clear to me what you're trying to do. Can you provide a small example of the input and expected output you want? - Chris
|
Hi Mike, It's not quite clear to me what you're trying to do. Can you provide a small example of the input and expected output you want? - Chris
|
By
Chris Papademetrious
· #47307
·
|
|
Building links from XML content, “-dita-use-content” - suggestion
Hi David, Topics don't have to be in separate files. You can nest subtopic elements within a topic: <topic id="root"> <title>Features</title> <body>...</body> <topic id="featureA"> <title>Feature A</t
|
Hi David, Topics don't have to be in separate files. You can nest subtopic elements within a topic: <topic id="root"> <title>Features</title> <body>...</body> <topic id="featureA"> <title>Feature A</t
|
By
Chris Papademetrious
· #47299
·
|
|
Building links from XML content, “-dita-use-content” - suggestion
Hi David, Are you looking for a simple way to (1) apply <varname> semantics to produce consistent visual formatting and (2) also create a cross-reference link to the definition? My first thought was t
|
Hi David, Are you looking for a simple way to (1) apply <varname> semantics to produce consistent visual formatting and (2) also create a cross-reference link to the definition? My first thought was t
|
By
Chris Papademetrious
· #47281
·
|
|
Cross-reference to a topic which is not in the DITA map
Hi Yves, I'm guessing that you might be using @href for your topic #2 reference. Cross-map references that use @href will pull the target topic files into the transformation like this. Cross-map refer
|
Hi Yves, I'm guessing that you might be using @href for your topic #2 reference. Cross-map references that use @href will pull the target topic files into the transformation like this. Cross-map refer
|
By
Chris Papademetrious
· #47277
·
|
|
Force missing keydef to generate an error?
Another might be a plugin-based solution to somehow cause unresolved keys to become an error condition. Maybe that is worth exploring. - Chris
|
Another might be a plugin-based solution to somehow cause unresolved keys to become an error condition. Maybe that is worth exploring. - Chris
|
By
Chris Papademetrious
· #47253
·
|
|
Force missing keydef to generate an error?
Hi Radu, Thanks for posting those links! Hi Scott, According to the OASIS DITA specification (2.3.4.6 Processing key references), But I agree with you - if content has a key reference that did not res
|
Hi Radu, Thanks for posting those links! Hi Scott, According to the OASIS DITA specification (2.3.4.6 Processing key references), But I agree with you - if content has a key reference that did not res
|
By
Chris Papademetrious
· #47249
·
|
|
attributes at the root element
Hi Shane, That's exactly how we use them. Writers can make a topic that self-declares which products it is valid for, then our utility synchronizes this information to the map so the profiling conditi
|
Hi Shane, That's exactly how we use them. Writers can make a topic that self-declares which products it is valid for, then our utility synchronizes this information to the map so the profiling conditi
|
By
Chris Papademetrious
· #47248
·
|
|
attributes at the root element
Hi Wayne, Our writers sometimes set profiling attributes on topic root elements. This can be handy when a topic is used in multiple maps. However, as you point out, an issue arises if a map reference
|
Hi Wayne, Our writers sometimes set profiling attributes on topic root elements. This can be handy when a topic is used in multiple maps. However, as you point out, an issue arises if a map reference
|
By
Chris Papademetrious
· #47242
·
|
|
do you use <tt>, <codeph>, or something else for code font stuff?
Hi Julio, Thanks for the reply! I figure we're all probably doing something a bit different (or maybe not?), so I was curious to hear what everyone had to share. I like the idea of semantics in theory
|
Hi Julio, Thanks for the reply! I figure we're all probably doing something a bit different (or maybe not?), so I was curious to hear what everyone had to share. I like the idea of semantics in theory
|
By
Chris Papademetrious
· #47222
·
|
|
do you use <tt>, <codeph>, or something else for code font stuff?
Hi everyone, For inline code-font content, do you use <tt>, <codeph>, or something else? When I configured our DITA schema, I chose <codeph> because it was similar to the <code> element our writers us
|
Hi everyone, For inline code-font content, do you use <tt>, <codeph>, or something else? When I configured our DITA schema, I chose <codeph> because it was similar to the <code> element our writers us
|
By
Chris Papademetrious
· #47219
·
|
|
some thoughts on how a DITA/Git CI/CD pipeline could work
Hi David, Your make-based approach sounds interesting! I have some questions: Did you dynamically generate the makefile from the DITA source before each build to handle changes in dependencies? Did yo
|
Hi David, Your make-based approach sounds interesting! I have some questions: Did you dynamically generate the makefile from the DITA source before each build to handle changes in dependencies? Did yo
|
By
Chris Papademetrious
· #47174
·
|
|
some thoughts on how a DITA/Git CI/CD pipeline could work
Hi Eliot, Your Git monorepos sound even more ornery than ours! I am also interested in submodules, but I think I would want to somehow fracture our existing repos in a way that preserves their history
|
Hi Eliot, Your Git monorepos sound even more ornery than ours! I am also interested in submodules, but I think I would want to somehow fracture our existing repos in a way that preserves their history
|
By
Chris Papademetrious
· #47166
·
|
|
Debugging XSLT files from Dita-OT plugins
Hi Eliot, Thanks for sharing this! For the tunnel variable, I like that you can enable debugging only for a certain template and below. I was trying to figure out why you needed to redefine the tunnel
|
Hi Eliot, Thanks for sharing this! For the tunnel variable, I like that you can enable debugging only for a certain template and below. I was trying to figure out why you needed to redefine the tunnel
|
By
Chris Papademetrious
· #47163
·
|
|
some thoughts on how a DITA/Git CI/CD pipeline could work
Hi Nicholas, Your CI/CD pipeline sounds interesting! We divided our documentation into three monorepos (by business unit), but now even each of those is becoming awkwardly large. And writers want cros
|
Hi Nicholas, Your CI/CD pipeline sounds interesting! We divided our documentation into three monorepos (by business unit), but now even each of those is becoming awkwardly large. And writers want cros
|
By
Chris Papademetrious
· #47157
·
|
|
some thoughts on how a DITA/Git CI/CD pipeline could work
Hi everyone, I recently watched John Kirkilis' DITA-OT Day 2022 presentation and it got me thinking about how to implement CI/CD in our DITA/Git environment. Traditionally when a Git commit is pushed,
|
Hi everyone, I recently watched John Kirkilis' DITA-OT Day 2022 presentation and it got me thinking about how to implement CI/CD in our DITA/Git environment. Traditionally when a Git commit is pushed,
|
By
Chris Papademetrious
· #47153
·
|
|
Going from FrameMaker to oXygen
Hi Frank, If you are not using the DITA Perspective in Oxygen, I suggest enabling it: https://www.oxygenxml.com/doc/versions/25.0/ug-author/topics/dita-perspective.html It applies a collection of sett
|
Hi Frank, If you are not using the DITA Perspective in Oxygen, I suggest enabling it: https://www.oxygenxml.com/doc/versions/25.0/ug-author/topics/dita-perspective.html It applies a collection of sett
|
By
Chris Papademetrious
· #47143
·
|
|
Document owner metadata
Hi Dave, We use <author> as Radu suggests, except that: We use a type of "owner" instead of "creator" as books change ownership and the historical owner is not too important to us. We use usernames in
|
Hi Dave, We use <author> as Radu suggests, except that: We use a type of "owner" instead of "creator" as books change ownership and the historical owner is not too important to us. We use usernames in
|
By
Chris Papademetrious
· #47135
·
|
|
Linking to/from reused topics
Hi Frank, Thanks for the testcase! I simplified it down to the attached testcase. The DITA-OT can duplicate multiple-instance topic files in the following preprocessing steps, in this order: branch-fi
|
Hi Frank, Thanks for the testcase! I simplified it down to the attached testcase. The DITA-OT can duplicate multiple-instance topic files in the following preprocessing steps, in this order: branch-fi
|
By
Chris Papademetrious
· #47131
·
|
|
Linking to/from reused topics
Hi Frank, Can you attach an archive with your testcase? - Chris
|
Hi Frank, Can you attach an archive with your testcase? - Chris
|
By
Chris Papademetrious
· #47124
·
|
