Bug 909647 - Spell checking does not work well with "ft=docbk"
Summary: Spell checking does not work well with "ft=docbk"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 18
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-10 04:02 UTC by Jaromir Hradilek
Modified: 2014-02-05 19:04 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:04:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
A patch for the /usr/share/vim/vim73/syntax/docbk.vim file (1.97 KB, patch)
2013-02-10 04:02 UTC, Jaromir Hradilek
no flags Details | Diff
A sample DocBook XML file that can serve as a reproducer (528 bytes, application/docbook+xml)
2013-02-10 04:05 UTC, Jaromir Hradilek
no flags Details

Description Jaromir Hradilek 2013-02-10 04:02:40 UTC
Created attachment 695657 [details]
A patch for the /usr/share/vim/vim73/syntax/docbk.vim file

Description of problem:
When editing a DocBook XML file with spell checking enabled, Vim only checks the spelling of XML attributes and comments, not the actual text between the XML tags. This makes perfect sense when working with generic XML, which may contain data, but DocBook was specifically designed for technical documentation where it is quite important to have a working spell checker.

Version-Release number of selected component (if applicable):
vim-common-7.3.712-1.fc18.x86_64
vim-enhanced-7.3.712-1.fc18.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Open a DocBook XML file in Vim:

   $ vim Test_Chapter.xml

2. Make sure the file type is set to "docbk":

   :set ft=docbk
 
3. Make sure that spell checking is enabled:

   :set spl=en spell
  
Actual results:
Only spelling errors in XML attributes and comments are highlighted.

Expected results:
All spelling errors, especially those in the actual text, are highlighted.

Additional info:
I have sent a similar patch upstream.

Comment 1 Jaromir Hradilek 2013-02-10 04:05:09 UTC
Created attachment 695658 [details]
A sample DocBook XML file that can serve as a reproducer

Comment 2 Fedora End Of Life 2013-12-21 11:17:42 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 19:04:17 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.