Permalink
Browse files

Doc: replace 4 references to SVN with Git #6698 (#7036)

  • Loading branch information...
andythenorth authored and planetmaker committed Jan 11, 2019
1 parent c693463 commit f99f993e99b662fe3621013d3468c3d75a12ecac
Showing with 4 additions and 4 deletions.
  1. +2 −2 README.md
  2. +2 −2 docs/HOWTO_compile_lang_files.txt
@@ -78,7 +78,7 @@ When you are sure it is not already reported you should:
After you have done all that you can report the bug. Please include the
following information in your bug report:

- OpenTTD version (PLEASE test the latest SVN/nightly build)
- OpenTTD version (PLEASE test the latest Git revision/nightly build)
- Bug details, including instructions how to reproduce it
- Platform (Windows, Linux, FreeBSD, …) and compiler (including version) if
you compiled OpenTTD yourself.
@@ -655,7 +655,7 @@ someone else may have already started translating to the same language.
So, now that you have notified the development team about your intention to
translate (You did, right? Of course you did.) you can pick up english.txt
(found in the SVN repository under /src/lang) and translate.
(found in the Git repository under /src/lang) and translate.
You must change the first two lines of the file appropriately:
@@ -29,7 +29,7 @@ english.txt to work. Below are some examples of strgen usage.
1.1) Examples
---- --------
Example 1:
if you are in the root of your working copy (svn code), you should type
if you are in the root of your working copy (git repository), you should type
strgen/strgen -s lang lang/english.txt
to compile englist.txt into english.lng. It will be placed in the lang dir

@@ -50,7 +50,7 @@ You can interchange english.txt to whichever language you want to generate a
1.2) strgen command switches
---- -----------------------
-v | --version
strgen will tell what svn revision it was last modified
strgen will tell what git revision it was last modified

-t | --todo
strgen will add <TODO> to any untranslated/missing strings and use the english

0 comments on commit f99f993

Please sign in to comment.