I would create a duplicate set of sources, in both languages, with one one of them with [[ ]] around language 1, and the second copy around language 2. This way you can send in their native language, with the brackets around the other version. Then, if they get Legacy for themselves, they can then downloaded either private or public. That gives the reciever a choice, and once set up, you never have to re-edit your docs. Rich in LA CA
--- Erik Pilgaard Vinther <[EMAIL PROTECTED]> wrote: > My primary concern is the Event Notes and Source > Text as the event names and > event sentence definitions are translated > automatically when I switch > language in Legacy (in my case I'm so fortunate that > Legacy supports both > languages in question). > > As you suggest, properly the easiest solution is to > write a separate > paragraph in both languages in the Notes and thus > produce true bilingual > reports, but I'd still prefer single-language > reports. > > As Kathy suggest, the privacy brackets could be used > as part of the > solution. This approach, as I understand it, gives > the possibility of > including or excluding one of languages in the > reports, but the other > language will always be printed. > > Considering the international distribution of Legacy > users, it's strange > that bilingual (or multilingual) reports etc. are > not supported in a better > way by Legacy. > > Regards > Erik > > -----Oprindelig meddelelse----- > Fra: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > På vegne af C.G. Ouimet > Sendt: 26. april 2008 17:53 > Til: LegacyUserGroup@legacyfamilytree.com > Emne: RE: [LegacyUG] Bi-lingual report issue > > The other option is to have bilingual events and > sources with notes in both > languages. I don't worry too much about bilingual > sources but I usually have > bilingual events like Godfather/Parrain ... > > > > C.G. Ouimet > Kingston, ON > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Erik > Pilgaard Vinther > Sent: Saturday, April 26, 2008 09:52 > To: LegacyUserGroup@legacyfamilytree.com > Subject: SV: [LegacyUG] Bi-lingual report issue > > That's certainly an idea. To follow that line I'd > also have to double all > events as I usually add descriptive notes to events. > My initial idea was to > generate two reports, but I don't think is it > possible to have the report > generator select sources and event based on language > (or other criterias for > that matter)? An alternative would be to generate > just one bi-lingual report > containing all double sources and events. > > Erik > DK > > -----Oprindelig meddelelse----- > Fra: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > På vegne af C.G. Ouimet > Sendt: 26. april 2008 15:30 > Til: LegacyUserGroup@legacyfamilytree.com > Emne: RE: [LegacyUG] Bi-lingual report issue > > > I suppose you could double source, one in each of > the two languages. ??? > > > > C.G. Ouimet > Kingston, ON > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Erik > Pilgaard Vinther > Sent: Saturday, April 26, 2008 06:30 > To: LegacyUserGroup@legacyfamilytree.com > Subject: [LegacyUG] Bi-lingual report issue > > Hi, > > I have the need of generation Legacy reports and > books in at least two > languages, depending on the nationality of the > people I want to address. I > expect many other Legacy users must have the same > needs. > > By changing the Language in Legacy itself and/or > changing the Report > Language, I can easily change the standard wording > and standard phrases in > reports and books, but all descriptions, notes and > transcripts are naturally > printed in the language they are entered. I don't > expect Legacy to > automatically translate these texts for me, but I'm > looking for some advice > on a practical way of handling this bi-lingual > problem. I could of course > maintain two Legacy files, but that's not an > attractive solution to me. > > Any comments, ideas and advice are very welcome. > > Thanks > Erik > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > === message truncated === Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
