Include encoding in XML preamble for easier translation.

  • 1
  • Idea
  • Updated 8 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Inactive threads; archiving to prevent necroposing

The XML preamble of cmproj is currently:
Suggested is to add the default encoding UTF-8.
Photo of Guido Leenders

Guido Leenders

  • 12 Posts
  • 1 Reply Like

Posted 8 years ago

  • 1
Photo of Dave O'Rourke

Dave O'Rourke, Senior Software Engineer

  • 1444 Posts
  • 419 Reply Likes
Hi Guido,

Thanks for the suggestion.

You mentioned translation. Can you explain your process in a little more detail? We have had others request methods for easier translation of captions, callouts, and other text used in the video. It sounds like you're trying to automate this process in some way, but that's a guess. I'd like to know more about what you're trying to accomplish, so that we can get to the root of the problem, instead of just the symptoms.

Thanks for any additional details you can provide.
Photo of Guido Leenders

Guido Leenders

  • 12 Posts
  • 1 Reply Like
Hi dro,

you are welcome. Although it is already Unicode making it explicit makes it easier to detect problems. Xml namespace would be nico. But in fact therre is no problem; I am just trying to solve possible future problems.

For translation, we have been using Adobe Encore and Premiere (our designer uses a lot of Adobe tools, we purchased an expensive includes it all package). But it is rather awkward.

We are currently testing Camtasia for the whole publication process, not only for recording instruction videos.

The camproj contains the texts and it is great that is in XML. We have written a filter for the translation package OmegaT (we have standardized on it for all translation work into 8 languages). This filter allows translating the camproj file into all other languages in an automated way. Also, the existing glossaries and translation memories are available to the translators. And OmegaT allows incremental changes: change one sentence and the translator just needs to translate the changed sentence. The rest is token from the translation memory.

For publication we still need to publish manually and type in the Youtube data, but the largest part can be scripted in PS1 or ant or shell.

We would definitely be helped in further automating the publication process by a command line interface to publish to Youtube and mp4. And when the description, category and tags for YouTube would be taken from the project description in camproj.

I hope these details help you to understand our needs.
Photo of Guido Leenders

Guido Leenders

  • 12 Posts
  • 1 Reply Like
Hi dro, forgot to mention, the content will be published on http://www.invantive.com. If you like to I can send you a private URL for YouTube. It is not yet publicly available.
Photo of Dave O'Rourke

Dave O'Rourke, Senior Software Engineer

  • 1444 Posts
  • 419 Reply Likes
Guido,

Thanks for the additional detail on your process.

This conversation is no longer open for comments or replies.