Jennifer #1 and #2 - there is a Legacy User Group in greater Melbourne - a part of VicGUM. I should have journeyed east to their meetings but haven't; now that GSV has moved location to another part of Melbourne CBD, I'm not sure if VicGUM can make use of a room for meetings in the city.
http://www.vicgum.asn.au/ Ian Thomas Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Jennifer Hardess Sent: Friday, 21 April 2017 12:21 PM To: Legacy User Group <[email protected]> Subject: Re: [LegacyUG] Emdash rendered '97 I also have this problem with Trove. It's helpful to read other suggestions & I agree with Ian that it is a good way to have to read the article thoroughly, in- stead of just scanning as we all do (but it is still annoying). I notice that there are a couple of Melbournites replying to these emails these days. There used to be a Legacy User group operating in Melbourne; it was good to meet other users and discuss "issues" especially for us computer illiterates. I haven't braved upgrading to 9 yet. Jennifer Montrose, Victoria, Australia Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Jennifer Crockett<mailto:[email protected]> Sent: Friday, 21 April 2017 11:25 AM To: 'Legacy User Group'<mailto:[email protected]> Subject: Re: [LegacyUG] Emdash rendered '97 Trove is where all my notes with Emdash come from. When correcting the OCR there is a place at the top of the page where you can insert a symbol and Emdash is top of the list. I have been inserting the symbol in place of a simple dash if an Emdash is shown on the image of the article. I then do as you do and copy the article into a .txt file (I use Notepad++) and tidy it up before copying and pasting into Legacy. In Legacy v 7.5 there was no problem with the Emdash. As it looks like this is an ongoing problem in Legacy post v 7.5, I will need to go and replace all those '97 instances with a simple dash (if I can find them all) , and remember to just use a dash in the .txt file from Trove before pasting into Legacy. Jennifer Ringwood North, Victoria, Australia From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Ian Thomas Sent: Friday, 21 April 2017 10:47 AM To: Legacy User Group <[email protected]<mailto:[email protected]>> Subject: Re: [LegacyUG] Emdash rendered '97 This is probably peripheral to the discussion on Emdash / Endash and Legacy FT's clean-up abilities. One source of information that I use a lot is from digitized (Australian) newspapers, at Trove<http://trove.nla.gov.au/newspaper/>. The OCR text usually requires correction (human recognition) and that includes changing Emdash to hyphen, inserting spaces, concatenating hyphenated words, etc etc. But a simple Copy then Paste into a Notes field in Legacy isn't an option for me. Stripping the HTML doesn't improve the situation - but that's fine by me. Routinely, I paste into a plain-text editor set up in a simple Encoding (for PC of course) - using an Encoding like Unicode BOM is asking for trouble, I have found. Then, I create accurate text but sometimes leave it in newspaper column format - or, make it more readable in continuous-text paragraphs. This process is much lengthier than just changing a few single-symbol bits like an Emdash. But I have seen the 'conversion' by Legacy to '97' which is why I adopted the method described. I find it has a benefit - I read more attentively, and understand better. Some of the articles - and even common-place advertisements - are fascinating. >From Trove, an image or PDF file at a selectable range of resolutions can be >saved to disk, so the scanned source imagery is available and can be attached >to Legacy as a media file, if warranted. Ian Thomas Albert Park, Victoria 3206 Australia
-- 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]/
