代胜的共享空间

ounded in 2005, Transn has the honor to be the strongest multilingual information processing service provider as well as a leading professional translation and localization company in China.

Transn has been committed to growing into customers’ Virtual Language/Localization Department (VLD), helping global top enterprises with fast entry into the Chinese market and providing competitive products and services in conformity with China’s actual conditions. Besides, Transn also provides Chinese customers with multilingual channels for globalization.

With the boast of rich language expert resources, a strong capacity of engineering technology and professional experience in project management, Transn is capable of providing customers in IT, manufacturing, automobile, finance and other fields with a wide range of products and services including professional translation, software localization, software localization test, translation and localization trust, multilingual aided translation platforms and multilingual information solutions.

Transn has an integrated system with independent intellectual property right consisting of Translation Process Management (TPM), Transn Computer Aided Translation (TCAT) and Web Terms Management (WTM). This system can ensure a seamless connection between customers’ existing systems and our lingual services, and enable customers to directly view the overall progress of projects, the status of all procedures and intervention process management. Meanwhile, the system provides customer service groups with Internet-based functions like collaborating translation, synchronous proofreading, online exchange and project management so as to considerably improve project quality, shorten delivery period and reduce customers’ costs.

Headquartered in the central business district (CBD) in Beijing with over 400 employees, Transn has established branches in Wuhan, Shanghai, Shandong, Hong Kong and Singapore, and developed a number of linguistic teams in major European and Asian markets. Transn currently manages over 30,000 translators, interpreters and suppliers

引用

LCJ 完成法语、德语和意大利语的 Microsoft Office 2007 本地化项目

LCJ Completes Localization of 2007 Microsoft Office into French, German and Italian

High volumes and tight deadlines mastered easily by LCJ’s proven methodologies and processes

Dortmund, Germany – February 14, 2007 – LCJ EEIG, one of only four Microsoft Premier Vendors performing product localization for Microsoft Corporation, today announced that it has completed the localization into French, German and Italian of the 2007 Microsoft Office system in readiness for its global release in early 2007. This achievement demonstrates LCJ’s success in conducting high-profile, large-scale international localization projects.

Matthias Caesar, Managing Director at LCJ, said, “We are delighted to have had this prestigious opportunity. The 2007 Microsoft Office system, the latest release of the well known desktop productivity software, and its localization is one of the most visible projects of its kind.”

LCJ’s commitment to the project included 23 full time internal resources for 13 months, 10 additional internal resources available as required over the same period and up to 161 translators and subcontractors at any one time.

“The key challenge was completing the high volume of work within the required timeline,” said Igor Kupecek, Global Office Project Manager at LCJ. “This demanded meticulous planning that choreographed targeted recruitment and training, to guarantee the availability of appropriately skilled staff, with effective project management, to ensure successful execution.”

Kupecek summarized, “We succeeded because of the following factors: our early collaboration with Microsoft to prepare the project, the experience and expertise of our internal teams, and the seamless support of our flexible methodologies and processes that are specifically designed for large projects. All human and system resources worked together to deliver an efficient, streamlined project.”

About LCJ

LCJ Group, Europe’s largest independent localization solution provider, is a partnership between leading vendors Locatech GmbH (Germany), CrossGap srl (Italy), Jonckers Translation and Engineering sa (Belgium), and Logoscript S.L. (Spain). Founded in 1999, LCJ employs more than 200 employees. Their combined linguistic, project management and technical expertise has positioned the company as one of the foremost localization service providers in the world, capable of delivering turnkey localization solutions for software products, websites, and e-commerce applications, whatever the language, technical complexity and size of the project. For more information please visit www.lcj-eeig.com

引用

Robohelp 文件的本地化 - 基础篇

Localizing Robohelp Files - The Basics

We get a lot of search engine queries like "localize Robohelp file" and "translate help project." I'm pretty sure that most of them come from technical writers who have used Robohelp to create help projects (Compiled HTML Help Format), and who have suddenly received the assignment to get the projects localized.
The short answer
Find a localization company who can demonstrate to your satisfaction that it has done this before, and hand off the entire English version of your project - .hpj, .hhc, .hhk, .htm/.html and, of course, the .chm. Then go back to your regularly scheduled crisis. You should give the final version a quick smoke test before releasing it, for your own edification as well as to see whether anything is conspicuously missing or wrong.
The medium answer
Maybe you don't have the inclination or budget to have this done professionally, and you want to localize the CHM in house. Or perhaps you're the in-country partner of a company whose product needs localizing, and you've convinced yourself that it cannot be that much harder than translating a text file, so why not try it?
You're partially right: it's not impossible. In fact, it's even possible to decompile all of the HTML pages out of the binary CHM and start work from there. But your best bet is to obtain the entire help project mentioned above and then use translation memory software to simplify the process. Once you've finished translating, you'll need to compile the localized CHM using Robohelp or another help-authoring product (even hhc.exe).
The long answer
This is the medium answer with a bit more detail and several warnings.

• There may be a way to translate inside the compiled help file, but I wouldn't trust it. Fundamentally, it's necessary to translate all of the HTML pages, then recompile the CHM; thus, it requires translation talent and some light engineering talent. If you don't have either one, then stop and go back to The Short Answer.
• hhc.exe is the Microsoft HTML Help compiler that comes with Windows. It's part of the HTML Help Workshop freely available from Microsoft. This workshop is not an authoring environment like Robohelp, but it offers the engineering muscle to create a CHM once you have created all of the HTML content. If you have to localize a CHM without recourse to the original project, you can use hhc.exe to decompile all of the HTML pages out of the CHM.
• Robohelp combines an authoring environment for creating the HTML pages and the hooks to the HTML Help compiler. As such, it is the one-stop shopping solution for creating a CHM. However, it is known to introduce formatting and features that confuse the standard compiler, such that some Robohelp projects need to be compiled in Robohelp.
• Robohelp was developed by BlueSky Software, which morphed into eHelp, which was acquired by Macromedia, which Adobe bought. Along the way it made some decisions about Asian languages that resulted in the need to compile Asian language projects with the Asian language version of Robohelp. This non-international approach was complicated by the fact that not all English versions of Robohelp were available for Asian languages. Perhaps Adobe has dealt with this by now, but if you're still authoring in early versions, be prepared for your localization vendor to tell you that it needs to use an even earlier Asian- language version.
• Because the hierarchical table of contents is not HTML, you may find that you need to assign to it a different encoding from that of the HTML pages for everything to show up properly in the localized CHM, especially in double-byte languages.
• The main value in a CHM lies in the links from one page to another. In a complex project, these links can get quite long. Translators should stay away from them, and the best way to accomplish that is with translation memory software such as Déjà Vu, SDL Trados, across or Wordfast. These tools insulate tags and other untouchable elements from even novice translators.

We've marveled at how many search engine queries there are about localizing these projects, and we think that Robohelp and the other authoring environments have done a poor job explaining what's involved.
If you liked this article have a look at "Localizing Robohelp Projects."

Labels: CHM localization, documentation localization, help localization, HTML localization, localization engineering, localization tools, RoboHelp localization, technical writers, translation Robohelp

posted by John White, Localization Guy at 18:03

 

URL: http://www.1-for-all.com/l10n_blog/2008/05/localizing-robohelp-files-basics.html

引用

翻译专业化道路的几点思考

Some thoughts on translation specializations

http://thoughtsontranslation.com/2008/07/16/some-thoughts-on-translation-specializations/

July 16, 2008 by Corinne McKay

One of the issues with which beginning translators most frequently struggle is specializing: what to specialize in, how to decide what to specialize in, what the most/least requested specializations are, how important it is to specialize, etc. While there aren’t too many hard and fast rules when it comes to translation specializations, here are a few general guidelines.

• The larger the language, the greater the need to specialize. Here in the U.S., translators in smaller-diffusion languages like Finnish or Thai often don’t need to specialize at all, because there are so few of them that specializing would be impractical. On the other hand, French, German and Spanish translators must specialize in order to find a niche in a rather large market.
• Pick a specialization that you enjoy researching. This advice comes from Jill Sommer, who teaches in the graduate translation program at Kent State, and I agree completely. Think about picking up a news magazine; which section are you most likely to read first? Business? Finance? Health? Technology? Any area that you enjoy learning more about is a potential specialization.
• Realize that for better or for worse, many translators are self-taught in their specializations. Many people seem daunted by the idea of specializing, fearing that they need to go back to school and get a nursing degree to be a medical translator, or become a paralegal to be a legal translator. Certainly, many translators do have a strong background in their areas of specialization, and if you come into the field as a former financial analyst, physician or attorney, you are likely to command a higher income than a translator who learned that terminology on the job. But if you’re entering the market with a general liberal arts background, don’t be intimidated by the idea of selecting a specialization.
• Oddly enough, specialization can lead to more work rather than less, as clients think of you as the go-to person for documents in your area of expertise. Also, as several people have commented on this blog, one way to make more money as a freelance translator is to work faster, and the better you know the terminology of the documents you work on, the faster you can translate.
• While it’s theoretically possible to specialize in almost anything (I’ve met translators specializing in horses, philately, and fisheries, to name a few), you’ll probably want to pick an area that you know is in demand. A few such domains would be medicine, medical instrumentation, pharmaceuticals, law, finance, automotive, computer hardware and software, engineering, environmental science, patents, advertising, technology, the hard sciences and general business documents.
• Consider delving deeper into a specialization that you enjoy. A great way to position yourself ahead of your competition is to take courses in the terminology of your specialization, or to spend a day at a place of business or an industrial facility that works in your specialization, then let your clients know about it!

引用

文档本地化开始前的准备工作

Getting your Documentation Ready for Localization

http://www.1-for-all.com/l10n_blog/2008/07/getting-your-documentation-ready-for.html

Have you had to prepare your documentation for localization yet? My experience is that in almost all companies, writers have far too many other oppressive concerns gnawing at them to think about writing for localization.
A few days ago an industry colleague sent me a message asking, "Do you have experience making recommendations for how documentation can be authored for localization? I am looking to make our doc  process more efficient to reduce costs."
I replied that, given his stature and tenure in the industry, there was not likely anything I could suggest that he hadn't already considered. Nevertheless, I sent him a list of ideas, in increasing order of difficulty:

1. Make sure all the writers' computers are plugged in. (A bit of ironic humor I could not resist.)
2. Is it easy to get from the authoring tool(s) into TM, and back out into publishable format? This is my current headache with an API reference manual we localize for one client, because moving from source language to the translator tools and back to target format is a colossal headache. If you have similar problems, devote some cycles at the format-layer, even if it means writing an interface between your content management system and the translation tool.
3. There are "authoring memory" tools that can suggest and re-use already-xlated source text, so that writers don't say nearly the same thing multiple times and incur unnecessary TM penalties. Sajan has one, and SDLX contains one as well. I've never used either one, but I can imagine that success with the tools would require somebody with the documentation-familiarity of a technical writer and the global consciousness of a localization manager. Like you.
4. I've presented on localization to a variety of audiences, and have consistently found tech writers to be the most interested in it, vastly more so than developers. When you show writers how the TM tools work, tell them how they can save money and re-use content, and let them know that you care about the impact of their work on international products, they will smell the coffee and engage. This takes a bit of evangelism, but it's worth it if the writers change their own practices.
5. Convert everything to XML. Although Renato and Don of Common Sense Advisory joke that that will fix any L10n problem, it's nonetheless a good, long-term direction in which to move. It's easier to re-use text, and easier to mark text that should/should not be translated. That will save you money.
6. Start a program of controlled language authoring (dumbing down the sentences, always writing in a structure that machine translation will recognize, etc.). I guess that GM and Caterpillar are poster children for this kind of thing, but it puts the writers (and you, in the bargain) through the change of life, which is why I mention it last.

What about you? Have you faced this in your organization? How have you made document localization easier for the company, without driving your writers crazy?
If you liked this post, have a look at Getting Writers to Care about Localized Documents.

Labels: documentation internationalization, documentation localization, machine translation, technical writers, writing for localization