New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| In February 2005, the theme system was built using PHP, which is a templating language itself, after all. The theme system breaks a theme down into its component parts — header, footer, and sidebar, for example. Each part is an individual file that a designer can customize. A native WordPress theme system, as opposed to a templating system such as Smarty, meant that designers could design and build themes without learning an entirely new syntax. | En février 2005, le principe du thème WP fut construit à l’aide du langage PHP (qui lui-même est un système de templating, après tout). Ce principe est basé sur des fichiers modèles servant de composant au thème : en-tête, pied de page, colonne latérale, etc. Chaque partie dispose de son fichier individuel pouvant être personnalisé par un designer. Ce système de thème WordPress permet aux développeurs et aux développeuses WordPress de travailler en utilisant un principe commun. | Details | |
Original current
In February 2005, the theme system was built using PHP, which is a templating language itself, after all. The theme system breaks a theme down into its component parts — header, footer, and sidebar, for example. Each part is an individual file that a designer can customize. A native WordPress theme system, as opposed to a templating system such as Smarty, meant that designers could design and build themes without learning an entirely new syntax.
You have to log in to edit this translation. |
|||
| The source code for any program binaries or minified external scripts that are included with WordPress can be freely obtained from our <a href="%s">sources repository</a>. | Le code source de tout programme binaire ou script externe minifié inclus avec WordPress peut être obtenu gratuitement à partir de notre <a href="%s">dépôt de sources</a>. | Details | |
Original current
The source code for any program binaries or minified external scripts that are included with WordPress can be freely obtained from our <a href="%s">sources repository</a>.
You have to log in to edit this translation. |
|||
| About Us: Our Mission | À propos de nous : Notre mission | Details | |
Original current |
|||
| Accept Declaration and Request Export | Accepter la déclaration et la demande d’exportation | Details | |
Original current
Accept Declaration and Request Export
You have to log in to edit this translation. |
|||
| Data Export Request | Demande d’exportation des données | Details | |
Original current
Data Export Request
ContextPage titleReferences
You have to log in to edit this translation. |
|||
| The core of WordPress will always provide a solid array of basic features. It’s designed to be lean and fast and will always stay that way. We are constantly asked “when will X feature be built” or “why isn’t X plugin integrated into the core”. The rule of thumb is that the core should provide features that 80% or more of end users will actually appreciate and use. If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. If we stick to the 80% principle then this should never happen. | Le cœur de WordPress fournira toujours une solide liste de fonctionnalités. Il est conçu pour être rapide et précis et le restera toujours. On nous demande constamment « quand est-ce que la fonctionnalité X sera disponible » ou « pourquoi l’extension X n’est pas intégrée au cœur ». La règle de base est qu’une fonctionnalité doit être appréciée et utilisée par au moins 80% des utilisateurs et utilisatrices. Si la prochaine version du cœur de WordPress apporte une fonctionnalité que la plupart des gens veulent désactiver ou qu’ils ne l’utiliseront jamais, nous la rejetons. Si nous nous tenons au principe des 80%, ce cas de figure ne devrait pas se présenter. | Details | |
Original current
The core of WordPress will always provide a solid array of basic features. It’s designed to be lean and fast and will always stay that way. We are constantly asked “when will X feature be built” or “why isn’t X plugin integrated into the core”. The rule of thumb is that the core should provide features that 80% or more of end users will actually appreciate and use. If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. If we stick to the 80% principle then this should never happen.
You have to log in to edit this translation. |
|||
| You can be WordPress too! Help to build WordPress, answer questions on the support forums, write documentation, translate WordPress into your language, speak at a WordCamp, write about WordPress on your blog. Whatever your skill, <a href="%s">we’d love to have you</a>! | Vous pouvez aussi faire partie de WordPress ! Aidez à construire WordPress, répondez aux questions sur les forums de support, écrivez de la documentation, traduisez WordPress dans votre langue, parlez à un WordCamp, écrivez à propos de WordPress sur votre blog. Quelque soit votre compétence, <a href="%s">nous serions ravis de vous compter parmi nous</a>. | Details | |
Original current
You can be WordPress too! Help to build WordPress, answer questions on the support forums, write documentation, translate WordPress into your language, speak at a WordCamp, write about WordPress on your blog. Whatever your skill, <a href="%s">we’d love to have you</a>!
You have to log in to edit this translation. |
|||
| WordPress Accessibility | Accessibilité WordPress | Details | |
Original current
WordPress Accessibility
You have to log in to edit this translation. |
|||
Export as