Re: [LegacyUG] Hyphen versus Dash in file names

[MikeFry]

On 25 Feb 2016 6:38 PM, Bobby Johnson wrote:


Mike, I agree that the problem is not generated by LFT but it has a
tremendous effect on LFT when you restore a backup.  The zip program I use
is 7-zip.  Don't know if it was installed as a part of Win 8 or a factory
installed program by the computer maker. Windows is perfectly happy with the
dash as you point out but Legacy sure doesn’t like it when a file name gets
changed and in this case the zip/unzip does change the file name.


7-zip is 3rd-party software. Normally available as freeware. It's old.

--
Regards,
Mike Fry (Jhb)

___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Bobby Johnson]

Mike, I agree that the problem is not generated by LFT but it has a tremendous 
effect on LFT when you restore a backup.  The zip program I use  is 7-zip.  
Don't know if it was installed as a part of Win 8 or a factory installed 
program by the computer maker.
Windows is perfectly happy with the dash as you point out but Legacy sure 
doesn’t like it when a file name gets changed and in this case the zip/unzip 
does change the file name.
Bobby

> -Original Message-
> From: LegacyUserGroup [mailto:legacyusergroup-
> boun...@legacyusers.com] On Behalf Of MikeFry
> Sent: Thursday, February 25, 2016 3:42 AM
> To: legacyusergroup@legacyusers.com
> Subject: Re: [LegacyUG] Hyphen versus Dash in file names
> 
> On 25 Feb 2016 4:43 AM, Bobby Johnson wrote:
> 
> > Yep, I have been chipping away at it.  May take a while.
> My main
> > objective was to let people know that some and maybe all
> of the
> > extended ascii characters will not go through a zip/unzip
> operation in tact.
> 
> I would have thought that this was a Windows restriction
> and not a Legacy problem. Windows has a list of disallows
> characters and your Alt-0150 is not on that list. It does say
> that not all filename strings are valid on all file systems. This
> becomes important when moving files between, say,
> Windows and a Mac.
> 
> This paragraph might cast some light (from
> <https://msdn.microsoft.com/en-
> us/library/windows/desktop/aa365247%28v=vs.85%29.aspx
> ?f=255&MSPPError=-2147217396>)
> 
> Use any character in the current code page for a name,
> including Unicode characters and characters in the extended
> character set (128–255), except for the following:
> 
>  The following reserved characters:
>  < (less than)
>  > (greater than)
>  : (colon)
>  " (double quote)
>  / (forward slash)
>  \ (backslash)
>  | (vertical bar or pipe)
>  ? (question mark)
>  * (asterisk)
> 
> Your Alt-0150 might only be really valid on a pure Unicode
> system.
> 
> 
> One question though: What software did you use for the
> ZIP/UNZIP? Software that expects 'normal' filenames might
> have problems with 'exotic' characters.
> 
> --
> Regards,
> Mike Fry (Jhb)
> 
> ___
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> http://legacyusers.com/mailman/listinfo/legacyusergroup_l
> egacyusers.com


___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[MikeFry]

On 25 Feb 2016 4:43 AM, Bobby Johnson wrote:


Yep, I have been chipping away at it.  May take a while.  My main objective was
to let people know that some and maybe all of the extended ascii characters will
not go through a zip/unzip operation in tact.


I would have thought that this was a Windows restriction and not a Legacy 
problem. Windows has a list of disallows characters and your Alt-0150 is not on 
that list. It does say that not all filename strings are valid on all file 
systems. This becomes important when moving files between, say, Windows and a Mac.


This paragraph might cast some light (from 
)


Use any character in the current code page for a name, including Unicode 
characters and characters in the extended character set (128–255), except for 
the following:


The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

Your Alt-0150 might only be really valid on a pure Unicode system.


One question though: What software did you use for the ZIP/UNZIP? Software that 
expects 'normal' filenames might have problems with 'exotic' characters.


--
Regards,
Mike Fry (Jhb)

___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Bobby Johnson]

Yep, I have been chipping away at it.  May take a while.  My main objective was 
to let people know that some and maybe all of the extended ascii characters 
will not go through a zip/unzip operation in tact.

Bobby

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Cathy Pinner
Sent: Wednesday, February 24, 2016 9:04 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Hyphen versus Dash in file names

 

Bobby,

I was assuming you'd use the File Renamer to replace the dash with the hyphen 
or whichever way it was to re-establish the links.
If you still have the links, yes you need to use the Picture Centre and go one 
by one. 

Cathy

Bobby Johnson wrote:




Cathy,

I don’t believe file renamer is the way to go.  I believe I will need 
to rename the files using Picture Center or have a real mess of 
relinking to do.  The built in relinker will not work  on files that 
have been renamed without using Picture Center.

Bobby



___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Cathy Pinner]

Bobby,



I was assuming you'd use the File Renamer to replace the dash with the 
hyphen or whichever way it was to re-establish the links.

If you still have the links, yes you need to use the Picture Centre and 
go one by one. 



Cathy



Bobby Johnson wrote:


Cathy,

I don’t believe file renamer is the way to go.  I believe I will need 
to rename the files using Picture Center or have a real mess of 
relinking to do.  The built in relinker will not work  on files that 
have been renamed without using Picture Center.

Bobby

*From:*LegacyUserGroup 
[mailto:legacyusergroup-boun...@legacyusers.com] *On Behalf Of *Cathy 
Pinner
*Sent:* Wednesday, February 24, 2016 6:33 PM
*To:* Mailing List for users of Legacy Family Tree software 

*Subject:* Re: [LegacyUG] Hyphen versus Dash in file names

Bobby,

An interesting issue.
You can fix it with a file renamer. I use File Renamer Basic free from 
sherrodcomputers.com

Cathy



___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Bobby Johnson]

Cathy, 

I don’t believe file renamer is the way to go.  I believe I will need to rename 
the files using Picture Center or have a real mess of relinking to do.  The 
built in relinker will not work  on files that have been renamed without using 
Picture Center.

Bobby

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Cathy Pinner
Sent: Wednesday, February 24, 2016 6:33 PM
To: Mailing List for users of Legacy Family Tree software 

Subject: Re: [LegacyUG] Hyphen versus Dash in file names

 

Bobby,

An interesting issue.
You can fix it with a file renamer. I use File Renamer Basic free from 
sherrodcomputers.com

Cathy




___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Cathy Pinner]

Bobby,

An interesting issue.
You can fix it with a file renamer. I use File Renamer Basic free from 
sherrodcomputers.com


Cathy

Linda Hodges wrote:


I always use underscores.

On Feb 24, 2016 1:38 PM, "Bobby Johnson" mailto:b...@brmemc.net>> wrote:

I have recently been struggling with a problem with media
files. On many occasions I use Dragon NaturallySpeaking to
enter data into legacy. The problem I ran into deals with
file names. As an example:
Census - Bradley County, Tennessee - 1940 - John Doe
is the name of a file I would use. The character between
census and Bradley is a hyphen(ascii 45) as opposed to a
dash(ascii 0150). Using Dragon to dictate this file name, I
would use the word dash which would enter a space before and
after the dash. In doing so everything seemed to work fine
including the file sorting. However, when I backed up the
media files and use the backup file to restore them on
another computer I found many media files missing.

I have discovered that when you zip a file with a dash(ascii
0150) and then unzip the file the dash is returned as a
hyphen. Therefore the file name has changed and LFT cannot
find this media file.

This is a warning for anyone who might for any reason do a
backup with a file name that contains a dash.


___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com

http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Michael Griffin]

Thanks Linda, rechecking file names .
Mike

 
  From: Linda Hodges 
 To: Mailing List for users of Legacy Family Tree software 
 
 Sent: Wednesday, February 24, 2016 12:55 PM
 Subject: Re: [LegacyUG] Hyphen versus Dash in file names
   
I always use underscores.On Feb 24, 2016 1:38 PM, "Bobby Johnson" 
 wrote:

I have recently been struggling with a problem with media
files. On many occasions I use Dragon NaturallySpeaking to
enter data into legacy. The problem I ran into deals with
file names. As an example:
Census - Bradley County, Tennessee - 1940 - John Doe
is the name of a file I would use. The character between
census and Bradley is a hyphen(ascii 45) as opposed to a
dash(ascii 0150). Using Dragon to dictate this file name, I
would use the word dash which would enter a space before and
after the dash. In doing so everything seemed to work fine
including the file sorting. However, when I backed up the
media files and use the backup file to restore them on
another computer I found many media files missing.

I have discovered that when you zip a file with a dash(ascii
0150) and then unzip the file the dash is returned as a
hyphen. Therefore the file name has changed and LFT cannot
find this media file.

This is a warning for anyone who might for any reason do a
backup with a file name that contains a dash.


___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com


___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com


   
 ___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Re: [LegacyUG] Hyphen versus Dash in file names

[Linda Hodges]

I always use underscores.
On Feb 24, 2016 1:38 PM, "Bobby Johnson"  wrote:

> I have recently been struggling with a problem with media
> files. On many occasions I use Dragon NaturallySpeaking to
> enter data into legacy. The problem I ran into deals with
> file names. As an example:
> Census - Bradley County, Tennessee - 1940 - John Doe
> is the name of a file I would use. The character between
> census and Bradley is a hyphen(ascii 45) as opposed to a
> dash(ascii 0150). Using Dragon to dictate this file name, I
> would use the word dash which would enter a space before and
> after the dash. In doing so everything seemed to work fine
> including the file sorting. However, when I backed up the
> media files and use the backup file to restore them on
> another computer I found many media files missing.
>
> I have discovered that when you zip a file with a dash(ascii
> 0150) and then unzip the file the dash is returned as a
> hyphen. Therefore the file name has changed and LFT cannot
> find this media file.
>
> This is a warning for anyone who might for any reason do a
> backup with a file name that contains a dash.
>
>
> ___
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>
___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

[LegacyUG] Hyphen versus Dash in file names

[Bobby Johnson]

I have recently been struggling with a problem with media
files. On many occasions I use Dragon NaturallySpeaking to
enter data into legacy. The problem I ran into deals with
file names. As an example:
Census - Bradley County, Tennessee - 1940 - John Doe
is the name of a file I would use. The character between
census and Bradley is a hyphen(ascii 45) as opposed to a
dash(ascii 0150). Using Dragon to dictate this file name, I
would use the word dash which would enter a space before and
after the dash. In doing so everything seemed to work fine
including the file sorting. However, when I backed up the
media files and use the backup file to restore them on
another computer I found many media files missing.

I have discovered that when you zip a file with a dash(ascii
0150) and then unzip the file the dash is returned as a
hyphen. Therefore the file name has changed and LFT cannot
find this media file.

This is a warning for anyone who might for any reason do a
backup with a file name that contains a dash.


___
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com