Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.7.4
-
Fix Version/s: None
-
Component/s: others
-
Labels:None
-
Environment:
Windows 7 x64 (Toshiba Satellite) Home Premium edition.
Fully patched.Sword utilities bundled with Xiphos.
imp2vs.exe Revision $Rev: 2234 $
Same version as last compliled by Greg H.
Description
According to our wiki page on file format, IMP format is
"Each entry consists of a key line and any number of content lines."
Yesterday, I observed what might be a buggy behaviour while using imp2vs.exe to build a module.
The IMP file I have currently has Unix style EOLs (LF) rather than Windows style (CRLF).
The module thus built joined the last word of content line N to the first word of line N+1 (under the same key).
It ought to have inserted a space!
Even stranger - adding a space at the end of each content line did not fix the issue.
With multiline entries for many keys, changing to Windows style EOLs did NOT solve the issue.
Aside: Being the sort of chap I am, I also tried Old Mac style EOLs (CR).
Result = empty module. No records added! Less critical to be sure!
How many source files do we get with Old Mac EOLs?
It appears that imp2vs.exe does not fully comply with the definition of IMP format in
http://crosswire.org/wiki/File_Formats#IMP