Marion, I have used Legacy from the year dot (ie. from the first public release). I have never had problems having spaces in my file names in my .jpg files. I have used Legacy with Windows, currently on Win 8.1 I use Legacy 7.5 (though I have Legacy 8 installed I have no problem with filen ames with spaces. :) Margaret
On 13 August 2015 at 14:29, marion wimsett <[email protected]> wrote: > Hi Bob, > > Every single one of the paths and file names have spaces in them - both in > the ones that are linking and the ones that are not. On my own tree I have > a similar format in the way of spaces and there is no problem, so I don't > feel it will be that but I will change things bit by bit first - the type > of extension then change the file name (leaving spaces in) and at the end > will remove spaces if needs be but I will wait for Brian first, he has done > a lot of work on this to date. Thank you for the suggestion, will keep it > in mind. > > Regards, > > Marion > > On 13 August 2015 at 11:52, BobsTree2-Gmail <[email protected]> wrote: > >> Some versions of Windows used to have problems with "space" characters in >> paths and filenames. This is easily fixed by enclosing the entire path in >> "double quotes". Does that help? >> >> Bob Hansen >> >> >> On Aug 12, 2015, at 23:37, marion wimsett <[email protected]> wrote: >> >> Brian, >> >> I decided to try one now as I might forget tonight (grey cells sleep >> early!). >> First one I tried is a .PNG - which is allowable in the list. >> It doesn't link it, doesn't do anything. Just blank with no message (I am >> linking it myself as the Media Relinker said it couldn't find it. >> Dimensions are 941 x 1121 pixels. Bit depth 24. Size 478 kb >> Location Is : \\NASWIMSETT\Family Tree AW\Stephen Edward Wimsett >> (Wilmshurst) & Sarah Cushman\Stephen arrival notice.png >> Before I change anything with this (file name first and then change it to >> a jpg) is there anything you can see that is wrong? >> >> Thank you again, >> >> Marion >> >> On 13 August 2015 at 10:36, marion wimsett <[email protected]> wrote: >> >>> Thank you Brian for keeping an eye on this one. I have no idea what the >>> problem would have been, I gave up at one point as it was getting too hard >>> to go in and change the file name and then relink but I will have another >>> look at it tonight and see how many are "missing" and do a trial on one or >>> two again and let you know. If it wasn't the length of the file name there >>> must be something in the file name itself. >>> I will let you know if there are problems with the linking on the file >>> later today or tomorrow. >>> >>> Again thank you for your investigation - any information helps. >>> >>> Marion >>> >>> On 12 August 2015 at 00:22, Brian/Support <[email protected]> >>> wrote: >>> >>>> I have tested a long path/filename string in Legacy. I created a long >>>> path with nested folders until windows would not let me add another >>>> because filenames would not fit into the limit of path lengths. I then >>>> placed a picture in the next-to-last folder in that path. I had >>>> previously linked the file to a person in Legacy 8.0. I used the media >>>> relinker to rebuild to link to the picture and did not get any >>>> unsupported format message. I then added characters to the file name >>>> until Windows would not accept any more. In this way I think I hit the >>>> windows limit on path/filename length. This time, since the file name >>>> was different I told the legacy I would look for the file myself. I >>>> browsed to the long folder/filename and linked it without problem. >>>> >>>> I did not count the characters in the path but I am satisfied that >>>> Legacy can use the longest path allowed by Windows and will not give any >>>> "unsupported format" message. >>>> >>>> Brian >>>> Customer Support >>>> Millennia Corporation >>>> [email protected] >>>> http://www.LegacyFamilyTree.com >>>> >>>> On 25/06/2015 11:41 AM, Brian L. Lightfoot wrote: >>>> > Yeah, I surmised as much but then the idea of creating a folder for >>>> every event and for every person just doesn't sit well with me. But once >>>> again, to each their own. And even with the addition characters in the NAS >>>> drive path, I think the OP is still far from the 255 characters. I just >>>> gotta find time to test this out but I'm stuck painting a house for the >>>> next 3 days. >>>> > >>>> > Brian in CA >>>> >>> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
