Tim name explanation - passport Jan 2023
documentlook: clean
style: letter1 pages render unknown
Text layer
250 words
250 words on 1 pages, from pdftotext. This is what search finds in the file.
Show the text
Explanation of the spelling of our son's name January 5, 2023 Submitted with Form DS-11 for Timofey Pavlovich Zaretsky, born April 9, 2013 in Yekaterinburg, Russia. We are the applicant's parents. Our son's name is written in different ways in the documents we are submitting. They all refer to one child. In Russian his name is Зарецкий Тимофей Павлович. Document Name as written Russian birth certificate III-АИ No. 714283 Зарецкий Тимофей Павлович Certified translation of the birth certificate, December 20, 2022 Zaretsky Timofey Pavlovich Russian passport 71 5820934, issued 2014 ZARETCKII TIMOFEI H-4 visa, 2014, and Permanent Resident Card, 2017 ZARETCKII, TIMOFEI Social Security card, 2017 TIMOFEI ZARETCKII Russian passport 53 4471908, issued 2019 ZARETSKII TIMOFEI The difference comes from the rules used to put Russian letters into Latin letters, which were changed between his two Russian passports. His American documents copied the spelling of the passport he entered the United States with in 2014. We were naturalized on November 18, 2022, and the court changed our names to Pavel Igorevich Zaretsky and Yulia Andreevna Zaretskaya. Our certificates of naturalization show the old and the new spellings. Timofey became a citizen with us on that day. We ask that his passport be issued in the name TIMOFEY PAVLOVICH ZARETSKY, as in the certified translation of his birth certificate, so that his surname is spelled the same way as his father's. P. Zaretsky Y. Zaretskaya Pavel I. Zaretsky and Yulia A. Zaretskaya, 8-17 Larkmoor Terrace, Fair Lawn, NJ 07410, (201) 555-0143
Comments
0
Comments are added in the local viewer; this copy is read-only.
Values from records
0render unknown
The record values this file is made from: the ones its text names with {{record.field}}, and the fields its template reads. A value here is in the file's source; whether it is readable depends on the look.
None: everything on it is written in attachments.yaml.
The values at render time were not recorded: the file was rendered before files/rendered.json existed. Rendering it again records them.