Recherche avancée

Médias (91)

Autres articles (64)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • 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" (...)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

Sur d’autres sites (8967)

  • fate/matroska : Stop using unicode in command line paramters

    21 août 2023, par Martin Storsjö
    fate/matroska : Stop using unicode in command line paramters
    

    The fate-run.sh shell script exports LC_ALL=C before invoking the
    test executables ; this is probably done for consistency.

    When executing Windows binaries with Wine, it normally handles
    UTF-8 command line parameters just fine - but with LC_ALL set to
    C, it treats them as plain ASCII.

    As the unicode command line parameters wasn't the main thing
    being tested here, just convert them to plain ASCII, for
    portability. This fixes the test for all test configurations that
    use Wine.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] tests/fate/matroska.mak
    • [DH] tests/ref/fate/matroska-stereo_mode
  • Revision 6f53eee531 : Code cleanup in vp9_onyx_if.c. Using clamp and MIN/MAX functions instead of pla

    2 avril 2013, par Dmitry Kovalev

    Changed Paths : Modify /vp9/encoder/vp9_onyx_if.c Code cleanup in vp9_onyx_if.c. Using clamp and MIN/MAX functions instead of plain C code. Lower case variable names. Removing redundant parenthesis. Change-Id : Ibf7cc5fbe4fbdb5029049a599af71534176e6f42

  • libavutil : Add wchartoutf8(), wchartoansi(), utf8toansi(), getenv_utf8(), freeenv_utf...

    20 juin 2022, par Nil Admirari
    libavutil : Add wchartoutf8(), wchartoansi(), utf8toansi(), getenv_utf8(), freeenv_utf8() and getenv_dup()
    

    wchartoutf8() converts strings returned by WinAPI into UTF-8,
    which is FFmpeg's preffered encoding.

    Some external dependencies, such as AviSynth, are still
    not Unicode-enabled. utf8toansi() converts UTF-8 strings
    into ANSI in two steps : UTF-8 -> wchar_t -> ANSI.
    wchartoansi() is responsible for the second step of the conversion.
    Conversion in just one step is not supported by WinAPI.

    Since these character converting functions allocate the buffer
    of necessary size, they also facilitate the removal of MAX_PATH limit
    in places where fixed-size ANSI/WCHAR strings were used
    as filename buffers.

    On Windows, getenv_utf8() wraps _wgetenv() converting its input from
    and its output to UTF-8. Strings returned by getenv_utf8()
    must be freed by freeenv_utf8().

    On all other platforms getenv_utf8() is a wrapper around getenv(),
    and freeenv_utf8() is a no-op.

    The value returned by plain getenv() cannot be modified ;
    av_strdup() is usually used when modifications are required.
    However, on Windows, av_strdup() after getenv_utf8() leads to
    unnecessary allocation. getenv_dup() is introduced to avoid
    such an allocation. Value returned by getenv_dup() must be freed
    by av_free().

    Because of cleanup complexities, in places that only test the existence
    of an environment variable or compare its value with a string
    consisting entirely of ASCII characters, the use of plain getenv()
    is still preferred. (libavutil/log.c check_color_terminal()
    is an example of such a place.)

    Plain getenv() is also preffered in UNIX-only code,
    such as bktr.c, fbdev_common.c, oss.c in libavdevice
    or af_ladspa.c in libavfilter.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] configure
    • [DH] libavutil/getenv_utf8.h
    • [DH] libavutil/wchar_filename.h