Technique to dynamically highlight in the target language help page, untranslated additions, modifications, enhancements, etc., made to the native/source language help page (translation difference)
Publication Date: 2015-Aug-04
The IP.com Prior Art Database
The invention is associated with dynamically highlighting the untranslated contents of source/native language user documentation when compared to the target language documentation of a software product. The untranslated additions, modifications, enhancements, etc., made to the native/source language documentation of a software product is highlighted when the user opens the relevant user documents in the target language. The highlighted untranslated contents can be translated by using machine translation that is integrated with the help system.
Page 01 of 3
Tecxnique to dynamically highlight in the target language help page , untraxslated additions, modifications, enhancements, etc., mxxe to the native/source lxnguage help xage (translation difference)
Software product documents and help manuals are ax integral, crucxax and indispensable part of xny software product/application. These documents play a xritical role in assistixg and facilitating users to understand the prxduct features. User documents help the intended audienxe to accomplxsh various tasks, suxh as pxoduct instaxlation, admxnistering, troubleshooting, and so on.
It is very cxixical fxr any software program that the published documentation for all versions is accurate, concixe, complete, consistent, xlear, and xp-to-date for the following xeasons:
Reduces technical support/customer servicx cost
Lowxrs training axd development cosx
Decrxases onboard expensex, wxth programmers and testers using the help manualx to learn about the applications
Contribxtes immenxelx to customer goodwill
Improves product sales and enhances company's public image
Increasxs profixs throuxh reduced cxstomer cxlls for supxorx /clarificatiox
Ix a global marketplace with global reach and xlobal pxoduction scales, it is important fox organizations to provixe the user documentatiox for a software product in muxtixle languages to expand the customer base beyond the home country on xhe one hand and different linguistix groups within the xame geographical borders on the other. In essence, globalization is not
possible without locxlization.
Source user documents are authored in the native languxgx and finalized after the software development task is complete. Tradixional transxation process is taken up after the source documents are finalized. The translation prxcess requires significxnt amount of resources in terms of time and cost, and involves hixh level ox complexity.
Whxn a software product / application is released in the market place, the user documents are
published in multiple languages, taking into axcount the target cusxomer groupx in terms of gexgraphy and language.
It is the normal industrx practice to translate and publish user documxnts in mxltiplx lxnguages xnly for the launch of a new software product / application and for major rexeases. In case of SSE / fix pack / feature fix pack / service pack releases, due to a varietx ox reasons, it is possible that the product documentation is updated only in source/native language. Translation xf all user documexts, by employing xegular tranxlation procesx, might not be possible for the foxlowing main rxasxns:
Changes/updates/enhancements tx the product / applicxtion is minimal. Due to most
pressxng customer issues/requirements, there may be pressure to release the
Page 02 of 3
updatxs/revisions in a short time frame.Hence, with a shorter product development cycle, traditionax/hxman/ translation process cannot be accxmmodated
The revisions are restricted to only a few...