Russians taking over site???
been online all day…’bout an hour ago, all the dates started changing to Cyrillic. Ok. Now when I add information in, it only gives Cyrillic letter. I am in USA, my computer is set to English. I went to the family search pick or language and it is set for English. I went to my settings page on FamilySearch and the entire page is in Cyrillic. It is very difficult to work like this.
Answers
-
0
-
Weird thought: what are the first two characters in the ID of the profile you were on? Or was it doing that for every profile?
I remember a little while ago it came up that some methods of trying to go to a particular profile's "fluff" ("About") page changed the language to Latvian. It turned out that a shortcut in the generated URL caused the first two letters of the profile's ID, LV, to be interpreted as a language code. (The "full" URL has "en" in it, but it also mostly works without that — except when it doesn't.)
Of course, given that PIDs don't use vowels, I don't know what language code it could possibly be seeing that would cause Cyrillic….
3 -
@Julia Szent-Györgyi said "Of course, given that PIDs don't use vowels, I don't know what language code it could possibly be seeing that would cause Cyrillic…."
The two languages supported by FamilySearch that fit the bill would be "bg" (Bulgarian) and "mn" (Mongolian). The other languages that use Cyrillic are "ru" (Russian) and "uk" (Ukrainian), but those language codes contain vowels. I don't believe that any PIDs have been issued in the production site that start with BG or MN, so although this is an interesting theory based on that weird problem, I doubt that it explains what is happening here. But you do have a great memory and it's an interesting possibility to consider. Perhaps there are other identifiers besides PIDs at play here.
1 -
@dar barber Clearing your FamilySearch cookies might help. Another simpler option might be to explicitly pick a language other than English (and Apply it) and then choose English again (and Apply it).
2 -
note this may not even be a FamilySearch issue at all
I think in many cases it is your browser detecting something that makes it think it needs to display in another language,
I have also seen this on occasion.1 -
I already had tried the cookie/cache thing and even changed the language back and forth. Good news is no such problems today! Thanks for y’all’s help and responses!
1