Options for Family Map

Data set Case-sensible name for the data set, uploaded to the tyoma.com server. It is a good practice to restrict names to alpha-numeric characters, including underscore "_", otherwise, good results cannot be guarantied. No warning is given when you misspell the data set name, but the default data set "tyoma" is loaded.
Person ID The initial person from the data set above. Normally, you are getting both data set and person Id from the family map author. I would say, those two parameters are mandatory fields of sorts. In case you only know the data set name, setting Id to 1 is a good initial guess. You can also ask the program to select some Person Id from the data set.
The field must be an integer, with one exception: the old GEDCOM style indicator of a person's ID in the format @I123@ is also accepted.
Language The language of the Family Map. The default selection in most cases gives English for the labels and family relations calculations. If you can read Cyrillic alphabet and have, for example, some Russian roots, you can switch into the Russian mode. For the data set created with one of the Cyrillic encodings, the default mode is Russian, so you can set language back to English.
Legacy mode The great majority of the modern browsers are capable of displaying formatted XML web pages. In case the page behaves strange, buttons don't work, nothing or everything is displayed, etc., you can try to turn the legacy mode on. In the legacy mode, the server makes all operations on its side, sending the final file in html format to the browser. Although this mode is much more conventional, it is much less convenient, because the size of the html file can be as much as 50(!) larger compare to xml file. For large data sets, like the default "tyoma" and modem connections, the loading of the initial map would be rather slow in legacy mode and visitor would have no fun on reloading all the data again upon changing the key person.
Legacy mode is automatically turned on for Internet Explorer 4 and 5, although some of the Internet Explorer 5.5 are capable of operating in the xml mode.
Encoding Encoding of the data set. If it is Cyrillic (ISO or Windows) and is clearly specified in the data set ("CHAR" field), the auto encoding takes the value from the data set. If encoding is unknown or undefined in the data set, then the program tries to guess it, setting it to Windows Cyrillic, if an unusually high percentage of the characters in the names come from the upper half of the ASCII table, and to the Latin 1 otherwise. You can always force the program to use a particular encoding.
The list of possible encodings actually lacks several important entries:
  • ansel - The standard encoding for GEDCOM files. Real legacy encoding, not supported by Java standards. Yet to be done.
  • UTF - The standard encoding for the modern multi-language programs. Will be added soon.
  • DOS, Mac - IIt is always possible to get away with Windows encoding...
Browser The two categories of supported browsers are Microsoft Internet Explorer, (including old versions) and Gecko-based browsers: Firefox, Mozilla, Netscape 6 and up. For the other browsers you can try either option, switching to legacy mode. For example, Safari looks OK in legacy mode for Firefox.