Recherche avancée

Médias (0)

Mot : - Tags -/médias

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (91)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (20945)

  • Is there a library for editing MP4 Metadata with Scala or Java ? [on hold]

    8 août 2013, par Zack Yoshyaro

    I've been using ffmpeg for the task by simply calling it from Scala. However, it's remarkably overkill to do so, as ffmpeg requires you to have an output file. So I'm creating entire copies of video files just so I can modify the ID3 tags. It's time, and CPU taxing to say the least.

    Obviously, they can be editing in place (for instance, by manually changing the tags in the property dialog in windows). Surely there's a way to do the same thing programatically ?

  • Evolution #4730 : Rendre le plug 100% traduisable

    15 avril 2021

    Pour les format de date, plusieurs remarques :

    1) on utilise les chaines de langues de d3js time-format : https://git.spip.net/spip/statistiques/src/branch/master/lib/d3/time-format/locale
    2) ici ça se passe beaucoup en JS et JS sait maintenant traduire (la plupart des navigateurs) différents formats de date https://caniuse.com/mdn-javascript_builtins_intl_locale_script https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/script donc au pire on aurait pu utiliser ça (et d3 l’utilisera probablement un jour qui sait mais pas pour le moment https://github.com/d3/d3-time-format/issues/57)

    La traduction qui manque pour le moment est "Visites" j’ai aperçu, et faut que je vois pourquoi.

  • configure : allow the gas-preprocessor to be called with an absolute path.

    16 avril 2013, par Lars Hammarstrand
    configure : allow the gas-preprocessor to be called with an absolute path.

    Allow the configure tool to call the gas-preprocessor with an absolute
    
path when included with either the "—as" or with a separate "—gas"
    
option.  The patch is backward compatible and will not break any current
    
configuration setups.
    

    The new behavior that comes with this option can be utilized in the
    
following ways :
    

    Examples :
    

    - Just as single option that includes both the gas-preprocessor.pl and
    
  cc/as at the same time :
    

      $ configure —as="/opt/app/build-tools/gas-preprocessor.pl \
    
                   /Applications/Xcode.app/.../Developer/usr/bin/gcc"
    

    - Call gas-preprocessor with a separate option in conjunction with —as :
    

      $ configure —gas="/opt/app/build-tools/gas-preprocessor.pl" \
    
               —as="/Applications/Xcode.app/.../Developer/usr/bin/gcc"
    

    - Address only the the gas-preprocessor and it will automatically fall
    
  back to as or cc whichever that’s defined :
    
  $ configure —gas="/opt/app/build-tools/gas-preprocessor.pl"
    

    - Or if no gas-preprocessor.pl is explicitly defined, it falls back to
    
  the old behaivor.
    • [DH] configure

Navigation