Spanish/French Items in Roosevelt Campaign Need Transcribing or Review

Thanks!  I will look at the French, and depending on complexity may be able to do some.

Note that accents are quite easy to add without a specialized keyboard:

• For Mac/iOS:  hold down the key for the letter in question, and it will bring up all accents possible for that letter.

• For Windows: There are keyboard shortcuts to add accents.  The most common ones are easily learned.
• https://support.microsoft.com/en-us/office/keyboard-shortcuts-to-add-language-accent-marks-in-word-3801b103-6a8d-42a5-b8…

I would encourage everyone to add accents and diacritics on first transcription, as that avoids the possibility that someone else may approve the document without them. They are not optional and can change meaning of words entirely.

Hi Diane- I came across this newspaper article in French. I don't know if you would be willing to transcribe it.

Thanks,

Henry

https://crowd.loc.gov/campaigns/rough-rider-bull-moose-theodore-roosevelt/5-july-16-1904-sept-23-1905-president-in-his-own-right/mss382990049/mss382990049-252/

Laurie: Thanks! This could be an issue with the site. One thing that struck me as very odd was that minor errors like the misspelling of “département” in the header and extra spaces in hyphenated words had been reinstated exactly as previously.

I saved often over the hour I worked on this, so I’m very surprised it would revert to something several dozen saves previously.

How does one report a page?

I have often had the experience you mention about faux messages saying someone else is working on it and I believe it can sometimes result from accessing the document from multiple devices.

Hi all…

the following page in the document list has the rest of the article. It is transcribed incorrectly but locked as complete.

Maybe it could be reopened for editing???

Ethan: thanks for the excellent deductions!

I believe this page is from the Le Matin issue of November 6,1904 (with its reference to Vermont voting the week past), but could not find a copy of it online anywhere to validate the text. November 5, yes. November 7, yes. November 6, no.

If you email crowd@loc.gov you can report a page or at the bottom of any document, go to Questions?, then Technical Issue? and report the page.

Thanks, Diane, for pointing out where the rest of the article is.

Ethan

Thanks, Ms. Algee.

(And Thanks to Diane (I saw the post in my email inbox, but not here) for your nice words about my deductions and for your trying to pin down which issue of Le Matin the article came from. )

I plan to complete the transcription (of this page; the question of whether the rest of the article (following page) will be re-opened is still unanswered) today.

Ethan.

PS (about 12:10 PM Eastern Time) : I have completed the transcription (and added a cedilla to the "c" in "façon" 2 lines after the line which begins "près"). I will present the transcription for review.

E.

Dear Henry (and everyone else here),

It seems that there is material in this subset of the Theodore Roosevelt Papers in at least 1 language not often taught in the United States: when I clicked (out of curiosity) "asking" the system to suggest another page to transcribe after I submitted the article page for Review, it brought me to page 530 -- which seems to contain (handwritten) text in a Scandinavian language (the writer is identified in brackets as having the family name of "HANSEN").

(Someone tried to transcribe the first few lines of the text and (it seems) gave up; I wouldn't really want to try to decipher it myself -- as I would be too uncertain of how to read the letters in it.)

(Note to Library of Congress staff looking in: it might be difficult getting a transcriber to finish work on that text in page 530.)

Ethan.

Thanks for flagging this page, Ethan. We do occasionally see that some non-English pages sit unfinished for a while because the we don't seem to have any volunteers who can transcribe the specific language or dialect. We've occasionally reached out to some of the amazing Library of Congress language specialists for help. Since the library collects internationally, we have staff do acquisitions and/or cataloging for nearly every language. Though it's really outside of their job descriptions, they've been kind enough to help us transcribe some small sections. We could eventually consider doing that for this page as well, though we might try tweeting and sharing it with the public in other targeted ways first.

You can read about one German language specialist who helped us with archaic German script in this blogpost: https://blogs.loc.gov/international-collections/2020/05/unlocking-the-secrets-of-german-handwritten-documents/

I have reopened the following page as well (https://crowd.loc.gov/campaigns/rough-rider-bull-moose-theodore-roosevelt/5-july-16-1904-sept-23-1905-president-in-his-o… ). 

For future reference, the best way to get a completed page opened is sending an email to crowd@loc.gov with the URL(s). Sometimes it can be a challenge to keep up with the lively chatter and branches of comments here in History Hub!

Yes, Henry's instructions are correct!  Just shoot us an email directly or through the Questions button at the bottom of the page.

We have had several people report page reservation or transcription loss in the last few months, but have been unable to figure out what's going on. I think I will also start a new History Hub thread as a place where people can share about these issues. The more information we have about exactly what you did, the browser and type of device you were using, what page it was, and when, the more likely it is we can determine the problem and find a solution!

Yes, Henry's instructions are correct!  Just shoot us an email directly or through the Questions button at the bottom of the page.

We have had several people report page reservation or transcription loss in the last few months, but have been unable to figure out what's going on. I think I will also start a new History Hub thread as a place where people can share about these issues. The more information we have about exactly what you did, the browser and type of device you were using, what page it was, and when, the more likely it is we can determine the problem and find a solution!