Recherche avancée

Sur d’autres sites (8868)

• 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 map ffmpeg formats to MIME types and file extensions ?

  17 mai 2017, par odigity

  Anyone know of a reference for mapping ffmpeg format values to MIME types and recommended file extension ? My google attempt failed to turn up anything.

  I did manually put together a small list with guess-work and clues from Wikipedia, IANA, and the Mozilla Developer Network for the subset of formats that I encountered in my video input test collection :

  ffmpeg Format             Extension  MIME Type
  
  ───────────────────────   ─────────  ────────────────────── 
  
  asf                       asf        application/vnd.ms-asf
  
  avi                       avi        video/x-msvideo
  
  flv                       flv        video/x-flv
  
  matroska,webm             webm       video/webm
  
  m4v                       m4v        video/x-m4v
  
  mov,mp4,m4a,3gp,3g2,mj2   mp4        video/mp4
  
  mpeg                      mpeg       video/mpeg
  
  mpegts                    mpeg       video/mpeg
  
  mpegvideo                 mpeg       video/mpeg
  
  ogg                       ogv        video/ogg
  
  matroska                  mkv        video/x-matroska
  
  webm                      webm       video/webm

  No idea if I’ve made the right calls, though.

  (The test files already have file extensions, but I’m operating on the assumption that the extension of a file a user uploads is irrelevant, and that the file should be renamed based on ffprobe and intelligent mapping...)

• What is the "Error initializing filter 'drawtext' with args..." error in using of ffmpeg at c# process class ?

  7 novembre 2016, par parsa

  I used this below code for create a resolution of a video and write text on it.

      var proc = new System.Diagnostics.Process();
  
      strin OrginalResolution="nhd";
  
      proc.EnableRaisingEvents = false;
  
      proc.StartInfo.FileName = ffmpegPath;
  
      proc.StartInfo.Arguments = "-i \"" + fileIn +
  
                                 "\" -f mp4 -s " + OrginalResolution + " -vf drawtext=fontfile=/OtherProjects/ConvertProj/ff‌​mpeg/OpenSans-Reg‌​ular.ttf:text=Parsa" \"" + fileOut.Split('.')[0] +
  
                                 ".mp4";
  
      proc.StartInfo.UseShellExecute = false;
  
      proc.StartInfo.CreateNoWindow = false;
  
      proc.StartInfo.RedirectStandardOutput = true;
  
      proc.StartInfo.RedirectStandardError = true;
  
  
  
      proc.Start();
  
      proc.WaitForExit();
  
      string sdsd = proc.StandardError.ReadToEnd();
  
      proc.Close();

  I faced with this problem(some string output of StandardError is in below) :

  Fontconfig error: Cannot load default config file\r\n[Parsed_drawtext_0       
  
  @0000000002fd8c20] Cannot find a valid font for the family 
  
  Sans\r\n[AVFilterGraph @ 0000000000511660] Error initializing 
  
  filter'drawtext' with args 
  
  'fontfile=/OtherProjects/ConvertProj/ffmpeg/OpenSans-
  
  Regular.ttf:text=parsa'\r\nError opening 
  
  filters!\r\n

  In cmd the same argument value of process works fine.
  I read that this issue related to how to using quotation mark at using
  of text property of drawtext in ffmpeg.but I can’t find any
  solution for solving this issue.
  Can anyone help me ?

  Can anyone help me still ?Is this a bug ?
  I used any solutions for escape from : in my code,but can’t solve this problem.
  It can’t find font.I delete other filters of drawtext to findout that any of filters don’t mistake, but still error exists yet.

  expansion=none property of drawtext doesn’t influence on this case, for escape :.