Advantages of built-in SVN tool versus external one?

[tomjohnson1492]

I'm trying to decide what SVN tool to use for my help content. I'm using OxygenXML, so my inclination is to use the SVN tool that Oxygen provides, but my company has Mercurial already set up (it's used by developers). It would be a breeze to create a new Mercurial repo for us to use. Can you tell me what the advantages of using the SVN integration built directly into OxygenXML versus a third-party SVN tool such as Mercurial? Thanks,

Tom

[adrian]

Hi,

I'm not sure if you are referring to SVN (Subversion) tools in specific or if you are referring to version control system tools in general. SVN is only one such type of version control system. AFAIK Mercurial is a different version control system that has its own type of repository, but incidentally can also access Subversion (SVN) repositories. If you work with Subversion (SVN), then you can use whatever SVN Client you like and even mix various clients.

There are no obvious advantages for using the built-in tool. The Syncro SVN Client that Oxygen bundles has a limited integration within Oxygen. It is pretty much a distinct tool with its own separate window.

Regards,
Adrian

[tomjohnson1492]

Thanks. Your reply answers my question.

By SVN, I meant to refer generically to version control systems.

If there aren't any really tight integration points or nifty doc-specific features with the Syncro soft version control system and Oxygen, then maybe it makes the most sense for me to use the built-in infrastructure already in place with Mercurial. Thanks.

Tom