Hi

 

                Using a ‘special’ character in any field within Legacy’s own 
database should not cause any issues, unless Legacy itself is putting limits in 
place. 

 

However, using a name, valid as a field within Legacy, as part of a file name 
within Windows can could issues since they must be constrained by the limits 
within Windows. This is from the Microsoft website

 

1.       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:

a.       The following reserved characters:

                                                                           i.   
   < (less than)

                                                                         ii.    
  > (greater than)

                                                                       iii.     
 : (colon)

                                                                       iv.      
" (double quote)

                                                                         v.     
 / (forward slash)

                                                                       vi.      
\ (backslash)

                                                                      vii.      
| (vertical bar or pipe)

                                                                    viii.      
? (question mark)

                                                                        ix.     
 * (asterisk)

b.       Integer value zero, sometimes referred to as the ASCII NUL character.

c.       Characters whose integer representations are in the range from 1 
through 31, except for alternate data streams where these characters are 
allowed.

d.       Any other character that the target file system does not allow.

 

The problems originally occurred when the filename does not match the 
‘traditional’ US naming standards, based on ASCII 32-127 characters sets. You 
then become dependent on limitations built into the operating system, ZIP 
software etc. and on the current code page in use. Changing the code page can 
result in value of text and filenames to change. Strictly, the value does not 
change but the visual display of it may – that was always an issue 20-30 years 
ago, but should not be now. 

 

Also be aware that there is a limit within Windows on the length of a file name 
and path to a maximum of 256 characters. This seems to being resolved on the 
latest updates to Win 10. It is also interesting that the filename and path are 
stored as Unicode character sets, which should enable the use of any Unicode 
character in a file name. The IJ is a single character, Unicode 0132 defined as 
LATIN CAPITAL LIGATURE IJ, and Unicode 0133 is the lower case version of it. 
Always with Unicode character sets, you need to be sure that the software 
supports it and that the fonts know how to show it. That should not be an issue 
now, especially since web addresses are now supporting Unicode character naming.

Certainly, I have just created, in Win 7, a file named IJ.txt, containing IJ as 
its text, and created a ZIPped version of it with IZARC.

 

Regards

 

Chris

 

From: LegacyUserGroup [mailto:[email protected]] On 
Behalf Of alex aj
Sent: 24 December 2016 20:00
To: 'Legacy User Group' <[email protected]>
Subject: Re: [LegacyUG] ZZRE: Special characters in surnames.

 

Hi William,

Just backed up Legacy files using Legacy internal backup, all OK.

 

From: LegacyUserGroup [mailto:[email protected]] On 
Behalf Of William Boswell
Sent: Sunday, 25 December 2016 3:46 a.m.
To: 'Legacy User Group'
Subject: [LegacyUG] ZZRE: Special characters in surnames.

 

My guess is using some special characters in Legacy may cause problems when 
backed up to a ZIP file within the software.  I get error messages when I ZIP 
files in Windows then have to go back into the offending file to fix it because 
it has a special character Windows doesn’t like.

 

 

From: LegacyUserGroup [mailto:[email protected]] On 
Behalf Of Evert van Dijken
Sent: Saturday, December 24, 2016 1:09 AM
To: Legacy User Group <[email protected] 
<mailto:[email protected]> >
Subject: Re: [LegacyUG] Special characters in surnames.

 

In Dutch the ij isn't a special character you just type the i and the j. It's a 
long time ago I have seen a Dutch keyboard with a separate letter ij. Most 
Dutch use the English International keyboard.

Evert

 

Op za 24 dec. 2016 om 00:37 schreef alex aj <[email protected] 
<mailto:[email protected]> >

How do I add a special character in a surname.

In Dutch a character can be either a “y” or “ij”.

Entering the “y” is no problem but how do I create the “ij” as a special 
character?

Thanks in advance.

 

Ciao

 

Alex van Crasbeek

10 Lloyd Ave

Mt Albert

AUCKLAND 1025

(   +64 9 846-4967

(   +64 2 11 808 999

*  <mailto:[email protected]> [email protected]

 

--



LegacyUserGroup mailing list

[email protected] <mailto:[email protected]> 

To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com

Archives at:

http://www.mail-archive.com/[email protected]/

-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to