Actually, I don't believe I explained my problem well enough. My first preference is to work with one program and one database. Legacy comes very close to allowing that. One very nice lady from the User Group wrote to me privately and helped me phrase my needs better. She also lead me to experiment a bit more. My conclusion is that I need to do four things in Legacy to use two languages:
1. I need the ability to universally change the display field names next to the data entry "boxes": Born, died, etc. Legacy allows this and I can save the default view as 1-English and then change the display field names to the Norwegian equivalents and save that view as 2-Norwegian. Now I can right click on the display field names and just select the language for the display field names. This works universally - the display field names remain in the chosen language even when I change records. This is fast and easy. 2. I need the ability to universally change the display field names for "Husband", "Wife" and "Married". These can be changed to Norwegian for each individual (marriage) record, but not for all at one time. I need to be able to customize these so that I have an English default and a Norwegian default that works universally on the screen view and in reports. Currently, the only two options seem to be changing each and every record - and/or do a find and replace in reports. 3. I need the ability to change generation titles in reports so there is an "English" and a "Norwegian" setup. I am able to change the wording (sentence) structure and save the setup so it is possible to quickly switch back and forth between the English default and the Norwegian setup for almost all text. Report titles can also be customized. But there are some important text items that are coded into Legacy and don't allow for customization. One example is the names for generations: Parents, Grandparents, Great-Grandparents, etc. The only option I find here is to a "find and replace" in each report. 4. I need the ability to use the Norwegian or English spelling for month abbreviations - and to switch back and forth. For example: Oct=Okt, Dec=Des, etc. I need a choice in Legacy that allows the use of the same dating system for the region my PC is setup for as well as the English default. I write notes in both languages so that relatives in the States and older relatives in Norway can each read the same information, but in their native language. Even though they both may speak and understand English and Norwegian, it does not mean that they can read it equally as well. The "dual language" notes help them to understand, perhaps learn a bit and converse more readily with each other. However, the report language (word sentence structure) used for the report itself needs to be in the reader's native language or it is confusing for them. It is as difficult for an American to remember that his great-grandfather is his "oldefar" and his male cousin is his "fetter" while his female cousin is his "kusine" as it his for a Norwegian to remember the other way round. :-)) I do have a chart where they can make the association, but I strive to create reports that are easy for the reader to follow. The problem I have is not that it can't be done. Almost everything can be done in Legacy. It is a fantastic program and very adaptable. It often happens that a family member comes to me with documents, letters, etc and wants to look at Legacy while I enter the data - and then perhaps take an updated report home. The report usually has to be checked and edited (search and replace) to change English titles to their Norwegian equivalent. If Legacy would just allow a bit more flexibility for customization of reports, I would be able to save a lot of time and work. Of course, this flexibility would have to include the ability to switch back to English (default) for all when sending reports to relatives in the States. I am open to any and all suggestions :-)) Sharon in Norway At 21.01.2002 12:32 -0600, John Lancaster wrote: >The major question - on the original query - would be about languages. >Will opening the second file (Norwegian/English) force both files into the >same language? She wanted to be able to work back and forth between two >databases, one in Norwegian, the other in English. > >I don't know the answer to that part, but by opening one database, going >to split view, then opening the second database in one of the views >(View->Split Screen View), she should be able to view both databases and >work back and forth between them. Note that when she splits the screen, >Legacy asks whether she wants to open a second database. > >The options - for that kind of operation - would ideally be the same >between the two database files. > >trapper >John Lancaster, Freelance Business/Tech Writer To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
