* @@ Bug

[Ron Melby]

The random changing of @S1900@ and NigelFarage@Brexit.com to @@S1900@@ and NigelFarage@@Brexit.com appears to have been occurring for some time.

I see a fix in plugins to run. one does not remember to run it all the time. Is there a control framework somewhere that allows event callbacks something like
On {FILE Open} Then {Run Plug-in Fix}
or
On {File Close) Then {Run Plug-in Fix}

[Jane]

When storing @ in a Gedcom file it should be doubled when storing. Except where it is a tag which is stored against a valid Gedcom line so I would expect if looking in the gedcom file to see @@ in an email address.

Without seeing the context for the source id I suspect it's not on a valid gedcom tag for a source record line.

The Ancient @@ bug where at signs were doubled over and over again does not occur so the only time you normally see them in the program is when invalid gedcom has been converted to a valid tag.

[tatewise]

Changing @S1900@ to @@S1900@@ only occurs when preceding Tag is invalid GEDCOM as far as FH is concerned.

Changing NigelFarage@Brexit.com to NigelFarage@@Brexit.com is standard GEDCOM to avoid any possible confusion with @S1900@.
i.e. @S1900@ represents a link pointer to record id S1900.
@@S1900@@ represents the plain text @S1900@.
But some products do not honour that GEDCOM requirement.

Currently there is no way to run Plugins automatically on File Open or File Close.

The problems with invalid GEDCOM resulting in @@S1900@@ cannot only sometimes be fixed with a Plugin, but it only need be run once, not every time you open a valid FH Gedcom file.
The problems with different programs handling @@ in different ways is resolved by the Export Gedcom File Plugin, but you only use that when preparing to export to another product.