Vera Nagel

I use TMG's most recent program version, TMGv9.05 (!!) on OS Windows 7. As you found all of these special Norwegian characters which you list are part of the ANSI character set which TMG supports. I have a very small test project -for testing means only- which only contains some people/names and place names using these characters. I just exported it to GEDCOM 5.5, character set ANSI and without any exception or issue at all, all of these special Norwegian characters perfectly exported to GEDCOM. As an aside / for the records only: During the development circle of TMGv9 (!!) some previously existing collate sequence issues pertaining to these Norwegian characters were fixed. ################## Next I imported my GEDCOM file into TMGv8.08 (!!) -which is also still installed on one of my machines-, exported that project to GEDCOM 5.5, character set ANSI and again don't run into any issues at all with any of these special Norwegian characters - say everything exported to GEDCOM just fine. Besides that TMG has a bunch of Norwegian users and I never came across any of these users complaining about any GEDCOM export issues regarding these special Norwegian characters. When you inspect a GEDCOM file be sure to use a pure text editor and not any other program which may "interpret" such characters. Regarding the correct export please also see the attached GEDCOM file for reference which I renamed from .ged to .txt Norwegian_characters_to_gedcom_v8.txt

Peter, although I still think that using [D] would be the way to go, you could even today use [Y] for the special situations you have in mind. If your policy is to use [Y] i.e. for dates for which the sentence output should read i.e. "circa 1700" then you could hardcode the word "circa" within your sentence, like However, if today's limited functionality regarding omitted date modifiers for [Y] might ever be changed, you will have to modify your sentences. Just something to keep in mind.

Peter, as you found the [Y] variable has limited functionality only. As TMG Help indicates: a year -and only the pure year without any date modifiers- will be returned for exact, before, after, circa and say dates. Either/or or From/to date modifiers will return "an unknown year". However, as you know, you can easily achieve what you want by simply using the [D] variable instead. ############################### What's the background of your wish, please - anything special which you can't achieve right now?

Hello Mark, you're very welcome. Re: Bevern..... to move here in 2013 was something like "back to the roots" and we really love to be here. Funny to learn that some of your ancestors originate from this place.... isn't the world small??

Mark, you asked whether the tilde sign isn't an "international unique understandable" character. I am afraid, but NO it is not. As Harry pointed out (Thanks, Harry) in Belgium and in the Netherlands a different sign is used to indicate a baptism. In South-Africa for instance a double tilde (wavy equal character) is used instead. The simple tilde sign is primarily used as a symbol for baptisms in German speaking countries only. As you certainly know and for the benefit of others being interested please also see here: http://wiki-de.genealogy.net/Genealogische_Zeichen

Hello Mark, yes, you're correct the ~ (tilde) symbol -used in Germany for baptisms- is not showing up in VCF reports. However, that's not a TMGv9.01 issue, but instead isn't working at least since TMGv7. (I've just verified that.) As to your question how to fix it: you can't fix it yourself, I am afraid, other than to manually correct / modify the created VCF-chart. [i'll report this as a bug in order to get this fixed within any future TMG version.]

In case "Title" was indeed a separate tag what you try to do should most likely be quite easy going. However, since "Title" is only one field/part of the Name-Var tag I for one don't see a way by either using TMG or TMG Utiliy to accomplish your goal. Sorry. On the other hand what's been recorded into the Title field of a Name-Var tag perfectly exports to GEDCOM for me. Run a test GEDCOM by exporting a single person's data where to used the Title field to GEDCOM only. Then open the created GEDCOM file using a text editor (i.e. Notepad, Write) and check whether you find a line: 1 TITL

Hallo Ampel, es ist nicht ueblich hier im Forum nach privaten Email-Adressen oder Kontaktdaten von Mitgliedern zu fragen. Bitte stellen Sie Ihre Frage hier. (It's no common practice in this forum to ask for private email addresses or privat contact data of members. So please ask your question here.)

A question please, Mark: why would you think that non working exclusion markers in the Short Place Field are an issue? You are either able to use place variables within the Short Place Field or you can even explicitly type the exact place information which you want to appear i.e. in reports into the Short Place Field. No so?

Henning, I tried to replicate what you reported using TMG's Sample Project and have to say: sorry, I can't. That is: regardless which of the 3 ways/methods you listed above I use the result is always identical - all selected names are correctly exported to GEDCOM.

See i.e. here: http://www.whollygenes.com/forums201/index.php?showtopic=14178 or http://www.whollygenes.com/forums201/index.php?showtopic=15220

It's an issue caused by a third party program running while TMG's GEDCOM export run. For additional reference please see this topic: http://www.whollygenes.com/forums201/index.php?showtopic=14178

Schön das Alles geklappt hat, Max.

Hallo Max, für die US-Version geht auch dieser Link: http://whollygenes.swmirror.com/tmg8setup.exe oder für die UK-Version analog: http://whollygenes.swmirror.com/tmg8uksetup.exe (TMGv8.08 ist übrigens Montag Nacht unserer Zeit erschienen.)

This issue was fixed in TMG v8.08.