russian translation fix

roadmap/README.md

@@ -11,7 +11,7 @@ Ravencoin (RVN) is a Proof of Work coin built on the Bitcoin UTXO model. As with
 *  Network Port: 8767
 *  RPC Port: 8766
 
-### Phase 2 - Assets (in progress)
+### Phase 2 - Assets (Complete)
 
 #### ASIC Resistance
 
@@ -41,7 +41,7 @@ Asset transfers require the standard RVN transaction fees for transfer from one
 
 #### Metadata
 
-Metadata about the token can be stored in IPFS. Initially this cannot be changed. If there is a demand, the system can be updated to allow updating the metadata by the token issuer.
+Metadata about the token can be stored in IPFS.
 
 #### Rewards
 
@@ -51,13 +51,13 @@ Example: A small software company issues an asset GAMECO that represents a share
 
 #### Block Size
 
-Raven may increase the blocksize from 1 MB to X MB to allow for more on-chain transactions.
+Raven may increase the blocksize from 2 MB to X MB to allow for more on-chain transactions.
 
 ### Phase 3 - Rewards
 
 Rewards allow payment in RVN to asset holders.
 
-### Phase 4 - Unique Assets
+### Phase 4 - Unique Assets (Complete)
 
 Once created, assets can be made unique for a cost of 5 RVN. Only non-divisible assets can be made unique. This moves an asset to a UTXO and associates a unique identifier with the txid. From this point the asset can be moved from one address to another and can be traced back to its origin. Only the issuer of the original asset can make an asset unique.  
 The costs to make unique assets will be sent to a burn address.  
@@ -71,47 +71,43 @@ are unique tokens.
 
 ### Phase 5 - Messaging
 
-Messaging to token holders by authorized senders will be layered on top of the Phase 3 unique assets. See KAAAWWW Protocol for additional information.
+Messaging to token holders by authorized senders will be layered on top of the Phase 4 unique assets. See KAAAWWW Protocol for additional information.
 
 ### Phase 6 - Voting
 
 Voting will be accomplished by creating and distributing parallel tokens to token holders. These tokens can be sent to RVN addresses to record a vote.
 
+### Phase 7 - Compatibility Mode
+
+Allows newly created assets to appear exactly like RVN, LTC, or Bitcoin for easy integration into exchanges, wallets, explorers, etc.
+Speeds adoption into the larger crypto ecosystem.
+
 ### Appendix A - RPC commands for assets
 
-`issue(to_address, asset_name, qty, units=1, reissuable=false)`  
+`issue (asset_name, qty, to_address, change_address, units, reissuable, has_ipfs, ipfs_hash)`  
 Issue an asset with unique name. Unit as 1 for whole units, or 0.00000001 for satoshi-like units. Qty should be whole number. Reissuable is true/false for whether additional units can be issued by the
 original issuer.  
 
-`issuefrom(from_address, to_address, qty, units, units=1, reissuable=false)`  
-Issue an asset with unique name from a specific address -- allows control of which address/private_key is used to issue the asset. Unit as 1 for whole units, or 0.00000001 for satoshi-like units. Qty should be whole number. Reissuable is true/false for whether additional units can be issued by the original issuer.
-
-`issuemore(to_address, asset_name, qty)`  
-Issue more of a specific asset. This is only allowed by the original issuer of the asset and if the reissuable flag was set to true at the time of original issuance.  
-
-`makeuniqueasset(address, asset_name, unique_id)`  
+`issueunique (root_name, asset_tags, ipfs_hash, to_address, change_address) `  
 Creates a unique asset from a pool of assets with a specific name. Example: If the asset name is SOFTLICENSE, then this could make unique assets like SOFTLICENSE:38293 and SOFTLICENSE:48382 This would be called once per unique asset needed.  
 
-`listassets(assets=*, verbose=false, count=MAX, start=0)`  
-This lists assets that have already been created. It does not distinguish unique assets.  
-
-`listuniqueassets(asset)`  
-This lists the assets that have been made unique, and the address that owns the asset.  
-
-`sendasset(to_address, asset, amount)`  
-This sends assets from one asset holder to another.  
+`reissue (reissue asset_name, qty, to_address, change_address, reissuable, new_unit, new_ipfs )`
+Issue more of a specific asset. This is only allowed by the original issuer of the asset and if the reissuable flag was set to true at the time of original issuance.
 
-`sendassetfrom(from_address, to_address, asset, amount)`  
-This sends asset from one asset holder to another, but allows specifying which address to send from, so that if a wallet that has multiple addresses holding a given asset, the send can disambiguate the address from which to send.  
+`transfer (asset_name, qty, to_address)`  
+This sends assets from one asset holder to another.
 
-`getassettransaction(asset, txid)`  
-This returns details for a specific asset transaction.  
+`listassets (assets, verbose, count, start)`  
+This lists assets that have already been created. 
+
+`listmyassets ( asset_name, verbose, count, start )`
+Lists your assets.
 
-`listassettransactions(asset, verbose=false, count=100, start=0)`  
-This returns a list of transactions for a given asset.  
+`listassetbalancesbyaddress (address)`
+Lists asset balance by address.
 
-`reward(from_address, asset, amount, except=[])`  
-Sends RVN to holders of the the specified asset. The Raven is split pro-rata to holders of the asset. Any remainder that cannot be evenly divided to the satoshi (1/100,000,000 RVN) level will be added to the mining fee. ​except​ is a list of addresses to exclude from the distribution - used so that you could exclude treasury shares that do not participate in the reward.  
+`listaddressesbyasset (asset_name)` 
+Lists addresses by asset.
 
-`send_asset(from_address, from_asset, to_asset, amount, except=[])`  
-Sends an asset to holders of the the specified to_asset. This can be used to send a voting token to holders of an asset. Combined with a messaging protocol explaining the vote, it could act as a distributed voting system.
+`getassetdata (asset_name)`
+Lists asset data of an asset.

src/qt/locale/raven_ru.ts

@@ -169,7 +169,7 @@
     </message>
     <message>
         <source>Warning: If you encrypt your wallet and lose your passphrase, you will &lt;b&gt;LOSE ALL OF YOUR RAVENS&lt;/b&gt;!</source>
-        <translation>Предупреждение: если вы зашифруете бумажник и потеряете пароль, вы &lt;b&gt;ПОТЕРЯЕТЕ ВСЕ ВАШИ БИТКОИНЫ&lt;/b&gt;!</translation>
+        <translation>Предупреждение: если вы зашифруете бумажник и потеряете пароль, вы &lt;b&gt;ПОТЕРЯЕТЕ ВСЕ ВАШИ RAVENS&lt;/b&gt;!</translation>
     </message>
     <message>
         <source>Are you sure you wish to encrypt your wallet?</source>
@@ -181,7 +181,7 @@
     </message>
     <message>
         <source>%1 will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your ravens from being stolen by malware infecting your computer.</source>
-        <translation>Сейчас %1 закроется для завершения процесса шифрования. Помните, что шифрование вашего бумажника не может полностью защитить ваши биткоины от кражи с помощью инфицирования вашего компьютера вредоносным ПО.</translation>
+        <translation>Сейчас %1 закроется для завершения процесса шифрования. Помните, что шифрование вашего бумажника не может полностью защитить ваши ravens от кражи с помощью инфицирования вашего компьютера вредоносным ПО.</translation>
     </message>
     <message>
         <source>IMPORTANT: Any previous backups you have made of your wallet file should be replaced with the newly generated, encrypted wallet file. For security reasons, previous backups of the unencrypted wallet file will become useless as soon as you start using the new, encrypted wallet.</source>
@@ -891,7 +891,7 @@
     </message>
     <message>
         <source>Attempting to spend ravens that are affected by not-yet-displayed transactions will not be accepted by the network.</source>
-        <translation>Попытка потратить биткоины из ещё не отображённых транзакций будет отвергнута сетью.</translation>
+        <translation>Попытка потратить ravens из ещё не отображённых транзакций будет отвергнута сетью.</translation>
     </message>
     <message>
         <source>Number of blocks left</source>
@@ -2265,7 +2265,7 @@
     </message>
     <message>
         <source>The fee will be deducted from the amount being sent. The recipient will receive less ravens than you enter in the amount field. If multiple recipients are selected, the fee is split equally.</source>
-        <translation>С отправляемой суммы будет удержана комиссия. Получателю придёт меньше биткоинов, чем вы вводите в поле количества. Если выбрано несколько получателей, комиссия распределяется поровну.</translation>
+        <translation>С отправляемой суммы будет удержана комиссия. Получателю придёт меньше ravens, чем вы вводите в поле количества. Если выбрано несколько получателей, комиссия распределяется поровну.</translation>
     </message>
     <message>
         <source>S&amp;ubtract fee from amount</source>
@@ -2334,7 +2334,7 @@
     </message>
     <message>
         <source>You can sign messages/agreements with your addresses to prove you can receive ravens sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</source>
-        <translation>Вы можете подписывать сообщения/соглашения своими адресами, чтобы доказать свою возможность получать биткоины на них. Будьте осторожны, не подписывайте что-то неопределённое или случайное, так как фишинговые атаки могут обманным путём заставить вас подписать нежелательные сообщения. Подписывайте только те сообщения, с которыми вы согласны вплоть до мелочей.</translation>
+        <translation>Вы можете подписывать сообщения/соглашения своими адресами, чтобы доказать свою возможность получать ravens на них. Будьте осторожны, не подписывайте что-то неопределённое или случайное, так как фишинговые атаки могут обманным путём заставить вас подписать нежелательные сообщения. Подписывайте только те сообщения, с которыми вы согласны вплоть до мелочей.</translation>
     </message>
     <message>
         <source>The Raven address to sign the message with</source>

src/qt/locale/raven_ru_RU.ts

@@ -523,7 +523,7 @@
     <name>QObject</name>
     <message>
         <source>Enter a Raven address (e.g. %1)</source>
-        <translation>Введите биткоин-адрес (напр. %1)</translation>
+        <translation>Введите Raven-адрес (напр. %1)</translation>
     </message>
     <message numerus="yes">
         <source>%n hour(s)</source>