
Recherche avancée
Autres articles (80)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Gestion de la ferme
2 mars 2010, parLa ferme est gérée dans son ensemble par des "super admins".
Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
Dans un premier temps il utilise le plugin "Gestion de mutualisation"
Sur d’autres sites (9166)
-
avcodec/dvdsubenc : Add dvdsub workaround for some players
9 juillet 2014, par Oliver Frommeavcodec/dvdsubenc : Add dvdsub workaround for some players
The issue affects dvdsub subtitles (a.k.a. VOBSUB).
Some players — in particular hardware players — cut off
the lowest row of pixels if the number of rows in the subtitle
is odd.The patch below implements a work-around for that. If the
number of rows is odd, it is simply rounded up to an even
number, adding an invisible (i.e. fully transparent) row.
The work-around can be enabled or disabled with a new
option -even_rows_fix. The default is disabled, so there
is no change of behaviour for users who don’t care about it.The overhead for the fix is low, and in many cases even zero :
For subtitles with an odd number of rows (i.e. in 50% of
cases on average), the size increases by two bytes because
a fully transparent row is encoded as 0x00 0x00. However,
in the VOBSUB standard, all data packets are padded to 2KB
anyway, so in most cases the additional bytes just use some
part of the padding, so there is no overhead. Only in the
rare case that the 2KB boundary is hit (0.1% chance), a full
2KB block is added.Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
-
Piwik is now using Github issues as our Issue Tracker !
9 juillet 2014, par Matthieu Aubry — Community, DevelopmentThis is an announcement regarding the Issue Tracker used for the Piwik project. We are excited to announce that Piwik has migrated from Trac to now using Github issues for managing our issues !
More than 5,400 tickets and 20,000+ comments from 1,000+ users were migrated to Github. Read on for more information.
Where do I find Piwik Issue Tracker ?
- Piwik main project issue tracker (piwik/piwik)
- Piwik Mobile issues (piwik/mobile2)
- Device Detector issues (piwik/device-detector)
- Piwik iOS SDK (piwik/piwik-sdk-ios)
- See other repositories at github.com/piwik
Benefits of using Github Issues for the Piwik project
There are several advantages of moving to Github issues :
- Faster and responsive user interface
- Better cross-project referencing of issues
- Ability to notify people with the @username functionality
- No spam
- Integration with Pull requests and our Git repository
How do I get notifications for all Piwik tickets ?
To receive notifications for new tickets or new comments in the Piwik project, go to github.com/piwik/piwik, then click the Watch button at the top of the page.
In Github, watching a repository lets you follow new commits, pull requests, and issues that are created.
How do I report a bug in Piwik ?
See Submitting a bug report.How do I suggest a new feature ?
See Submitting a feature request.Next steps
At Piwik we care a lot about Data ownership. For this reason we need to have an up to date copy of all our tickets and comments out of github.com servers. Our next step will be to create and release as open source a tool to let anyone create a Mirror of their Github issues. See #5299.
For more information about the Trac->migration, see #5273.
We look forward to reading your issues on Github !
-
flac and metaflac : Don’t always call setlocale() in Windows.
19 juillet 2014, par Erik de Castro Lopoflac and metaflac : Don’t always call setlocale() in Windows.
Windows (MSVC, MinGW) versions of setlocale don’t care about LC_*
environment variables. For example, flac cannot pass the test for
— until and —skip options the script calls it with —skip=0:01.1001
and it expects decimal comma (—skip=0:01,1001) on some locales.Solve this (on Windows) by calling setlocale(LC_ALL, "") if some
LC_* variable is set to "C".Patch-from : lvqcl <lvqcl.mail@gmail.com>