Specialized DOCTYPE not reproduced in output
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- xml
- Domain
- tooling
Research direction
Start in the org.dita.normalize repository by reproducing the DITA-OT 3.0.1 transformation with the specialized DOCTYPE shown in the report. Trace where the output DOCTYPE is generated and compare its public identifier with the input; done means the specialized identifier is preserved or the expected behavior is documented.
Written by the indexing model from the issue text.
Description
Hi,
I've successfully run the transformation that comes with DITA-OT 3.0.1 after integrating our own specialization. However, the specialized DOCTYPE's public identifier is not reproduced in the output so
<!DOCTYPE datasheet PUBLIC "-//MY//DTD Datasheet//EN" "datasheet.dtd"> becomes
<!DOCTYPE datasheet PUBLIC "-//OASIS//DTD DITA Datasheet//EN" "datasheet.dtd">.
Is this the desired behavior or a bug?
Best regards,
Frank
- Dominant language
- XSLT
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dita-ot/org.dita.normalize
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
dita-ot/org.dita.normalize#5 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Possibly add parameter which specified whether merged map or individual topics should be obtainedOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
dita-ot/org.dita.normalize#1 · 2 comments ·
All issues in dita-ot/org.dita.normalize
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jbacalso24/mimry#459 · 1 comment ·
Maintainers usually reply within 1 day
-
False Negative: InnerTypeLastCheck does not report members declared after inner enums or annotationsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
checkstyle/checkstyle#22027 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest skip-changelog
Difficulty 2/5 1-3 hours Newbie friendliness 95/100
wassim-azi/agy-powerline#69 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day