On Sat, 14 Jul 2012 10:44:38 -0700 (PDT)
sturdy <sturdy2@...> wrote:
>Can anyone offer a suggestion as to how I can accomplish the import. My
>tree has too many media citations to correct manually/individually.
Spaces are never a good idea in file or directory names, for the reason
you have found; They can truncate the path prematurely. The way around
it is to put the whole path and file name in quote marks thus;
"/path to/a/file name"
Or 'escaping' the spaces thus;
/path\ to/a/file\ name
Adding the leading double quote shouldn't be too onerous (find and
replace /media with "/media), but adding the trailing one is beyond my
current ability. However, it'll need a program to detect where /media
occurs in the GEDCOM, and somehow determine where the path and filename
end. Most likely, this will involve 'grep', amongst other things.
Similar methods can be used to enter the escape character.
Finally, it's not unheard of for some (mainly proprietary) programs to
play "fast and loose" with the GEDCOM standard, using certain parts for
their own purpose. As a result it's almost impossible to get a 100%
successful import using GEDCOM. The bigger the database, the greater
the likelihood of data loss, of course.
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
I am alone there's nobody there
I Look Alone - Buzzcocks