Translating Soholaunch

From Sohowiki
(Difference between revisions)
Jump to: navigation, search
m
 
(29 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
 
For purposes of example, let's say we want to translate Soholaunch into Piglatin.
 
For purposes of example, let's say we want to translate Soholaunch into Piglatin.
  
Line 12: Line 13:
 
<pre>sohoadmin/language/english.php</pre>
 
<pre>sohoadmin/language/english.php</pre>
  
Rename your copy to "KOI8-RU.php", like so:
+
Rename your copy to "mylanguage.php", like so:
<pre>pigcirilitc.php</pre>
+
<pre>piglatin.php</pre>
  
Open the file (KOI8-RU.php) in some kind of text/code editor. Plain-ol' Windows' Notepad will work, but I'd recommend something that has syntax highlighting for php files (for the sake of readability).
+
Open the file (piglatin.php) in some kind of text/code editor. Plain-ol' Windows' Notepad will work, but I'd recommend something that has syntax highlighting for php files (for the sake of readability).
  
 
Now it's just a matter of going through and translating every line.
 
Now it's just a matter of going through and translating every line.
  
 
For example, you'd change this line...
 
For example, you'd change this line...
<pre>$lang["Main Menu"] = "Мое меню";</pre>
+
<pre>$lang["Main Menu"] = "Main Menu";</pre>
  
 
...into something like this:
 
...into something like this:
Line 27: Line 28:
 
When you're finished, send your translated language file to tech.team at soholaunch.com and we'll integrate it into the next product build.
 
When you're finished, send your translated language file to tech.team at soholaunch.com and we'll integrate it into the next product build.
  
 
+
==Notes/Tips==
 
+
*Make sure your language strings file (e.g., piglatin.php) does not have any trailing spaces or line breaks after the closing "?>" at the bottom or certain site elements could go haywire (e.g., pages protected with a security group are completely blank).
[http://www.magical-casino.com/security.html Casinos security online.]
+
[http://www.casinos-new.com/blackjack.html Online casino - Blackjack online]
+
[http://www.3wcasinos.com/roulette-tips/index.html roulette tips]
+
[http://www.casinos-go.com/online-casino-tips/free-online-casino-slot.html free online casino slot]
+
[http://www.casino-web-gambling.com/blackjack-tips/blackjack-hints.html blackjack hints]
+
[http://www.casinos-new.com/internet-casino.html Online casino - Internet Casinos]
+
[http://www.slots-wiki.com/index.php/slots_tips slots tips]
+
[http://www.gambling-online-theory.com/online-casino/bet-online-casino.html bet online casino]
+
[http://www.casinos-go.com/online-casino-tips/online-casino-on-the-net.html online casino on the net]
+
[http://www.casino-theory.com/online-casino-royale/play-free-online-casino.html play free online casino]
+

Latest revision as of 16:54, 23 May 2007

For purposes of example, let's say we want to translate Soholaunch into Piglatin.

Basic overview

1. Make a copy of the current english.php strings file

2. Rename file to mylanguage.php, open it up, translate

3. Send it to us so we can integrate it into the next product build

Detailed instructions

Grab this file from one of your soho sites (make sure it's on the latest available version so you get the most up-to-date strings file)...

sohoadmin/language/english.php

Rename your copy to "mylanguage.php", like so:

piglatin.php

Open the file (piglatin.php) in some kind of text/code editor. Plain-ol' Windows' Notepad will work, but I'd recommend something that has syntax highlighting for php files (for the sake of readability).

Now it's just a matter of going through and translating every line.

For example, you'd change this line...

$lang["Main Menu"] = "Main Menu";

...into something like this:

$lang["Main Menu"] = "Ainmay Enumay";

When you're finished, send your translated language file to tech.team at soholaunch.com and we'll integrate it into the next product build.

Notes/Tips

  • Make sure your language strings file (e.g., piglatin.php) does not have any trailing spaces or line breaks after the closing "?>" at the bottom or certain site elements could go haywire (e.g., pages protected with a security group are completely blank).
Personal tools