Changes between Version 2 and Version 3 of TranslationGuide


Ignore:
Timestamp:
05/26/07 18:49:32 (13 years ago)
Author:
Eoin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TranslationGuide

    v2 v3  
    44a wiki page would have quickly become very unwieldy. Unfortunately this does mean the any translators will need to use SVN too. However, anyone who doesn't want to go to that difficultly can get in touch with me through email. 
    55 
    6 For those happy to use the SVN setup let me explain how to use it.  
     6For those happy to use the SVN setup let me explain how to use it. To get write access to the lang folder you need to use the user name and password. To try and avoid casual spam these won't be posted but are available upon request, just send me a mail. 
    77 
    88=== Using SVN commandline === 
    99 
    10 In many ways the commandline svn approach is the easiest to explain. 
    11  
    12 To login in for the first time cd the a desired working directory and issue the command 
     10In many ways the commandline svn approach is the easiest to explain. To login in for the first time cd the a desired working directory and issue the command 
    1311{{{ 
    1412svn checkout svn://svn.geekisp.com/halite/lang 
     
    3230=== Using RapidSVN === 
    3331 
    34 Alternatively I'd recommend RapidSVN as an easy to use GUI to Subversion. When you fire it goto ''''''Bookmmarks' >> 'Add existing repository'''''' and use the URL [svn://svn.geekisp.com/halite]. To get write access to the lang folder you need to use the user name and password. To try and avoid casual spam these won't be posted but are available upon request, just send me a mail. 
     32Alternatively I'd recommend RapidSVN as an easy to use GUI to Subversion. When you fire it goto ''''''Bookmmarks' >> 'Add existing repository'''''' and use the URL [svn://svn.geekisp.com/halite].  
    3533 
    3634=== The file format ===