|
CLICK HERE TO ASK A QUESTION!
|
|
Answers are contained in the Comments. Though you can ask questions in the blogs, asking them here has some important advantages. L10NCafe members sign up to receive notifications on questions asked here and so your questions are pushed to the appropriate people. Also, when someone answers your question here, you receive an email with their answer.
Use the 'Email this Post' link to send the post to someone or to
report
inappropriate content like advertisments. To report
inappropriate content, send the email to support@L10NCafe.com. |
It is beginning to take significant time to tag the content we syndicate on L10NCafe.com. Moreover, I'm not sure we catching everything by doing it manually. Now that we have a good set of industry terms I'm thinking it would be more efficient to get a tool to help. I know there are expensive options. Is there a free way to aim a list of topics at something like JEdit to get a list of tags that apply to a piece of content? It would need to be able to find forms of words as well... Hi all
I am searching for the correct term used in a USA-located hospital's CSSD (Central Sterile Supply Department).
After loading a sterilizer and sterilizing the sets/trays and instruments, and after completing the sterilization cycle, the sterilizer's content is checked. If everything is OK, then the responsible CSSD staff member will release or commit the load. That's the question: What term is more common, release or commit?
Up to now we have used the term release in our software, for example load release, release an entire load, release protocol, and so on. Now (after more than five years) our partner company in the USA tells us that the CSSD staff has problems understanding the term release, we should use commit instead.
What is your opinion? What term should we use?
Thanks in advance
Andreas Ternes I got this link (http://www.lukew.com/ff/entry.asp?1071) earlier today from the Information Design maillist (http://www.informationdesign.org/). It's a useful reference for touch gestures on several platforms. The guide is offered as:
1) an overview of the core gestures used for most touch commands
2) how to utilize these gestures to support major user actions
3) visual representations of each gesture to use in design documentation and deliverables
4) an outline of how popular software platforms support core touch gestures.
With specific reference to #3, has anybody done any work on the i18n/l10n of such platforms? Historically, I would always have been wary of hand gestures in documentation as a rich source of potential cultural misinterpretation. But, what to do when they play an an integral role in the use of the device? In theory, a tool like Acrolinx can help an author use strings that have a TM match in languages. But given frequent updates of source strings in an Agile-like development environment, it's likely there will be a build up of various versions (based on multiple revisions) of the same string -- aired with translationsof those strings. Acrolinx is going to look for the closest match to what the author wrote, not the closest match to what the author should have written.
Because TMs don't inherently do version control it leaves you with a possibility like this: An author writes a sentence. Acrolinx searches the TM and finds a fuzzy match to a similar source string. The author accepts the Acrolinx suggestion. What's unknown to the author is that the Acrolinx offering was translated in an earlier version of the product but was subsequently revised/updated because was ultimately inaccurate. But because Acrolinx serves up the string as "in the TM and already translated, guaranteed to save the company $, the writer accepts the English string without hesitation.
Acrolinx has just facilitated the perpetuation of good translation of bad source.
So how do you manage your TMs to avoid a situation like this? |
|
|
|
|