Other than the Geolocator, I suppose it serves no other function other than to keep all us Yanks on the same page as far as location descriptions are concerned. But while that may work for nearly all of the US in the modern world, it still runs into problems with century old locations in the US. I've got some locations and census images from places as weird as the "Dakota Territory" and that's before there were any states known as North or South Dakota much less any counties within those states.
What I'd like to see is a user option to set up a more specific format for locations. This would make many users in the US happy as well as our cousins across the pond in the UK. We have options to set up different day/month/year formats so why not an option for locations? Maybe I'm not fully thinking this out and this could potentially expose more problems than just putting up with the annoyance of the extra commas. Brian in CA -----Original Message----- From: Ron Ferguson [mailto:[email protected]] Sent: Monday, December 03, 2012 1:56 PM To: [email protected] Subject: Re: [LegacyUG] Event sentences Why, o why!!! Surely the only reason for the comma/space is so that a location can be read in the Geolocator. Well, a TBD will ensure that it won't be. And I'm sure that when it is on the web or in a report/book that the whole world will know what it means. I never use the four field convention anyhow - no good in the UK. --- Ron Ferguson http://www.fergys.co.uk/ GOONS #5307 "Pat Hickin" <[email protected]> wrote: >I like that idea too. > >Pat > >On Mon, Dec 3, 2012 at 4:23 PM, Louise <[email protected]> wrote: > >> I like the idea of using TBD as a possible way to mark "investigate >> further". Any drawbacks you've found? >> >> >> On 3 December 2012 10:16, [email protected] <[email protected]>wrote: >> >>> Location search and replace: >>> Open location master and edit the location. It will take effect >>> everywhere it is used. Use a space char before the first comma for >>> the missing city. Assume ypu are using city,county,state,country format. >>> >>> Or you use TBD (to be determined) for missing values, might look >>> better than a comma and is a visual todo item, get the value >>> >>> Sent from my phone, please excuse typos >>> >>> Bob >>> >>> Pat Hickin <[email protected]> wrote: >>> >>> >A question: >>> > >>> >In my placenames, I frequently use a comma when I don't know the >>> >precise location, e.g. >>> >", Surrey Co., VA, USA". >>> > >>> >When I'm creating a report is there any way to get Legacy to drop >>> >the >>> comma? >>> > >>> >I could make the *short* location name read "Surrey Co., VA". >>> > >>> >But that's a lot of trouble! Unless there's some way to do a >>> >Search & Replace that I don't know about. >>> > >>> >Thanks for your ideas, >>> >Pat >>> > >>> 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://www.LegacyFamilyTree.com/Help.asp 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
