Recherche avancée

Sur d’autres sites (8015)

• How to make your plugin multilingual – Introducing the Piwik Platform

  29 octobre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was Generating test data – Introducing the Piwik Platform). This time you’ll learn how to equip your plugin with translations. Users of your plugin will be very thankful that they can use and translate the plugin in their language !

  Getting started

  In this post, we assume that you have already set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Managing translations

  Piwik is available in over 50 languages and comes with many translations. The core itself provides some basic translations for words like “Visitor” and “Help”. They are stored in the directory /lang. In addition, each plugin can provide its own translations for wordings that are used in this plugin. They are located in /plugins/*/lang. In those directories you’ll find one JSON file for each language. Each language file consists in turn of tokens that belong to a group.

  {
  
      "MyPlugin":{
  
          "BlogPost": "Blog post",
  
          "MyToken": "My translation",
  
          "InteractionRate": "Interaction Rate"
  
      }
  
  }

  A group usually represents the name of a plugin, in this case “MyPlugin”. Within this group, all the tokens are listed on the left side and the related translations on the right side.

  Building a translation key

  As you will later see to actually translate a word or a sentence you’ll need to know the corresponding translation key. This key is built by combining a group and a token separated by an underscore. You can for instance use the key MyPlugin_BlogPost to get a translation of “Blog post”. Defining a new key is as easy as adding a new entry to the “MyPlugin” group.

  Providing default translations

  If a translation cannot be found then the English translation will be used as a default. Therefore, you should always provide a default translation in English for all keys in the file en.json (ie, /plugins/MyPlugin/lang/en.json).

  Adding translations for other languages

  This is as easy as creating new files in the lang subdirectory of your plugin. The filename consists of a 2 letter ISO 639-1 language code completed by the extension .json. This means German translations go into a file named de.json, French ones into a file named fr.json. To see a list of languages you can use have a look at the /lang directory.

  Reusing translations

  As mentioned Piwik comes with quite a lot of translations. You can and should reuse them but you are supposed to be aware that a translation key might be removed or renamed in the future. It is also possible that a translation key was added in a recent version and therefore is not available in older versions of Piwik. We do not currently announce any of such changes. Still, 99% of the translation keys do not change and it is therefore usually a good idea to reuse existing translations. Especially when you or your company would otherwise not be able to provide them. To find any existing translation keys go to Settings => Translation search in your Piwik installation. The menu item will only appear if the development mode is enabled.

  Translations in PHP

  Use the Piwik::translate() function to translate any text in PHP. Simply pass any existing translation key and you will get the translated text in the language of the current user in return. The English translation will be returned in case none for the current language exists.

  $translatedText = Piwik::translate('MyPlugin_BlogPost');

  Translations in Twig Templates

  To translate text in Twig templates, use the translate filter.

  {{ 'MyPlugin_BlogPost'|translate }}

  Contributing translations to Piwik

  Did you know you can contribute translations to Piwik ? In case you want to improve an existing translation, translate a missing one or add a new language go to Piwik Translations and sign up for an account. You won’t need any knowledge in development to do this.

  Advanced features

  Of course there are more useful things you can do with translations. For instance you can use placeholders like %s in your translations and you can use translations in JavaScript as well. In case you want to know more about those topics check out our Internationalization guide. Currently, this guide only covers translations but we will cover more topics like formatting numbers and handling currencies in the future.

  Congratulations, you have learnt how to make your plugin multilingual !

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.

• How to make your plugin multilingual – Introducing the Piwik Platform

  29 octobre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was Generating test data – Introducing the Piwik Platform). This time you’ll learn how to equip your plugin with translations. Users of your plugin will be very thankful that they can use and translate the plugin in their language !

  Getting started

  In this post, we assume that you have already set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Managing translations

  Piwik is available in over 50 languages and comes with many translations. The core itself provides some basic translations for words like “Visitor” and “Help”. They are stored in the directory /lang. In addition, each plugin can provide its own translations for wordings that are used in this plugin. They are located in /plugins/*/lang. In those directories you’ll find one JSON file for each language. Each language file consists in turn of tokens that belong to a group.

  {
  
      "MyPlugin":{
  
          "BlogPost": "Blog post",
  
          "MyToken": "My translation",
  
          "InteractionRate": "Interaction Rate"
  
      }
  
  }

  A group usually represents the name of a plugin, in this case “MyPlugin”. Within this group, all the tokens are listed on the left side and the related translations on the right side.

  Building a translation key

  As you will later see to actually translate a word or a sentence you’ll need to know the corresponding translation key. This key is built by combining a group and a token separated by an underscore. You can for instance use the key MyPlugin_BlogPost to get a translation of “Blog post”. Defining a new key is as easy as adding a new entry to the “MyPlugin” group.

  Providing default translations

  If a translation cannot be found then the English translation will be used as a default. Therefore, you should always provide a default translation in English for all keys in the file en.json (ie, /plugins/MyPlugin/lang/en.json).

  Adding translations for other languages

  This is as easy as creating new files in the lang subdirectory of your plugin. The filename consists of a 2 letter ISO 639-1 language code completed by the extension .json. This means German translations go into a file named de.json, French ones into a file named fr.json. To see a list of languages you can use have a look at the /lang directory.

  Reusing translations

  As mentioned Piwik comes with quite a lot of translations. You can and should reuse them but you are supposed to be aware that a translation key might be removed or renamed in the future. It is also possible that a translation key was added in a recent version and therefore is not available in older versions of Piwik. We do not currently announce any of such changes. Still, 99% of the translation keys do not change and it is therefore usually a good idea to reuse existing translations. Especially when you or your company would otherwise not be able to provide them. To find any existing translation keys go to Settings => Translation search in your Piwik installation. The menu item will only appear if the development mode is enabled.

  Translations in PHP

  Use the Piwik::translate() function to translate any text in PHP. Simply pass any existing translation key and you will get the translated text in the language of the current user in return. The English translation will be returned in case none for the current language exists.

  $translatedText = Piwik::translate('MyPlugin_BlogPost');

  Translations in Twig Templates

  To translate text in Twig templates, use the translate filter.

  {{ 'MyPlugin_BlogPost'|translate }}

  Contributing translations to Piwik

  Did you know you can contribute translations to Piwik ? In case you want to improve an existing translation, translate a missing one or add a new language go to Piwik Translations and sign up for an account. You won’t need any knowledge in development to do this.

  Advanced features

  Of course there are more useful things you can do with translations. For instance you can use placeholders like %s in your translations and you can use translations in JavaScript as well. In case you want to know more about those topics check out our Internationalization guide. Currently, this guide only covers translations but we will cover more topics like formatting numbers and handling currencies in the future.

  Congratulations, you have learnt how to make your plugin multilingual !

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.

• How to install this nodejs Application

  15 février 2016, par metalbug

  https://github.com/hexator/live4chan

  i have VMware run ubuntu-14.10-server and 15.10-server

  sudo apt-get install -y 
  
       git mongodb imagemagick libcairo2-dev libjpeg8-dev 
  
       libpango1.0-dev libgif-dev build-essential g++ ffmpeg curl

  install success

  git clone https://github.com/hexator/live4chan.git; 
  
  cd live4chan; 
  
  npm install

  but have errors

  test@ubuntu:~/live4chan$ npm start
  
  
  
      LiveChan@0.0.1 start /home/test/live4chan
  
      node lib/index.js
  
  
  
  Missing certificate or private key
  
  Running with insecure server
  
  info - socket.io started
  
  connect.limit() will be removed in connect 3.0
  
  connect.multipart() will be removed in connect 3.0
  
  visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
  
  connect.limit() will be removed in connect 3.0
  
  
  
  module.js:340
  
  throw err;
  
  ^
  
  Error: Cannot find module 'carrier'
  
  at Function.Module._resolveFilename (module.js:338:15)
  
  at Function.Module._load (module.js:280:25)
  
  at Module.require (module.js:364:17)
  
  at require (module.js:380:17)
  
  at Object. (/home/test/ircd.js/lib/server.js:24:15)
  
  at Module._compile (module.js:456:26)
  
  at Object.Module._extensions..js (module.js:474:10)
  
  at Module.load (module.js:356:32)
  
  at Function.Module._load (module.js:312:12)
  
  at Module.require (module.js:364:17)
  
  
  
  npm ERR! Linux 4.2.0-16-generic
  
  npm ERR! argv "node" "/usr/local/bin/npm" "start"
  
  npm ERR! node v0.10.42
  
  npm ERR! npm v3.7.2
  
  npm ERR! code ELIFECYCLE
  
  npm ERR! LiveChan@0.0.1 start: node lib/index.js
  
  npm ERR! Exit status 8
  
  npm ERR!
  
  npm ERR! Failed at the LiveChan@0.0.1 start script 'node lib/index.js'.
  
  npm ERR! Make sure you have the latest version of node.js and npm installed.
  
  npm ERR! If you do, this is most likely a problem with the LiveChan package,
  
  npm ERR! not with npm itself.
  
  npm ERR! Tell the author that this fails on your system:
  
  npm ERR! node lib/index.js
  
  npm ERR! You can get information on how to open an issue for this project with:
  
  npm ERR! npm bugs LiveChan
  
  npm ERR! Or if that isn't available, you can get their info via:
  
  npm ERR! npm owner ls LiveChan
  
  npm ERR! There is likely additional logging output above.
  
  
  
  npm ERR! Please include the following file with any support request:
  
  npm ERR! /home/test/live4chan/npm-debug.log
  
  
  
  ==========================================================
  
  /home/test/live4chan/npm-debug.log
  
  
  
  0 info it worked if it ends with ok
  
  1 verbose cli [ 'node', '/usr/local/bin/npm', 'start' ]
  
  2 info using npm@3.7.2
  
  3 info using node@v0.10.42
  
  4 verbose run-script [ 'prestart', 'start', 'poststart' ]
  
  5 info lifecycle LiveChan@0.0.1~prestart: LiveChan@0.0.1
  
  6 silly lifecycle LiveChan@0.0.1~prestart: no script for prestart, continuing
  
  7 info lifecycle LiveChan@0.0.1~start: LiveChan@0.0.1
  
  8 verbose lifecycle LiveChan@0.0.1~start: unsafe-perm in lifecycle true
  
  9 verbose lifecycle LiveChan@0.0.1~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/test/live4chan/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  
  10 verbose lifecycle LiveChan@0.0.1~start: CWD: /home/test/live4chan
  
  11 silly lifecycle LiveChan@0.0.1~start: Args: [ '-c', 'node lib/index.js' ]
  
  12 silly lifecycle LiveChan@0.0.1~start: Returned: code: 8 signal: null
  
  13 info lifecycle LiveChan@0.0.1~start: Failed to exec start script
  
  14 verbose stack Error: LiveChan@0.0.1 start: node lib/index.js
  
  14 verbose stack Exit status 8
  
  14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
  
  14 verbose stack at EventEmitter.emit (events.js:98:17)
  
  14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
  
  14 verbose stack at ChildProcess.emit (events.js:98:17)
  
  14 verbose stack at maybeClose (child_process.js:766:16)
  
  14 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:833:5)
  
  15 verbose pkgid LiveChan@0.0.1
  
  16 verbose cwd /home/test/live4chan
  
  17 error Linux 4.2.0-16-generic
  
  18 error argv "node" "/usr/local/bin/npm" "start"
  
  19 error node v0.10.42
  
  20 error npm v3.7.2
  
  21 error code ELIFECYCLE
  
  22 error LiveChan@0.0.1 start: node lib/index.js
  
  22 error Exit status 8
  
  23 error Failed at the LiveChan@0.0.1 start script 'node lib/index.js'.
  
  23 error Make sure you have the latest version of node.js and npm installed.
  
  23 error If you do, this is most likely a problem with the LiveChan package,
  
  23 error not with npm itself.
  
  23 error Tell the author that this fails on your system:
  
  23 error node lib/index.js
  
  23 error You can get information on how to open an issue for this project with:
  
  23 error npm bugs LiveChan
  
  23 error Or if that isn't available, you can get their info via:
  
  23 error npm owner ls LiveChan
  
  23 error There is likely additional logging output above.
  
  24 verbose exit [ 1, true ]

  I tried this :
  npm install carrier

  Or an error.

  and install Other versions of nodejs

  wget http://nodejs.org/dist/latest-v0.10.x/node-v0.10.42.tar.gz
  
  wget http://nodejs.org/dist/latest-v0.12.x/node-v0.12.10.tar.gz 
  
  wget http://nodejs.org/dist/latest-v4.x/node-v4.3.0.tar.gz
  
  wget http://nodejs.org/dist/latest-v5.x/node-v5.6.0.tar.gz
  
  tar zxvf node-v4.3.0.tar.gz
  
  cd node-v4.3.0
  
  ./configure 
  
  make
  
  sudo make install

  Nothing happened

  please help me
  Or you can tell me how to install, detailed, thank you very much !