How can I translate the documentation into another language?

General Feedback & Requests
, , ,
1

Hi! My name is, I’m from Russia, and that’s why I am interesting in translation of documentation. I understand that unreal engine 4 is just started and You have a lot of other issues besides translation, but one thing You can do right now if You have it of course. I am talking about documentation format. The fact that there is a translation program called SDL Trados Studio, it is designed to translate the documentation and it can import some of the documentation formats, here they are:
SDLXLIFF Documents (.sdlxliff)
TRADOStag Documents (.ttx)
SDL Edit Documents (.itd)
Microsoft Word 2000-2003 Documents (.doc;.dot)
Microsoft Word 2007-2010 Documents (.docx;.dotx;.docm;.dotm)
Microsoft PowerPoint XP-2003 Documents (.ppt;.pps;.pot)
Microsoft PowerPoint 2007-2010 Documents (.pptx;.ppsx;.potx;.pptm;.potm;.ppsm)
Microsoft Excel 2007-2010 Documents (.xlsx;.xltx;.xlsm)
Microsoft Excel 2000-2003 Documents (.xls;.xlt)
SDL Trados Translator’s Workbench Documents (.doc;.docx)
Rich Text Format IRTF) Documents (.rtf)
XHTML 1.1 Documents (.html;.htm)
HTML Documents (.htm;.html;.jsp;.asp;.aspx;.ascx;.inc;.ph p;.hhk;.hhc)
Adobe FrameMaker Documents (.mif)
Adobe InDesign I NX Documents (.inx)
IDML Documents (.idml)
Adobe InCopy CS4-CS6ICML (.icml)
OpenDocument Text Documents (.odt;.ott;.odm)
OpenDocument Presentation Documents [.odp;.otp)
OpenDocument Spreadsheet Documents (.ods;.ots)
QuarkXPress Export Documents (.xtg;.tag)
XUFF Documents (.xlf;.xliff)
WsXIiff Documents (.xlf)
PDF Documents (.pdf)
Comma Delimited (CSV) Documents (.csv)
Tab Delimited Text Documents (.txt)
Java Resource Documents (.properties)
Microsoft .NET Resource Files (.resx)
DITAXML Documents (.xml;.dita)
DocBookXML Documents (.xml)
ITS XML Documents (.xml)
XML Documents (.xml)
Text Documents (*.txt)

The most interesting are the formats for the documentation of special programs such as easyDITA, DocBook, oXygen XML Editor, MadCap Flare etc. The point is that if you have the documentation in this format, you can easily generate *.html code in the appropriate program, while the translation of documents in SDL Trados Studio does not affect any document links, but only change the language, in that case you do not need to translate each *.html page of the documentation, and then combine them, You just put the entire project of documentation in SDL Trados Studio and take it back translated, after it You can generate *.html or any other formats You like in the original program there You make the documentation.

And now the questions…

You make the documentation in some of the special programs for the documentation?
And if so, can You share with the project file from that program, so that everyone can easily translate You documentation in they own language?

2

We actually do provide the source to the documentation and the tools we use to create it. As far as I know, you can get them from the source code on GitHub. They should be under Engine/Documentation/Source. Somewhat ironically, though, our documentation format and tools are not very well documented. Haha. I’ll be working on fixing that as time allows, but I can answer specific questions about it here. The source format is an extended form of Markdown and the conversion tools are completely custom. There is also a plugin for Visual Studio that shows a realize preview directly in VS located in Engine/Extras/MarkdownMode.

We plan to move the documentation over to the wiki in the near future, which will mean anyone can create translations of the pages into any language they want pretty easily.