Text translation efforts of the USSF are being handled by the Language Access working group & a wonderful team of over 50 translators. Website & online materials translations are being sent in by the Comm-Media working group and about 5-10 web editors in particular.
Need something translated? This is how it works:
1) Send all requests to Roberto@ussf2010.org. Roberto will introduce them into the marvelous mechanism set up by our tech friends. From there the bad-ass translators will do their thing.
2) Please submit everything as a doc. The pipeline is set up to up/download and forward documents. These can be either .doc or .rtf. Please do not send links to websites. This will require copy/pasting webpages into document form.
3) Please make sure that to include the following information in your email:
a. Word Count (in MS Word this can be found in the Tools drop-down menu).
b. Due date. This is especially important for time-sensitive documents (plz remember that everything is dependant on capacity). For now, we will work under the assumption that the website submissions all need to be done asap. Still, if a certain webpage needs special priority (registration, donations) please make sure to indicate that
c. Title – please make these as obvious as possible (Credit Card Form, Childcare request, etc). For webpages, I suggest using the title that is found on the site map. That will make it easier to verify and/or cross-reference.
d. Who to return it to. I would suggest that docs be returned to the person submitting. That person can then post on the website themselves or forward if necessary. If however, the document should be returned to someone other than the submitter, please let us know (include complete email address). All returned docs will be returned with the suffix – SP. For example, if you submit at doc names Housing Request Form, the one you get back will be names Housing Request FormSP. The suffix will help us keep track of the source and translated docs and will let you know that has been translated.
4) Please, please make sure that you are sending us the final copy of documents. This should be less of a challenge with long-standing static docs and webpages. For works in progress however, please make to have all your wordsmithing, edits, etc, done before sending for translation. It disrupts the workflow to get things set back for editorial changes. Also, there is no guarantee that you will get a quick turnaround on edits.
Note** for Comm-Media members who are translating workshops:
Whenever someone needs something translated it gets posted to http://organize.ussf2010.org/projects/language-justice
When the translator finishes a doc it gets posted back to the pipeline, as well as any other directions given for the particular doc (i.e., please email to fulano). the translator edits the original task and adds the translated doc as an attachment.
Workshops Translations- need to be uploaded to USSF website ASAP: Details for workshops translations process: There are lots of entries in the pipeline that are "#x - short descriptions." the x starts with "1" and will end with "266." each doc has 4 short descriptions. each short description also has the node id for the workshop in english. this means you can pull up the workshop by going to http://organize.ussf2010.org/nodeid and click the Espanol button and edit and enter the short description.
happy to walk people thru this. also very open to people coming up with more efficient ways to doing this. j