What are the practical consequences of not using Notepad to paste text into the comments/text field of a source cite? Previously, I copied and pasted text directly from Word (which I had copied from a database in Ancestry, for example). My reason for copying into Word first is that I like to replace all hard carriage returns with semicolons so as to take up less space on the page. Is there an impact on how the comments/text appears in reports or when the gedcom is uploaded to other websites? What is the "default" font and type size when pasting from Notepad? Thanks, Barton
On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote: For info only. Memo fields are where ms access store legacy type note fields. They have a very large capacity as opposed to normal fields which are restricted to a maximum of 256 characters. Memo fields can be set up as text only or rtf (richvtext format) which means they would support all word type formatting. Legacy appear to use the former setting hence the need to use a txt editor such as notepad. It is not a user settings but a setting used by legacy designers and programmers. Adrian Sent from my android device. -----Original Message----- From: Barton Lewis <[email protected]> To: [email protected] Cc: [email protected] Sent: Tue, 23 Jun 2015 2:13 AM Subject: RE: [LegacyUG] line breaks in event detail Thank, Adrian. I noticed when I input or paste source text into text/comments that the font is not consistent. I will use Notepad from now on to paste my text from when entering in the text/comments field. Sorry I don’t know what the “memo fields” are. Barton From: [email protected] [mailto:[email protected]] Sent: Monday, June 22, 2015 3:37 AM To: [email protected] Cc: [email protected] Subject: RE: [LegacyUG] line breaks in event detail Legacy/Access store documents as txt but word is not a true text editor it is a docx/rtf editor. Notepad is a true txt editor. Very strange things can happen when posting from non txt to txt fields. It mainly happens vecause various formats/systems have different new line characters. CR/LF, CR, LF, LF, CR where CR is carriage return and LF line feed ascii codes. Sorry technical. Thus always best if having problems to go via notepad. Legacy, access can support RTF in memo fields. Have you looked at this? Adrian Sent from my android device. -----Original Message----- From: Barton Lewis <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Cc: [email protected] <mailto:[email protected]> Sent: Mon, 22 Jun 2015 4:14 AM Subject: RE: [LegacyUG] line breaks in event detail Thanks, Adrian. I really never use Notepad, but your technique of pasting into it and then pasting into Legacy worked great (line breaks were preserved). Is it standard to copy/paste text/comments from Word into Notepad before pasting into Legacy? Thanks again, Barton From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] Sent: Sunday, June 21, 2015 7:08 PM To: [email protected] <mailto:[email protected]> Cc: [email protected] <mailto:[email protected]> Subject: RE: [LegacyUG] line breaks in event detail I believe it may be the pasting action that is causing the problem. If you paste the edited will into notepad does it format as you require. Make sure you have wordwrap turned off in notepad. If not correct in notepad then add returns there and then paste into legacy. Access by the way is the database where Legacy stores its data. Legacy is a front-end to an ms access database. Adrian Sent from my android device. -----Original Message----- From: Barton Lewis <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Sent: Sun, 21 Jun 2015 10:12 PM Subject: RE: [LegacyUG] line breaks in event detail This did not fix it. It is still breaking differently than what is in the document. I don’t know what you mean by “Access database.” This is just a Word document in my C drive. My assumption is that breaks cannot be preserved and that Legacy wraps according to its own limitations/specifications. I wanted to see how it looked in a Descendant Report and have several questions about that. First, when I click on “Publishing Center” and choose “Descendant Book Report” I get a 66 page document for this particular ancestor. When I choose “Descendant Book Report” I get an 88 page document. I am not changing any settings. What are the functional differences between these 2 reports? Also, for the first report, no source detail prints with the source. For the second report, source detail is showing for certain sources (e.g. censuses) but not for the will of my ancestor which I added as an Event. I find no option in the report for including or not including source detail. I am sure it is somewhere – can you tell me where? Thanks, Barton From: Cathy Pinner [mailto:[email protected] <mailto:[email protected]> ] Sent: Saturday, June 20, 2015 11:12 PM To: [email protected] <mailto:[email protected]> Subject: Re: [LegacyUG] line breaks in event detail Use hard line breaks/paragraphs Do a search and replace in your Word document. I think this is a limitation of the Access database where the data is stored. Barton Lewis wrote: I transcribed the will of my ancestor and put soft returns at the end of lines to preserve exactly how the will was written. When I paste the text into the detail for the Event (Will), it is breaking the lines before they end in many cases. This, despite the fact that the lines are already shortened from the regular margins of a Word document due to my soft line breaks. How can I get Legacy not to do this and preserve the line breaks as they occur in the will? Thanks, Barton Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp <http://www.LegacyFamilyTree.com/Etiquette.asp> Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Online technical support: http://support.legacyfamilytree.com <http://support.legacyfamilytree.com> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree <http://www.facebook.com/LegacyFamilyTree> ) and on our blog (http://news.LegacyFamilyTree.com <http://news.LegacyFamilyTree.com> ). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp <http://www.LegacyFamilyTree.com/LegacyLists.asp> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp <http://www.LegacyFamilyTree.com/Etiquette.asp> Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Online technical support: http://support.legacyfamilytree.com <http://support.legacyfamilytree.com> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree <http://www.facebook.com/LegacyFamilyTree> ) and on our blog (http://news.LegacyFamilyTree.com <http://news.LegacyFamilyTree.com> ). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp <http://www.LegacyFamilyTree.com/LegacyLists.asp> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp <http://www.LegacyFamilyTree.com/Etiquette.asp> Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Online technical support: http://support.legacyfamilytree.com <http://support.legacyfamilytree.com> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree <http://www.facebook.com/LegacyFamilyTree> ) and on our blog (http://news.LegacyFamilyTree.com <http://news.LegacyFamilyTree.com> ). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp <http://www.LegacyFamilyTree.com/LegacyLists.asp> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp <http://www.LegacyFamilyTree.com/Etiquette.asp> Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Online technical support: http://support.legacyfamilytree.com <http://support.legacyfamilytree.com> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree <http://www.facebook.com/LegacyFamilyTree> ) and on our blog (http://news.LegacyFamilyTree.com <http://news.LegacyFamilyTree.com> ). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp <http://www.LegacyFamilyTree.com/LegacyLists.asp> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp <http://www.LegacyFamilyTree.com/Etiquette.asp> Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/> Online technical support: http://support.legacyfamilytree.com <http://support.legacyfamilytree.com> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree <http://www.facebook.com/LegacyFamilyTree> ) and on our blog (http://news.LegacyFamilyTree.com <http://news.LegacyFamilyTree.com> ). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp <http://www.LegacyFamilyTree.com/LegacyLists.asp> 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 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 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
