https://docs.sandbox.joomla.org/api.php?action=feedcontributions&feedformat=atom&user=Sandra97Joomla! Documentation - User contributions [en]2026-08-11T16:41:20ZUser contributionsMediaWiki 1.43.0https://docs.sandbox.joomla.org/index.php?title=User_talk:Sandra97&diff=1010303User talk:Sandra972023-07-18T07:30:34Z<p>Sandra97: /* Please add to the translation team */</p>
<hr />
<div>{{Translator welcome}}<br />
<br />
== New Tables ==<br />
<br />
Sandra<br />
<br />
I added two pages to your user pages: [[User:Sandra97/Responsive Tables]] and [[User:Sandra97/jforeground.css]]. Adjust the css page to see the changes immediately after saving it. Have fun!<br />
<br />
Tom<br />
<br />
Placed by [[User:JoomlaWikiBot|JoomlaWikiBot]] ([[User talk:JoomlaWikiBot|talk]]) 10:48, 2 July 2017 (CDT)<br />
<br />
== Mori0725ken: Joomla Volunteers Portal Account has added ==<br />
<br />
Hello Sandra,<br />
<br />
I'm Mori0725ken. I have created an Joomla Volunteers Portal Account, so you can add me to the Documentation Translation Team.<br />
<br />
For any other question, please tell me anytime.<br />
<br />
Thank you!<br />
<br />
Liao Yu Hsuan (KenSanzhi,DenshadeGo)<br />
<br />
[[User:Mori0725ken|電車でGO]] ([[User talk:Mori0725ken|talk]]) 19:14, 4 July 2017 (CDT)<br />
<br />
<sub>Texte en indice</sub>== A new volunteer ==<br />
Hello, would you please add me to "Translator" group. (Russian) --[[User:Cronolio|Cronolio]] ([[User talk:Cronolio|talk]]) 10:33, 25 April 2018 (CDT)<br />
<br /><br />
<br /><br />
<br />
Hello, <br /><br />
You need first to confirm your email and add your name to this page: [[JDOC:Documentation_Translators|Translate JDocs]], in your language section.<br /><br />
Then, I will grant you translator permissions and send you a welcome message with useful links. <br />
I stay at your disposal of course! <br /><br />
<br />
== Help to translate "typehinted to require a callable" ==<br />
<br />
Bonjour Sandra, je tombe régulièrement sur cette expression dans cette page https://docs.joomla.org/index.php?title=Special:Translate&group=page-Potential+backward+compatibility+issues+in+Joomla+4&language=fr&action=page et je ne sais pas la traduire : "typehinted to require a callable". Pourrais-tu m'aider, s'il te plaît ?<br />
<br />
Laurent<br />
<br />
<br />
---<br />
<br />
Bonjour Laurent, <br /><br />
Je présume que cela a à voir avec les fonctions TypeHint et Call. Je me renseigne et reviens vers toi<br />
<br />
---<br /><br />
Re bonjour Laurent,<br />
<br /><br />
Apparemment un paramètre Type Hint a été ajouté. Ainsi, au lieu d'être une classe dans Joomla (par exemple, Japplication), c'est tout ce qui est appelable (par exemple, une fonction anonyme, un tableau de classe / fonction etc)<br />
<br />
([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 10:47, 25 April 2018 (CDT))<br />
<br />
== Comment traduire une page qui n'est pas "Traduire cette page"==<br />
<br />
Bonjour Sandra, la page https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha ne peux pas être traduite. Du coup, j'ai modifié la page et ajouté les balises permettant la traduction. Est-ce comme cela qu'il faut procéder ? Y-a-t'il une autre demande à faire quelque part pour que l'on puisse la traduire ?<br />
<br />
<br />
Bonjour, <br />
<br />
C'est bon, je l'ai marquée. En effet, une fois les balises ajoutées, il faut cliquer sur 'marquer la page pour traduction" pour activer le système.<br /><br />
La seule modification que j'ai faite est au niveau des balises de traductions pour les catégories (je te laisse le soin de regarder dans le code source).<br />
<br />
---<br />
<br />
Bonjour,<br />
<br />
Merci pour l'information. Mais où trouves-tu l'information "marquer la page pour traduction" ? Je ne vois pas où mettre cela.<br />
J'ai une nouvelle page que je voulais mettre à traduire ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_IIS/IIS7<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
C'est indiqué en haut de la page, à la place de "traduire la page". <br />
J'ai marqué l'autre page à traduire. <br />
Bonne soirée<br />
<br />
---<br />
<br />
Merci, mais je n'ai pas cela d'indiqué en haut de la page mais un texte du genre "Cette page n'est pas marquée pour la traduction" et ce n'est pas cliquable. Tu dois avoir des droits que je n'ai pas.<br />
<br />
---<br />
<br />
Oui, il faut des droits spéciaux pour pouvoir marquer une page<br />
<br />
---<br />
<br />
OK. Merci pour l'info. Du coup, c'est à toi que je demande pour mettre une page à traduire où il y a un lieu pour cela ?<br />
<br />
Voici une nouvelle page à marquer pour la traduction, s'il te plaît ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Nginx.<br />
<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
Non ce n'est pas à moi, je ne suis plus active sur la doc. Tu peux demander à Mike Brandner, qui est le chef d'équipe de la doc.<br />
<br />
== Please add to the translation team ==<br />
<br />
Hello Sandra97.<br />
I hope I have not disturbed you. Can you approve me as a translator? I left the application on the right page.<br />
<br />
<br />
===<br />
Hi, I'm not part of the team anymore. I hope a team admin will grant you the permissions asap.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=JDOC:Documentation_Translators&diff=1001861JDOC:Documentation Translators2023-05-23T12:09:54Z<p>Sandra97: /* de - Deutsch - German */ Translator permission granted</p>
<hr />
<div>[[File:JDOC translation icon.png|right]]<br />
Here, people '''translating''' {{SITENAME}} can sign up as a translator. Please be sure to read the required reading list below. <br />
<br />
After you add your username to the list below under the appropriate language heading, a [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator you can start translating! Please be on the look out for a [[Template:Translator welcome|welcome message]] with more information posted to your user talk page.<br />
<br />
{{tip|title=<translate>New to contributing to Joomla! Documentation?</translate>|text=<translate>If you're new to helping with Joomla! Documentation, and have come to this page as a starting point, we suggest you start at the [[JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|How to Contribute to Joomla! Documentation]] page instead.</translate>}}<br />
<br />
{{-}}<br />
<br />
==Required Reading==<br />
* Getting started with contributing to Joomla! Documentation, [[S:MyLanguage/JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|start here]].<br />
* Getting started translating, read [[S:MyLanguage/JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]<br />
* Detailed explanation of translating, [[S:MyLanguage/JDOC:Page Translation Explained|Page Translation Explained]].<br />
* Our [[S:MyLanguage/JDOC:Language policy|Language policy]]<br />
* [[S:MyLanguage/JDOC:Translator Tips|Translator Tips]]<br />
* [[S:MyLanguage/Joomla:JDOC%27s_Translation_Guidelines|Translation Guidelines]]<br />
* Having an [[S:MyLanguage/JDOC:Translation Questions|issue or need help]]?<br />
<br />
{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}<br />
<br />
===Add Your Language===<br />
If your language isn't listed below, please add it using the format:<br />
<br />
<code><lang code> - Localised language name - English language name </code><br />
<br />
Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code><br />
<br />
When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.<br />
<br />
==Current Translations Teams==<br />
<br />
Documentation language codes are different from Joomla! language codes, they are ISO 639-1 2 letter code. A small quantity of 4 letter language codes are used as an exception, but these language codes are all lowercase.<br />
<br />
=== ar - عربي - arabe ===<br />
* {{User|ghilo}}<br />
* {{User|HawraMilani}}<br />
* {{User|hossen}}<br />
* {{User|ahmadm42}}<br />
<br />
=== af - Afrikaans ===<br />
*{{User|JoeSA}}<br />
*{{User|Llewellyn}}<br />
<br />
=== as - অসমীয়া - Assamese ===<br />
*{{User|Mohsin Ali}}<br />
<br />
=== az - Azərbaycan - Azerbaijani ===<br />
* {{User|Special}} - requested<br />
<br />
=== be - Беларуская - Belarusian ===<br />
* {{User|Nikolice}}<br />
<br />
=== bg - Български - Bulgarian ===<br />
* {{User|bdimov}}<br />
* {{User|Mastwd}}<br />
<br />
=== bn - বাংলা - Bengali ===<br />
* {{User|ashiks}}<br />
* {{User|shamsbd71}}<br />
* {{User|theanamhossain}}<br />
* {{User|Azadulkabir455}}<br />
<br />
=== ca - Català - Catalan === <br />
* {{User|el_libre}}<br />
<br />
=== cs - Čeština - Czech ===<br />
* {{User|fredericco-cz}}<br />
* {{User|Bart}}<br />
* {{User|n3tcz}}<br />
* {{User|svatas}}<br />
<br />
=== cy - Cymraeg - Welsh ===<br />
* {{User|Dyfrig}}<br />
<br />
=== da - Dansk - Danish ===<br />
* {{User|ot2sen}}<br />
* {{User|rbuelund}}<br />
* {{User|BBRA}}<br />
<br />
=== de - Deutsch - German ===<br />
* {{User|Astridx}}<br />
* {{User|Assmann}}<br />
* {{User|Alexander-metzler}}<br />
* {{User|Balzercomp}}<br />
* {{User|Batmin}}<br />
* {{User|bbkSecond}}<br />
* {{User|Blancanieve}}<br />
* {{User|blueforce}}<br />
* {{User|ceus1984}}<br />
* {{User|Chmst}}<br />
* {{User|chrishoefliger}}<br />
* {{User|David0296}}<br />
* {{User|Dimkk}}<br />
* {{User|Drmenzelit}}<br />
* {{User|es_ka}}<br />
* {{User|FancyFranci}}<br />
* {{User|Farrell}}<br />
* {{User|Florian}}<br />
* {{User|FLin1}}<br />
* {{User|FrankyD}}<br />
* {{User|Franz.wohlkoenig}}<br />
* {{User|fruppel}}<br />
* {{User|goethe}}<br />
* {{User|gorgonz}}<br />
* {{User|Hleithner}}<br />
* {{User|Indigo66}}<br />
* {{User|Isarbella}}<br />
* {{User|jehacgn}}<br />
* {{User|joomla-agency}}<br />
* {{User|Joomti}}<br />
* {{User|Ka3media}}<br />
* {{User|King_Louis_1}}<br />
* {{User|Knig.Markus}}<br />
* {{User|Kolvar}}<br />
* {{User|Krauthos}}<br />
* {{User|Kurztipp}}<br />
* {{User|LadySolveig}}<br />
* {{User|m-b-o}}<br />
* {{User|Maggus}}<br />
* {{User|MAIN}}<br />
* {{User|Max123kl}}<br />
* {{User|McWiesl}}<br />
* {{User|michaelmyk}}<br />
* {{User|Nathan.k}}<br />
* {{User|oliverhh}}<br />
* {{User|Paterna}}<br />
* {{User|Pc-doppler}}<br />
* {{User|Pete71}}<br />
* {{User|phillopp}}<br />
* {{User|plocher}}<br />
* {{User|Prof.Logout}}<br />
* {{User|quiltgabi}}<br />
* {{User|RMajewski}}<br />
* {{User|Redback}}<br />
* {{User|Schmidie64}}<br />
* {{User|SeigetsuShoen}}<br />
* {{User|Sieger66}}<br />
* {{User|Sisko1990}}<br />
* {{User|Spannama}}<br />
* {{User|Stefanie}}<br />
* {{User|tfecha}}<br />
* {{User|Tkahl}}<br />
* {{User|UCFnet002}}<br />
* {{User|Usimon}}<br />
* {{User|Uta}}<br />
* {{User|Webberry}}<br />
* {{User|Yvesh}}<br />
* {{User|zero24}}<br />
* {{User|Xadomir}}<br />
* {{User|Vovos}}<br />
* {{User|waldiwhz}}<br />
* {{User|Widmann}}<br />
* {{User|Zeroweb1}}<br />
* {{User|Zeroweb2}}<br />
* {{User|RobertMittl}}<br />
* {{User|Jeswanth}}<br />
<br />
=== el - Ελληνικά - Greek ===<br />
* {{User|Aris_Ntatsis}}<br />
* {{User|Tonia_Chan}}<br />
* {{User|Alphapi}}<br />
* {{User|Alcaeusd}}<br />
* {{User|TaDrik}}<br />
* {{User|SiteworksGr}}<br />
* {{User|pnkr}}<br />
* {{User|Gfakas}}<br />
* {{User|Stekarag}}<br />
* {{User|Proudpixel}}<br />
* {{User|Tropos}}<br />
* {{User|ARTIFIEDWEB}}<br />
* {{User|Fotis}}<br />
<br />
=== es - Español - Spanish ===<br />
* {{User|Abulafia}}<br />
* {{User|AlejandroVega}}<br />
* {{User|Alejoasotelo}}<br />
* {{User|Andrea Gentil}}<br />
* {{user|Antoniofmunoz}}<br />
* {{User|BNovoa.S}}<br />
* {{User|brucevalle}}<br />
* {{User|carcam}}<br />
* {{User|cristobal.vio}}<br />
* {{User|Crsanchez}}<br />
* {{User|danielperaza}}<br />
* {{User|duoduo}}<br />
* {{User|filisfutsarov}}<br />
* {{User|framon}}<br />
* {{User|Irene.lopez}}<br />
* {{User|isidrobaq}}<br />
* {{User|ivanramosnet}}<br />
* {{User|Javiparati}}<br />
* {{User|Jcollver}}<br />
* {{User|Jolfig}}<br />
* {{User|Koa}}<br />
* {{User|Leo_Soto}}<br />
* {{User|netandsoftware}}<br />
* {{User|NunoLopes}}<br />
* {{User|Maikolort}} - requested<br />
* {{User|Pabloarias}}<br />
* {{User|pdavila2709}}<br />
* {{User|pfvidal}}<br />
* {{User|Quivro}}<br />
* {{User|shaz}}<br />
* {{User|Urielmx}}<br />
* {{User|VictorYork87}}<br />
* {{User|viena}}<br />
* {{User|Willin}}<br />
* {{User|ITEtnonautas}}<br />
<br />
=== et - Eesti - Estonian ===<br />
* {{User|Eraser}}<br />
<br />
=== fa - فارسی - Persian ===<br />
* {{User|azolfagharj}}<br />
* {{User|Grand}}<br />
* {{User|Heydari}}<br />
* {{User|Joomlafarsi}}<br />
* {{User|Levelup}}<br />
* {{User|mhehm}}<br />
* {{User|ٰVahid}}<br />
<br />
=== fr - Français - French ===<br />
* {{User|alatak}}<br />
* {{User|david613}}<br />
* {{User|Cavo789}}<br />
* {{User|Christophe}}<br />
* {{User|Daneel}}<br />
* {{User|edelouche}}<br />
* {{User|Erix}}<br />
* {{User|Garstud}}<br />
* {{User|Lorangerart}}<br />
* {{User|MaximeK7}}<br />
* {{User|Opware2000}}<br />
* {{User|Patpat}}<br />
* {{User|Perete}}<br />
* {{User|Remi1945}}<br />
* {{User|Sandra97}}<br />
* {{User|Serge}}<br />
* {{User|Shim-sao}}<br />
* {{User|Thefbi}}<br />
* {{User|Thierry}}<br />
* {{User|Twister65}}<br />
* {{User|wisgar}}<br />
* {{User|smilecollector}}<br />
* {{User|Valky68}}<br />
* {{User|mkylmr}}<br />
<br />
=== ga - Gaeilge - Irish ===<br />
* {{User|rvbgnu}}<br />
<br />
=== he - עברית - Hebrew ===<br />
* {{User|ydl}}<br />
* {{User|shirdesign}}<br />
<br />
=== hi - हिंदी - Hindi ===<br />
* {{User|AlamM}}<br />
* {{User|Rana}}<br />
* {{User|JatinSalve}}<br />
* {{User|Syhussaini}}<br />
* {{User|Shivamrajput}}<br />
* {{User|ankitify}}<br />
<br />
=== hr - Hrvatski - Croatian ===<br />
* {{User|limoo}}<br />
<br />
=== hu - Magyar - Hungarian ===<br />
* {{User|Balazs}}<br />
* {{User|webgobe}}<br />
<br />
=== hy - Հայերեն - Armenian ===<br />
* {{User|Aaleksanyants}}<br />
<br />
=== id - Bahasa Indonesia - Indonesian ===<br />
* {{User|dw1Rianto}}<br />
* {{User|Micokelana}}<br />
* {{User|sikumbang}}<br />
<br />
=== it - Italiano - Italian ===<br />
* {{User|alexred}}<br />
* {{User|aleorco}}<br />
* {{User|alikon}}<br />
* {{User|Andreacarriero}}<br />
* {{User|CinziaDesign}}<br />
* {{User|donato}}<br />
* {{User|ino}}<br />
* {{User|Ladyj}}<br />
* {{User|Luca.marzo}}<br />
* {{User|marioluciani}}<br />
* {{User|moqui}}<br />
* {{User|nemo_bis}} (occasionally)<br />
* {{User|Paolo Alberti}}<br />
* {{User|Fabio Caracciolo}}<br />
* {{User|robertolongo}}<br />
* {{User|ste}}<br />
* {{User|Ing Pulizzi}}<br />
* {{User|Davidemessia}}<br />
* {{User|NioBee}}<br />
* {{User|Aurora}}<br />
* {{User|Cristina Martorana}}<br />
* {{User|Razzo}}<br />
* {{User|Sportegioco}}<br />
* {{User|ITEtnonautas}}<br />
<br />
=== ja - 日本語 - Japanese ===<br />
* {{User|Koji Hijikuro}}<br />
* {{User|Nishikawa}}<br />
* {{User|Nori}}<br />
* {{User|Richell}}<br />
* {{User|Yama}}<br />
* {{User|Yui}}<br />
<br />
=== lg - Luganda ===<br />
*{{User|Bongomindaniel}}<br />
<br />
=== nl - Nederlands - Dutch ===<br />
* {{User|HildaAbbing}}<br />
* {{User|AboutTime}}<br />
* {{User|Alex0703}}<br />
* {{User|Annemiek}}<br />
* {{User|Arkomat}}<br />
* {{User|BCWebdesign}}<br />
* {{User|crommie}}<br />
* {{User|Grubosoft}}<br />
* {{User|fcschippers}}<br />
* {{User|HermanPeeren}}<br />
* {{User|Hvdmeer}}<br />
* {{User|janvankuijk}}<br />
* {{User|John Flour}}<br />
* {{User|JorSanders}}<br />
* {{User|Josien}}<br />
* {{User|LtB}}<br />
* {{User|Lianne}}<br />
* {{User|klatte88}}<br />
* {{User|ManuAmpe}}<br />
* {{User|Marcelk}}<br />
* {{User|marionnijhuis}}<br />
* {{User|Marnix}}<br />
* {{User|MartijnM}}<br />
* {{User|Meta}}<br />
* {{User|metdick}}<br />
* {{User|Mtb}}<br />
* {{User|n9iels}}<br />
* {{User|Nemphias}}<br />
* {{User|Nico-van-Leeuwen}}<br />
* {{User|Onderzoekspraktijk}}<br />
* {{User|12pooh}}<br />
* {{User|rachel73}}<br />
* {{User|Renem}}<br />
* {{User|Ries}}<br />
* {{User|Rineke}}<br />
* {{User|Schrijvers123}}<br />
* {{User|slibbe}}<br />
* {{User|Sloekers}}<br />
* {{User|Stitch123}}<br />
* {{User|Vertaalbirdy}}<br />
* {{User|webmiep}}<br />
* {{User|Webcase}}<br />
* {{User|webcatsolutions}}<br />
* {{User|willoweb}}<br />
* {{User|wimstrik}}<br />
* {{User|Astrid}} - requested<br />
<br />
=== pl - Polski - Polish ===<br />
* {{User|Vaco}}<br />
* {{User|Derek}}<br />
* {{User|justyna}}<br />
* {{User|MiloW}}<br />
* {{User|Zwiastun}}<br />
<br />
=== pt - Português (Portugal) - Portuguese (Portugal) ===<br />
* {{User|Djesus}}<br />
* {{User|Horus_68}}<br />
* {{User|Lampreia Lopes}}<br />
* {{User|Mansil}}<br />
* {{User|Nunof}}<br />
* {{User|NunoLopes}}<br />
* {{User|Ricardo.fusco}}<br />
<br />
=== pt-br - Português Brasil - Brazilian Portuguese ===<br />
* {{User|Airton}}<br />
* {{User|alangustavo}}<br />
* {{User|AleMorettiSan}}<br />
* {{User|Anabarcellos}}<br />
* {{User|Ariadnepinheiro}}<br />
* {{User|Belisards}}<br />
* {{User|Ctiburski}}<br />
* {{User|Dagoberto}}<br />
* {{User|DiLeu}}<br />
* {{User|Filipetorres}}<br />
* {{User|gkiyoshinishimoto}}<br />
* {{User|Gleisonsoares}}<br />
* {{User|Helvecio}}<br />
* {{User|Henrydouglas}}<br />
* {{User|Jeann Wilson}}<br />
* {{User|Juliano.freitas}}<br />
* {{User|Murilotimo}}<br />
* {{User|VitorAdonai}}<br />
* {{User|Vizetti}}<br />
* {{User|Welkson Ramos}}<br />
<br />
=== ro - Română - Romanian ===<br />
* {{User|andreeastefan}}<br />
* {{User|isac}}<br />
* {{User|Dudi161}}<br />
<br />
=== ru - Русский - Russian ===<br />
* {{User|AlexSmirnov}}<br />
* {{User|Antonio3}}<br />
* {{User|b2z}}<br />
* {{User|cadko}}<br />
* {{User|Cronolio}}<br />
* {{User|Dosfanat}}<br />
* {{User|Dzandut}}<br />
* {{User|Igor}}<br />
* {{User|Kanta}}<br />
* {{User|Leo240}}<br />
* {{User|Nikitm}}<br />
* {{User|Nikolice}}<br />
* {{User|Serg SSN}}<br />
* {{User|Vyatka}}<br />
* {{User|Yambergaa}}<br />
* {{User|Powercoder}}<br />
* {{User|Sergeytolkachyov}}<br />
* {{User|Mazay}}<br />
* {{User|Iwsby}}<br />
<br />
=== si - සිංහල - Sinhala ===<br />
* {{User|helabasa}}<br />
* {{User|Yasirunilan}}<br />
* {{User|Supun}}<br />
<br />
=== sk - Slovenčina - Slovak ===<br />
* {{User|adambako}}<br />
<br />
=== sw - Kiswahili ===<br />
*<br />
<br />
=== yu - Srpski (Latin) - Serbian (Latin) ===<br />
* {{User|novii}}<br />
<br />
=== sr - Српски (Ћирилица) - Serbian (Cyrillic) ===<br />
* {{User|novii}}<br />
<br />
=== sv - Svenska - Swedish ===<br />
* {{User|Propellerhuvud}}<br />
* {{User|Sgagner}}<br />
<br />
=== sw - Kiswahili - Swahili ===<br />
* {{User|Ayeko}}<br />
<br />
=== th - ไทย - Thai ===<br />
* {{User|Supachai_chai}}<br />
* {{User|Mrs.siam}}<br />
* {{User|Ariesanywhere}}<br />
<br />
=== tr - Türkçe - Turkish ===<br />
* {{User|Ugur}}<br />
* {{User|Umitkenan}<br />
* {{User|GokhanDumlu}}<br />
<br />
=== ukr - Українська - Ukrainian ===<br />
* {{User|Olesya6968ak}}<br />
* {{User|sera527}}<br />
* {{User|trv}}<br />
<br />
=== ur - ur-PK - اردو - Urdu Pakistan ===<br />
* {{User|sayfrndship}} - requested<br />
* {{User|hoornayyer}}<br />
<br />
=== vec - Veneto - Vèneto ===<br />
* {{User|ino}}<br />
<br />
=== vi - Tiếng Việt - Vietnamese ===<br />
* {{User|huyhoa}}<br />
<br />
=== zh - 中文 - Chinese ===<br />
* {{User|asika32764}}<br />
* {{User|eyesofkids}}<br />
* {{User|Guozhanfeng}}<br />
* {{User|KellyXYM}}<br />
* {{User|lai32290}}<br />
* {{User|Mori0725ken}}<br />
* {{User|myskies}}<br />
* {{User|Wulijun01234}}<br />
* {{User|Zace}}<br />
* {{User|Zhang19min88}}<br />
* {{User|Zhous98}}<br />
* {{User|ryle}}<br />
<br />
=== zh-tw - 繁體中文 - Traditional Chinese ===<br />
* {{User|Yuhoward}}<br />
* {{User|shawnhy}}<br />
<br />
==Translation Administrators==<br />
<br />
The responsibilities of a Translation Administrator will require slightly more attention to the documents for translation. Translation Administrators should feel comfortable with using wiki markup, made hundreds of contributions to their specific language and assisted others in translation of docs. Administrators will need to check the documentation every few days and perform any required tasks. These tasks include re-marking pages in en-GB with edit changes, tracking language units which need translation and welcoming new translators. Ideally, we should have at least one Translation Administrator who will not be tied to any specific language and when the time comes, one Translation Administrator for active language teams.<br />
<br />
===Current Volunteer Translation Administrators===<br />
{{:Special:ListUsers/translationadmins}}<br />
<br />
==Common Language Codes==<br />
<div class="small-4 columns"> afr - Afrikaans - Afrikaans<br />
</div><div class="small-4 columns"> ar - عربي - Arabic<br />
</div><div class="small-4 columns"> as - অসমীয়া - Assamese<br />
</div><div class="small-4 columns"> az - Azərbaycan - Azerbaijani<br />
</div><div class="small-4 columns"> be - Беларуская - Belarusian<br />
</div><div class="small-4 columns"> bg - Български - Bulgarian<br />
</div><div class="small-4 columns"> bn - বাংলা - Bengali<br />
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan<br />
</div><div class="small-4 columns"> ca - Català - Catalan<br />
</div><div class="small-4 columns"> ce - Nohçi - Chechen<br />
</div><div class="small-4 columns"> da - Dansk - Danish<br />
</div><div class="small-4 columns"> de - Deutsch - German<br />
</div><div class="small-4 columns"> es - Español - Spanish<br />
</div><div class="small-4 columns"> fa - فارسی - Persian<br />
</div><div class="small-4 columns"> fi - Suomi - Finnish<br />
</div><div class="small-4 columns"> fr - Français - French<br />
</div><div class="small-4 columns"> hu - Magyar - Hungarian<br />
</div><div class="small-4 columns"> hy - Հայերեն - Armenian<br />
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian<br />
</div><div class="small-4 columns"> is - Íslenska - Icelandic<br />
</div><div class="small-4 columns"> it - Italiano - Italian<br />
</div><div class="small-4 columns"> ja - 日本語 - Japanese<br />
</div><div class="small-4 columns"> ko - 한국어 - Korean<br />
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish<br />
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang<br />
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam<br />
</div><div class="small-4 columns"> mr - मराठी - Marathi<br />
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay<br />
</div><div class="small-4 columns"> nl - Nederlands - Dutch<br />
</div><div class="small-4 columns"> pl - Polski - Polish<br />
</div><div class="small-4 columns"> pt - Português - Portuguese<br />
</div><div class="small-4 columns"> pt-br - Português do Brasil - Brazilian Portuguese<br />
</div><div class="small-4 columns"> ro - Română - Romanian<br />
</div><div class="small-4 columns"> ru - Русский - Russian<br />
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók<br />
</div><div class="small-4 columns"> sq - Shqip - Albanian<br />
</div><div class="small-4 columns"> sv - Svenska - Swedish<br />
</div><div class="small-4 columns"> sw - Kiswahili - Swahili<br />
</div><div class="small-4 columns"> ta - தமிழ் - Tamil<br />
</div><div class="small-4 columns"> th - ไทย - Thai<br />
</div><div class="small-4 columns"> tr - Türkçe - Turkish<br />
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese<br />
</div><div class="small-4 columns"> zh - 中文 - Chinese<br />
</div><div class="small-4 columns"> zh-tw - 繁體中文 - Traditional Chinese<br />
</div><br />
<br />
<noinclude><br />
[[Category:Documentation Wiki Policies and Guidelines{{#translation:}}]]<br />
[[Category:Documentation Translation{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Thefbi&diff=1000121User talk:Thefbi2023-03-15T10:52:59Z<p>Sandra97: Created page with "{{Translator welcome}} (~~~~)"</p>
<hr />
<div>{{Translator welcome}} ([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 05:52, 15 March 2023 (CDT))</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=JDOC:Documentation_Translators&diff=1000120JDOC:Documentation Translators2023-03-15T10:52:42Z<p>Sandra97: /* fr - Français - French */</p>
<hr />
<div>[[File:JDOC translation icon.png|right]]<br />
Here, people '''translating''' {{SITENAME}} can sign up as a translator. Please be sure to read the required reading list below. <br />
<br />
After you add your username to the list below under the appropriate language heading, a [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator you can start translating! Please be on the look out for a [[Template:Translator welcome|welcome message]] with more information posted to your user talk page.<br />
<br />
{{tip|title=<translate>New to contributing to Joomla! Documentation?</translate>|text=<translate>If you're new to helping with Joomla! Documentation, and have come to this page as a starting point, we suggest you start at the [[JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|How to Contribute to Joomla! Documentation]] page instead.</translate>}}<br />
<br />
{{-}}<br />
<br />
==Required Reading==<br />
* Getting started with contributing to Joomla! Documentation, [[S:MyLanguage/JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|start here]].<br />
* Getting started translating, read [[S:MyLanguage/JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]<br />
* Detailed explanation of translating, [[S:MyLanguage/JDOC:Page Translation Explained|Page Translation Explained]].<br />
* Our [[S:MyLanguage/JDOC:Language policy|Language policy]]<br />
* [[S:MyLanguage/JDOC:Translator Tips|Translator Tips]]<br />
* [[S:MyLanguage/Joomla:JDOC%27s_Translation_Guidelines|Translation Guidelines]]<br />
* Having an [[S:MyLanguage/JDOC:Translation Questions|issue or need help]]?<br />
<br />
{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}<br />
<br />
===Add Your Language===<br />
If your language isn't listed below, please add it using the format:<br />
<br />
<code><lang code> - Localised language name - English language name </code><br />
<br />
Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code><br />
<br />
When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.<br />
<br />
==Current Translations Teams==<br />
<br />
Documentation language codes are different from Joomla! language codes, they are ISO 639-1 2 letter code. A small quantity of 4 letter language codes are used as an exception, but these language codes are all lowercase.<br />
<br />
=== ar - عربي - arabe ===<br />
* {{User|ghilo}}<br />
* {{User|HawraMilani}}<br />
* {{User|hossen}}<br />
* {{User|ahmadm42}}<br />
<br />
=== af - Afrikaans ===<br />
*{{User|JoeSA}}<br />
*{{User|Llewellyn}}<br />
<br />
=== as - অসমীয়া - Assamese ===<br />
*{{User|Mohsin Ali}}<br />
<br />
=== az - Azərbaycan - Azerbaijani ===<br />
* {{User|Special}} - requested<br />
<br />
=== be - Беларуская - Belarusian ===<br />
* {{User|Nikolice}}<br />
<br />
=== bg - Български - Bulgarian ===<br />
* {{User|bdimov}}<br />
* {{User|Mastwd}}<br />
<br />
=== bn - বাংলা - Bengali ===<br />
* {{User|ashiks}}<br />
* {{User|shamsbd71}}<br />
* {{User|theanamhossain}}<br />
* {{User|Azadulkabir455}}<br />
<br />
=== ca - Català - Catalan === <br />
* {{User|el_libre}}<br />
<br />
=== cs - Čeština - Czech ===<br />
* {{User|fredericco-cz}}<br />
* {{User|Bart}}<br />
* {{User|n3tcz}}<br />
* {{User|svatas}}<br />
<br />
=== cy - Cymraeg - Welsh ===<br />
* {{User|Dyfrig}}<br />
<br />
=== da - Dansk - Danish ===<br />
* {{User|ot2sen}}<br />
* {{User|rbuelund}}<br />
* {{User|BBRA}}<br />
<br />
=== de - Deutsch - German ===<br />
* {{User|Astridx}}<br />
* {{User|Assmann}}<br />
* {{User|Alexander-metzler}}<br />
* {{User|Balzercomp}}<br />
* {{User|Batmin}}<br />
* {{User|bbkSecond}}<br />
* {{User|Blancanieve}}<br />
* {{User|blueforce}}<br />
* {{User|ceus1984}}<br />
* {{User|Chmst}}<br />
* {{User|chrishoefliger}}<br />
* {{User|David0296}}<br />
* {{User|Dimkk}}<br />
* {{User|Drmenzelit}}<br />
* {{User|es_ka}}<br />
* {{User|FancyFranci}}<br />
* {{User|Farrell}}<br />
* {{User|Florian}}<br />
* {{User|FLin1}}<br />
* {{User|FrankyD}}<br />
* {{User|Franz.wohlkoenig}}<br />
* {{User|fruppel}}<br />
* {{User|goethe}}<br />
* {{User|gorgonz}}<br />
* {{User|Hleithner}}<br />
* {{User|Indigo66}}<br />
* {{User|Isarbella}}<br />
* {{User|jehacgn}}<br />
* {{User|joomla-agency}}<br />
* {{User|Joomti}}<br />
* {{User|Ka3media}}<br />
* {{User|King_Louis_1}}<br />
* {{User|Knig.Markus}}<br />
* {{User|Kolvar}}<br />
* {{User|Krauthos}}<br />
* {{User|Kurztipp}}<br />
* {{User|LadySolveig}}<br />
* {{User|m-b-o}}<br />
* {{User|Maggus}}<br />
* {{User|MAIN}}<br />
* {{User|Max123kl}}<br />
* {{User|McWiesl}}<br />
* {{User|michaelmyk}}<br />
* {{User|Nathan.k}}<br />
* {{User|oliverhh}}<br />
* {{User|Paterna}}<br />
* {{User|Pc-doppler}}<br />
* {{User|Pete71}}<br />
* {{User|phillopp}}<br />
* {{User|plocher}}<br />
* {{User|Prof.Logout}}<br />
* {{User|quiltgabi}}<br />
* {{User|RMajewski}}<br />
* {{User|Redback}}<br />
* {{User|Schmidie64}}<br />
* {{User|SeigetsuShoen}}<br />
* {{User|Sieger66}}<br />
* {{User|Sisko1990}}<br />
* {{User|Spannama}}<br />
* {{User|Stefanie}}<br />
* {{User|tfecha}}<br />
* {{User|Tkahl}}<br />
* {{User|UCFnet002}}<br />
* {{User|Usimon}}<br />
* {{User|Uta}}<br />
* {{User|Webberry}}<br />
* {{User|Yvesh}}<br />
* {{User|zero24}}<br />
* {{User|Xadomir}}<br />
* {{User|Vovos}}<br />
* {{User|waldiwhz}}<br />
* {{User|Widmann}}<br />
* {{User|Zeroweb1}}<br />
* {{User|Zeroweb2}}<br />
* {{User|RobertMittl}}<br />
* {{User|Jeswanth}} - requested<br />
<br />
=== el - Ελληνικά - Greek ===<br />
* {{User|Aris_Ntatsis}}<br />
* {{User|Tonia_Chan}}<br />
* {{User|Alphapi}}<br />
* {{User|Alcaeusd}}<br />
* {{User|TaDrik}}<br />
* {{User|SiteworksGr}}<br />
* {{User|pnkr}}<br />
* {{User|Gfakas}}<br />
* {{User|Stekarag}}<br />
* {{User|Proudpixel}}<br />
* {{User|Tropos}}<br />
* {{User|ARTIFIEDWEB}}<br />
* {{User|Fotis}}<br />
<br />
=== es - Español - Spanish ===<br />
* {{User|Abulafia}}<br />
* {{User|AlejandroVega}}<br />
* {{User|Alejoasotelo}}<br />
* {{User|Andrea Gentil}}<br />
* {{user|Antoniofmunoz}}<br />
* {{User|BNovoa.S}}<br />
* {{User|brucevalle}}<br />
* {{User|carcam}}<br />
* {{User|cristobal.vio}}<br />
* {{User|Crsanchez}}<br />
* {{User|danielperaza}}<br />
* {{User|duoduo}}<br />
* {{User|filisfutsarov}}<br />
* {{User|framon}}<br />
* {{User|Irene.lopez}}<br />
* {{User|isidrobaq}}<br />
* {{User|ivanramosnet}}<br />
* {{User|Javiparati}}<br />
* {{User|Jcollver}}<br />
* {{User|Jolfig}}<br />
* {{User|Koa}}<br />
* {{User|Leo_Soto}}<br />
* {{User|netandsoftware}}<br />
* {{User|NunoLopes}}<br />
* {{User|Maikolort}} - requested<br />
* {{User|Pabloarias}}<br />
* {{User|pdavila2709}}<br />
* {{User|pfvidal}}<br />
* {{User|Quivro}}<br />
* {{User|shaz}}<br />
* {{User|Urielmx}}<br />
* {{User|VictorYork87}}<br />
* {{User|viena}}<br />
* {{User|Willin}}<br />
<br />
=== et - Eesti - Estonian ===<br />
* {{User|Eraser}}<br />
<br />
=== fa - فارسی - Persian ===<br />
* {{User|azolfagharj}}<br />
* {{User|Grand}}<br />
* {{User|Heydari}}<br />
* {{User|Joomlafarsi}}<br />
* {{User|Levelup}}<br />
* {{User|mhehm}}<br />
* {{User|ٰVahid}}<br />
<br />
=== fr - Français - French ===<br />
* {{User|alatak}}<br />
* {{User|david613}}<br />
* {{User|Cavo789}}<br />
* {{User|Christophe}}<br />
* {{User|Daneel}}<br />
* {{User|edelouche}}<br />
* {{User|Erix}}<br />
* {{User|Garstud}}<br />
* {{User|Lorangerart}}<br />
* {{User|MaximeK7}}<br />
* {{User|Opware2000}}<br />
* {{User|Patpat}}<br />
* {{User|Perete}}<br />
* {{User|Remi1945}}<br />
* {{User|Sandra97}}<br />
* {{User|Serge}}<br />
* {{User|Shim-sao}}<br />
* {{User|Thefbi}}<br />
* {{User|Thierry}}<br />
* {{User|Twister65}}<br />
* {{User|wisgar}}<br />
* {{User|smilecollector}}<br />
* {{User|Valky68}}<br />
<br />
=== ga - Gaeilge - Irish ===<br />
* {{User|rvbgnu}}<br />
<br />
=== he - עברית - Hebrew ===<br />
* {{User|ydl}}<br />
* {{User|shirdesign}}<br />
<br />
=== hi - हिंदी - Hindi ===<br />
* {{User|AlamM}}<br />
* {{User|Rana}}<br />
* {{User|JatinSalve}}<br />
* {{User|Syhussaini}}<br />
* {{User|Shivamrajput}}<br />
* {{User|ankitify}}<br />
<br />
=== hr - Hrvatski - Croatian ===<br />
* {{User|limoo}}<br />
<br />
=== hu - Magyar - Hungarian ===<br />
* {{User|Balazs}}<br />
* {{User|webgobe}}<br />
<br />
=== hy - Հայերեն - Armenian ===<br />
* {{User|Aaleksanyants}}<br />
<br />
=== id - Bahasa Indonesia - Indonesian ===<br />
* {{User|dw1Rianto}}<br />
* {{User|Micokelana}}<br />
* {{User|sikumbang}}<br />
<br />
=== it - Italiano - Italian ===<br />
* {{User|alexred}}<br />
* {{User|aleorco}}<br />
* {{User|alikon}}<br />
* {{User|Andreacarriero}}<br />
* {{User|CinziaDesign}}<br />
* {{User|donato}}<br />
* {{User|ino}}<br />
* {{User|Ladyj}}<br />
* {{User|Luca.marzo}}<br />
* {{User|marioluciani}}<br />
* {{User|moqui}}<br />
* {{User|nemo_bis}} (occasionally)<br />
* {{User|Paolo Alberti}}<br />
* {{User|Fabio Caracciolo}}<br />
* {{User|robertolongo}}<br />
* {{User|ste}}<br />
* {{User|Ing Pulizzi}}<br />
* {{User|Davidemessia}}<br />
* {{User|NioBee}}<br />
* {{User|Aurora}}<br />
* {{User|Cristina Martorana}}<br />
* {{User|Razzo}}<br />
* {{User|Sportegioco}}<br />
<br />
=== ja - 日本語 - Japanese ===<br />
* {{User|Koji Hijikuro}}<br />
* {{User|Nishikawa}}<br />
* {{User|Nori}}<br />
* {{User|Richell}}<br />
* {{User|Yama}}<br />
* {{User|Yui}}<br />
<br />
=== lg - Luganda ===<br />
*{{User|Bongomindaniel}}<br />
<br />
=== nl - Nederlands - Dutch ===<br />
* {{User|HildaAbbing}}<br />
* {{User|AboutTime}}<br />
* {{User|Alex0703}}<br />
* {{User|Annemiek}}<br />
* {{User|Arkomat}}<br />
* {{User|BCWebdesign}}<br />
* {{User|crommie}}<br />
* {{User|Grubosoft}}<br />
* {{User|fcschippers}}<br />
* {{User|HermanPeeren}}<br />
* {{User|Hvdmeer}}<br />
* {{User|janvankuijk}}<br />
* {{User|John Flour}}<br />
* {{User|JorSanders}}<br />
* {{User|Josien}}<br />
* {{User|LtB}}<br />
* {{User|Lianne}}<br />
* {{User|klatte88}}<br />
* {{User|ManuAmpe}}<br />
* {{User|Marcelk}}<br />
* {{User|marionnijhuis}}<br />
* {{User|Marnix}}<br />
* {{User|MartijnM}}<br />
* {{User|Meta}}<br />
* {{User|metdick}}<br />
* {{User|Mtb}}<br />
* {{User|n9iels}}<br />
* {{User|Nemphias}}<br />
* {{User|Nico-van-Leeuwen}}<br />
* {{User|Onderzoekspraktijk}}<br />
* {{User|12pooh}}<br />
* {{User|rachel73}}<br />
* {{User|Renem}}<br />
* {{User|Ries}}<br />
* {{User|Rineke}}<br />
* {{User|Schrijvers123}}<br />
* {{User|slibbe}}<br />
* {{User|Sloekers}}<br />
* {{User|Stitch123}}<br />
* {{User|Vertaalbirdy}}<br />
* {{User|webmiep}}<br />
* {{User|Webcase}}<br />
* {{User|webcatsolutions}}<br />
* {{User|willoweb}}<br />
* {{User|wimstrik}}<br />
* {{User|Astrid}} - requested<br />
<br />
=== pl - Polski - Polish ===<br />
* {{User|Vaco}}<br />
* {{User|Derek}}<br />
* {{User|justyna}}<br />
* {{User|MiloW}}<br />
* {{User|Zwiastun}}<br />
<br />
=== pt - Português (Portugal) - Portuguese (Portugal) ===<br />
* {{User|Djesus}}<br />
* {{User|Horus_68}}<br />
* {{User|Lampreia Lopes}}<br />
* {{User|Mansil}}<br />
* {{User|Nunof}}<br />
* {{User|NunoLopes}}<br />
* {{User|Ricardo.fusco}}<br />
<br />
=== pt-br - Português Brasil - Brazilian Portuguese ===<br />
* {{User|Airton}}<br />
* {{User|alangustavo}}<br />
* {{User|AleMorettiSan}}<br />
* {{User|Anabarcellos}}<br />
* {{User|Ariadnepinheiro}}<br />
* {{User|Belisards}}<br />
* {{User|Ctiburski}}<br />
* {{User|Dagoberto}}<br />
* {{User|DiLeu}}<br />
* {{User|Filipetorres}}<br />
* {{User|gkiyoshinishimoto}}<br />
* {{User|Gleisonsoares}}<br />
* {{User|Helvecio}}<br />
* {{User|Henrydouglas}}<br />
* {{User|Jeann Wilson}}<br />
* {{User|Juliano.freitas}}<br />
* {{User|Murilotimo}}<br />
* {{User|VitorAdonai}}<br />
* {{User|Vizetti}}<br />
* {{User|Welkson Ramos}}<br />
<br />
=== ro - Română - Romanian ===<br />
* {{User|andreeastefan}}<br />
* {{User|isac}}<br />
* {{User|Dudi161}}<br />
<br />
=== ru - Русский - Russian ===<br />
* {{User|AlexSmirnov}}<br />
* {{User|Antonio3}}<br />
* {{User|b2z}}<br />
* {{User|cadko}}<br />
* {{User|Cronolio}}<br />
* {{User|Dosfanat}}<br />
* {{User|Dzandut}}<br />
* {{User|Igor}}<br />
* {{User|Kanta}}<br />
* {{User|Leo240}}<br />
* {{User|Nikitm}}<br />
* {{User|Nikolice}}<br />
* {{User|Serg SSN}}<br />
* {{User|Vyatka}}<br />
* {{User|Yambergaa}}<br />
* {{User|Powercoder}}<br />
* {{User|Sergeytolkachyov}}<br />
* {{User|Mazay}}<br />
* {{User|Iwsby}}<br />
<br />
=== si - සිංහල - Sinhala ===<br />
* {{User|helabasa}}<br />
* {{User|Yasirunilan}}<br />
* {{User|Supun}}<br />
<br />
=== sk - Slovenčina - Slovak ===<br />
* {{User|adambako}}<br />
<br />
=== sw - Kiswahili ===<br />
*<br />
<br />
=== yu - Srpski (Latin) - Serbian (Latin) ===<br />
* {{User|novii}}<br />
<br />
=== sr - Српски (Ћирилица) - Serbian (Cyrillic) ===<br />
* {{User|novii}}<br />
<br />
=== sv - Svenska - Swedish ===<br />
* {{User|Propellerhuvud}}<br />
* {{User|Sgagner}}<br />
<br />
=== sw - Kiswahili - Swahili ===<br />
* {{User|Ayeko}}<br />
<br />
=== th - ไทย - Thai ===<br />
* {{User|Supachai_chai}}<br />
* {{User|Mrs.siam}}<br />
* {{User|Ariesanywhere}}<br />
<br />
=== tr - Türkçe - Turkish ===<br />
* {{User|Ugur}}<br />
* {{User|Umitkenan}<br />
* {{User|GokhanDumlu}}<br />
<br />
=== ukr - Українська - Ukrainian ===<br />
* {{User|Olesya6968ak}}<br />
* {{User|sera527}}<br />
* {{User|trv}}<br />
<br />
=== ur - ur-PK - اردو - Urdu Pakistan ===<br />
* {{User|sayfrndship}} - requested<br />
* {{User|hoornayyer}}<br />
<br />
=== vec - Veneto - Vèneto ===<br />
* {{User|ino}}<br />
<br />
=== vi - Tiếng Việt - Vietnamese ===<br />
* {{User|huyhoa}}<br />
<br />
=== zh - 中文 - Chinese ===<br />
* {{User|asika32764}}<br />
* {{User|eyesofkids}}<br />
* {{User|Guozhanfeng}}<br />
* {{User|KellyXYM}}<br />
* {{User|lai32290}}<br />
* {{User|Mori0725ken}}<br />
* {{User|myskies}}<br />
* {{User|Wulijun01234}}<br />
* {{User|Zace}}<br />
* {{User|Zhang19min88}}<br />
* {{User|Zhous98}}<br />
* {{User|ryle}}<br />
<br />
=== zh-tw - 繁體中文 - Traditional Chinese ===<br />
* {{User|Yuhoward}}<br />
* {{User|shawnhy}}<br />
<br />
==Translation Administrators==<br />
<br />
The responsibilities of a Translation Administrator will require slightly more attention to the documents for translation. Translation Administrators should feel comfortable with using wiki markup, made hundreds of contributions to their specific language and assisted others in translation of docs. Administrators will need to check the documentation every few days and perform any required tasks. These tasks include re-marking pages in en-GB with edit changes, tracking language units which need translation and welcoming new translators. Ideally, we should have at least one Translation Administrator who will not be tied to any specific language and when the time comes, one Translation Administrator for active language teams.<br />
<br />
===Current Volunteer Translation Administrators===<br />
{{:Special:ListUsers/translationadmins}}<br />
<br />
==Common Language Codes==<br />
<div class="small-4 columns"> afr - Afrikaans - Afrikaans<br />
</div><div class="small-4 columns"> ar - عربي - Arabic<br />
</div><div class="small-4 columns"> as - অসমীয়া - Assamese<br />
</div><div class="small-4 columns"> az - Azərbaycan - Azerbaijani<br />
</div><div class="small-4 columns"> be - Беларуская - Belarusian<br />
</div><div class="small-4 columns"> bg - Български - Bulgarian<br />
</div><div class="small-4 columns"> bn - বাংলা - Bengali<br />
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan<br />
</div><div class="small-4 columns"> ca - Català - Catalan<br />
</div><div class="small-4 columns"> ce - Nohçi - Chechen<br />
</div><div class="small-4 columns"> da - Dansk - Danish<br />
</div><div class="small-4 columns"> de - Deutsch - German<br />
</div><div class="small-4 columns"> es - Español - Spanish<br />
</div><div class="small-4 columns"> fa - فارسی - Persian<br />
</div><div class="small-4 columns"> fi - Suomi - Finnish<br />
</div><div class="small-4 columns"> fr - Français - French<br />
</div><div class="small-4 columns"> hu - Magyar - Hungarian<br />
</div><div class="small-4 columns"> hy - Հայերեն - Armenian<br />
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian<br />
</div><div class="small-4 columns"> is - Íslenska - Icelandic<br />
</div><div class="small-4 columns"> it - Italiano - Italian<br />
</div><div class="small-4 columns"> ja - 日本語 - Japanese<br />
</div><div class="small-4 columns"> ko - 한국어 - Korean<br />
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish<br />
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang<br />
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam<br />
</div><div class="small-4 columns"> mr - मराठी - Marathi<br />
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay<br />
</div><div class="small-4 columns"> nl - Nederlands - Dutch<br />
</div><div class="small-4 columns"> pl - Polski - Polish<br />
</div><div class="small-4 columns"> pt - Português - Portuguese<br />
</div><div class="small-4 columns"> pt-br - Português do Brasil - Brazilian Portuguese<br />
</div><div class="small-4 columns"> ro - Română - Romanian<br />
</div><div class="small-4 columns"> ru - Русский - Russian<br />
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók<br />
</div><div class="small-4 columns"> sq - Shqip - Albanian<br />
</div><div class="small-4 columns"> sv - Svenska - Swedish<br />
</div><div class="small-4 columns"> sw - Kiswahili - Swahili<br />
</div><div class="small-4 columns"> ta - தமிழ் - Tamil<br />
</div><div class="small-4 columns"> th - ไทย - Thai<br />
</div><div class="small-4 columns"> tr - Türkçe - Turkish<br />
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese<br />
</div><div class="small-4 columns"> zh - 中文 - Chinese<br />
</div><div class="small-4 columns"> zh-tw - 繁體中文 - Traditional Chinese<br />
</div><br />
<br />
<noinclude><br />
[[Category:Documentation Wiki Policies and Guidelines{{#translation:}}]]<br />
[[Category:Documentation Translation{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=JDOC:Documentation_Translators&diff=999550JDOC:Documentation Translators2023-03-10T17:06:54Z<p>Sandra97: /* fr - Français - French */</p>
<hr />
<div>[[File:JDOC translation icon.png|right]]<br />
Here, people '''translating''' {{SITENAME}} can sign up as a translator. Please be sure to read the required reading list below. <br />
<br />
After you add your username to the list below under the appropriate language heading, a [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator you can start translating! Please be on the look out for a [[Template:Translator welcome|welcome message]] with more information posted to your user talk page.<br />
<br />
{{tip|title=<translate>New to contributing to Joomla! Documentation?</translate>|text=<translate>If you're new to helping with Joomla! Documentation, and have come to this page as a starting point, we suggest you start at the [[JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|How to Contribute to Joomla! Documentation]] page instead.</translate>}}<br />
<br />
{{-}}<br />
<br />
==Required Reading==<br />
* Getting started with contributing to Joomla! Documentation, [[S:MyLanguage/JDOC:How to Contribute to Joomla! Documentation{{#translation:}}|start here]].<br />
* Getting started translating, read [[S:MyLanguage/JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]<br />
* Detailed explanation of translating, [[S:MyLanguage/JDOC:Page Translation Explained|Page Translation Explained]].<br />
* Our [[S:MyLanguage/JDOC:Language policy|Language policy]]<br />
* [[S:MyLanguage/JDOC:Translator Tips|Translator Tips]]<br />
* [[S:MyLanguage/Joomla:JDOC%27s_Translation_Guidelines|Translation Guidelines]]<br />
* Having an [[S:MyLanguage/JDOC:Translation Questions|issue or need help]]?<br />
<br />
{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}<br />
<br />
===Add Your Language===<br />
If your language isn't listed below, please add it using the format:<br />
<br />
<code><lang code> - Localised language name - English language name </code><br />
<br />
Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code><br />
<br />
When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.<br />
<br />
==Current Translations Teams==<br />
<br />
Documentation language codes are different from Joomla! language codes, they are ISO 639-1 2 letter code. A small quantity of 4 letter language codes are used as an exception, but these language codes are all lowercase.<br />
<br />
=== ar - عربي - arabe ===<br />
* {{User|ghilo}}<br />
* {{User|HawraMilani}}<br />
* {{User|hossen}}<br />
* {{User|ahmadm42}}<br />
<br />
=== af - Afrikaans ===<br />
*{{User|JoeSA}}<br />
*{{User|Llewellyn}}<br />
<br />
=== as - অসমীয়া - Assamese ===<br />
*{{User|Mohsin Ali}}<br />
<br />
=== az - Azərbaycan - Azerbaijani ===<br />
* {{User|Special}} - requested<br />
<br />
=== be - Беларуская - Belarusian ===<br />
* {{User|Nikolice}}<br />
<br />
=== bg - Български - Bulgarian ===<br />
* {{User|bdimov}}<br />
* {{User|Mastwd}}<br />
<br />
=== bn - বাংলা - Bengali ===<br />
* {{User|ashiks}}<br />
* {{User|shamsbd71}}<br />
* {{User|theanamhossain}}<br />
* {{User|Azadulkabir455}}<br />
<br />
=== ca - Català - Catalan === <br />
* {{User|el_libre}}<br />
<br />
=== cs - Čeština - Czech ===<br />
* {{User|fredericco-cz}}<br />
* {{User|Bart}}<br />
* {{User|n3tcz}}<br />
* {{User|svatas}}<br />
<br />
=== cy - Cymraeg - Welsh ===<br />
* {{User|Dyfrig}}<br />
<br />
=== da - Dansk - Danish ===<br />
* {{User|ot2sen}}<br />
* {{User|rbuelund}}<br />
* {{User|BBRA}}<br />
<br />
=== de - Deutsch - German ===<br />
* {{User|Astridx}}<br />
* {{User|Assmann}}<br />
* {{User|Alexander-metzler}}<br />
* {{User|Balzercomp}}<br />
* {{User|Batmin}}<br />
* {{User|bbkSecond}}<br />
* {{User|Blancanieve}}<br />
* {{User|blueforce}}<br />
* {{User|ceus1984}}<br />
* {{User|Chmst}}<br />
* {{User|chrishoefliger}}<br />
* {{User|David0296}}<br />
* {{User|Dimkk}}<br />
* {{User|Drmenzelit}}<br />
* {{User|es_ka}}<br />
* {{User|FancyFranci}}<br />
* {{User|Farrell}}<br />
* {{User|Florian}}<br />
* {{User|FLin1}}<br />
* {{User|FrankyD}}<br />
* {{User|Franz.wohlkoenig}}<br />
* {{User|fruppel}}<br />
* {{User|goethe}}<br />
* {{User|gorgonz}}<br />
* {{User|Hleithner}}<br />
* {{User|Indigo66}}<br />
* {{User|Isarbella}}<br />
* {{User|jehacgn}}<br />
* {{User|joomla-agency}}<br />
* {{User|Joomti}}<br />
* {{User|Ka3media}}<br />
* {{User|King_Louis_1}}<br />
* {{User|Knig.Markus}}<br />
* {{User|Kolvar}}<br />
* {{User|Krauthos}}<br />
* {{User|Kurztipp}}<br />
* {{User|LadySolveig}}<br />
* {{User|m-b-o}}<br />
* {{User|Maggus}}<br />
* {{User|MAIN}}<br />
* {{User|Max123kl}}<br />
* {{User|McWiesl}}<br />
* {{User|michaelmyk}}<br />
* {{User|Nathan.k}}<br />
* {{User|oliverhh}}<br />
* {{User|Paterna}}<br />
* {{User|Pc-doppler}}<br />
* {{User|Pete71}}<br />
* {{User|phillopp}}<br />
* {{User|plocher}}<br />
* {{User|Prof.Logout}}<br />
* {{User|quiltgabi}}<br />
* {{User|RMajewski}}<br />
* {{User|Redback}}<br />
* {{User|Schmidie64}}<br />
* {{User|SeigetsuShoen}}<br />
* {{User|Sieger66}}<br />
* {{User|Sisko1990}}<br />
* {{User|Spannama}}<br />
* {{User|Stefanie}}<br />
* {{User|tfecha}}<br />
* {{User|Tkahl}}<br />
* {{User|UCFnet002}}<br />
* {{User|Usimon}}<br />
* {{User|Uta}}<br />
* {{User|Webberry}}<br />
* {{User|Yvesh}}<br />
* {{User|zero24}}<br />
* {{User|Xadomir}}<br />
* {{User|Vovos}}<br />
* {{User|waldiwhz}}<br />
* {{User|Widmann}}<br />
* {{User|Zeroweb1}}<br />
* {{User|Zeroweb2}}<br />
* {{User|RobertMittl}}<br />
* {{User|Jeswanth}} - requested<br />
<br />
=== el - Ελληνικά - Greek ===<br />
* {{User|Aris_Ntatsis}}<br />
* {{User|Tonia_Chan}}<br />
* {{User|Alphapi}}<br />
* {{User|Alcaeusd}}<br />
* {{User|TaDrik}}<br />
* {{User|SiteworksGr}}<br />
* {{User|pnkr}}<br />
* {{User|Gfakas}}<br />
* {{User|Stekarag}}<br />
* {{User|Proudpixel}}<br />
* {{User|Tropos}}<br />
* {{User|ARTIFIEDWEB}}<br />
* {{User|Fotis}}<br />
<br />
=== es - Español - Spanish ===<br />
* {{User|Abulafia}}<br />
* {{User|AlejandroVega}}<br />
* {{User|Alejoasotelo}}<br />
* {{User|Andrea Gentil}}<br />
* {{user|Antoniofmunoz}}<br />
* {{User|BNovoa.S}}<br />
* {{User|brucevalle}}<br />
* {{User|carcam}}<br />
* {{User|cristobal.vio}}<br />
* {{User|Crsanchez}}<br />
* {{User|danielperaza}}<br />
* {{User|duoduo}}<br />
* {{User|filisfutsarov}}<br />
* {{User|framon}}<br />
* {{User|Irene.lopez}}<br />
* {{User|isidrobaq}}<br />
* {{User|ivanramosnet}}<br />
* {{User|Javiparati}}<br />
* {{User|Jcollver}}<br />
* {{User|Jolfig}}<br />
* {{User|Koa}}<br />
* {{User|Leo_Soto}}<br />
* {{User|netandsoftware}}<br />
* {{User|NunoLopes}}<br />
* {{User|Maikolort}} - requested<br />
* {{User|Pabloarias}}<br />
* {{User|pdavila2709}}<br />
* {{User|pfvidal}}<br />
* {{User|Quivro}}<br />
* {{User|shaz}}<br />
* {{User|Urielmx}}<br />
* {{User|VictorYork87}}<br />
* {{User|viena}}<br />
* {{User|Willin}}<br />
<br />
=== et - Eesti - Estonian ===<br />
* {{User|Eraser}}<br />
<br />
=== fa - فارسی - Persian ===<br />
* {{User|azolfagharj}}<br />
* {{User|Grand}}<br />
* {{User|Heydari}}<br />
* {{User|Joomlafarsi}}<br />
* {{User|Levelup}}<br />
* {{User|mhehm}}<br />
* {{User|ٰVahid}}<br />
<br />
=== fr - Français - French ===<br />
* {{User|alatak}}<br />
* {{User|david613}}<br />
* {{User|Cavo789}}<br />
* {{User|Christophe}}<br />
* {{User|Daneel}}<br />
* {{User|edelouche}}<br />
* {{User|Erix}}<br />
* {{User|Garstud}}<br />
* {{User|Lorangerart}}<br />
* {{User|MaximeK7}}<br />
* {{User|Opware2000}}<br />
* {{User|Patpat}}<br />
* {{User|Perete}}<br />
* {{User|Remi1945}}<br />
* {{User|Sandra97}}<br />
* {{User|Serge}}<br />
* {{User|Shim-sao}}<br />
* {{User|Thierry}}<br />
* {{User|Twister65}}<br />
* {{User|wisgar}}<br />
* {{User|smilecollector}}<br />
* {{User|Valky68}}<br />
<br />
=== ga - Gaeilge - Irish ===<br />
* {{User|rvbgnu}}<br />
<br />
=== he - עברית - Hebrew ===<br />
* {{User|ydl}}<br />
* {{User|shirdesign}}<br />
<br />
=== hi - हिंदी - Hindi ===<br />
* {{User|AlamM}}<br />
* {{User|Rana}}<br />
* {{User|JatinSalve}}<br />
* {{User|Syhussaini}}<br />
* {{User|Shivamrajput}}<br />
* {{User|ankitify}}<br />
<br />
=== hr - Hrvatski - Croatian ===<br />
* {{User|limoo}}<br />
<br />
=== hu - Magyar - Hungarian ===<br />
* {{User|Balazs}}<br />
* {{User|webgobe}}<br />
<br />
=== hy - Հայերեն - Armenian ===<br />
* {{User|Aaleksanyants}}<br />
<br />
=== id - Bahasa Indonesia - Indonesian ===<br />
* {{User|dw1Rianto}}<br />
* {{User|Micokelana}}<br />
* {{User|sikumbang}}<br />
<br />
=== it - Italiano - Italian ===<br />
* {{User|alexred}}<br />
* {{User|aleorco}}<br />
* {{User|alikon}}<br />
* {{User|Andreacarriero}}<br />
* {{User|CinziaDesign}}<br />
* {{User|donato}}<br />
* {{User|ino}}<br />
* {{User|Ladyj}}<br />
* {{User|Luca.marzo}}<br />
* {{User|marioluciani}}<br />
* {{User|moqui}}<br />
* {{User|nemo_bis}} (occasionally)<br />
* {{User|Paolo Alberti}}<br />
* {{User|Fabio Caracciolo}}<br />
* {{User|robertolongo}}<br />
* {{User|ste}}<br />
* {{User|Ing Pulizzi}}<br />
* {{User|Davidemessia}}<br />
* {{User|NioBee}}<br />
* {{User|Aurora}}<br />
* {{User|Cristina Martorana}}<br />
* {{User|Razzo}}<br />
* {{User|Sportegioco}}<br />
<br />
=== ja - 日本語 - Japanese ===<br />
* {{User|Koji Hijikuro}}<br />
* {{User|Nishikawa}}<br />
* {{User|Nori}}<br />
* {{User|Richell}}<br />
* {{User|Yama}}<br />
* {{User|Yui}}<br />
<br />
=== lg - Luganda ===<br />
*{{User|Bongomindaniel}}<br />
<br />
=== nl - Nederlands - Dutch ===<br />
* {{User|HildaAbbing}}<br />
* {{User|AboutTime}}<br />
* {{User|Alex0703}}<br />
* {{User|Annemiek}}<br />
* {{User|Arkomat}}<br />
* {{User|BCWebdesign}}<br />
* {{User|crommie}}<br />
* {{User|Grubosoft}}<br />
* {{User|fcschippers}}<br />
* {{User|HermanPeeren}}<br />
* {{User|Hvdmeer}}<br />
* {{User|janvankuijk}}<br />
* {{User|John Flour}}<br />
* {{User|JorSanders}}<br />
* {{User|Josien}}<br />
* {{User|LtB}}<br />
* {{User|Lianne}}<br />
* {{User|klatte88}}<br />
* {{User|ManuAmpe}}<br />
* {{User|Marcelk}}<br />
* {{User|marionnijhuis}}<br />
* {{User|Marnix}}<br />
* {{User|MartijnM}}<br />
* {{User|Meta}}<br />
* {{User|metdick}}<br />
* {{User|Mtb}}<br />
* {{User|n9iels}}<br />
* {{User|Nemphias}}<br />
* {{User|Nico-van-Leeuwen}}<br />
* {{User|Onderzoekspraktijk}}<br />
* {{User|12pooh}}<br />
* {{User|rachel73}}<br />
* {{User|Renem}}<br />
* {{User|Ries}}<br />
* {{User|Rineke}}<br />
* {{User|Schrijvers123}}<br />
* {{User|slibbe}}<br />
* {{User|Sloekers}}<br />
* {{User|Stitch123}}<br />
* {{User|Vertaalbirdy}}<br />
* {{User|webmiep}}<br />
* {{User|Webcase}}<br />
* {{User|webcatsolutions}}<br />
* {{User|willoweb}}<br />
* {{User|wimstrik}}<br />
* {{User|Astrid}} - requested<br />
<br />
=== pl - Polski - Polish ===<br />
* {{User|Vaco}}<br />
* {{User|Derek}}<br />
* {{User|justyna}}<br />
* {{User|MiloW}}<br />
* {{User|Zwiastun}}<br />
<br />
=== pt - Português (Portugal) - Portuguese (Portugal) ===<br />
* {{User|Djesus}}<br />
* {{User|Horus_68}}<br />
* {{User|Lampreia Lopes}}<br />
* {{User|Mansil}}<br />
* {{User|Nunof}}<br />
* {{User|NunoLopes}}<br />
* {{User|Ricardo.fusco}}<br />
<br />
=== pt-br - Português Brasil - Brazilian Portuguese ===<br />
* {{User|Airton}}<br />
* {{User|alangustavo}}<br />
* {{User|AleMorettiSan}}<br />
* {{User|Anabarcellos}}<br />
* {{User|Ariadnepinheiro}}<br />
* {{User|Belisards}}<br />
* {{User|Ctiburski}}<br />
* {{User|Dagoberto}}<br />
* {{User|DiLeu}}<br />
* {{User|Filipetorres}}<br />
* {{User|gkiyoshinishimoto}}<br />
* {{User|Gleisonsoares}}<br />
* {{User|Helvecio}}<br />
* {{User|Henrydouglas}}<br />
* {{User|Jeann Wilson}}<br />
* {{User|Juliano.freitas}}<br />
* {{User|Murilotimo}}<br />
* {{User|VitorAdonai}}<br />
* {{User|Vizetti}}<br />
* {{User|Welkson Ramos}}<br />
<br />
=== ro - Română - Romanian ===<br />
* {{User|andreeastefan}}<br />
* {{User|isac}}<br />
* {{User|Dudi161}}<br />
<br />
=== ru - Русский - Russian ===<br />
* {{User|AlexSmirnov}}<br />
* {{User|Antonio3}}<br />
* {{User|b2z}}<br />
* {{User|cadko}}<br />
* {{User|Cronolio}}<br />
* {{User|Dosfanat}}<br />
* {{User|Dzandut}}<br />
* {{User|Igor}}<br />
* {{User|Kanta}}<br />
* {{User|Leo240}}<br />
* {{User|Nikitm}}<br />
* {{User|Nikolice}}<br />
* {{User|Serg SSN}}<br />
* {{User|Vyatka}}<br />
* {{User|Yambergaa}}<br />
* {{User|Powercoder}}<br />
* {{User|Sergeytolkachyov}}<br />
* {{User|Mazay}}<br />
* {{User|Iwsby}}<br />
<br />
=== si - සිංහල - Sinhala ===<br />
* {{User|helabasa}}<br />
* {{User|Yasirunilan}}<br />
* {{User|Supun}}<br />
<br />
=== sk - Slovenčina - Slovak ===<br />
* {{User|adambako}}<br />
<br />
=== sw - Kiswahili ===<br />
*<br />
<br />
=== yu - Srpski (Latin) - Serbian (Latin) ===<br />
* {{User|novii}}<br />
<br />
=== sr - Српски (Ћирилица) - Serbian (Cyrillic) ===<br />
* {{User|novii}}<br />
<br />
=== sv - Svenska - Swedish ===<br />
* {{User|Propellerhuvud}}<br />
* {{User|Sgagner}}<br />
<br />
=== sw - Kiswahili - Swahili ===<br />
* {{User|Ayeko}}<br />
<br />
=== th - ไทย - Thai ===<br />
* {{User|Supachai_chai}}<br />
* {{User|Mrs.siam}}<br />
* {{User|Ariesanywhere}}<br />
<br />
=== tr - Türkçe - Turkish ===<br />
* {{User|Ugur}}<br />
* {{User|Umitkenan}<br />
* {{User|GokhanDumlu}}<br />
<br />
=== ukr - Українська - Ukrainian ===<br />
* {{User|Olesya6968ak}}<br />
* {{User|sera527}}<br />
* {{User|trv}}<br />
<br />
=== ur - ur-PK - اردو - Urdu Pakistan ===<br />
* {{User|sayfrndship}} - requested<br />
* {{User|hoornayyer}}<br />
<br />
=== vec - Veneto - Vèneto ===<br />
* {{User|ino}}<br />
<br />
=== vi - Tiếng Việt - Vietnamese ===<br />
* {{User|huyhoa}}<br />
<br />
=== zh - 中文 - Chinese ===<br />
* {{User|asika32764}}<br />
* {{User|eyesofkids}}<br />
* {{User|Guozhanfeng}}<br />
* {{User|KellyXYM}}<br />
* {{User|lai32290}}<br />
* {{User|Mori0725ken}}<br />
* {{User|myskies}}<br />
* {{User|Wulijun01234}}<br />
* {{User|Zace}}<br />
* {{User|Zhang19min88}}<br />
* {{User|Zhous98}}<br />
* {{User|ryle}}<br />
<br />
=== zh-tw - 繁體中文 - Traditional Chinese ===<br />
* {{User|Yuhoward}}<br />
* {{User|shawnhy}}<br />
<br />
==Translation Administrators==<br />
<br />
The responsibilities of a Translation Administrator will require slightly more attention to the documents for translation. Translation Administrators should feel comfortable with using wiki markup, made hundreds of contributions to their specific language and assisted others in translation of docs. Administrators will need to check the documentation every few days and perform any required tasks. These tasks include re-marking pages in en-GB with edit changes, tracking language units which need translation and welcoming new translators. Ideally, we should have at least one Translation Administrator who will not be tied to any specific language and when the time comes, one Translation Administrator for active language teams.<br />
<br />
===Current Volunteer Translation Administrators===<br />
{{:Special:ListUsers/translationadmins}}<br />
<br />
==Common Language Codes==<br />
<div class="small-4 columns"> afr - Afrikaans - Afrikaans<br />
</div><div class="small-4 columns"> ar - عربي - Arabic<br />
</div><div class="small-4 columns"> as - অসমীয়া - Assamese<br />
</div><div class="small-4 columns"> az - Azərbaycan - Azerbaijani<br />
</div><div class="small-4 columns"> be - Беларуская - Belarusian<br />
</div><div class="small-4 columns"> bg - Български - Bulgarian<br />
</div><div class="small-4 columns"> bn - বাংলা - Bengali<br />
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan<br />
</div><div class="small-4 columns"> ca - Català - Catalan<br />
</div><div class="small-4 columns"> ce - Nohçi - Chechen<br />
</div><div class="small-4 columns"> da - Dansk - Danish<br />
</div><div class="small-4 columns"> de - Deutsch - German<br />
</div><div class="small-4 columns"> es - Español - Spanish<br />
</div><div class="small-4 columns"> fa - فارسی - Persian<br />
</div><div class="small-4 columns"> fi - Suomi - Finnish<br />
</div><div class="small-4 columns"> fr - Français - French<br />
</div><div class="small-4 columns"> hu - Magyar - Hungarian<br />
</div><div class="small-4 columns"> hy - Հայերեն - Armenian<br />
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian<br />
</div><div class="small-4 columns"> is - Íslenska - Icelandic<br />
</div><div class="small-4 columns"> it - Italiano - Italian<br />
</div><div class="small-4 columns"> ja - 日本語 - Japanese<br />
</div><div class="small-4 columns"> ko - 한국어 - Korean<br />
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish<br />
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang<br />
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam<br />
</div><div class="small-4 columns"> mr - मराठी - Marathi<br />
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay<br />
</div><div class="small-4 columns"> nl - Nederlands - Dutch<br />
</div><div class="small-4 columns"> pl - Polski - Polish<br />
</div><div class="small-4 columns"> pt - Português - Portuguese<br />
</div><div class="small-4 columns"> pt-br - Português do Brasil - Brazilian Portuguese<br />
</div><div class="small-4 columns"> ro - Română - Romanian<br />
</div><div class="small-4 columns"> ru - Русский - Russian<br />
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók<br />
</div><div class="small-4 columns"> sq - Shqip - Albanian<br />
</div><div class="small-4 columns"> sv - Svenska - Swedish<br />
</div><div class="small-4 columns"> sw - Kiswahili - Swahili<br />
</div><div class="small-4 columns"> ta - தமிழ் - Tamil<br />
</div><div class="small-4 columns"> th - ไทย - Thai<br />
</div><div class="small-4 columns"> tr - Türkçe - Turkish<br />
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese<br />
</div><div class="small-4 columns"> zh - 中文 - Chinese<br />
</div><div class="small-4 columns"> zh-tw - 繁體中文 - Traditional Chinese<br />
</div><br />
<br />
<noinclude><br />
[[Category:Documentation Wiki Policies and Guidelines{{#translation:}}]]<br />
[[Category:Documentation Translation{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User:Serge&diff=999549User:Serge2023-03-10T17:05:41Z<p>Sandra97: Created page with " {{Translator welcome}} (~~~~)"</p>
<hr />
<div> {{Translator welcome}} ([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 11:05, 10 March 2023 (CST))</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_3.x_to_4.x_Step_by_Step_Migration/fr&diff=911210Joomla 3.x to 4.x Step by Step Migration/fr2022-05-09T12:10:06Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{warning|title=Attention !|Ce guide suppose que vous démarrez sur Joomla 3.10.x. Si vous êtes sur une version antérieure, assurez-vous de mettre à niveau vers Joomla 3.10 avant de passer à Joomla 4. <br />
<br />
Il n'y a pas d'urgence. Assurez-vous que toutes vos extensions sont prêtes pour Joomla 4.x. Joomla 3.10.x sera supporté jusqu'au 16 août 2023.}}<br />
<br />
Voici les instructions étape par étape pour migrer votre site 3.10.x vers Joomla ! 4.x. Bien qu'il existe des centaines de scénarios différents, ceci vous donnera la procédure de base à suivre. Les migrations très complexes seront probablement le résultat d'extensions tierces installées. Nous vous encourageons à contacter les développeurs des extensions tierces installées sur votre site Joomla pour connaître le chemin qu'ils suggèrent pour migrer leurs extensions.<br />
<br />
== Intro ==<br />
La migration de Joomla ! 3.10.x vers 4.x est considérée comme une mini-migration. En effet, les extensions de base de Joomla seront mises à niveau en un seul clic via le composant de mise à jour de Joomla ! dans la partie administrateur de Joomla. De nombreuses extensions tierces peuvent également être mises à niveau en un clic. D'autres ne le sont pas. Vous devez examiner chacune d'entre elles et déterminer le chemin que l'extension doit suivre pour passer de la version 3.10 à la version 4.x. Si vous ne l'avez pas encore fait, vous pourriez être intéressé par la lecture des documents suivants : [[S:MyLanguage/Migration Step by Step Self Assessment|Auto-évaluation]] et [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planification de la migration de 3.10 à 4.x]] avant de suivre les étapes suivantes<br />
</br>Les extensions de base de Joomla ! sont :<br />
* Catégories<br />
* Articles<br />
* Menus<br />
* Modules (modules de base - pas de modules tiers)<br />
* Journaux d'activité<br />
* Bannières<br />
* Champs<br />
* Historique du contenu<br />
* Contacts<br />
* Messagerie<br />
* Flux d'actualités<br />
* Redirections<br />
* Recherche (séparé en 4.x. Les sites 3.x existants pourront toujours migrer. Cependant, nous recommandons d'utiliser La recherche avancée à l'avenir. Voir les notes de la section Évaluation de chaque extension)<br />
* Recherche avancée<br />
* Tags<br />
* Liens web (séparé mais votre site peut l'utiliser et il migrera. Voir les notes de la section Évaluation de chaque extension)<br />
<br />
== Etape par étape ==<br />
=== Créez un environnement de développement ===<br />
# Assurez-vous que vous exécutez la dernière version de Joomla 3.10.x avant de poursuivre.<br />
# Faites une sauvegarde de votre site 3.10.x. Vous pouvez utiliser un outil suggéré (voir les ''Outils suggérés'' en bas de page) ou vous pouvez le faire manuellement.<br />
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Principes de base de la sauvegarde d'un site web Joomla ! ]]<br />
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|Quelles sont les meilleures pratiques pour les sauvegardes de sites ?]]<br />
# Assurez-vous que votre environnement est conforme aux [https://downloads.joomla.org/technical-requirements exigences techniques pour Joomla 4] avant de poursuivre.<br />
# Créez une nouvelle base de données et un nouvel utilisateur pour restaurer votre site 3.10.x. <br />
# Créez un site de test ou une zone de développement pour travailler et restaurez la copie de sauvegarde de votre site 3.10.x à l'un des endroits suivants :<br />
#* Un sous-domaine.<br />
#* Un sous-répertoire.<br />
#* Un périphérique local. Joomla a un tutoriel détaillé sur l'installation de [https://sourceforge.net/projects/xampp/ XAMPP] à [[XAMPP]]. Cependant, [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] sont toutes des alternatives appropriées.<br />
#* Un nouveau compte d'hébergement sur un domaine temporaire à la racine. (Si vous souhaitez changer d'hébergement au cours du processus de migration).<br />
#** Restauration d'un site sur un périphérique local. Voir [[S:MyLanguage/Installing Joomla locally|Installation de Joomla localement]] et [[S:MyLanguage/Setting up your workstation for Joomla development|Configuration de votre poste de travail pour le développement de Joomla]].<br />
#** Restauration d'un site avec un outil listé en bas de page. (Lisez la documentation du développeur).<br />
# Dans votre emplacement de test, mettez à jour votre instance Joomla ! 3.10.x vers la dernière version de maintenance.<br />
# Assurez-vous que vous avez le dernier schéma de base de données mis à jour vers la dernière version 3.10.x en allant dans l'onglet {{rarr|Gestion des Extensions,Base de données}}. Si votre schéma n'est pas à jour comme dans l'image suivante, cliquez sur le bouton '''Corriger''' :{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]<br />
# Vider la corbeille : Avez-vous des articles dans la corbeille ? Si c'est le cas, supprimez-les (ainsi que tous les médias qui peuvent leur être associés s'ils ne sont pas utilisés ailleurs sur le site). Les articles (ainsi que les catégories et les éléments de menu) laissés dans la corbeille peuvent empêcher une migration de se terminer sans erreur.<br />
# Tester.<br />
# Faites une nouvelle sauvegarde.<br />
<br />
=== Evaluer chaque extension ===<br />
Dans votre [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], vous avez déterminé quelles extensions tierces restaient ou partaient et comment elles migraient. Pour cette partie de l'étape par étape, vous allez utiliser deux sections différentes du site de manière intensive ; La vérification avant mise à jour dans {{rarr|Composants,Mise à jour de Joomla !}} et {{rarr|Extensions,Gestion des extensions,Gerer}}. Vous allez examiner chaque extension installée sur votre site. Vous allez déterminer si elles doivent être mises à jour vers la dernière version ou désinstallées. Plus de précisions dans la [[Special:MyLanguage/:Pre-Update_Check|Vérification avant mise à jour]].<br />
# Utilisation du contrôle de "pré-mise à jour" : pour pouvoir utiliser le contrôle de pré-mise à jour, vous devez configurer le composant de mise à jour de Joomla ! pour Joomla 4. Pour ce faire, procédez comme suit :<br />
# Allez sur {{rarr|Components,Mise à jour de Joomla}}. (Il devrait indiquer qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version (doit être 3.10.x) et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez ''Joomla Next'' dans le menu déroulant pour le canal de mise à jour.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}<br />
# Cliquez sur Enregistrer et fermer<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du package de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour consulter cette page.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{amboxNew|image=notice|style=notice|title={{{title|Note importante}}}|text='''Ne faites PAS la mise à jour vers Joomla ! 4 maintenant. C'est seulement pour préparer vos extensions tierces et rendre le site compatible avec Joomla ! 4.'''}}<br />
# Regardez le contrôle de pré-mise à jour et le contrôle de pré-mise à jour des extensions dans l'onglet Contrôle de pré-mise à jour du composant Joomla Update. Si une extension qui n'est pas dans votre planning est listée ici, ajoutez-la à votre liste d'extensions à examiner.<br />
# Si vous avez migré de Joomla ! 2.5 à 3.x dans le passé, il peut y avoir quelques extensions restantes qui doivent être nettoyées. Voici les anciennes extensions 2.5 ou 3.x qui doivent être désinstallées avant la mise à jour vers Joomla 4 :<br />
#;* plg_content_geshi<br />
#;* template admin Bluestork<br />
#;* Beez_20<br />
#;* Beez5<br />
#;* Atomic<br />
## En ce qui concerne les templates, désinstallez tous les templates frontend ou backend de base, sauf Protostar et Beez3 (templates frontend) et Isis ou Hathor (templates administrateur). '''NOTE : Protostar n'est PAS compatible avec Joomla 4'''. Lors de la migration, il disparaîtra. Vous aurez besoin d'avoir un template sélectionné comme "par défaut" et vous pouvez utiliser Protostar ou Beez3. Protostar disparaîtra lors de la migration vers Joomla 4.x.<br />
### Si vous rencontrez d'autres fichiers qui doivent être désinstallés, veuillez les ajouter à cette page. Ceci est un wiki, donc tout le monde peut ajouter à la page. Merci d'avance pour votre service.<br />
# Vous remarquerez les balises indiquant si une extension est compatible ou non. Ces balises indiquent généralement la vérité si elles disent Non ou Oui. Si elles disent "Balise de compatibilité manquante", cela signifie que le développeur de l'extension n'a pas utilisé de balise dans son extension et que nous ne savons pas si elle est ou non compatible avec Joomla 4. Contactez le développeur pour vérifier.<br />
# Mise à jour des extensions : mettez à jour toutes les extensions que vous conserverez dans votre site Web. Dans Joomla ! 3.10.x, vous pouvez aller dans {{rarr|Gestionnaire d'extensions, onglet Mise à jour}} et cliquer sur '''Trouver les mises à jour''' qui ajoutera une info-bulle dans la colonne Version, sous l'onglet Gérer, donnant quelques informations de compatibilité depuis le backend. Cette fonctionnalité ne prend en charge que les extensions qui se mettent à jour via l'onglet Mise à jour du gestionnaire d'extensions. Si vous avez installé des extensions qui n'utilisent pas la mise à jour des extensions Joomla, elles doivent être évaluées manuellement comme indiqué ci-dessous. Il en va de même pour les extensions qui ont une info-bulle. Vous devrez toujours vérifier le type de paquet et le chemin de migration avec le développeur de l'extension pour vérifier comment mettre à niveau/migrer.<br />
# Désinstaller et examiner les extensions : allez dans {{rarr|Gestionnaire d'extensions, onglet Gérer}}.<br />
# Cliquez sur le bouton ''Outils de recherche'' pour afficher les options de filtrage.<br />
# Sélectionnez le package dans la liste déroulante.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|Il est recommandé de sélectionner d'abord le package, car si vous devez désinstaller quelque chose dans un package, il désinstallera automatiquement et en une seule fois les modules, les plugins ou tout autre élément associé dans le package.}}<br />
# Désinstallez tous les packages qui ne sont plus nécessaires ou qui ne seront pas transférés vers Joomla 4.<br />
# Répétez ce processus en passant par l'onglet Gérer pour tous les types dans la liste déroulante : Composant, Fichier, Langue, Bibliothèque, Module, Plugin et Template. Si l'auteur indique projet Joomla, ne touchez pas à ces extensions. Pour toutes les autres, assurez-vous de désinstaller celles qui ne sont pas utilisées ou qui ne sont pas compatibles avec Joomla!&nbsp;4.x.{{-}}{{note|'''NOTE!''' Vous ne pourrez pas désinstaller un template qui est défini par défaut. Vous devrez sélectionner un template supporté par Core comme Beez3 ou Protostar et ensuite désinstaller le template si vous avez besoin de le faire. <br />''Autre rappel :''' '''Protostar n'est pas compatible avec Joomla 4.x'''. Lors de la migration, il disparaîtra. En le sélectionnant par défaut, vous arrivez simplement à Joomla 4.x.|type=serious}}<br />
# Notez toutes les versions des packages et des composants en cours d'exécution que vous conserverez sur votre site. Vous pouvez les copier/coller dans un document pour référence.<br />
# Pour toutes les extensions que vous gardez mais n'utilisez pas le gestionnaire d'extensions pour mettre à jour en un clic ({{rarr|Extensions,Gérer,Mettre à jour}}) mettez à jour toutes les extensions avec les dernières versions.<br />
# Avant et pendant la mise à jour, notez si les extensions ont les versions 3.10.x et 4.x dans le même package. Si c'est le cas, elles pourront être mises à jour en un clic. Si ce n'est pas le cas, et que les versions 3.10 et 4.x ont des packages différents, vous devez les examiner au cas par cas. En règle générale, elles relèvent de l'un des scénarios suivants :<br />
#* L'extension a des packages séparés mais lors de la mise à jour vers 4.x, ils détectent automatiquement cela et fonctionnent toujours. Assurez-vous que le développeur le confirme.<br />
#* L'extension a des packages séparés qui doivent être désinstallés dans 3.10.x et ensuite installés avec la version de Joomla 4.x une fois que le site est migré. Un exemple de ceci pourrait être un plugin de contenu. Il est très simple de le désinstaller en 3.10.x puis de le réinstaller en 4.x.<br />
#* Voir [[S:MyLanguage/Template_Considerations_During_Migration|Considérations sur les templates]] pour des informations plus spécifiques sur les templates et [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Conversion d'un template précédent de version de Joomla ! ]].<br />
<br />
==== Notes sur la recherche (com_search) ====<br />
Search (com_search) sera séparé de Joomla 4.x. La recherche (com_search) migrera vers Joomla 4. Après la migration, vous devrez le mettre à jour vers la version de Joomla 4.x via com_installer. Il continuera à être maintenu, mais plus de la même manière qu'une extension tierce en recevant des mises à jour via com_installer. Il est recommandé d'utiliserla Recherche avancée (com_finder) à l'avenir. La recherche sera toujours disponible à l'adresse https://extensions.joomla.org/category/official-extensions/ .<br />
<br />
==== Notes sur les liens web ====<br />
Les liens Web ont été dissociés dans la version 3.4 de Joomla. S'il était utilisé sur un site 2.5, le processus de migration en prendrait note et migrerait le composant liens web et ses données. Pour la migration de 3.10.x à 4.x, il en sera de même. Il est toujours disponible et maintenu sur le JED à l'adresse [https://extensions.joomla.org/category/official-extensions/ Official Extensions].<br />
<br />
==== Notes sur l'ancien routage d'URL ==== <br />
L'ancien routage ne sera pas disponible dans Joomla 4.x. Seul le routage moderne sera disponible. Lorsque vous effectuez la migration, si vous utilisez le routage héritage, le système le changera automatiquement en routage moderne. Vous devrez exécuter un vérificateur de liens brisés sur votre site après la migration vers Joomla 4.x et "avant de mettre en ligne".<br />
<br />
=== Passage à Joomla ! 4.x ===<br />
Une fois que vous avez mis à jour ou désinstallé vos extensions tierces pour que seules celles compatibles avec Joomla ! 4 restent dans votre installation, continuez avec les étapes suivantes :<br />
# Allez dans {{rarr|Système,Configuration,onglet Serveur}} et faites passer le rapport d'erreur de de Défaut à Maximum. Veillez enregistrer et fermer.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]<br />
# Faites une autre sauvegarde.<br />
# Allez sur {{rarr|Composants, mise à jour de Joomla}}. (Il devrait être indiqué qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez 'Joomla Next'' dans la liste déroulante pour le serveur de mise à jour.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]<br />
# Cliquez sur Enregistrer et fermer.<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du paquet de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour revoir cette page{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]<br />
# Si la mise à jour ne s'affiche pas, allez dans {{rarr|Gestionnaire d'extension,Mise à jour}} et cliquez sur Purge du Cache dans la barre d'outils. La mise à jour vers Joomla ! 4 devrait maintenant s'afficher.<br />
# Croisez les doigts, et assurez-vous d'avoir cette sauvegarde disponible au cas où.<br />
# Cliquez sur le bouton Installer la mise à jour.<br />
# Faites du thé pendant que la barre d'état passe au vert. Le temps que cela prend dépend de votre site, de votre connexion Internet et de la vitesse du serveur. Le processus prend environ deux minutes. Lorsque la mise à jour est terminée, vous serez probablement déconnecté de l'administrateur. Reconnectez-vous. Deux fois.<br />
# Si tout se passe bien, vous obtiendrez un tout nouveau look pour le panneau de l'administrateur du backend.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]<br />
# Allez dans {{rarr|Système,Maintenance,Base de données}} et cliquez sur ''Réparer'' si des erreurs apparaissent.<br />
# Dans {{rarr|Système,Installation,Découvrir}} voyez s'il y a des extensions à installer. (Il ne devrait pas y en avoir !)<br />
# Allez à l'interface de votre site et voyez s'il s'affiche même si ce n'est pas le bon template. Si oui, continuez. Si non, voir [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|les erreurs fréquentes lors d'une migration]].<br />
# Faites une sauvegarde.<br />
# Installez votre nouveau template ou d'autres extensions si vous en avez à installer. Sauvegardez souvent.<br />
# Configurez-les. Sauvegardez souvent.<br />
# Exécutez un vérificateur de liens brisés et réparez tous les liens brisés.<br />
# Testez tout. Sauvegardez souvent.<br />
# Si tout fonctionne comme prévu, remettez le rapport d'erreur sur le système par défaut ({{rarr|Système,Configuration globale,onglet Système de configuration}}). Veillez à enregistrer et à fermer.<br />
<br />
=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4| Modifications du htaccess après Joomla 4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur. <br />
<br />
Si des données ont été modifiées sur le site 3.10 pendant la migration vers la version 4.x, vous devrez les transférer sur le site 4.x avant la mise en ligne. Vous pouvez le faire manuellement (assurez-vous de conserver les mêmes identifiants d'utilisateur - allez-y dans l'ordre) ou en utilisant une [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ extension tierce].<br />
<br />
== Outils suggérés ==<br />
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] est très populaire pour la sauvegarde et la restauration. Voir d'autres [https://extensions.joomla.org/tags/backup/ outils de sauvegarde].<br />
==Informations connexes== <br />
[[Special:MyLanguage/:Pre-Update_Check|Vérification préalable à la mise à jour]]<br />
<noinclude><br />
[[Category:Migration/fr|Migration]]<br />
[[Category:Tutorials/fr|Tutoriels]]<br />
[[Category:Joomla! 4.x/fr{{#translation:}}]]</noinclude><br />
<noinclude>[[Category:Needs to be marked for translation]]</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_3.x_to_4.x_Step_by_Step_Migration/fr&diff=911209Joomla 3.x to 4.x Step by Step Migration/fr2022-05-09T12:09:41Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{warning|title=Attention !|Ce guide suppose que vous démarrez sur Joomla 3.10.x. Si vous êtes sur une version antérieure, assurez-vous de mettre à niveau vers Joomla 3.10 avant de passer à Joomla 4. <br />
<br />
Il n'y a pas d'urgence. Assurez-vous que toutes vos extensions sont prêtes pour Joomla 4.x. Joomla 3.10.x sera supporté jusqu'au 16 août 2023.}}<br />
<br />
Voici les instructions étape par étape pour migrer votre site 3.10.x vers Joomla ! 4.x. Bien qu'il existe des centaines de scénarios différents, ceci vous donnera la procédure de base à suivre. Les migrations très complexes seront probablement le résultat d'extensions tierces installées. Nous vous encourageons à contacter les développeurs des extensions tierces installées sur votre site Joomla pour connaître le chemin qu'ils suggèrent pour migrer leurs extensions.<br />
<br />
== Intro ==<br />
La migration de Joomla ! 3.10.x vers 4.x est considérée comme une mini-migration. En effet, les extensions de base de Joomla seront mises à niveau en un seul clic via le composant de mise à jour de Joomla ! dans la partie administrateur de Joomla. De nombreuses extensions tierces peuvent également être mises à niveau en un clic. D'autres ne le sont pas. Vous devez examiner chacune d'entre elles et déterminer le chemin que l'extension doit suivre pour passer de la version 3.10 à la version 4.x. Si vous ne l'avez pas encore fait, vous pourriez être intéressé par la lecture des documents suivants : [[S:MyLanguage/Migration Step by Step Self Assessment|Auto-évaluation]] et [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planification de la migration de 3.10 à 4.x]] avant de suivre les étapes suivantes<br />
</br>Les extensions de base de Joomla ! sont :<br />
* Catégories<br />
* Articles<br />
* Menus<br />
* Modules (modules de base - pas de modules tiers)<br />
* Journaux d'activité<br />
* Bannières<br />
* Champs<br />
* Historique du contenu<br />
* Contacts<br />
* Messagerie<br />
* Flux d'actualités<br />
* Redirections<br />
* Recherche (séparé en 4.x. Les sites 3.x existants pourront toujours migrer. Cependant, nous recommandons d'utiliser La recherche avancée à l'avenir. Voir les notes de la section Évaluation de chaque extension)<br />
* Recherche avancée<br />
* Tags<br />
* Liens web (séparé mais votre site peut l'utiliser et il migrera. Voir les notes de la section Évaluation de chaque extension)<br />
<br />
== Etape par étape ==<br />
=== Créez un environnement de développement ===<br />
# Assurez-vous que vous exécutez la dernière version de Joomla 3.10.x avant de poursuivre.<br />
# Faites une sauvegarde de votre site 3.10.x. Vous pouvez utiliser un outil suggéré (voir les ''Outils suggérés'' en bas de page) ou vous pouvez le faire manuellement.<br />
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Principes de base de la sauvegarde d'un site web Joomla ! ]]<br />
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|Quelles sont les meilleures pratiques pour les sauvegardes de sites ?]]<br />
# Assurez-vous que votre environnement est conforme aux [https://downloads.joomla.org/technical-requirements exigences techniques pour Joomla 4] avant de poursuivre.<br />
# Créez une nouvelle base de données et un nouvel utilisateur pour restaurer votre site 3.10.x. <br />
# Créez un site de test ou une zone de développement pour travailler et restaurez la copie de sauvegarde de votre site 3.10.x à l'un des endroits suivants :<br />
#* Un sous-domaine.<br />
#* Un sous-répertoire.<br />
#* Un périphérique local. Joomla a un tutoriel détaillé sur l'installation de [https://sourceforge.net/projects/xampp/ XAMPP] à [[XAMPP]]. Cependant, [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] sont toutes des alternatives appropriées.<br />
#* Un nouveau compte d'hébergement sur un domaine temporaire à la racine. (Si vous souhaitez changer d'hébergement au cours du processus de migration).<br />
#** Restauration d'un site sur un périphérique local. Voir [[S:MyLanguage/Installing Joomla locally|Installation de Joomla localement]] et [[S:MyLanguage/Setting up your workstation for Joomla development|Configuration de votre poste de travail pour le développement de Joomla]].<br />
#** Restauration d'un site avec un outil listé en bas de page. (Lisez la documentation du développeur).<br />
# Dans votre emplacement de test, mettez à jour votre instance Joomla ! 3.10.x vers la dernière version de maintenance.<br />
# Assurez-vous que vous avez le dernier schéma de base de données mis à jour vers la dernière version 3.10.x en allant dans l'onglet {{rarr|Gestion des Extensions,Base de données}}. Si votre schéma n'est pas à jour comme dans l'image suivante, cliquez sur le bouton '''Corriger''' :{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]<br />
# Vider la corbeille : Avez-vous des articles dans la corbeille ? Si c'est le cas, supprimez-les (ainsi que tous les médias qui peuvent leur être associés s'ils ne sont pas utilisés ailleurs sur le site). Les articles (ainsi que les catégories et les éléments de menu) laissés dans la corbeille peuvent empêcher une migration de se terminer sans erreur.<br />
# Tester.<br />
# Faites une nouvelle sauvegarde.<br />
<br />
=== Evaluer chaque extension ===<br />
Dans votre [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], vous avez déterminé quelles extensions tierces restaient ou partaient et comment elles migraient. Pour cette partie de l'étape par étape, vous allez utiliser deux sections différentes du site de manière intensive ; La vérification avant mise à jour dans {{rarr|Composants,Mise à jour de Joomla !}} et {{rarr|Extensions,Gestion des extensions,Gerer}}. Vous allez examiner chaque extension installée sur votre site. Vous allez déterminer si elles doivent être mises à jour vers la dernière version ou désinstallées. Plus de précisions dans la [[Special:MyLanguage/:Pre-Update_Check|Vérification avant mise à jour]].<br />
# Utilisation du contrôle de "pré-mise à jour" : pour pouvoir utiliser le contrôle de pré-mise à jour, vous devez configurer le composant de mise à jour de Joomla ! pour Joomla 4. Pour ce faire, procédez comme suit :<br />
# Allez sur {{rarr|Components,Mise à jour de Joomla}}. (Il devrait indiquer qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version (doit être 3.10.x) et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez ''Joomla Next'' dans le menu déroulant pour le canal de mise à jour.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}<br />
# Cliquez sur Enregistrer et fermer<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du package de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour consulter cette page.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{amboxNew|image=notice|style=notice|title={{{title|Note importante}}}|text='''Ne faites PAS la mise à jour vers Joomla ! 4 maintenant. C'est seulement pour préparer vos extensions tierces et rendre le site compatible avec Joomla ! 4.'''}}<br />
# Regardez le contrôle de pré-mise à jour et le contrôle de pré-mise à jour des extensions dans l'onglet Contrôle de pré-mise à jour du composant Joomla Update. Si une extension qui n'est pas dans votre planning est listée ici, ajoutez-la à votre liste d'extensions à examiner.<br />
# Si vous avez migré de Joomla ! 2.5 à 3.x dans le passé, il peut y avoir quelques extensions restantes qui doivent être nettoyées. Voici les anciennes extensions 2.5 ou 3.x qui doivent être désinstallées avant la mise à jour vers Joomla 4 :<br />
#;* plg_content_geshi<br />
#;* template admin Bluestork<br />
#;* Beez_20<br />
#;* Beez5<br />
#;* Atomic<br />
## En ce qui concerne les templates, désinstallez tous les templates frontend ou backend de base, sauf Protostar et Beez3 (templates frontend) et Isis ou Hathor (templates administrateur). '''NOTE : Protostar n'est PAS compatible avec Joomla 4'''. Lors de la migration, il disparaîtra. Vous aurez besoin d'avoir un template sélectionné comme "par défaut" et vous pouvez utiliser Protostar ou Beez3. Protostar disparaîtra lors de la migration vers Joomla 4.x.<br />
### Si vous rencontrez d'autres fichiers qui doivent être désinstallés, veuillez les ajouter à cette page. Ceci est un wiki, donc tout le monde peut ajouter à la page. Merci d'avance pour votre service.<br />
# Vous remarquerez les balises indiquant si une extension est compatible ou non. Ces balises indiquent généralement la vérité si elles disent Non ou Oui. Si elles disent "Balise de compatibilité manquante", cela signifie que le développeur de l'extension n'a pas utilisé de balise dans son extension et que nous ne savons pas si elle est ou non compatible avec Joomla 4. Contactez le développeur pour vérifier.<br />
# Mise à jour des extensions : mettez à jour toutes les extensions que vous conserverez dans votre site Web. Dans Joomla ! 3.10.x, vous pouvez aller dans {{rarr|Gestionnaire d'extensions, onglet Mise à jour}} et cliquer sur '''Trouver les mises à jour''' qui ajoutera une info-bulle dans la colonne Version, sous l'onglet Gérer, donnant quelques informations de compatibilité depuis le backend. Cette fonctionnalité ne prend en charge que les extensions qui se mettent à jour via l'onglet Mise à jour du gestionnaire d'extensions. Si vous avez installé des extensions qui n'utilisent pas la mise à jour des extensions Joomla, elles doivent être évaluées manuellement comme indiqué ci-dessous. Il en va de même pour les extensions qui ont une info-bulle. Vous devrez toujours vérifier le type de paquet et le chemin de migration avec le développeur de l'extension pour vérifier comment mettre à niveau/migrer.<br />
# Désinstaller et examiner les extensions : allez dans {{rarr|Gestionnaire d'extensions, onglet Gérer}}.<br />
# Cliquez sur le bouton ''Outils de recherche'' pour afficher les options de filtrage.<br />
# Sélectionnez le package dans la liste déroulante.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|Il est recommandé de sélectionner d'abord le package, car si vous devez désinstaller quelque chose dans un package, il désinstallera automatiquement et en une seule fois les modules, les plugins ou tout autre élément associé dans le package.}}<br />
# Désinstallez tous les packages qui ne sont plus nécessaires ou qui ne seront pas transférés vers Joomla 4.<br />
# Répétez ce processus en passant par l'onglet Gérer pour tous les types dans la liste déroulante : Composant, Fichier, Langue, Bibliothèque, Module, Plugin et Template. Si l'auteur indique projet Joomla, ne touchez pas à ces extensions. Pour toutes les autres, assurez-vous de désinstaller celles qui ne sont pas utilisées ou qui ne sont pas compatibles avec Joomla!&nbsp;4.x.{{-}}{{note|'''NOTE!''' Vous ne pourrez pas désinstaller un template qui est défini par défaut. Vous devrez sélectionner un template supporté par Core comme Beez3 ou Protostar et ensuite désinstaller le template si vous avez besoin de le faire. <br />''Autre rappel :''' '''Protostar n'est pas compatible avec Joomla 4.x'''. Lors de la migration, il disparaîtra. En le sélectionnant par défaut, vous arrivez simplement à Joomla 4.x.|type=serious}}<br />
# Notez toutes les versions des packages et des composants en cours d'exécution que vous conserverez sur votre site. Vous pouvez les copier/coller dans un document pour référence.<br />
# Pour toutes les extensions que vous gardez mais n'utilisez pas le gestionnaire d'extensions pour mettre à jour en un clic ({{rarr|Extensions,Gérer,Mettre à jour}}) mettez à jour toutes les extensions avec les dernières versions.<br />
# Avant et pendant la mise à jour, notez si les extensions ont les versions 3.10.x et 4.x dans le même package. Si c'est le cas, elles pourront être mises à jour en un clic. Si ce n'est pas le cas, et que les versions 3.10 et 4.x ont des packages différents, vous devez les examiner au cas par cas. En règle générale, elles relèvent de l'un des scénarios suivants :<br />
#* L'extension a des packages séparés mais lors de la mise à jour vers 4.x, ils détectent automatiquement cela et fonctionnent toujours. Assurez-vous que le développeur le confirme.<br />
#* L'extension a des packages séparés qui doivent être désinstallés dans 3.10.x et ensuite installés avec la version de Joomla 4.x une fois que le site est migré. Un exemple de ceci pourrait être un plugin de contenu. Il est très simple de le désinstaller en 3.10.x puis de le réinstaller en 4.x.<br />
#* Voir [[S:MyLanguage/Template_Considerations_During_Migration|Considérations sur les templates]] pour des informations plus spécifiques sur les templates et [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Conversion d'un template précédent de version de Joomla ! ]].<br />
<br />
==== Notes sur la recherche (com_search) ====<br />
Search (com_search) sera séparé de Joomla 4.x. La recherche (com_search) migrera vers Joomla 4. Après la migration, vous devrez le mettre à jour vers la version de Joomla 4.x via com_installer. Il continuera à être maintenu, mais plus de la même manière qu'une extension tierce en recevant des mises à jour via com_installer. Il est recommandé d'utiliserla Recherche avancée (com_finder) à l'avenir. La recherche sera toujours disponible à l'adresse https://extensions.joomla.org/category/official-extensions/ .<br />
<br />
==== Notes sur les liens web ====<br />
Les liens Web ont été dissociés dans la version 3.4 de Joomla. S'il était utilisé sur un site 2.5, le processus de migration en prendrait note et migrerait le composant liens web et ses données. Pour la migration de 3.10.x à 4.x, il en sera de même. Il est toujours disponible et maintenu sur le JED à l'adresse [https://extensions.joomla.org/category/official-extensions/ Official Extensions].<br />
<br />
==== Notes sur l'ancien routage d'URL ==== <br />
L'ancien routage ne sera pas disponible dans Joomla 4.x. Seul le routage moderne sera disponible. Lorsque vous effectuez la migration, si vous utilisez le routage héritage, le système le changera automatiquement en routage moderne. Vous devrez exécuter un vérificateur de liens brisés sur votre site après la migration vers Joomla 4.x et "avant de mettre en ligne".<br />
<br />
=== Passage à Joomla ! 4.x ===<br />
Une fois que vous avez mis à jour ou désinstallé vos extensions tierces pour que seules celles compatibles avec Joomla ! 4 restent dans votre installation, continuez avec les étapes suivantes :<br />
# Allez dans {{rarr|Système,Configuration,onglet Serveur}} et faites passer le rapport d'erreur de de Défaut à Maximum. Veillez enregistrer et fermer.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]<br />
# Faites une autre sauvegarde.<br />
# Allez sur {{rarr|Composants, mise à jour de Joomla}}. (Il devrait être indiqué qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez 'Joomla Next'' dans la liste déroulante pour le serveur de mise à jour.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]<br />
# Cliquez sur Enregistrer et fermer.<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du paquet de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour revoir cette page{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]<br />
# Si la mise à jour ne s'affiche pas, allez dans {{rarr|Gestionnaire d'extension,Mise à jour}} et cliquez sur Purge du Cache dans la barre d'outils. La mise à jour vers Joomla ! 4 devrait maintenant s'afficher.<br />
# Croisez les doigts, et assurez-vous d'avoir cette sauvegarde disponible au cas où.<br />
# Cliquez sur le bouton Installer la mise à jour.<br />
# Faites du thé pendant que la barre d'état passe au vert. Le temps que cela prend dépend de votre site, de votre connexion Internet et de la vitesse du serveur. Le processus prend environ deux minutes. Lorsque la mise à jour est terminée, vous serez probablement déconnecté de l'administrateur. Reconnectez-vous. Deux fois.<br />
# Si tout se passe bien, vous obtiendrez un tout nouveau look pour le panneau de l'administrateur du backend.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]<br />
# Allez dans {{rarr|Système,Maintenance,Base de données}} et cliquez sur ''Réparer'' si des erreurs apparaissent.<br />
# Dans {{rarr|Système,Installation,Découvrir}} voyez s'il y a des extensions à installer. (Il ne devrait pas y en avoir !)<br />
# Allez à l'interface de votre site et voyez s'il s'affiche même si ce n'est pas le bon template. Si oui, continuez. Si non, voir [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|les erreurs fréquentes lors d'une migration]].<br />
# Faites une sauvegarde.<br />
# Installez votre nouveau template ou d'autres extensions si vous en avez à installer. Sauvegardez souvent.<br />
# Configurez-les. Sauvegardez souvent.<br />
# Exécutez un vérificateur de liens brisés et réparez tous les liens brisés.<br />
# Testez tout. Sauvegardez souvent.<br />
# Si tout fonctionne comme prévu, remettez le rapport d'erreur sur le système par défaut ({{rarr|Système,Configuration globale,onglet Système de configuration}}). Veillez à enregistrer et à fermer.<br />
<br />
=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4| Modifications du htaccess après joomla4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur. <br />
<br />
Si des données ont été modifiées sur le site 3.10 pendant la migration vers la version 4.x, vous devrez les transférer sur le site 4.x avant la mise en ligne. Vous pouvez le faire manuellement (assurez-vous de conserver les mêmes identifiants d'utilisateur - allez-y dans l'ordre) ou en utilisant une [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ extension tierce].<br />
<br />
== Outils suggérés ==<br />
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] est très populaire pour la sauvegarde et la restauration. Voir d'autres [https://extensions.joomla.org/tags/backup/ outils de sauvegarde].<br />
==Informations connexes== <br />
[[Special:MyLanguage/:Pre-Update_Check|Vérification préalable à la mise à jour]]<br />
<noinclude><br />
[[Category:Migration/fr|Migration]]<br />
[[Category:Tutorials/fr|Tutoriels]]<br />
[[Category:Joomla! 4.x/fr{{#translation:}}]]</noinclude><br />
<noinclude>[[Category:Needs to be marked for translation]]</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Joomla_3.x_to_4.x_Step_by_Step_Migration/26/fr&diff=911208Translations:Joomla 3.x to 4.x Step by Step Migration/26/fr2022-05-09T12:09:41Z<p>Sandra97: </p>
<hr />
<div>=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4| Modifications du htaccess après Joomla 4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Joomla_3.x_to_4.x_Step_by_Step_Migration/26/fr&diff=911207Translations:Joomla 3.x to 4.x Step by Step Migration/26/fr2022-05-09T12:09:29Z<p>Sandra97: </p>
<hr />
<div>=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4| Modifications du htaccess après joomla4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_3.x_to_4.x_Step_by_Step_Migration/fr&diff=911206Joomla 3.x to 4.x Step by Step Migration/fr2022-05-09T12:08:39Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{warning|title=Attention !|Ce guide suppose que vous démarrez sur Joomla 3.10.x. Si vous êtes sur une version antérieure, assurez-vous de mettre à niveau vers Joomla 3.10 avant de passer à Joomla 4. <br />
<br />
Il n'y a pas d'urgence. Assurez-vous que toutes vos extensions sont prêtes pour Joomla 4.x. Joomla 3.10.x sera supporté jusqu'au 16 août 2023.}}<br />
<br />
Voici les instructions étape par étape pour migrer votre site 3.10.x vers Joomla ! 4.x. Bien qu'il existe des centaines de scénarios différents, ceci vous donnera la procédure de base à suivre. Les migrations très complexes seront probablement le résultat d'extensions tierces installées. Nous vous encourageons à contacter les développeurs des extensions tierces installées sur votre site Joomla pour connaître le chemin qu'ils suggèrent pour migrer leurs extensions.<br />
<br />
== Intro ==<br />
La migration de Joomla ! 3.10.x vers 4.x est considérée comme une mini-migration. En effet, les extensions de base de Joomla seront mises à niveau en un seul clic via le composant de mise à jour de Joomla ! dans la partie administrateur de Joomla. De nombreuses extensions tierces peuvent également être mises à niveau en un clic. D'autres ne le sont pas. Vous devez examiner chacune d'entre elles et déterminer le chemin que l'extension doit suivre pour passer de la version 3.10 à la version 4.x. Si vous ne l'avez pas encore fait, vous pourriez être intéressé par la lecture des documents suivants : [[S:MyLanguage/Migration Step by Step Self Assessment|Auto-évaluation]] et [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planification de la migration de 3.10 à 4.x]] avant de suivre les étapes suivantes<br />
</br>Les extensions de base de Joomla ! sont :<br />
* Catégories<br />
* Articles<br />
* Menus<br />
* Modules (modules de base - pas de modules tiers)<br />
* Journaux d'activité<br />
* Bannières<br />
* Champs<br />
* Historique du contenu<br />
* Contacts<br />
* Messagerie<br />
* Flux d'actualités<br />
* Redirections<br />
* Recherche (séparé en 4.x. Les sites 3.x existants pourront toujours migrer. Cependant, nous recommandons d'utiliser La recherche avancée à l'avenir. Voir les notes de la section Évaluation de chaque extension)<br />
* Recherche avancée<br />
* Tags<br />
* Liens web (séparé mais votre site peut l'utiliser et il migrera. Voir les notes de la section Évaluation de chaque extension)<br />
<br />
== Etape par étape ==<br />
=== Créez un environnement de développement ===<br />
# Assurez-vous que vous exécutez la dernière version de Joomla 3.10.x avant de poursuivre.<br />
# Faites une sauvegarde de votre site 3.10.x. Vous pouvez utiliser un outil suggéré (voir les ''Outils suggérés'' en bas de page) ou vous pouvez le faire manuellement.<br />
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Principes de base de la sauvegarde d'un site web Joomla ! ]]<br />
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|Quelles sont les meilleures pratiques pour les sauvegardes de sites ?]]<br />
# Assurez-vous que votre environnement est conforme aux [https://downloads.joomla.org/technical-requirements exigences techniques pour Joomla 4] avant de poursuivre.<br />
# Créez une nouvelle base de données et un nouvel utilisateur pour restaurer votre site 3.10.x. <br />
# Créez un site de test ou une zone de développement pour travailler et restaurez la copie de sauvegarde de votre site 3.10.x à l'un des endroits suivants :<br />
#* Un sous-domaine.<br />
#* Un sous-répertoire.<br />
#* Un périphérique local. Joomla a un tutoriel détaillé sur l'installation de [https://sourceforge.net/projects/xampp/ XAMPP] à [[XAMPP]]. Cependant, [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] sont toutes des alternatives appropriées.<br />
#* Un nouveau compte d'hébergement sur un domaine temporaire à la racine. (Si vous souhaitez changer d'hébergement au cours du processus de migration).<br />
#** Restauration d'un site sur un périphérique local. Voir [[S:MyLanguage/Installing Joomla locally|Installation de Joomla localement]] et [[S:MyLanguage/Setting up your workstation for Joomla development|Configuration de votre poste de travail pour le développement de Joomla]].<br />
#** Restauration d'un site avec un outil listé en bas de page. (Lisez la documentation du développeur).<br />
# Dans votre emplacement de test, mettez à jour votre instance Joomla ! 3.10.x vers la dernière version de maintenance.<br />
# Assurez-vous que vous avez le dernier schéma de base de données mis à jour vers la dernière version 3.10.x en allant dans l'onglet {{rarr|Gestion des Extensions,Base de données}}. Si votre schéma n'est pas à jour comme dans l'image suivante, cliquez sur le bouton '''Corriger''' :{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]<br />
# Vider la corbeille : Avez-vous des articles dans la corbeille ? Si c'est le cas, supprimez-les (ainsi que tous les médias qui peuvent leur être associés s'ils ne sont pas utilisés ailleurs sur le site). Les articles (ainsi que les catégories et les éléments de menu) laissés dans la corbeille peuvent empêcher une migration de se terminer sans erreur.<br />
# Tester.<br />
# Faites une nouvelle sauvegarde.<br />
<br />
=== Evaluer chaque extension ===<br />
Dans votre [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], vous avez déterminé quelles extensions tierces restaient ou partaient et comment elles migraient. Pour cette partie de l'étape par étape, vous allez utiliser deux sections différentes du site de manière intensive ; La vérification avant mise à jour dans {{rarr|Composants,Mise à jour de Joomla !}} et {{rarr|Extensions,Gestion des extensions,Gerer}}. Vous allez examiner chaque extension installée sur votre site. Vous allez déterminer si elles doivent être mises à jour vers la dernière version ou désinstallées. Plus de précisions dans la [[Special:MyLanguage/:Pre-Update_Check|Vérification avant mise à jour]].<br />
# Utilisation du contrôle de "pré-mise à jour" : pour pouvoir utiliser le contrôle de pré-mise à jour, vous devez configurer le composant de mise à jour de Joomla ! pour Joomla 4. Pour ce faire, procédez comme suit :<br />
# Allez sur {{rarr|Components,Mise à jour de Joomla}}. (Il devrait indiquer qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version (doit être 3.10.x) et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez ''Joomla Next'' dans le menu déroulant pour le canal de mise à jour.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}<br />
# Cliquez sur Enregistrer et fermer<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du package de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour consulter cette page.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{amboxNew|image=notice|style=notice|title={{{title|Note importante}}}|text='''Ne faites PAS la mise à jour vers Joomla ! 4 maintenant. C'est seulement pour préparer vos extensions tierces et rendre le site compatible avec Joomla ! 4.'''}}<br />
# Regardez le contrôle de pré-mise à jour et le contrôle de pré-mise à jour des extensions dans l'onglet Contrôle de pré-mise à jour du composant Joomla Update. Si une extension qui n'est pas dans votre planning est listée ici, ajoutez-la à votre liste d'extensions à examiner.<br />
# Si vous avez migré de Joomla ! 2.5 à 3.x dans le passé, il peut y avoir quelques extensions restantes qui doivent être nettoyées. Voici les anciennes extensions 2.5 ou 3.x qui doivent être désinstallées avant la mise à jour vers Joomla 4 :<br />
#;* plg_content_geshi<br />
#;* template admin Bluestork<br />
#;* Beez_20<br />
#;* Beez5<br />
#;* Atomic<br />
## En ce qui concerne les templates, désinstallez tous les templates frontend ou backend de base, sauf Protostar et Beez3 (templates frontend) et Isis ou Hathor (templates administrateur). '''NOTE : Protostar n'est PAS compatible avec Joomla 4'''. Lors de la migration, il disparaîtra. Vous aurez besoin d'avoir un template sélectionné comme "par défaut" et vous pouvez utiliser Protostar ou Beez3. Protostar disparaîtra lors de la migration vers Joomla 4.x.<br />
### Si vous rencontrez d'autres fichiers qui doivent être désinstallés, veuillez les ajouter à cette page. Ceci est un wiki, donc tout le monde peut ajouter à la page. Merci d'avance pour votre service.<br />
# Vous remarquerez les balises indiquant si une extension est compatible ou non. Ces balises indiquent généralement la vérité si elles disent Non ou Oui. Si elles disent "Balise de compatibilité manquante", cela signifie que le développeur de l'extension n'a pas utilisé de balise dans son extension et que nous ne savons pas si elle est ou non compatible avec Joomla 4. Contactez le développeur pour vérifier.<br />
# Mise à jour des extensions : mettez à jour toutes les extensions que vous conserverez dans votre site Web. Dans Joomla ! 3.10.x, vous pouvez aller dans {{rarr|Gestionnaire d'extensions, onglet Mise à jour}} et cliquer sur '''Trouver les mises à jour''' qui ajoutera une info-bulle dans la colonne Version, sous l'onglet Gérer, donnant quelques informations de compatibilité depuis le backend. Cette fonctionnalité ne prend en charge que les extensions qui se mettent à jour via l'onglet Mise à jour du gestionnaire d'extensions. Si vous avez installé des extensions qui n'utilisent pas la mise à jour des extensions Joomla, elles doivent être évaluées manuellement comme indiqué ci-dessous. Il en va de même pour les extensions qui ont une info-bulle. Vous devrez toujours vérifier le type de paquet et le chemin de migration avec le développeur de l'extension pour vérifier comment mettre à niveau/migrer.<br />
# Désinstaller et examiner les extensions : allez dans {{rarr|Gestionnaire d'extensions, onglet Gérer}}.<br />
# Cliquez sur le bouton ''Outils de recherche'' pour afficher les options de filtrage.<br />
# Sélectionnez le package dans la liste déroulante.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|Il est recommandé de sélectionner d'abord le package, car si vous devez désinstaller quelque chose dans un package, il désinstallera automatiquement et en une seule fois les modules, les plugins ou tout autre élément associé dans le package.}}<br />
# Désinstallez tous les packages qui ne sont plus nécessaires ou qui ne seront pas transférés vers Joomla 4.<br />
# Répétez ce processus en passant par l'onglet Gérer pour tous les types dans la liste déroulante : Composant, Fichier, Langue, Bibliothèque, Module, Plugin et Template. Si l'auteur indique projet Joomla, ne touchez pas à ces extensions. Pour toutes les autres, assurez-vous de désinstaller celles qui ne sont pas utilisées ou qui ne sont pas compatibles avec Joomla!&nbsp;4.x.{{-}}{{note|'''NOTE!''' Vous ne pourrez pas désinstaller un template qui est défini par défaut. Vous devrez sélectionner un template supporté par Core comme Beez3 ou Protostar et ensuite désinstaller le template si vous avez besoin de le faire. <br />''Autre rappel :''' '''Protostar n'est pas compatible avec Joomla 4.x'''. Lors de la migration, il disparaîtra. En le sélectionnant par défaut, vous arrivez simplement à Joomla 4.x.|type=serious}}<br />
# Notez toutes les versions des packages et des composants en cours d'exécution que vous conserverez sur votre site. Vous pouvez les copier/coller dans un document pour référence.<br />
# Pour toutes les extensions que vous gardez mais n'utilisez pas le gestionnaire d'extensions pour mettre à jour en un clic ({{rarr|Extensions,Gérer,Mettre à jour}}) mettez à jour toutes les extensions avec les dernières versions.<br />
# Avant et pendant la mise à jour, notez si les extensions ont les versions 3.10.x et 4.x dans le même package. Si c'est le cas, elles pourront être mises à jour en un clic. Si ce n'est pas le cas, et que les versions 3.10 et 4.x ont des packages différents, vous devez les examiner au cas par cas. En règle générale, elles relèvent de l'un des scénarios suivants :<br />
#* L'extension a des packages séparés mais lors de la mise à jour vers 4.x, ils détectent automatiquement cela et fonctionnent toujours. Assurez-vous que le développeur le confirme.<br />
#* L'extension a des packages séparés qui doivent être désinstallés dans 3.10.x et ensuite installés avec la version de Joomla 4.x une fois que le site est migré. Un exemple de ceci pourrait être un plugin de contenu. Il est très simple de le désinstaller en 3.10.x puis de le réinstaller en 4.x.<br />
#* Voir [[S:MyLanguage/Template_Considerations_During_Migration|Considérations sur les templates]] pour des informations plus spécifiques sur les templates et [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Conversion d'un template précédent de version de Joomla ! ]].<br />
<br />
==== Notes sur la recherche (com_search) ====<br />
Search (com_search) sera séparé de Joomla 4.x. La recherche (com_search) migrera vers Joomla 4. Après la migration, vous devrez le mettre à jour vers la version de Joomla 4.x via com_installer. Il continuera à être maintenu, mais plus de la même manière qu'une extension tierce en recevant des mises à jour via com_installer. Il est recommandé d'utiliserla Recherche avancée (com_finder) à l'avenir. La recherche sera toujours disponible à l'adresse https://extensions.joomla.org/category/official-extensions/ .<br />
<br />
==== Notes sur les liens web ====<br />
Les liens Web ont été dissociés dans la version 3.4 de Joomla. S'il était utilisé sur un site 2.5, le processus de migration en prendrait note et migrerait le composant liens web et ses données. Pour la migration de 3.10.x à 4.x, il en sera de même. Il est toujours disponible et maintenu sur le JED à l'adresse [https://extensions.joomla.org/category/official-extensions/ Official Extensions].<br />
<br />
==== Notes sur l'ancien routage d'URL ==== <br />
L'ancien routage ne sera pas disponible dans Joomla 4.x. Seul le routage moderne sera disponible. Lorsque vous effectuez la migration, si vous utilisez le routage héritage, le système le changera automatiquement en routage moderne. Vous devrez exécuter un vérificateur de liens brisés sur votre site après la migration vers Joomla 4.x et "avant de mettre en ligne".<br />
<br />
=== Passage à Joomla ! 4.x ===<br />
Une fois que vous avez mis à jour ou désinstallé vos extensions tierces pour que seules celles compatibles avec Joomla ! 4 restent dans votre installation, continuez avec les étapes suivantes :<br />
# Allez dans {{rarr|Système,Configuration,onglet Serveur}} et faites passer le rapport d'erreur de de Défaut à Maximum. Veillez enregistrer et fermer.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]<br />
# Faites une autre sauvegarde.<br />
# Allez sur {{rarr|Composants, mise à jour de Joomla}}. (Il devrait être indiqué qu'aucune mise à jour n'a été trouvée. Si ce n'est pas le cas, mettez à jour Joomla à la dernière version et testez. Puis faites une autre sauvegarde). Cliquez sur le bouton Options dans le coin supérieur droit.<br />
# Sélectionnez 'Joomla Next'' dans la liste déroulante pour le serveur de mise à jour.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]<br />
# Cliquez sur Enregistrer et fermer.<br />
# Vous verrez alors votre version installée de Joomla, la dernière version de Joomla ! et l'URL du paquet de mise à jour. Joomla vous montrera à nouveau la configuration requise pour Joomla 4. S'il signale que vous avez un système ou des extensions incompatibles, il vous le dira ici. Prenez un moment pour revoir cette page{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]<br />
# Si la mise à jour ne s'affiche pas, allez dans {{rarr|Gestionnaire d'extension,Mise à jour}} et cliquez sur Purge du Cache dans la barre d'outils. La mise à jour vers Joomla ! 4 devrait maintenant s'afficher.<br />
# Croisez les doigts, et assurez-vous d'avoir cette sauvegarde disponible au cas où.<br />
# Cliquez sur le bouton Installer la mise à jour.<br />
# Faites du thé pendant que la barre d'état passe au vert. Le temps que cela prend dépend de votre site, de votre connexion Internet et de la vitesse du serveur. Le processus prend environ deux minutes. Lorsque la mise à jour est terminée, vous serez probablement déconnecté de l'administrateur. Reconnectez-vous. Deux fois.<br />
# Si tout se passe bien, vous obtiendrez un tout nouveau look pour le panneau de l'administrateur du backend.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]<br />
# Allez dans {{rarr|Système,Maintenance,Base de données}} et cliquez sur ''Réparer'' si des erreurs apparaissent.<br />
# Dans {{rarr|Système,Installation,Découvrir}} voyez s'il y a des extensions à installer. (Il ne devrait pas y en avoir !)<br />
# Allez à l'interface de votre site et voyez s'il s'affiche même si ce n'est pas le bon template. Si oui, continuez. Si non, voir [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|les erreurs fréquentes lors d'une migration]].<br />
# Faites une sauvegarde.<br />
# Installez votre nouveau template ou d'autres extensions si vous en avez à installer. Sauvegardez souvent.<br />
# Configurez-les. Sauvegardez souvent.<br />
# Exécutez un vérificateur de liens brisés et réparez tous les liens brisés.<br />
# Testez tout. Sauvegardez souvent.<br />
# Si tout fonctionne comme prévu, remettez le rapport d'erreur sur le système par défaut ({{rarr|Système,Configuration globale,onglet Système de configuration}}). Veillez à enregistrer et à fermer.<br />
<br />
=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4 Modifications du htaccess après joomla4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur. <br />
<br />
Si des données ont été modifiées sur le site 3.10 pendant la migration vers la version 4.x, vous devrez les transférer sur le site 4.x avant la mise en ligne. Vous pouvez le faire manuellement (assurez-vous de conserver les mêmes identifiants d'utilisateur - allez-y dans l'ordre) ou en utilisant une [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ extension tierce].<br />
<br />
== Outils suggérés ==<br />
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] est très populaire pour la sauvegarde et la restauration. Voir d'autres [https://extensions.joomla.org/tags/backup/ outils de sauvegarde].<br />
==Informations connexes== <br />
[[Special:MyLanguage/:Pre-Update_Check|Vérification préalable à la mise à jour]]<br />
<noinclude><br />
[[Category:Migration/fr|Migration]]<br />
[[Category:Tutorials/fr|Tutoriels]]<br />
[[Category:Joomla! 4.x/fr{{#translation:}}]]</noinclude><br />
<noinclude>[[Category:Needs to be marked for translation]]</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Joomla_3.x_to_4.x_Step_by_Step_Migration/26/fr&diff=911205Translations:Joomla 3.x to 4.x Step by Step Migration/26/fr2022-05-09T12:08:19Z<p>Sandra97: </p>
<hr />
<div>=== Mise en service de votre site Joomla ! 4.x ===<br />
# Lorsque vous êtes prêt à mettre en ligne, sauvegardez votre site 3.10 pour la dernière fois. Restaurez-le dans un sous-répertoire ou un sous-domaine si vous le souhaitez.<br />
# Sauvegardez votre site Joomla ! 4.x et déplacez ou restaurez votre site Joomla ! 4.x à la racine (ou changez les serveurs de noms si vous construisiez sur un domaine temporaire à la racine d'un nouveau compte d'hébergement).<br />
# Testez à nouveau.<br />
# Si vous aviez apporté des modifications de sécurité au fichier .htaccess, vous aurez peut-être à modifier une ou plusieurs lignes pour passer à la prochaine version de Joomla 4. Veuillez consulter [[S:MyLanguage/Htaccess_changes_after_joomla4.0.4 Modifications du htaccess après joomla4.0.4]] pour déterminer si vous devez modifier votre fichier ou non. <br />
# Retirez le site Joomla ! 3.10 du serveur dans les deux jours qui suivent, sauf si vous avez modifié votre fichier ''robots.txt'' pour bloquer les robots des moteurs de recherche.<br />
# Supprimez tous les sites de développement sur lesquels vous avez travaillé ou mettez-les à jour s'ils utilisent une version actuelle afin d'éviter toute tentative de piratage de votre serveur.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J4.x:Redirects_from_Redirect_system_plugin_(if_enabled)_cause_internal_server_errors_500&diff=873352J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 5002022-01-23T09:49:17Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<br />
<br />
<translate><!--T:1--><br />
Joomla '''4.0.6''' (only) has a small regression<br />
[https://forum.joomla.org/viewtopic.php?f=9&t=991271 reported] affecting only sites that use the System - '''Redirect plugin'''. This plugin is '''disabled by default, so only very few sites may be affected'''. If your site uses this Redirect plugin, either stay at Joomla 4.0.5, waiting for Joomla 4.0.7 (which will be released only if needed) or next scheduled Joomla 4.1, due February 15th 2022. If you use this plugin and already upgraded to 4.0.6, you can apply one of the easy fixes below.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate> <br />
<translate><br />
<!--T:3--><br />
[https://github.com/joomla/joomla-cms/issues/36730 Bug report #36730]:<br />
System Redirect Plugin has a regression bug in Joomla 4.0.6 affecting only its redirects which display ''Internal Server Error 500'' instead of redirecting.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate> <br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''4.0.6'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<translate><!--T:8--> This is due to a PHP error in the Redirect plugin on updating the corresponding redirect counter, that is uncatched.</translate><br />
<br />
<translate>==How to fix== <!--T:9--><br />
</translate> <br />
<br />
<translate><!--T:10--> If you use the "System - Redirects" plugin and already upgraded to Joomla 4.0.6, you have the choice of one of these fixes:</translate><br />
* <translate><!--T:11--> Once Joomla 4.1 (or 4.0.7) are released, upgrade.</translate><br />
* <translate><!--T:12--> either downgrade your site to Joomla 4.0.5,</translate><br />
* <translate><!--T:13--> or temporarily disable the "System - Redirect" plugin</translate><br />
* <translate><!--T:14--><br />
or apply the [https://github.com/joomla/joomla-cms/pull/36733/files<br />
bugfix #36733] by editing file ''plugins/system/redirect/redirect.php'' and changing the part "''$db->''" to "''$this->db->''" on line 243 as shown in the diff on [https://github.com/joomla/joomla-cms/pull/36733/files bugfix #36733].</translate><br />
<br />
__NOTOC__<br />
<br />
<br />
<noinclude><br />
[[Category:Joomla! 4.x{{#translation:}}]]<br />
[[Category:Version_4.0_FAQ{{#translation:}}]]<br />
[[Category:Version 4.0.6 FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J4.x:Redirects_from_Redirect_system_plugin_(if_enabled)_cause_internal_server_errors_500&diff=873351J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 5002022-01-23T09:49:02Z<p>Sandra97: Tagged for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<br />
<br />
<translate>Joomla '''4.0.6''' (only) has a small regression<br />
[https://forum.joomla.org/viewtopic.php?f=9&t=991271 reported] affecting only sites that use the System - '''Redirect plugin'''. This plugin is '''disabled by default, so only very few sites may be affected'''. If your site uses this Redirect plugin, either stay at Joomla 4.0.5, waiting for Joomla 4.0.7 (which will be released only if needed) or next scheduled Joomla 4.1, due February 15th 2022. If you use this plugin and already upgraded to 4.0.6, you can apply one of the easy fixes below.</translate><br />
<br />
<translate><br />
==Errors reported==<br />
</translate> <br />
<translate><br />
[https://github.com/joomla/joomla-cms/issues/36730 Bug report #36730]:<br />
System Redirect Plugin has a regression bug in Joomla 4.0.6 affecting only its redirects which display ''Internal Server Error 500'' instead of redirecting.</translate><br />
<br />
<translate><br />
==Versions affected==<br />
</translate> <br />
{{tip|<translate>This pertains only to Joomla! version(s)</translate>: '''4.0.6'''|title=<translate>General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause==<br />
</translate><br />
<translate>This is due to a PHP error in the Redirect plugin on updating the corresponding redirect counter, that is uncatched.</translate><br />
<br />
<translate>==How to fix==<br />
</translate> <br />
<br />
<translate>If you use the "System - Redirects" plugin and already upgraded to Joomla 4.0.6, you have the choice of one of these fixes:</translate><br />
* <translate>Once Joomla 4.1 (or 4.0.7) are released, upgrade.</translate><br />
* <translate>either downgrade your site to Joomla 4.0.5,</translate><br />
* <translate>or temporarily disable the "System - Redirect" plugin</translate><br />
* <translate>or apply the [https://github.com/joomla/joomla-cms/pull/36733/files<br />
bugfix #36733] by editing file ''plugins/system/redirect/redirect.php'' and changing the part "''$db->''" to "''$this->db->''" on line 243 as shown in the diff on [https://github.com/joomla/joomla-cms/pull/36733/files bugfix #36733].</translate><br />
<br />
__NOTOC__<br />
<br />
<br />
<noinclude><br />
[[Category:Joomla! 4.x{{#translation:}}]]<br />
[[Category:Version_4.0_FAQ{{#translation:}}]]<br />
[[Category:Version 4.0.6 FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Redirects_from_Redirect_system_plugin_(if_enabled)_cause_internal_server_errors_500&diff=873350J3.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 5002022-01-23T09:46:05Z<p>Sandra97: Sandra97 moved page J3.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 500 to J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 500: Wrong namespace</p>
<hr />
<div>#REDIRECT [[J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 500]]</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J4.x:Redirects_from_Redirect_system_plugin_(if_enabled)_cause_internal_server_errors_500&diff=873349J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 5002022-01-23T09:46:05Z<p>Sandra97: Sandra97 moved page J3.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 500 to J4.x:Redirects from Redirect system plugin (if enabled) cause internal server errors 500: Wrong namespace</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<br />
<translate><!--T:1--> <br />
Joomla '''4.0.6''' (only) has a small regression<br />
[https://forum.joomla.org/viewtopic.php?f=9&t=991271 reported] affecting only sites that use the System - '''Redirect plugin'''. This plugin is '''disabled by default, so only very few sites may be affected'''. If your site uses this Redirect plugin, either stay at Joomla 4.0.5, waiting for Joomla 4.0.7 (which will be released only if needed) or next scheduled Joomla 4.1, due February 15th 2022. If you use this plugin and already upgraded to 4.0.6, you can apply one of the easy fixes below.<br />
<br />
<!--T:2--><br />
==Errors reported== <!-- Fill errors below --><br />
<br />
<!--T:3--><br />
[https://github.com/joomla/joomla-cms/issues/36730 Bug report #36730]:<br />
System Redirect Plugin has a regression bug in Joomla 4.0.6 affecting only its redirects which display ''Internal Server Error 500'' instead of redirecting.<br />
<br />
<!--T:4--><br />
==Versions affected== <!--refers to and other information below --><br />
{{tip|This pertains only to Joomla! version(s): '''4.0.6'''|title=General Information}} <!-- add the version(s) you need --><br />
<br />
<!--T:5--><br />
==What is the cause== <!-- Cause if known --><br />
<br />
<!--T:6--><br />
This is due to a PHP error in the Redirect plugin on updating the corresponding redirect counter, that is uncatched.<br />
<br />
<!--T:7--><br />
==How to fix== <!-- How to fix it if known --><br />
<br />
<!--T:8--><br />
If you use the "System - Redirects" plugin and already upgraded to Joomla 4.0.6, you have the choice of one of these fixes:<br />
* Once Joomla 4.1 (or 4.0.7) are released, upgrade.<br />
* either downgrade your site to Joomla 4.0.5,<br />
* or temporarily disable the "System - Redirect" plugin<br />
* or apply the [https://github.com/joomla/joomla-cms/pull/36733/files<br />
bugfix #36733] by editing file ''plugins/system/redirect/redirect.php'' and changing the part "''$db->''" to "''$this->db->''" on line 243 as shown in the diff on [https://github.com/joomla/joomla-cms/pull/36733/files bugfix #36733].</translate><br />
<br />
__NOTOC__<br />
<!-- Change if needed --><br />
<br />
<noinclude><br />
[[Category:Joomla! 4.x{{#translation:}}]]<br />
[[Category:Version_4.0_FAQ{{#translation:}}]]<br />
[[Category:Version 4.0.6 FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Sportegioco&diff=873348User talk:Sportegioco2022-01-23T09:43:09Z<p>Sandra97: Created page with "{{Translator welcome}} (~~~~)"</p>
<hr />
<div>{{Translator welcome}} ([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 03:43, 23 January 2022 (CST))</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Sandra97&diff=823837User talk:Sandra972021-09-29T05:39:13Z<p>Sandra97: /* Comment traduire une page qui n'est pas "Traduire cette page" */</p>
<hr />
<div>{{Translator welcome}}<br />
<br />
== New Tables ==<br />
<br />
Sandra<br />
<br />
I added two pages to your user pages: [[User:Sandra97/Responsive Tables]] and [[User:Sandra97/jforeground.css]]. Adjust the css page to see the changes immediately after saving it. Have fun!<br />
<br />
Tom<br />
<br />
Placed by [[User:JoomlaWikiBot|JoomlaWikiBot]] ([[User talk:JoomlaWikiBot|talk]]) 10:48, 2 July 2017 (CDT)<br />
<br />
== Mori0725ken: Joomla Volunteers Portal Account has added ==<br />
<br />
Hello Sandra,<br />
<br />
I'm Mori0725ken. I have created an Joomla Volunteers Portal Account, so you can add me to the Documentation Translation Team.<br />
<br />
For any other question, please tell me anytime.<br />
<br />
Thank you!<br />
<br />
Liao Yu Hsuan (KenSanzhi,DenshadeGo)<br />
<br />
[[User:Mori0725ken|電車でGO]] ([[User talk:Mori0725ken|talk]]) 19:14, 4 July 2017 (CDT)<br />
<br />
<sub>Texte en indice</sub>== A new volunteer ==<br />
Hello, would you please add me to "Translator" group. (Russian) --[[User:Cronolio|Cronolio]] ([[User talk:Cronolio|talk]]) 10:33, 25 April 2018 (CDT)<br />
<br /><br />
<br /><br />
<br />
Hello, <br /><br />
You need first to confirm your email and add your name to this page: [[JDOC:Documentation_Translators|Translate JDocs]], in your language section.<br /><br />
Then, I will grant you translator permissions and send you a welcome message with useful links. <br />
I stay at your disposal of course! <br /><br />
<br />
== Help to translate "typehinted to require a callable" ==<br />
<br />
Bonjour Sandra, je tombe régulièrement sur cette expression dans cette page https://docs.joomla.org/index.php?title=Special:Translate&group=page-Potential+backward+compatibility+issues+in+Joomla+4&language=fr&action=page et je ne sais pas la traduire : "typehinted to require a callable". Pourrais-tu m'aider, s'il te plaît ?<br />
<br />
Laurent<br />
<br />
<br />
---<br />
<br />
Bonjour Laurent, <br /><br />
Je présume que cela a à voir avec les fonctions TypeHint et Call. Je me renseigne et reviens vers toi<br />
<br />
---<br /><br />
Re bonjour Laurent,<br />
<br /><br />
Apparemment un paramètre Type Hint a été ajouté. Ainsi, au lieu d'être une classe dans Joomla (par exemple, Japplication), c'est tout ce qui est appelable (par exemple, une fonction anonyme, un tableau de classe / fonction etc)<br />
<br />
([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 10:47, 25 April 2018 (CDT))<br />
<br />
== Comment traduire une page qui n'est pas "Traduire cette page"==<br />
<br />
Bonjour Sandra, la page https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha ne peux pas être traduite. Du coup, j'ai modifié la page et ajouté les balises permettant la traduction. Est-ce comme cela qu'il faut procéder ? Y-a-t'il une autre demande à faire quelque part pour que l'on puisse la traduire ?<br />
<br />
<br />
Bonjour, <br />
<br />
C'est bon, je l'ai marquée. En effet, une fois les balises ajoutées, il faut cliquer sur 'marquer la page pour traduction" pour activer le système.<br /><br />
La seule modification que j'ai faite est au niveau des balises de traductions pour les catégories (je te laisse le soin de regarder dans le code source).<br />
<br />
---<br />
<br />
Bonjour,<br />
<br />
Merci pour l'information. Mais où trouves-tu l'information "marquer la page pour traduction" ? Je ne vois pas où mettre cela.<br />
J'ai une nouvelle page que je voulais mettre à traduire ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_IIS/IIS7<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
C'est indiqué en haut de la page, à la place de "traduire la page". <br />
J'ai marqué l'autre page à traduire. <br />
Bonne soirée<br />
<br />
---<br />
<br />
Merci, mais je n'ai pas cela d'indiqué en haut de la page mais un texte du genre "Cette page n'est pas marquée pour la traduction" et ce n'est pas cliquable. Tu dois avoir des droits que je n'ai pas.<br />
<br />
---<br />
<br />
Oui, il faut des droits spéciaux pour pouvoir marquer une page<br />
<br />
---<br />
<br />
OK. Merci pour l'info. Du coup, c'est à toi que je demande pour mettre une page à traduire où il y a un lieu pour cela ?<br />
<br />
Voici une nouvelle page à marquer pour la traduction, s'il te plaît ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Nginx.<br />
<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
Non ce n'est pas à moi, je ne suis plus active sur la doc. Tu peux demander à Mike Brandner, qui est le chef d'équipe de la doc.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Sandra97&diff=815620User talk:Sandra972021-09-21T16:22:05Z<p>Sandra97: </p>
<hr />
<div>{{Translator welcome}}<br />
<br />
== New Tables ==<br />
<br />
Sandra<br />
<br />
I added two pages to your user pages: [[User:Sandra97/Responsive Tables]] and [[User:Sandra97/jforeground.css]]. Adjust the css page to see the changes immediately after saving it. Have fun!<br />
<br />
Tom<br />
<br />
Placed by [[User:JoomlaWikiBot|JoomlaWikiBot]] ([[User talk:JoomlaWikiBot|talk]]) 10:48, 2 July 2017 (CDT)<br />
<br />
== Mori0725ken: Joomla Volunteers Portal Account has added ==<br />
<br />
Hello Sandra,<br />
<br />
I'm Mori0725ken. I have created an Joomla Volunteers Portal Account, so you can add me to the Documentation Translation Team.<br />
<br />
For any other question, please tell me anytime.<br />
<br />
Thank you!<br />
<br />
Liao Yu Hsuan (KenSanzhi,DenshadeGo)<br />
<br />
[[User:Mori0725ken|電車でGO]] ([[User talk:Mori0725ken|talk]]) 19:14, 4 July 2017 (CDT)<br />
<br />
<sub>Texte en indice</sub>== A new volunteer ==<br />
Hello, would you please add me to "Translator" group. (Russian) --[[User:Cronolio|Cronolio]] ([[User talk:Cronolio|talk]]) 10:33, 25 April 2018 (CDT)<br />
<br /><br />
<br /><br />
<br />
Hello, <br /><br />
You need first to confirm your email and add your name to this page: [[JDOC:Documentation_Translators|Translate JDocs]], in your language section.<br /><br />
Then, I will grant you translator permissions and send you a welcome message with useful links. <br />
I stay at your disposal of course! <br /><br />
<br />
== Help to translate "typehinted to require a callable" ==<br />
<br />
Bonjour Sandra, je tombe régulièrement sur cette expression dans cette page https://docs.joomla.org/index.php?title=Special:Translate&group=page-Potential+backward+compatibility+issues+in+Joomla+4&language=fr&action=page et je ne sais pas la traduire : "typehinted to require a callable". Pourrais-tu m'aider, s'il te plaît ?<br />
<br />
Laurent<br />
<br />
<br />
---<br />
<br />
Bonjour Laurent, <br /><br />
Je présume que cela a à voir avec les fonctions TypeHint et Call. Je me renseigne et reviens vers toi<br />
<br />
---<br /><br />
Re bonjour Laurent,<br />
<br /><br />
Apparemment un paramètre Type Hint a été ajouté. Ainsi, au lieu d'être une classe dans Joomla (par exemple, Japplication), c'est tout ce qui est appelable (par exemple, une fonction anonyme, un tableau de classe / fonction etc)<br />
<br />
([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 10:47, 25 April 2018 (CDT))<br />
<br />
== Comment traduire une page qui n'est pas "Traduire cette page"==<br />
<br />
Bonjour Sandra, la page https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha ne peux pas être traduite. Du coup, j'ai modifié la page et ajouté les balises permettant la traduction. Est-ce comme cela qu'il faut procéder ? Y-a-t'il une autre demande à faire quelque part pour que l'on puisse la traduire ?<br />
<br />
<br />
Bonjour, <br />
<br />
C'est bon, je l'ai marquée. En effet, une fois les balises ajoutées, il faut cliquer sur 'marquer la page pour traduction" pour activer le système.<br /><br />
La seule modification que j'ai faite est au niveau des balises de traductions pour les catégories (je te laisse le soin de regarder dans le code source).<br />
<br />
---<br />
<br />
Bonjour,<br />
<br />
Merci pour l'information. Mais où trouves-tu l'information "marquer la page pour traduction" ? Je ne vois pas où mettre cela.<br />
J'ai une nouvelle page que je voulais mettre à traduire ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_IIS/IIS7<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
C'est indiqué en haut de la page, à la place de "traduire la page". <br />
J'ai marqué l'autre page à traduire. <br />
Bonne soirée<br />
<br />
---<br />
<br />
Merci, mais je n'ai pas cela d'indiqué en haut de la page mais un texte du genre "Cette page n'est pas marquée pour la traduction" et ce n'est pas cliquable. Tu dois avoir des droits que je n'ai pas.<br />
<br />
---<br />
<br />
Oui, il faut des droits spéciaux pour pouvoir marquer une page</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Sandra97&diff=815590User talk:Sandra972021-09-21T15:16:29Z<p>Sandra97: /* Comment traduire une page qui n'est pas "Traduire cette page" */</p>
<hr />
<div>{{Translator welcome}}<br />
<br />
== New Tables ==<br />
<br />
Sandra<br />
<br />
I added two pages to your user pages: [[User:Sandra97/Responsive Tables]] and [[User:Sandra97/jforeground.css]]. Adjust the css page to see the changes immediately after saving it. Have fun!<br />
<br />
Tom<br />
<br />
Placed by [[User:JoomlaWikiBot|JoomlaWikiBot]] ([[User talk:JoomlaWikiBot|talk]]) 10:48, 2 July 2017 (CDT)<br />
<br />
== Mori0725ken: Joomla Volunteers Portal Account has added ==<br />
<br />
Hello Sandra,<br />
<br />
I'm Mori0725ken. I have created an Joomla Volunteers Portal Account, so you can add me to the Documentation Translation Team.<br />
<br />
For any other question, please tell me anytime.<br />
<br />
Thank you!<br />
<br />
Liao Yu Hsuan (KenSanzhi,DenshadeGo)<br />
<br />
[[User:Mori0725ken|電車でGO]] ([[User talk:Mori0725ken|talk]]) 19:14, 4 July 2017 (CDT)<br />
<br />
<sub>Texte en indice</sub>== A new volunteer ==<br />
Hello, would you please add me to "Translator" group. (Russian) --[[User:Cronolio|Cronolio]] ([[User talk:Cronolio|talk]]) 10:33, 25 April 2018 (CDT)<br />
<br /><br />
<br /><br />
<br />
Hello, <br /><br />
You need first to confirm your email and add your name to this page: [[JDOC:Documentation_Translators|Translate JDocs]], in your language section.<br /><br />
Then, I will grant you translator permissions and send you a welcome message with useful links. <br />
I stay at your disposal of course! <br /><br />
<br />
== Help to translate "typehinted to require a callable" ==<br />
<br />
Bonjour Sandra, je tombe régulièrement sur cette expression dans cette page https://docs.joomla.org/index.php?title=Special:Translate&group=page-Potential+backward+compatibility+issues+in+Joomla+4&language=fr&action=page et je ne sais pas la traduire : "typehinted to require a callable". Pourrais-tu m'aider, s'il te plaît ?<br />
<br />
Laurent<br />
<br />
<br />
---<br />
<br />
Bonjour Laurent, <br /><br />
Je présume que cela a à voir avec les fonctions TypeHint et Call. Je me renseigne et reviens vers toi<br />
<br />
---<br /><br />
Re bonjour Laurent,<br />
<br /><br />
Apparemment un paramètre Type Hint a été ajouté. Ainsi, au lieu d'être une classe dans Joomla (par exemple, Japplication), c'est tout ce qui est appelable (par exemple, une fonction anonyme, un tableau de classe / fonction etc)<br />
<br />
([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 10:47, 25 April 2018 (CDT))<br />
<br />
== Comment traduire une page qui n'est pas "Traduire cette page"==<br />
<br />
Bonjour Sandra, la page https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha ne peux pas être traduite. Du coup, j'ai modifié la page et ajouté les balises permettant la traduction. Est-ce comme cela qu'il faut procéder ? Y-a-t'il une autre demande à faire quelque part pour que l'on puisse la traduire ?<br />
<br />
<br />
Bonjour, <br />
<br />
C'est bon, je l'ai marquée. En effet, une fois les balises ajoutées, il faut cliquer sur 'marquer la page pour traduction" pour activer le système.<br /><br />
La seule modification que j'ai faite est au niveau des balises de traductions pour les catégories (je te laisse le soin de regarder dans le code source).<br />
<br />
Bonjour,<br />
<br />
Merci pour l'information. Mais où trouves-tu l'information "marquer la page pour traduction" ? Je ne vois pas où mettre cela.<br />
J'ai une nouvelle page que je voulais mettre à traduire ː https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_IIS/IIS7<br />
<br />
---<br />
<br />
Bonjour, <br />
<br />
C'est indiqué en haut de la page, à la place de "traduire la page". <br />
J'ai marqué l'autre page à traduire. <br />
Bonne soirée</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Enabling_Search_Engine_Friendly_(SEF)_URLs_on_IIS/IIS7&diff=815579Enabling Search Engine Friendly (SEF) URLs on IIS/IIS72021-09-21T15:15:04Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--><br />
If you have a server running IIS 7 and PHP, you can take advantage of IIS's own internal URL rewriting by using a web.config file similar to the one listed below.</translate><br />
<br />
<translate><!--T:2--><br />
You can create the file yourself or use the GUI in the IIS7 Manager. You can import .htaccess rules using the GUI/wizard.</translate><br />
<br />
<translate><!--T:3--><br />
This functionality depends on the presence of the '''IIS URL Rewrite Module''', which does not come with Windows. It is a free download and a Microsoft product.</translate><br />
<br />
<translate>===GUI=== <!--T:4--></translate><br />
<translate><!--T:5--><br />
If the IIS URL Rewrite module is installed, your website manager will have a tool for "URL Rewrite", visible in the IIS Manager's view of your site's configurable IIS modules. The interface is largely self-explanatory. Regular expressions, wildcards or exact matches are all supported.</translate><br />
<br />
<translate><!--T:6--><br />
In the Joomla config turn on both the SEF and Apache mod_rewrite, next create a rule under IIS URL Rewrite:</translate><br />
:Pattern field: '''^([^/]+)/?$'''<br />
:Ignore case '''ON'''<br />
:Action type: '''Rewrite'''<br />
:Rewrite URL: '''index.php/'''<br />
<br />
<translate>===web.config=== <!--T:7--></translate><br />
<translate><!--T:8--><br />
This has been tested on Joomla 1.5 with IIS 7 on Windows Server 2008 with no problems so far. For more information on converting .htaccess to web.config, check out http://learn.iis.net/page.aspx/557/translate-htaccess-content-to-iis-webconfig/</translate><br />
<br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<configuration><br />
<system.webServer><br />
<rewrite><br />
<rules><br />
<clear /><br />
<rule name="Common Exploit Blocking" stopProcessing="true"><br />
<match url="^(.*)$" /><br />
<conditions logicalGrouping="MatchAny"><br />
<add input="{QUERY_STRING}" pattern="mosConfig_[a-zA-Z_]{1,21}(=|\%3D)" /><br />
<add input="{QUERY_STRING}" pattern="base64_encode.*\(.*\)" /><br />
<add input="{QUERY_STRING}" pattern="(\&lt;|%3C).*script.*(\>|%3E)" /><br />
<add input="{QUERY_STRING}" pattern="GLOBALS(=|\[|\%[0-9A-Z]{0,2})" /><br />
<add input="{QUERY_STRING}" pattern="_REQUEST(=|\[|\%[0-9A-Z]{0,2})" /><br />
</conditions><br />
<action type="Redirect" url="index.php" appendQueryString="false" redirectType="SeeOther" /><br />
</rule><br />
<rule name="Joomla Search Rule" stopProcessing="true"><br />
<match url="(.*)" ignoreCase="true" /><br />
<conditions logicalGrouping="MatchAll"><br />
<add input="{URL}" pattern="^/search.php" ignoreCase="true" /><br />
</conditions><br />
<action type="Rewrite" url="/index.php?option=com_content&amp;view=article&amp;id=4" /><br />
</rule><br />
<rule name="Joomla Main Rewrite Rule" stopProcessing="true"><br />
<match url="(.*)" ignoreCase="true" /><br />
<conditions logicalGrouping="MatchAll"><br />
<add input="{URL}" pattern="(/[^.]*|\.(php|html?|feed|pdf|raw))$" /><br />
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /><br />
<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /><br />
</conditions><br />
<action type="Rewrite" url="index.php/" /><br />
</rule><br />
</rules><br />
</rewrite><br />
<caching><br />
<profiles><br />
<add extension=".php" policy="DisableCache" kernelCachePolicy="DisableCache" /><br />
</profiles><br />
</caching><br />
</system.webServer><br />
</configuration><br />
<br />
</source><br />
<noinclude><br />
[[Category:IIS]]<br />
[[Category:Search Engine Friendly URLs]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Sandra97&diff=815249User talk:Sandra972021-09-20T09:33:55Z<p>Sandra97: /* Comment traduire une page qui n'est pas "Traduire cette page" */</p>
<hr />
<div>{{Translator welcome}}<br />
<br />
== New Tables ==<br />
<br />
Sandra<br />
<br />
I added two pages to your user pages: [[User:Sandra97/Responsive Tables]] and [[User:Sandra97/jforeground.css]]. Adjust the css page to see the changes immediately after saving it. Have fun!<br />
<br />
Tom<br />
<br />
Placed by [[User:JoomlaWikiBot|JoomlaWikiBot]] ([[User talk:JoomlaWikiBot|talk]]) 10:48, 2 July 2017 (CDT)<br />
<br />
== Mori0725ken: Joomla Volunteers Portal Account has added ==<br />
<br />
Hello Sandra,<br />
<br />
I'm Mori0725ken. I have created an Joomla Volunteers Portal Account, so you can add me to the Documentation Translation Team.<br />
<br />
For any other question, please tell me anytime.<br />
<br />
Thank you!<br />
<br />
Liao Yu Hsuan (KenSanzhi,DenshadeGo)<br />
<br />
[[User:Mori0725ken|電車でGO]] ([[User talk:Mori0725ken|talk]]) 19:14, 4 July 2017 (CDT)<br />
<br />
<sub>Texte en indice</sub>== A new volunteer ==<br />
Hello, would you please add me to "Translator" group. (Russian) --[[User:Cronolio|Cronolio]] ([[User talk:Cronolio|talk]]) 10:33, 25 April 2018 (CDT)<br />
<br /><br />
<br /><br />
<br />
Hello, <br /><br />
You need first to confirm your email and add your name to this page: [[JDOC:Documentation_Translators|Translate JDocs]], in your language section.<br /><br />
Then, I will grant you translator permissions and send you a welcome message with useful links. <br />
I stay at your disposal of course! <br /><br />
<br />
== Help to translate "typehinted to require a callable" ==<br />
<br />
Bonjour Sandra, je tombe régulièrement sur cette expression dans cette page https://docs.joomla.org/index.php?title=Special:Translate&group=page-Potential+backward+compatibility+issues+in+Joomla+4&language=fr&action=page et je ne sais pas la traduire : "typehinted to require a callable". Pourrais-tu m'aider, s'il te plaît ?<br />
<br />
Laurent<br />
<br />
<br />
---<br />
<br />
Bonjour Laurent, <br /><br />
Je présume que cela a à voir avec les fonctions TypeHint et Call. Je me renseigne et reviens vers toi<br />
<br />
---<br /><br />
Re bonjour Laurent,<br />
<br /><br />
Apparemment un paramètre Type Hint a été ajouté. Ainsi, au lieu d'être une classe dans Joomla (par exemple, Japplication), c'est tout ce qui est appelable (par exemple, une fonction anonyme, un tableau de classe / fonction etc)<br />
<br />
([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 10:47, 25 April 2018 (CDT))<br />
<br />
== Comment traduire une page qui n'est pas "Traduire cette page"==<br />
<br />
Bonjour Sandra, la page https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha ne peux pas être traduite. Du coup, j'ai modifié la page et ajouté les balises permettant la traduction. Est-ce comme cela qu'il faut procéder ? Y-a-t'il une autre demande à faire quelque part pour que l'on puisse la traduire ?<br />
<br />
<br />
Bonjour, <br />
<br />
C'est bon, je l'ai marquée. En effet, une fois les balises ajoutées, il faut cliquer sur 'marquer la page pour traduction" pour activer le système.<br /><br />
La seule modification que j'ai faite est au niveau des balises de traductions pour les catégories (je te laisse le soin de regarder dans le code source).</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Hiawatha&diff=815244Enabling Search Engine Friendly (SEF) URLs on Hiawatha2021-09-20T09:31:31Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--><br />
Use the following UrlToolkit rule to enable clean URLs on the Hiawatha webserver:</translate><br />
<br />
<pre><br />
UrlToolkit {<br />
ToolkitID = joomla<br />
Match base64_encode.*\(.*\) DenyAccess<br />
Match (<|%3C).*script.*(>|%3E) DenyAccess<br />
Match GLOBALS(=|\[|\%[0-9A-Z]{0,2}) DenyAccess<br />
Match _REQUEST(=|\[|\%[0-9A-Z]{0,2}) DenyAccess<br />
RequestURI exists Return<br />
Match /index.php Return<br />
Match ^/component/ Skip 2<br />
Match ^(/|\.php|\.html|\.htm|\.feed|\.pdf|\.raw|/[^.]*)$ Skip 1<br />
Skip 1<br />
Match .* Rewrite /index.php<br />
}<br />
</pre><br />
<br />
<translate><!--T:2--><br />
Enable an UrlToolkit rule for a virtual host via the UseToolkit setting:</translate><br />
<br />
<pre><br />
VirtualHost {<br />
...<br />
UseToolkit = joomla<br />
}<br />
</pre><br />
<br />
<noinclude><br />
[[Category:Tips and tricks{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
[[Category:Installation{{#translation:}}]]<br />
[[Category:Server configurations{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784478J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:38:28Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate><br />
<br />
<translate><!--T:3--> The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate><br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<br />
<translate><!--T:8--> Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate><!--T:9--> * Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate><!--T:10--> * Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed == <!--T:11--><br />
</translate><br />
<br />
<translate><!--T:12--> Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate><!--T:13--> * Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate><!--T:14--> * Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate><!--T:15--> This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website== <!--T:16--><br />
</translate><br />
<br />
<translate><!--T:17--> As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<br />
[...]<br />
<translate><!--T:18--><br />
''I consider the practical risk of this to be low. In order to attack this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds twice, so one could maybe reduce the possible options for the key to a few million, which is still very impractical for a real attack.''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:19--> And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<br />
[...]<br />
<translate><!--T:20--><br />
''The code by default uses 10 bytes for the secret. 10 bytes is 80 bits. The risk here is low. 80 bits is still outside of any practical attack. Nevertheless I think security requirements (and even recommendations) of the RFC should be followed, so I recommend changing this to 20 bytes (aka 160 bits).''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:22--> Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate><!--T:23--> It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784477J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:37:58Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate><br />
<br />
<translate><!--T:3--> The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate><br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<br />
<translate><!--T:8--> Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate><!--T:9--> * Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate><!--T:10--> * Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed == <!--T:11--><br />
</translate><br />
<br />
<translate><!--T:12--> Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate><!--T:13--> * Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate><!--T:14--> * Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate><!--T:15--> This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website== <!--T:16--><br />
</translate><br />
<br />
<translate><!--T:17--> As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<br />
[...]<br />
<translate><!--T:18--><br />
''I consider the practical risk of this to be low. In order to attack this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds twice, so one could maybe reduce the possible options for the key to a few million, which is still very impractical for a real attack.''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:19--> And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<br />
[...]<br />
<translate><!--T:20--><br />
''The code by default uses 10 bytes for the secret. 10 bytes is 80 bits.''<br />
<br />
''The risk here is low. 80 bits is still outside of any practical attack. Nevertheless I think security requirements (and even recommendations) of the RFC should be followed, so I recommend changing this to 20 bytes (aka 160 bits).''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:22--> Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate><!--T:23--> It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784476J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:36:26Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate><br />
<br />
<translate><!--T:3--> The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate><br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<br />
<translate><!--T:8--> Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate><!--T:9--> * Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate><!--T:10--> * Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed == <!--T:11--><br />
</translate><br />
<br />
<translate><!--T:12--> Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate><!--T:13--> * Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate><!--T:14--> * Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate><!--T:15--> This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website== <!--T:16--><br />
</translate><br />
<br />
<translate><!--T:17--> As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<br />
[...]<br />
<translate><!--T:18--><br />
''I consider the practical risk of this to be low. In order to attack<br />
this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds<br />
twice, so one could maybe reduce the possible options for the key to a<br />
few million, which is still very impractical for a real attack.''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:19--> And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<br />
[...]<br />
<translate><!--T:20--><br />
''The code by default uses 10 bytes for the secret. 10 bytes is 80 bits.''<br />
<br />
<!--T:21--><br />
''The risk here is low. 80 bits is still outside of any practical attack.<br />
Nevertheless I think security requirements (and even recommendations)<br />
of the RFC should be followed, so I recommend changing this to 20 bytes<br />
(aka 160 bits).''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:22--> Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate><!--T:23--> It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784475J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:36:04Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate><br />
<br />
<translate><!--T:3--> The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate><br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<br />
<translate><!--T:8--> Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate><!--T:9--> * Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate><!--T:10--> * Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed == <!--T:11--><br />
</translate><br />
<br />
<translate><!--T:12--> Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate><!--T:13--> * Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate><!--T:14--> * Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate><!--T:15--> This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website== <!--T:16--><br />
</translate><br />
<br />
<translate><!--T:17--> As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<br />
[...]<br />
<translate><!--T:18--><br />
''I consider the practical risk of this to be low. In order to attack<br />
this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds<br />
twice, so one could maybe reduce the possible options for the key to a<br />
few million, which is still very impractical for a real attack.''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:19--> And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<br />
[...]<br />
<translate><!--T:20--><br />
''The code by default uses 10 bytes for the secret. 10 bytes is 80 bits.<br />
<br />
<!--T:21--><br />
The risk here is low. 80 bits is still outside of any practical attack.<br />
Nevertheless I think security requirements (and even recommendations)<br />
of the RFC should be followed, so I recommend changing this to 20 bytes<br />
(aka 160 bits).''</translate><br />
[...]<br />
<br />
<br />
<translate><!--T:22--> Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate><!--T:23--> It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784449J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:25:50Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported== <!--T:2--><br />
</translate><br />
<br />
<translate><!--T:3--> The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:4--><br />
</translate><br />
{{tip|<translate><!--T:5--> This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate><!--T:6--> General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause== <!--T:7--><br />
</translate><br />
<br />
<translate><!--T:8--> Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate><!--T:9--> * Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate><!--T:10--> * Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed == <!--T:11--><br />
</translate><br />
<br />
<translate><!--T:12--> Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate><!--T:13--> * Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate><!--T:14--> * Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate><!--T:15--> This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website== <!--T:16--><br />
</translate><br />
<br />
<translate><!--T:17--> As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<source><br />
[...]<br />
<translate><!--T:18--><br />
I consider the practical risk of this to be low. In order to attack<br />
this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds<br />
twice, so one could maybe reduce the possible options for the key to a<br />
few million, which is still very impractical for a real attack.</translate><br />
[...]<br />
</source><br />
<br />
<translate><!--T:19--> And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<source><br />
[...]<br />
<translate><!--T:20--><br />
The code by default uses 10 bytes for the secret. 10 bytes is 80 bits.<br />
<br />
<!--T:21--><br />
The risk here is low. 80 bits is still outside of any practical attack.<br />
Nevertheless I think security requirements (and even recommendations)<br />
of the RFC should be followed, so I recommend changing this to 20 bytes<br />
(aka 160 bits).</translate><br />
[...]<br />
</source><br />
<br />
<translate><!--T:22--> Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate><!--T:23--> It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites&diff=784448J3.x:Changes to the 2FA token generation recommendations for existing sites2021-03-04T15:25:32Z<p>Sandra97: Tag for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate>This page includes details about the security patches released with Joomla 3.9.25 regarding the 2FA setup. Here you can find an impact analyse and also recommendations for exisiting sites.</translate><br />
<br />
<translate><br />
==Errors reported==<br />
</translate><br />
<br />
<translate>The JSST has been contacted by the security reseacher Hanno Böck and has been made aware of two issues within the code that have been fixed by this update.</translate><br />
<br />
<translate><br />
==Versions affected==<br />
</translate><br />
{{tip|<translate>This pertains only to Joomla! version(s)</translate>: '''3.2.0 - 3.9.24'''|title=<translate>General Information</translate>}} <br />
<br />
<translate><br />
==What is the cause==<br />
</translate><br />
<br />
<translate>Starting from Joomla 3.2.0 the Joomla core ships with core support of 2FA / TOTP. Up until 3.9.25 the implementation had two minor security flaws:</translate><br />
<translate>* Usage of the insecure rand() function within the process of generating the 2FA secret.</translate><br />
<translate>* Usage of an insufficient length for the 2FA secret according to RFC 4226 of 10 bytes vs 20 bytes</translate> <br />
<br />
<translate><br />
==How it was fixed ==<br />
</translate><br />
<br />
<translate>Starting with Joomla 3.9.25 the Joomla core implementation has been updated to:</translate><br />
<translate>* Use an secure random function (random_int; backported to older PHP version by the library paragonie/random_compat)</translate><br />
<translate>* Use 20 bytes vs the old value of 10 bytes to generate the 2FA secret.</translate><br />
<br />
<translate>This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.</translate><br />
<br />
<translate><br />
==Does this affect my website==<br />
</translate><br />
<br />
<translate>As stated in the intilal report provided by Hanno Böck he said regarding the usage of the insecure rand function:</translate><br />
<source><br />
[...]<br />
<translate>I consider the practical risk of this to be low. In order to attack<br />
this an attacker would have to know the approximate time when the<br />
person created his TOTP secret. PHP internally mixes in microseconds<br />
twice, so one could maybe reduce the possible options for the key to a<br />
few million, which is still very impractical for a real attack.</translate><br />
[...]<br />
</source><br />
<br />
<translate>And for the usage of 10 vs 20 bytes he said the following:</translate><br />
<source><br />
[...]<br />
<translate>The code by default uses 10 bytes for the secret. 10 bytes is 80 bits.<br />
<br />
The risk here is low. 80 bits is still outside of any practical attack.<br />
Nevertheless I think security requirements (and even recommendations)<br />
of the RFC should be followed, so I recommend changing this to 20 bytes<br />
(aka 160 bits).</translate><br />
[...]<br />
</source><br />
<br />
<translate>Based on that information the JSST came to the conclusion to obviously implement the changes as note above but this does explicite not mean that practically all 2FA tokes generated prior the patch have to be regenerated as they still work as expected and are still secure form a practical standpoint.</translate><br />
<translate>It should also be obvious that the changes made here only affect secrets generated after this change.</translate> <br />
<br />
__NOTOC__<br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Unable_to_use_a_none_alphabethic_first_character_in_folder_name&diff=784415J3.x:Unable to use a none alphabethic first character in folder name2021-03-04T12:34:17Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> Websites updating to Joomla 3.9.25 trying to set an image or file path in com_media or a folder in mod_random_image which doesn't start with an alphabetic leads to an error.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:2--><br />
</translate><br />
{{tip|<translate><!--T:3--> This pertains only to Joomla! version(s):</translate> '''3.9.25'''|title=<translate><!--T:4--> General Information</translate>}}<br />
<br />
<translate><br />
==What is the cause== <!--T:5--></translate><br />
<translate><!--T:6--><br />
Due to a security update we no longer allow relative path strings in com_media configuration for image path and file path setting. The same filter is used in mod_random_image for the folder property. In case you try to use a character other then a-z as first character you get an error message that this path is not allowed for example "1-images".<br />
</translate><br />
<br />
{{tip|<translate><!--T:11--> When we talk about "folder" we only talk about the first main folder, not about subfolders. So creating "images/2021-03-01" is absolutely fine.</translate>|title= <translate><!--T:12--> Important Information</translate>}}<br />
<br />
* <translate><!--T:13--> Did you change the default images main folder in Joomla! in the com_media options? If you didn't change it you won't have any issues</translate><br />
* <translate><!--T:14--> If "Yes", did you change the default images main folder to a folder starting with a non-alphabetic character (like "1-images" or "Ø-test")? If you didn't, you won't have any issues.</translate><br />
* <translate><!--T:15--> If "Yes" then you can't save the com_media options anymore. (But as mentioned before all media files are still working fine).</translate><br />
<br />
<translate><!--T:16--> The same issue occurs in the "mod_random_image" module. Existing modules will continue working as before. If you create a new one and the first character in the folder path is a non-alphabetical character, you can't save the form.</translate><br />
<br />
<translate>==How to fix== <!--T:7--><br />
</translate><br />
<translate><!--T:8--><br />
Update to Joomla 3.9.26 when it is released.<br />
</translate><br />
<translate><!--T:9--><br />
'''Use the following workaround only if you really need it!'''<br />
<br />
<!--T:10--><br />
In the meantime you remove the lines 53 to 56 in the file libraries/src/Form/Rule/FilePathRule.php ([https://github.com/joomla/joomla-cms/blob/2387bb05a11232245dde236859e1896189b62f0d/libraries/src/Form/Rule/FilePathRule.php#L53-L56 File on Github])<br />
</translate><br />
<br />
__NOTOC__<br />
<br />
<!-- Change if needed --><br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Unable_to_use_a_none_alphabethic_first_character_in_folder_name&diff=784414J3.x:Unable to use a none alphabethic first character in folder name2021-03-04T12:33:54Z<p>Sandra97: Tag for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> Websites updating to Joomla 3.9.25 trying to set an image or file path in com_media or a folder in mod_random_image which doesn't start with an alphabetic leads to an error.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:2--><br />
</translate><br />
{{tip|<translate><!--T:3--> This pertains only to Joomla! version(s):</translate> '''3.9.25'''|title=<translate><!--T:4--> General Information</translate>}}<br />
<br />
<translate><br />
==What is the cause== <br />
<!--T:5--></translate><br />
<translate><!--T:6--><br />
Due to a security update we no longer allow relative path strings in com_media configuration for image path and file path setting. The same filter is used in mod_random_image for the folder property. In case you try to use a character other then a-z as first character you get an error message that this path is not allowed for example "1-images".<br />
</translate><br />
<br />
{{tip|<translate>When we talk about "folder" we only talk about the first main folder, not about subfolders. So creating "images/2021-03-01" is absolutely fine.</translate>|title= <translate>Important Information</translate>}}<br />
<br />
* <translate>Did you change the default images main folder in Joomla! in the com_media options? If you didn't change it you won't have any issues</translate><br />
* <translate>If "Yes", did you change the default images main folder to a folder starting with a non-alphabetic character (like "1-images" or "Ø-test")? If you didn't, you won't have any issues.</translate><br />
* <translate>If "Yes" then you can't save the com_media options anymore. (But as mentioned before all media files are still working fine).</translate><br />
<br />
<translate>The same issue occurs in the "mod_random_image" module. Existing modules will continue working as before. If you create a new one and the first character in the folder path is a non-alphabetical character, you can't save the form.</translate><br />
<br />
<translate>==How to fix== <!--T:7--><br />
</translate><br />
<translate><!--T:8--><br />
Update to Joomla 3.9.26 when it is released.<br />
</translate><br />
<translate><!--T:9--><br />
'''Use the following workaround only if you really need it!'''<br />
<br />
<!--T:10--><br />
In the meantime you remove the lines 53 to 56 in the file libraries/src/Form/Rule/FilePathRule.php ([https://github.com/joomla/joomla-cms/blob/2387bb05a11232245dde236859e1896189b62f0d/libraries/src/Form/Rule/FilePathRule.php#L53-L56 File on Github])<br />
</translate><br />
<br />
__NOTOC__<br />
<br />
<!-- Change if needed --><br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Unable_to_use_a_none_alphabethic_first_character_in_folder_name&diff=784299J3.x:Unable to use a none alphabethic first character in folder name2021-03-03T18:47:46Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> Websites updating to Joomla 3.9.25 trying to set a image or file path in com_media or a folder in mod_random_image which doesn't start with an alphabetic leads to an error.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:2--><br />
</translate><br />
{{tip|<translate><!--T:3--> This pertains only to Joomla! version(s):</translate> '''3.9.25'''|title=<translate><!--T:4--> General Information</translate>}}<br />
<br />
<translate><br />
==What is the cause== <!--T:5--></translate><br />
<translate><!--T:6--><br />
Due to a security update we no longer allow relative path strings in com_media configuration for image path and file path setting. The same filter is used in mod_random_image for the folder property. In case you try to use a character other then a-z as first character you get an error message that this path is not allowed for example "1-images".<br />
</translate><br />
<br />
<translate>==How to fix== <!--T:7--><br />
</translate><br />
<translate><!--T:8--><br />
Update to Joomla 3.9.26.<br />
</translate><br />
<translate><!--T:9--><br />
'''Use the following workaround only if you really need it!'''<br />
<br />
<!--T:10--><br />
In the meantime you remove the lines 53 to 56 in the file libraries/src/Form/Rule/FilePathRule.php ([https://github.com/joomla/joomla-cms/blob/2387bb05a11232245dde236859e1896189b62f0d/libraries/src/Form/Rule/FilePathRule.php#L53-L56 File on Github])<br />
</translate><br />
<br />
__NOTOC__<br />
<br />
<!-- Change if needed --><br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.25 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=J3.x:Send_test_mail_for_smtp_fails&diff=772586J3.x:Send test mail for smtp fails2020-12-26T07:07:18Z<p>Sandra97: Marked this version for translation</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--> Websites updating to Joomla 3.9.23 trying to send a test mail using smtp auth may fail.</translate><br />
<br />
<translate><br />
==Versions affected== <!--T:2--><br />
</translate><br />
{{tip|<translate><!--T:3--> This pertains only to Joomla! version(s):</translate> '''3.9.23'''|title=<translate><!--T:4--> General Information</translate>}}<br />
<br />
<translate><br />
==What is the cause== <!--T:5--></translate><br />
<translate><!--T:6--><br />
Due to a security update we no longer show passwords on the global configuration screen. The send test mail function uses the password from the current configuration screen which is empty after saving the configuration.<br />
</translate><br />
<br />
<translate>==How to fix== <!--T:7--><br />
</translate><br />
<translate><!--T:8--><br />
Update to Joomla 3.9.24.<br />
</translate><br />
<translate><!--T:9--><br />
In the meantime you have to entering the SMTP Auth password before sending a test mail.<br />
As alternative you can apply the [https://github.com/joomla/joomla-cms/pull/31515 Pull Request #31515] manually.</translate><br />
<br />
<br />
__NOTOC__<br />
<br />
<!-- Change if needed --><br />
<noinclude><br />
[[Category:Version 3.9 FAQ{{#translation:}}]]<br />
[[Category:Version 3.9.23 FAQ{{#translation:}}]]<br />
[[Category:FAQ{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Shawnhy&diff=772018User talk:Shawnhy2020-12-25T07:11:44Z<p>Sandra97: </p>
<hr />
<div>{{Translator welcome}} ([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 01:11, 25 December 2020 (CST))</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=User_talk:Shawnhy&diff=772017User talk:Shawnhy2020-12-25T07:11:20Z<p>Sandra97: Created page with "(~~~~)"</p>
<hr />
<div>([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 01:11, 25 December 2020 (CST))</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=JDOC:Administrators&diff=771654JDOC:Administrators2020-12-17T09:17:36Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><!--T:1--><br />
'''Administrators''' (also known as '''sysops''' or '''admins''') on [[S:MyLanguage/JDOC:About|Joomla! Documentation]] are users with the permissions to protect and delete pages, block users, and edit protected pages, among other things. Their job is to push forward wiki group projects, keep order and if the need arises, mediate disputes regarding page content.</translate><br />
<br />
<translate><!--T:2--><br />
If you need to contact an administrator, please post a message on their talk page.</translate><br />
<br />
<translate><br />
== Administrators for Joomla! Documentation == <!--T:3--><br />
</translate><br />
<br />
* {{Userlinks|Chris Davenport}} <br />
* {{Userlinks|Dextercowley}}<br />
* {{Userlinks|Tom Hutchison}} <translate><!--T:9--><br />
is a Production member - See [https://volunteers.joomla.org/teams/documentation-working-group Documentation Team]</translate><br />
* {{Userlinks|Wilsonge}} <translate><!--T:10--><br />
is the Production Department Coordinator - See [https://volunteers.joomla.org/departments/production Production Department]</translate><br />
* {{Userlinks|Sandra97}} <translate><!--T:11--><br />
is a Production member - See [https://volunteers.joomla.org/teams/documentation-working-group Documentation Team]</translate><br />
* {{Userlinks|Wilco.alsemgeest}} <translate><!--T:12--><br />
is Operations DC - See [https://volunteers.joomla.org/departments/operations Operations Department]</translate><br />
* {{Userlinks|MartijnM}} <translate><!--T:13--><br />
is a Production member - See [https://volunteers.joomla.org/teams/documentation-working-group Documentation Team]</translate><br />
<br />
<noinclude><br />
<translate><br />
<!--T:6--><br />
[[Category:Documentation Wiki Information]]<br />
</translate><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_Project_Translations&diff=771653Joomla Project Translations2020-12-17T09:09:27Z<p>Sandra97: Removed protection from "Translation of Language Packs"</p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{Top portal heading|color=white-bkgd|icon=language|icon-color=#5091cd|size=3x|text-color=#333|title=Joomla Project Translations}}<br />
<translate><br />
==Joomla! Project Translation and Localization Policy== <!--T:1--></translate><br />
<br />
<translate><br />
=== Preamble === <!--T:2--></translate><br />
<translate><br />
<!--T:3--><br />
UNWANTED MODIFICATION BY JM. The vision of the Joomla Project includes "people around the world using their preferred languages." Translation of the language in the Joomla core files, the help screens and documentation along with other tasks such as working with the Development Team to meet the needs of diverse language communities all help to achieve this.</translate> <translate><!--T:4--> This Translation and Localization Policy is intended to embody that vision while creating a worldwide community that is rewarding and enjoyable to participate in and that maintains the trust of its users. It builds on the core values of the Project which are: freedom, equality, trust, community, collaboration and usability.</translate><br />
<br />
<translate><br />
<!--T:5--><br />
The [https://volunteers.joomla.org/teams/core-translation-team Core Translation Team] is translating the Joomla core and is part of the [https://volunteers.joomla.org/departments/production Production Department].</translate><br />
<br />
<translate><br />
<!--T:6--><br />
The [https://volunteers.joomla.org/teams/community-translation-team Community Translation Team] is translating all the other things like Helpsreens, Documentation, Joomla websites and Marketing communication and is part of the [https://volunteers.joomla.org/departments/marketing-communication Marketing & Communication Department].</translate><br />
<br />
<br />
<translate><br />
=== Translation and Localization Policy === <!--T:7--></translate><br />
<translate><br />
<!--T:8--><br />
Only [https://volunteers.joomla.org/teams/core-translation-team Core Translation Team] members will have their work listed on Joomla.org and related sites and hosted on the [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository].</translate><br />
<br />
<translate><!--T:9--> The Joomla Translation Team Agreement sets the terms for being accepted and continuing as a Core Translation Team. The decision to accept or continue recognition of a Core Translation Team is taken by the [https://forum.joomla.org/memberlist.php?mode=group&g=47 Translation Coordination Team] which is composed of volunteer members drawn from the current local translation coordinators. The [https://forum.joomla.org/memberlist.php?mode=group&g=47 Translation Coordination Team] works under the general oversight of the [https://volunteers.joomla.org/departments/production Production Department].</translate><br />
<br />
<translate><!--T:10--> The Joomla Translation Team Agreement is considered accepted when the local Translation Coordinator is granted access to the Core Translation Team Forum.</translate><br />
<br />
<translate><!--T:11--> By accepting this Joomla Translation Team Agreement, you agree that breaking of any of the terms will lead to the agreement being cancelled. This means:</translate><br />
<br />
* <translate><!--T:12--> The Translation Team will be removed from the Core Translation Team Forum.</translate><br />
* <translate><!--T:13--> All listings on Joomla.org and related sites will be removed.</translate><br />
* <translate><!--T:14--> You will no longer be entitled to use the badge or refer to your team as a Core Translation Team.</translate><br />
<br />
<translate><br />
=== Joomla! Translation Team Agreement === <!--T:15--></translate><br />
<br />
# <translate><!--T:16--> Copies of all language packs, sample data, and help files shall be deposited on the [http://joomlacode.org/gf/project/jtranslation/ Joomla Translation Common Repository] that the Joomla Translation Coordination Team will manage on Joomlacode.org. All language packs will be available for public download. Joomla Translation Teams are encouraged to live up to the core Joomla Project values of freedom and equality as embodied in the GNU GPL by making their help files and sample data publicly available for download just as the works they are derived from are available.</translate><br />
# <translate><!--T:17--> All members of Joomla Translation Teams shall follow the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Code of Conduct for Joomla Volunteers] at all times.</translate><br />
# <translate><!--T:18--> Within specific languages, a spirit of collaboration shall be maintained. If there is already a Joomla Translation Team for a given language, new contributors and teams should seek to cooperate with that team. Existing Joomla Translation Teams must welcome and encourage new contributors.</translate><br />
# <translate><!--T:19--> Translation teams shall remain in contact with the Joomla Translation Coordination Team.</translate><br />
# <translate><!--T:20--> All Translators shall comply with the Open Source Matters trademark policies on name use, logo use, and domain names (See: http://www.opensourcematters.org/licensing.html) and any other relevant policies.</translate><br />
# <translate><!--T:21--> In accepting a Joomla Translation Team for a particular language the Joomla Project does not accept any social, cultural or political claims associated with that language or reject the claims of any other language.</translate><br />
# <translate><!--T:22--> All use of the Joomla Translation Team badge shall comply with the translation badge use policy (below) and the Open Source Matters policy for conditional use logos (link).</translate><br />
# <translate><!--T:23--> Language packs shall be released under the [http://www.fsf.org/licensing/licenses/gpl.html GNU GPL] v2 or later and be distributed at no cost to end users and without requiring registration.</translate><br />
# <translate><!--T:24--> All language packs shall be named: "[ISO name of language]_joomla_lang_[type of package].[joomla version][Eventual pack version]" where:</translate><br />
#* <translate><!--T:25--> [Iso name of language] = xx-XX</translate><br />
#* <translate><!--T:26--> [Eventual pack version] = v2, v3, etc.<br />see tutorial here: [[S:Mylanguage/J3.x:Making_a_Language_Pack_for_Joomla|Making a Language Pack for Joomla]]<br/>example: xx-XX_joomla_lang_full_3.4.1v2.zip</translate><br />
# <translate><!--T:27--> Language packs shall be kept up to date with the current releases of Joomla.</translate><br />
# <translate><!--T:28--> Online help files shall be reachable through Joomla administrator interface and must be available via the Web at no cost to end users. Help files must be licensed using the Joomla Electronic Documentation License and retain all licensing information.</translate><br />
# <translate><!--T:29--> Online help files shall be kept up to date with the current releases of Joomla.</translate><br />
# <translate><!--T:30--> Localized distributions shall not include advertising or links for any site other than Joomla.org sites, the Joomla Translation Team site or sites that are included in the core sample data. The sole exception to this is that a links to English resources or content in translations of the core sample data may be replaced with links to specific equivalent content in the relevant language. These may not be in the form of a general link to a local site.</translate><br />
# <translate><!--T:31--> Localized distributions may include specially created sample data as long as the tone and messages of the sample data are in accord with the Joomla Project's [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Mission, vision and values] and are not detrimental, e.g., harmful or damaging to the value of any of the Joomla Marks, or to the Joomla Project or OSM, its brand integrity, reputation or goodwill, such as by including content that (a) is vulgar, obscene, pornographic, disparaging, defamatory or hateful, (b) includes statements concerning that are libelous, slanderous or otherwise defamatory, or (c) would be considered a criminal offense or would encourage conduct that would be considered a criminal offense or create any civil liability. Requests for modification of sample content made by Open Source Matters must be addressed within five business days.</translate><br />
# <translate><!--T:32--> Localized sample content may include menu links to specific relevant resources in the translation language. It shall include a menu link to Joomla.org.</translate><br />
# <translate><!--T:33--> Localized distributions shall be released at no cost to end users and without requiring registration.</translate><br />
# <translate><!--T:34--> Localized distributions shall be named: "Joomla [version #] in X" where X is the official English name of the language corresponding to the ISO code. For example: en-US would be "Joomla 3.3.6 in English (United States)"</translate><br />
# <translate><!--T:35--> Localized distributions shall be kept up to date with the current releases of Joomla. When releases reach end of life on Joomlacode.org they shall no longer be available on Joomla Translation Team sites.</translate><br />
# <translate><!--T:36--> These terms may be changed by the Joomla Project from time to time. Notification of changes will be published in the Joomla Translation Teams Forum and policies will be posted on the opensourcematters.org Web site.</translate><br />
<br />
<translate><br />
=== Badge Use Policy === <!--T:37--></translate><br />
<translate><br />
<!--T:38--><br />
Joomla Translation Teams may use the Joomla Translation Team badge on their Web sites under certain conditions. These are:</translate><br />
# <translate><!--T:39--> The site is non commercial.</translate><br />
# <translate><!--T:40--> The site complies with all relevant Open Source Matters policies.</translate><br />
# <translate><!--T:41--> The badge must be linked to [http://community.joomla.org/translations.html community.joomla.org/translations.html].</translate><br />
# <translate><!--T:42--> The site makes it clear that it is not an official site of the Joomla Project.</translate><br />
# <translate><!--T:43--> The badge is not altered in any way.</translate><br />
<br />
<translate><br />
=== Licenses === <!--T:44--></translate><br />
# <translate><!--T:45--> Translation of the language in the core files ("language packs" and "sample data") are derivative works and must be licensed using the GNU GPL. Copyrights are both Open Source Matters and author's.</translate><br />
# <translate><!--T:46--> Translations of the installation files that are contributed for release in the official Joomla core release are derivative works and must be provided under GNU GPL. Copyrights are both Open Source Matters and author's. This work is acknowledged in the main credit file of the Joomla CMS. The XML file for the installation may contain author's name. The description should only contain the name of the language in English or local language.</translate><br />
# <translate><!--T:47--> Help screen translations for Joomla 1.5.x and later are governed by the Joomla Electronic Documentation license unless otherwise specified. The license terms and the original copyright attribution must remain unchanged. Translator attribution may be added per screen or globally on the site where the help screens are available online. A link to the JEDL has to be provided on the site.</translate><br />
# <translate><!--T:48--> Documentation translations made from the [[S:Mylanguage/Main_Page| docs.joomla.org]] English originals are governed by the Joomla Electronic Documentation License unless otherwise specified. Translators may add their authorship. Link to the JEDL should be provided on the site.</translate><br />
# <translate><!--T:49--> The following statement must be presented with any localized distribution: "This is an unofficial localized distribution of Joomla. Support of this distribution is only available from the team that created it. It is not warranted by the Joomla Project or Open Source Matters."</translate><br />
<br />
<translate><br />
=== Open Source Matters Policies === <!--T:50--></translate><br />
<translate><!--T:51--> Read this on https://tm.joomla.org/.</translate><br />
<br />
<translate><br />
=== FAQs === <!--T:52--></translate><br />
* <translate><!--T:53--> Are all Joomla Translation Teams required to have their own Web sites?<br /> No. A translator can simply contribute files to the [http://joomlacode.org/gf/project/jtranslation/ Joomla Translation Comon Repository].</translate><br />
* <translate><!--T:54--> Can a commercial company also be a Joomla Translation Team?<br /> Yes. However a commercial company may not use the Joomla Translation Team badge in connection with its business and the listing of teams shall not include the URL of that site. If desired, the listing may include an e-mail address for contacting the team.</translate><br />
* <translate><!--T:55--> Can a commercial company display the Joomla Translation Team badge on its Web site?<br /> No. The badge may only be displayed on noncommercial sites.</translate><br />
* <translate><!--T:56--><br />
I am the owner of a not-for-profit Joomla Translation Team site but I need to make also my living. Can I use using a part of the site for my business?<br /> No. You should have a separate site for your business, but you may place an advertisement for your business on your Joomla Translation Team site. If you have a forum, add a link to your for-profit site in your signature.<br />
* Can there be paid advertising on a Joomla Translation Team Web site?<br /> Yes.</translate><br />
* <translate><!--T:57--> Can I have advertisements for my business site on my Joomla Translation Team web site?<br /> Yes.</translate><br />
* <translate><!--T:58--> Can I have a menu link to my business on my Joomla Translation Team Web site?<br /> No.</translate><br />
* <translate><!--T:59--> Can I call myself a "Joomla Translator" in my forum signature on forum.joomla.org?<br /> Members of Joomla Translation Teams can use the wording:<br /> "Member of the [language] Joomla Translation Team"<br /> You are also encouraged to add the URL of your Joomla Translation Team listing on community.org: [http://community.joomla.org/translations.html community.joomla.org/translations.html]</translate><br />
<br />
<br />
* <translate><!--T:60--> Should I release a single pack for site and administrator translations?<br /> While not required, creating a single pack is for site and administration, including the pdf fonts if necessary, is strongly encouraged.</translate><br />
* <translate><!--T:61--> Where can I find technical guidelines for translation of Joomla?<br /> Language pack: [[S:Mylanguage/Making a Language Pack for Joomla|Making a Language Pack for Joomla 3.x]]<br/>Translation forum: https://forum.joomla.org/viewforum.php?f=11 and International forum: https://forum.joomla.org/viewforum.php?f=511</translate><br />
* <translate><!--T:62--> Do I have to be part of a Joomla Translation Team to create or distribute a Joomla translation?<br /> No. However, please note that all licensing, name use and other legal requirements apply whether or not your team is a Joomla Translation Team.</translate><br />
* <translate><!--T:63--> Can I propose packs for a language not listed?<br /> Please contact the [https://volunteers.joomla.org/teams/core-translation-team Core Translation team].</translate><br />
* <translate><!--T:64--> Do you have an issue with a the quality of a translation or want to collaborate with an existing team?<br /> Contact the Language coordinator listed here: https://community.joomla.org/translations/joomla-3-translations.html</translate><br />
* <translate><!--T:65--> Can the badge be used in printed materials?<br /> Yes, if the usage complies with the Open Source Matters conditional use policy rules for printed matter and the use is non-commercial.</translate><br />
* <translate><!--T:67--> Why must Language Packs be made available on joomlacode.org?<br /> Among other reasons, this will enable joomla.org to create a "Download Joomla in your Language" link that will be easy to use for users and easy access for webmasters who wish to create multilingual sites. As GNU GPL licensed code, Language Packs may also be made available on Joomla Translation Team and other sites.</translate><br />
* <translate><!--T:68--> Why must copies of help screens and sample data be deposited in the Joomla Translation Common Repository on joomlacode.org?<br /> It is important for continuity and assurance of availability for users who depend upon these resources that copies of team work be stored in a central [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository] .</translate><br />
* <translate><!--T:69--> Why are teams strongly encouraged to make sample data and help files available for public download?<br /> Freedom, equality and collaboration are core values of the Joomla Project. One expression of these values is the use of the GNU GPL for licensing. Although the GNU GPL and the JEDL do not require distribution, they strongly value providing users with the ability to use, modify, study and share. They also do not distinguish between classes of users. All Joomla Translation Team members are encouraged to [http://www.gnu.org/philosophy/free-sw.html Learn more about software freedom]. Translators in this sense are encouraged to work under the same principles as developers and documentors who are part of the Joomla Project.</translate><br />
* <translate><!--T:70--> Why does it say that the policy may be changed?<br /> Situations and needs of the Project and its community have changed in the past and will change in the future. As a result the Translation Policy, like all Project policies, may need to change. This statement ensures that notification is given to the entire community if the policy needs to change.</translate><br />
* <translate><!--T:71--> What is the process for making changes in policies?<br /> The Joomla Project makes policies based on discussions with community members, Working Group members, team leads and coordinators, the Leadership Team, and the board of Open Source Matters as well as on the basis of legal and financial advice. Final policy decisions are made by the Leadership Team or the OSM board as appropriate.</translate><br />
<br />
<translate><br />
=== Definitions === <!--T:72--></translate><br />
<br />
* <translate><!--T:73--> A translator is a translation team or individual that translates Joomla.</translate><br />
* <translate><!--T:74--> A translation team is an individual or group which creates or maintains Joomla translations in a specific language.</translate><br />
* <translate><!--T:75--> A Joomla Translation Team is a translation team that is represented in the Joomla Private Translation Forum.</translate><br />
* <translate><!--T:76--> A Local Translation Coordinator is the representative of a Joomla Translation Team who participates in the Joomla Translation Team forum.</translate><br />
* <translate><!--T:77--> A localized distribution is a distribution of Joomla that is preinstalled with a specific language package. It also may include sample content in that language and a link to online help in that language.</translate><br />
* <translate><!--T:78--> The Joomla Translation Coordination Team manages the [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository] and the Joomla Translation Team Forum and coordinates translation related communication with other parts of the Joomla Project. It is a small group drawn from the Local Translation Coordinators.</translate><br />
* <translate><!--T:79--> A Joomla translation team badge is an image file that may be used to identify a Joomla Translation Team if certain conditions are met.</translate><br />
* <translate><!--T:80--> The Joomla Translation Teams Agreement defines the terms and conditions for acceptance as a Joomla Translation Team.</translate><br />
* <translate><!--T:81--> A Joomla Translation Team web site is a site that distributes the work of a specific Joomla Translation Team (either exclusively or along with providing other information or services).</translate><br />
* <translate><!--T:82--> The Joomla Translation Common Repository is the area on [http://joomlacode.org joomlacode.org] where Joomla Translation Teams deposit their work. It is managed by the Joomla Translation Coordination Team.</translate><br />
* <translate><!--T:83--> The Joomla Translation Team Forum is a limited-access forum located on [http://forum.joomla.org/ forum.joomla.org/] for use of Local Translation Coordinators.</translate><br />
<br />
<noinclude><br />
<translate><br />
<!--T:84--><br />
[[Category:Languages]]<br />
[[Category:Language Development]]</translate><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_Project_Translations&diff=771652Joomla Project Translations2020-12-17T09:06:43Z<p>Sandra97: Protected "Translation of Language Packs" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{Top portal heading|color=white-bkgd|icon=language|icon-color=#5091cd|size=3x|text-color=#333|title=Joomla Project Translations}}<br />
<translate><br />
==Joomla! Project Translation and Localization Policy== <!--T:1--></translate><br />
<br />
<translate><br />
=== Preamble === <!--T:2--></translate><br />
<translate><br />
<!--T:3--><br />
UNWANTED MODIFICATION BY JM. The vision of the Joomla Project includes "people around the world using their preferred languages." Translation of the language in the Joomla core files, the help screens and documentation along with other tasks such as working with the Development Team to meet the needs of diverse language communities all help to achieve this.</translate> <translate><!--T:4--> This Translation and Localization Policy is intended to embody that vision while creating a worldwide community that is rewarding and enjoyable to participate in and that maintains the trust of its users. It builds on the core values of the Project which are: freedom, equality, trust, community, collaboration and usability.</translate><br />
<br />
<translate><br />
<!--T:5--><br />
The [https://volunteers.joomla.org/teams/core-translation-team Core Translation Team] is translating the Joomla core and is part of the [https://volunteers.joomla.org/departments/production Production Department].</translate><br />
<br />
<translate><br />
<!--T:6--><br />
The [https://volunteers.joomla.org/teams/community-translation-team Community Translation Team] is translating all the other things like Helpsreens, Documentation, Joomla websites and Marketing communication and is part of the [https://volunteers.joomla.org/departments/marketing-communication Marketing & Communication Department].</translate><br />
<br />
<br />
<translate><br />
=== Translation and Localization Policy === <!--T:7--></translate><br />
<translate><br />
<!--T:8--><br />
Only [https://volunteers.joomla.org/teams/core-translation-team Core Translation Team] members will have their work listed on Joomla.org and related sites and hosted on the [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository].</translate><br />
<br />
<translate><!--T:9--> The Joomla Translation Team Agreement sets the terms for being accepted and continuing as a Core Translation Team. The decision to accept or continue recognition of a Core Translation Team is taken by the [https://forum.joomla.org/memberlist.php?mode=group&g=47 Translation Coordination Team] which is composed of volunteer members drawn from the current local translation coordinators. The [https://forum.joomla.org/memberlist.php?mode=group&g=47 Translation Coordination Team] works under the general oversight of the [https://volunteers.joomla.org/departments/production Production Department].</translate><br />
<br />
<translate><!--T:10--> The Joomla Translation Team Agreement is considered accepted when the local Translation Coordinator is granted access to the Core Translation Team Forum.</translate><br />
<br />
<translate><!--T:11--> By accepting this Joomla Translation Team Agreement, you agree that breaking of any of the terms will lead to the agreement being cancelled. This means:</translate><br />
<br />
* <translate><!--T:12--> The Translation Team will be removed from the Core Translation Team Forum.</translate><br />
* <translate><!--T:13--> All listings on Joomla.org and related sites will be removed.</translate><br />
* <translate><!--T:14--> You will no longer be entitled to use the badge or refer to your team as a Core Translation Team.</translate><br />
<br />
<translate><br />
=== Joomla! Translation Team Agreement === <!--T:15--></translate><br />
<br />
# <translate><!--T:16--> Copies of all language packs, sample data, and help files shall be deposited on the [http://joomlacode.org/gf/project/jtranslation/ Joomla Translation Common Repository] that the Joomla Translation Coordination Team will manage on Joomlacode.org. All language packs will be available for public download. Joomla Translation Teams are encouraged to live up to the core Joomla Project values of freedom and equality as embodied in the GNU GPL by making their help files and sample data publicly available for download just as the works they are derived from are available.</translate><br />
# <translate><!--T:17--> All members of Joomla Translation Teams shall follow the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Code of Conduct for Joomla Volunteers] at all times.</translate><br />
# <translate><!--T:18--> Within specific languages, a spirit of collaboration shall be maintained. If there is already a Joomla Translation Team for a given language, new contributors and teams should seek to cooperate with that team. Existing Joomla Translation Teams must welcome and encourage new contributors.</translate><br />
# <translate><!--T:19--> Translation teams shall remain in contact with the Joomla Translation Coordination Team.</translate><br />
# <translate><!--T:20--> All Translators shall comply with the Open Source Matters trademark policies on name use, logo use, and domain names (See: http://www.opensourcematters.org/licensing.html) and any other relevant policies.</translate><br />
# <translate><!--T:21--> In accepting a Joomla Translation Team for a particular language the Joomla Project does not accept any social, cultural or political claims associated with that language or reject the claims of any other language.</translate><br />
# <translate><!--T:22--> All use of the Joomla Translation Team badge shall comply with the translation badge use policy (below) and the Open Source Matters policy for conditional use logos (link).</translate><br />
# <translate><!--T:23--> Language packs shall be released under the [http://www.fsf.org/licensing/licenses/gpl.html GNU GPL] v2 or later and be distributed at no cost to end users and without requiring registration.</translate><br />
# <translate><!--T:24--> All language packs shall be named: "[ISO name of language]_joomla_lang_[type of package].[joomla version][Eventual pack version]" where:</translate><br />
#* <translate><!--T:25--> [Iso name of language] = xx-XX</translate><br />
#* <translate><!--T:26--> [Eventual pack version] = v2, v3, etc.<br />see tutorial here: [[S:Mylanguage/J3.x:Making_a_Language_Pack_for_Joomla|Making a Language Pack for Joomla]]<br/>example: xx-XX_joomla_lang_full_3.4.1v2.zip</translate><br />
# <translate><!--T:27--> Language packs shall be kept up to date with the current releases of Joomla.</translate><br />
# <translate><!--T:28--> Online help files shall be reachable through Joomla administrator interface and must be available via the Web at no cost to end users. Help files must be licensed using the Joomla Electronic Documentation License and retain all licensing information.</translate><br />
# <translate><!--T:29--> Online help files shall be kept up to date with the current releases of Joomla.</translate><br />
# <translate><!--T:30--> Localized distributions shall not include advertising or links for any site other than Joomla.org sites, the Joomla Translation Team site or sites that are included in the core sample data. The sole exception to this is that a links to English resources or content in translations of the core sample data may be replaced with links to specific equivalent content in the relevant language. These may not be in the form of a general link to a local site.</translate><br />
# <translate><!--T:31--> Localized distributions may include specially created sample data as long as the tone and messages of the sample data are in accord with the Joomla Project's [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Mission, vision and values] and are not detrimental, e.g., harmful or damaging to the value of any of the Joomla Marks, or to the Joomla Project or OSM, its brand integrity, reputation or goodwill, such as by including content that (a) is vulgar, obscene, pornographic, disparaging, defamatory or hateful, (b) includes statements concerning that are libelous, slanderous or otherwise defamatory, or (c) would be considered a criminal offense or would encourage conduct that would be considered a criminal offense or create any civil liability. Requests for modification of sample content made by Open Source Matters must be addressed within five business days.</translate><br />
# <translate><!--T:32--> Localized sample content may include menu links to specific relevant resources in the translation language. It shall include a menu link to Joomla.org.</translate><br />
# <translate><!--T:33--> Localized distributions shall be released at no cost to end users and without requiring registration.</translate><br />
# <translate><!--T:34--> Localized distributions shall be named: "Joomla [version #] in X" where X is the official English name of the language corresponding to the ISO code. For example: en-US would be "Joomla 3.3.6 in English (United States)"</translate><br />
# <translate><!--T:35--> Localized distributions shall be kept up to date with the current releases of Joomla. When releases reach end of life on Joomlacode.org they shall no longer be available on Joomla Translation Team sites.</translate><br />
# <translate><!--T:36--> These terms may be changed by the Joomla Project from time to time. Notification of changes will be published in the Joomla Translation Teams Forum and policies will be posted on the opensourcematters.org Web site.</translate><br />
<br />
<translate><br />
=== Badge Use Policy === <!--T:37--></translate><br />
<translate><br />
<!--T:38--><br />
Joomla Translation Teams may use the Joomla Translation Team badge on their Web sites under certain conditions. These are:</translate><br />
# <translate><!--T:39--> The site is non commercial.</translate><br />
# <translate><!--T:40--> The site complies with all relevant Open Source Matters policies.</translate><br />
# <translate><!--T:41--> The badge must be linked to [http://community.joomla.org/translations.html community.joomla.org/translations.html].</translate><br />
# <translate><!--T:42--> The site makes it clear that it is not an official site of the Joomla Project.</translate><br />
# <translate><!--T:43--> The badge is not altered in any way.</translate><br />
<br />
<translate><br />
=== Licenses === <!--T:44--></translate><br />
# <translate><!--T:45--> Translation of the language in the core files ("language packs" and "sample data") are derivative works and must be licensed using the GNU GPL. Copyrights are both Open Source Matters and author's.</translate><br />
# <translate><!--T:46--> Translations of the installation files that are contributed for release in the official Joomla core release are derivative works and must be provided under GNU GPL. Copyrights are both Open Source Matters and author's. This work is acknowledged in the main credit file of the Joomla CMS. The XML file for the installation may contain author's name. The description should only contain the name of the language in English or local language.</translate><br />
# <translate><!--T:47--> Help screen translations for Joomla 1.5.x and later are governed by the Joomla Electronic Documentation license unless otherwise specified. The license terms and the original copyright attribution must remain unchanged. Translator attribution may be added per screen or globally on the site where the help screens are available online. A link to the JEDL has to be provided on the site.</translate><br />
# <translate><!--T:48--> Documentation translations made from the [[S:Mylanguage/Main_Page| docs.joomla.org]] English originals are governed by the Joomla Electronic Documentation License unless otherwise specified. Translators may add their authorship. Link to the JEDL should be provided on the site.</translate><br />
# <translate><!--T:49--> The following statement must be presented with any localized distribution: "This is an unofficial localized distribution of Joomla. Support of this distribution is only available from the team that created it. It is not warranted by the Joomla Project or Open Source Matters."</translate><br />
<br />
<translate><br />
=== Open Source Matters Policies === <!--T:50--></translate><br />
<translate><!--T:51--> Read this on https://tm.joomla.org/.</translate><br />
<br />
<translate><br />
=== FAQs === <!--T:52--></translate><br />
* <translate><!--T:53--> Are all Joomla Translation Teams required to have their own Web sites?<br /> No. A translator can simply contribute files to the [http://joomlacode.org/gf/project/jtranslation/ Joomla Translation Comon Repository].</translate><br />
* <translate><!--T:54--> Can a commercial company also be a Joomla Translation Team?<br /> Yes. However a commercial company may not use the Joomla Translation Team badge in connection with its business and the listing of teams shall not include the URL of that site. If desired, the listing may include an e-mail address for contacting the team.</translate><br />
* <translate><!--T:55--> Can a commercial company display the Joomla Translation Team badge on its Web site?<br /> No. The badge may only be displayed on noncommercial sites.</translate><br />
* <translate><!--T:56--><br />
I am the owner of a not-for-profit Joomla Translation Team site but I need to make also my living. Can I use using a part of the site for my business?<br /> No. You should have a separate site for your business, but you may place an advertisement for your business on your Joomla Translation Team site. If you have a forum, add a link to your for-profit site in your signature.<br />
* Can there be paid advertising on a Joomla Translation Team Web site?<br /> Yes.</translate><br />
* <translate><!--T:57--> Can I have advertisements for my business site on my Joomla Translation Team web site?<br /> Yes.</translate><br />
* <translate><!--T:58--> Can I have a menu link to my business on my Joomla Translation Team Web site?<br /> No.</translate><br />
* <translate><!--T:59--> Can I call myself a "Joomla Translator" in my forum signature on forum.joomla.org?<br /> Members of Joomla Translation Teams can use the wording:<br /> "Member of the [language] Joomla Translation Team"<br /> You are also encouraged to add the URL of your Joomla Translation Team listing on community.org: [http://community.joomla.org/translations.html community.joomla.org/translations.html]</translate><br />
<br />
<br />
* <translate><!--T:60--> Should I release a single pack for site and administrator translations?<br /> While not required, creating a single pack is for site and administration, including the pdf fonts if necessary, is strongly encouraged.</translate><br />
* <translate><!--T:61--> Where can I find technical guidelines for translation of Joomla?<br /> Language pack: [[S:Mylanguage/Making a Language Pack for Joomla|Making a Language Pack for Joomla 3.x]]<br/>Translation forum: https://forum.joomla.org/viewforum.php?f=11 and International forum: https://forum.joomla.org/viewforum.php?f=511</translate><br />
* <translate><!--T:62--> Do I have to be part of a Joomla Translation Team to create or distribute a Joomla translation?<br /> No. However, please note that all licensing, name use and other legal requirements apply whether or not your team is a Joomla Translation Team.</translate><br />
* <translate><!--T:63--> Can I propose packs for a language not listed?<br /> Please contact the [https://volunteers.joomla.org/teams/core-translation-team Core Translation team].</translate><br />
* <translate><!--T:64--> Do you have an issue with a the quality of a translation or want to collaborate with an existing team?<br /> Contact the Language coordinator listed here: https://community.joomla.org/translations/joomla-3-translations.html</translate><br />
* <translate><!--T:65--> Can the badge be used in printed materials?<br /> Yes, if the usage complies with the Open Source Matters conditional use policy rules for printed matter and the use is non-commercial.</translate><br />
* <translate><!--T:67--> Why must Language Packs be made available on joomlacode.org?<br /> Among other reasons, this will enable joomla.org to create a "Download Joomla in your Language" link that will be easy to use for users and easy access for webmasters who wish to create multilingual sites. As GNU GPL licensed code, Language Packs may also be made available on Joomla Translation Team and other sites.</translate><br />
* <translate><!--T:68--> Why must copies of help screens and sample data be deposited in the Joomla Translation Common Repository on joomlacode.org?<br /> It is important for continuity and assurance of availability for users who depend upon these resources that copies of team work be stored in a central [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository] .</translate><br />
* <translate><!--T:69--> Why are teams strongly encouraged to make sample data and help files available for public download?<br /> Freedom, equality and collaboration are core values of the Joomla Project. One expression of these values is the use of the GNU GPL for licensing. Although the GNU GPL and the JEDL do not require distribution, they strongly value providing users with the ability to use, modify, study and share. They also do not distinguish between classes of users. All Joomla Translation Team members are encouraged to [http://www.gnu.org/philosophy/free-sw.html Learn more about software freedom]. Translators in this sense are encouraged to work under the same principles as developers and documentors who are part of the Joomla Project.</translate><br />
* <translate><!--T:70--> Why does it say that the policy may be changed?<br /> Situations and needs of the Project and its community have changed in the past and will change in the future. As a result the Translation Policy, like all Project policies, may need to change. This statement ensures that notification is given to the entire community if the policy needs to change.</translate><br />
* <translate><!--T:71--> What is the process for making changes in policies?<br /> The Joomla Project makes policies based on discussions with community members, Working Group members, team leads and coordinators, the Leadership Team, and the board of Open Source Matters as well as on the basis of legal and financial advice. Final policy decisions are made by the Leadership Team or the OSM board as appropriate.</translate><br />
<br />
<translate><br />
=== Definitions === <!--T:72--></translate><br />
<br />
* <translate><!--T:73--> A translator is a translation team or individual that translates Joomla.</translate><br />
* <translate><!--T:74--> A translation team is an individual or group which creates or maintains Joomla translations in a specific language.</translate><br />
* <translate><!--T:75--> A Joomla Translation Team is a translation team that is represented in the Joomla Private Translation Forum.</translate><br />
* <translate><!--T:76--> A Local Translation Coordinator is the representative of a Joomla Translation Team who participates in the Joomla Translation Team forum.</translate><br />
* <translate><!--T:77--> A localized distribution is a distribution of Joomla that is preinstalled with a specific language package. It also may include sample content in that language and a link to online help in that language.</translate><br />
* <translate><!--T:78--> The Joomla Translation Coordination Team manages the [http://joomlacode.org/gf/project/jtranslation3_x/frs Joomla Translation Common Repository] and the Joomla Translation Team Forum and coordinates translation related communication with other parts of the Joomla Project. It is a small group drawn from the Local Translation Coordinators.</translate><br />
* <translate><!--T:79--> A Joomla translation team badge is an image file that may be used to identify a Joomla Translation Team if certain conditions are met.</translate><br />
* <translate><!--T:80--> The Joomla Translation Teams Agreement defines the terms and conditions for acceptance as a Joomla Translation Team.</translate><br />
* <translate><!--T:81--> A Joomla Translation Team web site is a site that distributes the work of a specific Joomla Translation Team (either exclusively or along with providing other information or services).</translate><br />
* <translate><!--T:82--> The Joomla Translation Common Repository is the area on [http://joomlacode.org joomlacode.org] where Joomla Translation Teams deposit their work. It is managed by the Joomla Translation Coordination Team.</translate><br />
* <translate><!--T:83--> The Joomla Translation Team Forum is a limited-access forum located on [http://forum.joomla.org/ forum.joomla.org/] for use of Local Translation Coordinators.</translate><br />
<br />
<noinclude><br />
<translate><br />
<!--T:84--><br />
[[Category:Languages]]<br />
[[Category:Language Development]]</translate><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Joomla_Project_Translations&diff=771227Joomla Project Translations2020-12-15T05:52:41Z<p>Sandra97: Creation of the page</p>
<hr />
<div><noinclude><languages /></noinclude><br />
{{Top portal heading|color=white-bkgd|icon=language|icon-color=#5091cd|size=3x|text-color=#333|title=Joomla Project Translations}}<br />
<br />
==Joomla! Project Translation and Localization Policy==<br />
Add the content of this page: https://community.joomla.org/translations/joomla-project-translation-and-localization-policy.html<br />
<br />
==FAQ==<br />
Add the content of the accordion of this page: https://community.joomla.org/translations/joomla-3-translations.html#more-information-about-translations<br />
<br />
<noinclude><br />
[[Category:Languages]]<br />
[[Category:Language Development]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Social_Media_Working_Group&diff=766613Social Media Working Group2020-11-10T07:10:47Z<p>Sandra97: I left GSoC and so don't manage GSoC account anymore</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><br />
<!--T:1--><br />
This page serves to document the Joomla's social media presence, to explain its content policies and strategies to the Joomla! community, and to collect and share information about the management of Joomla's accounts on the various social media channels.</translate><br />
<br />
<translate><br />
==Official way to contact the Joomla! Social Media Team== <!--T:61--><br />
</translate><br />
<translate><br />
<!--T:54--><br />
To contact the Joomla! Social Media Team please use the “Contact the Social Media Team” on Glip. If you would like to share something from official project's social media channel, or if you have any questions, simply comment in that group and we will answer you as soon as possible. If accepted we may edit and add tags etc as needed then share it. Please feel free to suggest appropriate copy and tags for the post topic.</translate><br />
<br />
<translate><!--T:65--> We created an official repository on [https://github.com/joomla/socialmedia GitHub] to contact the Joomla! Social Media Team. If you would like to share something from official project's social media channel, or if you have any question, simply open an issue in the repo and we will answer you as soon as possible. We will revise the content and if we accept it, we will share it.</translate> <br />
<br />
<translate><br />
==Team== <!--T:66--><br />
</translate><br />
<translate><!--T:67--> With the adaptation of the use of HootSuite, all of our Social Media Team members (SMT) have access to post on all of our platforms. While each platform has a team member/s specifically monitoring them, we have been utilizing the time and work savings of HootSuite to be able to schedule regular news posts. This responsibility is shared with all of the team rather than each post taking time from everyone.</translate> <br />
<br />
<translate><!--T:68--> Remember social media happens every day and our hard working team do their best to keep on top of things while also taking care of their own work and lives. If you see something to be shared or not right, drop a friendly note or tag us. We’re dancing as fast as we can.</translate> <br />
<br />
<translate><br />
== Help Us Help YOU! == <!--T:69--><br />
</translate><br />
<translate><!--T:70--> #Help us see your Joomla content by tagging Joomla</translate><br />
<translate><!--T:71--> #If you have a special event happening contact us and be sure to take photos of your event and supply text of what you want covered (you know your message best). This will allow us to post about your event on our channels.</translate> <br />
<translate><!--T:72--> #Have a group of posts you want to schedule for your team? Contact Alison and learn how to make it happen. We can set you up with our template to do your graphics.</translate> <br />
<translate><!--T:73--> #Did I mention TAG JOOMLA! We want to share your Joomla events out on our channels to show the world all the great things going on within the Joomla community.</translate> <br />
<br />
<translate><br />
==The Joomla Social Media Team== <!--T:74--><br />
</translate><br />
<translate><!--T:75--> The Joomla Social Media Team consists of:</translate><br />
#[https://volunteers.joomla.org/joomlers/232-hans-van-der-meer Hans van der Meer] - <translate><!--T:76--> Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/266-alison-meeks Alison Meeks] - <translate><!--T:77--> Assistant Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/186-sandra-decoux Sandra Decoux]<br />
#[https://volunteers.joomla.org/joomlers/1143-giovanni-genovino Giovanni Genovino]<br />
<translate><!--T:78--> Graphics for the Joomla posts if not included within the attached article or supplied by the team requesting the posts, are done by Sandra Decoux and Alison Meeks with the image support of our partner 123RF. Graphics for social are done both in horizontal format as recommended by FB/Tw/LinkedIn but also square for Instagram. Shout out thanks to the video team of Sandra and Brian Teeman who have been creating various videos for various special events for use on our social platforms.</translate> <br />
<br />
<translate><br />
<br />
==Guiding Principles== <!--T:79--><br />
</translate><br />
<translate><!--T:80--> #We promote the features and benefits of Joomla! to a worldwide audience of enthusiasts.</translate><br />
<translate><!--T:81--> #The SMT schedule regular posts via HootSuite and as well use it for news posts. Some days there is more news than others. We try to balance it out rather than flooding feeds.</translate> <br />
<translate><!--T:82--> #We strictly avoid controversial links, particularly those which involve Joomla! governance or community politics.</translate><br />
<translate><!--T:83--> #Absolute priority is given to Joomla! Releases. Especially in the event of a security or new version release.</translate><br />
<translate><!--T:84--> #We normally avoid mention of products or services developed by companies in the Joomla! Community that are not direct partners or sponsors.</translate> <br />
<translate><!--T:85--> #We do highlight events and teams in the community. Some of those are Certification, Showcase, JED, Open Source Friday’s, and volunteers.</translate> <br />
<translate><!--T:86--> #We coordinate our work with Joomla's release schedule and the marketing and communications needs of the project as a whole.</translate><br />
<br />
<translate><br />
==Moderation Guidelines== <!--T:87--><br />
</translate> <br />
<translate><!--T:88--> #The Joomla! Volunteer Code of Conduct fully applies to the Joomla! Community gathered on Social Media. Users must conform their behaviour accordingly. At no time will any of our team tolerate harassment or attacks.</translate><br />
<translate><!--T:89--> #Links should posted with the best pictures and images pulled via metadata, if any. Click-through metrics are significantly higher for posts which contain an image.</translate><br />
<translate><!--T:90--> #We direct Social Media participants to ask support questions about Joomla! at the Joomla! Forum or other Joomla support groups located around the web. The official Joomla support is the forum and we always provide a link to it. We do not provide support via any social platforms.</translate> <br />
<br />
== [http://www.facebook.com/joomla Facebook] ==<br />
<translate><br />
===Main Admin=== <!--T:91--><br />
</translate><br />
<translate><!--T:92--> The official Joomla Facebook page is monitored by Alison Meeks with backup support from the rest of the team. Alison is also a member of several Joomla groups on Facebook and shares key posts to them such as updates/security patches etc. The Facebook JoomlaNoSpam Group is not an official Joomla property. Alison is an administrator in this group also. Rules for the NoSpam group are posted within the group. Hans also helps in the group but are not admins.</translate><br />
<br />
== [https://twitter.com/joomla Twitter] ==<br />
<translate><br />
===Main Admin=== <!--T:93--><br />
</translate><br />
<translate><!--T:94--> The official Joomla Twitter account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
<translate><br />
===List of Joomla Twitter channels=== <!--T:15--><br />
</translate><br />
<translate><br />
====The"official" accounts==== <!--T:16--><br />
</translate><br />
<br />
*Twitter: [https://twitter.com/joomla @joomla] - <translate><!--T:18--> This account is for all kinds Joomla news and Joomla.org content. It is the go to Joomla Twitter account.</translate><br />
'''Note:''' Note: As far as possible, the main account follows current board members, team leaders and their assistants, former OSM presidents, JUGs, JoomlaDays, some major active contributors, and some accounts related to the Web.<br />
<br />
<translate><!--T:63--><br />
'''Twitter Accounts run by the Production or Marketing Departments''': </translate><br />
*Developer Network: [https://twitter.com/JoomlaDeveloper @JoomlaDeveloper] <br />
*Joomla! Documentation: [https://twitter.com/joomladocs @joomladocs] <br />
*Joomla! Framework: [https://twitter.com/joomlaframework @joomlaframework]<br />
*Joomla! Bug Squad: [https://twitter.com/JoomlaBugSquad @JoomlaBugSquad]<br />
*Joomla! Translation Centre: [https://twitter.com/JoomlaL10nC @JoomlaL10nC] <br />
*Joomla! GSoC: [https://twitter.com/Joomla_GSoC @Joomla_GSoC]<br />
*Joomla! Volunteers: [https://twitter.com/joomlers @joomlers] <br />
<translate><!--T:19--><br />
There are lists of accounts related to Joomla too </translate><br />
*[https://twitter.com/joomla/lists http://twitter.com/joomla/lists]<br />
<br />
<translate><br />
<br />
====Twitter Accounts run by other parts of the Joomla Project==== <!--T:21--><br />
</translate><br />
<translate><br />
<!--T:22--><br />
Do you know more? We want to get in contact with you to join forces! Join the chat!<br />
</translate><br />
*Twitter: [https://twitter.com/OSMatters @OSMatters]<br />
*Twitter: [https://twitter.com/JoomlaConnect @JoomlaConnect]<br />
*Twitter: [https://twitter.com/JoomlaJUGS @JoomlaJUGS]<br />
*Twitter: [https://twitter.com/Joomla_JED @Joomla_JED]<br />
*Twitter: [https://twitter.com/joomlaevents @joomlaevents]<br />
*Twitter: [https://twitter.com/jworldcon @jworldcon]<br />
*Twitter: [https://twitter.com/JoomlaVel @JoomlaVel]<br />
<br />
==[http://www.linkedin.com/companies/joomla Linkedin]== <br />
<translate><!--T:97--> The official Joomla LinkedIn account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
==[https://www.youtube.com/user/joomla/ YouTube]== <br />
<translate><!--T:98--> The official YouTube account is updated by Sandra Decoux and Alison Meeks.</translate> <br />
<br />
==[https://www.instagram.com/joomlaofficial/ Instagram]== <br />
<translate><!--T:99--> The official Joomla Instagram account is run and monitored by Sandra Decoux with backup by the team. Due to Instagram’s unique operation Sandra manages it and does the scheduled posts per her experience with the platform.</translate><br />
<br />
==[http://www.pinterest.com/joomla/ Pinterest]== <br />
<translate><!--T:100--> The official Joomla Pinterest account is monitored by Giovanni Genovino with backup by the team.</translate><br />
<br />
==MeWe==<br />
<translate><!--T:101--> A Joomla MeWe group account has been created by Alison Meeks to secure the name. Pages there are paid as they don’t do an “ads based” income program but the groups are free. If there gets to a point where there is enough interest we can approach the board for financial approval.</translate> <br />
<br />
<translate><br />
==Want to Join the Social Media Team?== <!--T:102--><br />
</translate><br />
<translate><!--T:103--> If you have the desire and are willing to commit the time we would love to have you join us on the Social Media Team. You can view available positions here: https://volunteers.joomla.org/teams/social-media-team</translate> <br />
<br />
<noinclude><br />
[[Category:Working Groups{{#translation:}}]]<br />
[[Category:Marketing Communication Department{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Social_Media_Working_Group&diff=766612Social Media Working Group2020-11-10T07:09:57Z<p>Sandra97: </p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><br />
<!--T:1--><br />
This page serves to document the Joomla's social media presence, to explain its content policies and strategies to the Joomla! community, and to collect and share information about the management of Joomla's accounts on the various social media channels.</translate><br />
<br />
<translate><br />
==Official way to contact the Joomla! Social Media Team== <!--T:61--><br />
</translate><br />
<translate><br />
<!--T:54--><br />
To contact the Joomla! Social Media Team please use the “Contact the Social Media Team” on Glip. If you would like to share something from official project's social media channel, or if you have any questions, simply comment in that group and we will answer you as soon as possible. If accepted we may edit and add tags etc as needed then share it. Please feel free to suggest appropriate copy and tags for the post topic.</translate><br />
<br />
<translate><!--T:65--> We created an official repository on [https://github.com/joomla/socialmedia GitHub] to contact the Joomla! Social Media Team. If you would like to share something from official project's social media channel, or if you have any question, simply open an issue in the repo and we will answer you as soon as possible. We will revise the content and if we accept it, we will share it.</translate> <br />
<br />
<translate><br />
==Team== <!--T:66--><br />
</translate><br />
<translate><!--T:67--> With the adaptation of the use of HootSuite, all of our Social Media Team members (SMT) have access to post on all of our platforms. While each platform has a team member/s specifically monitoring them, we have been utilizing the time and work savings of HootSuite to be able to schedule regular news posts. This responsibility is shared with all of the team rather than each post taking time from everyone.</translate> <br />
<br />
<translate><!--T:68--> Remember social media happens every day and our hard working team do their best to keep on top of things while also taking care of their own work and lives. If you see something to be shared or not right, drop a friendly note or tag us. We’re dancing as fast as we can.</translate> <br />
<br />
<translate><br />
== Help Us Help YOU! == <!--T:69--><br />
</translate><br />
<translate><!--T:70--> #Help us see your Joomla content by tagging Joomla</translate><br />
<translate><!--T:71--> #If you have a special event happening contact us and be sure to take photos of your event and supply text of what you want covered (you know your message best). This will allow us to post about your event on our channels.</translate> <br />
<translate><!--T:72--> #Have a group of posts you want to schedule for your team? Contact Alison and learn how to make it happen. We can set you up with our template to do your graphics.</translate> <br />
<translate><!--T:73--> #Did I mention TAG JOOMLA! We want to share your Joomla events out on our channels to show the world all the great things going on within the Joomla community.</translate> <br />
<br />
<translate><br />
==The Joomla Social Media Team== <!--T:74--><br />
</translate><br />
<translate><!--T:75--> The Joomla Social Media Team consists of:</translate><br />
#[https://volunteers.joomla.org/joomlers/232-hans-van-der-meer Hans van der Meer] - <translate><!--T:76--> Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/266-alison-meeks Alison Meeks] - <translate><!--T:77--> Assistant Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/186-sandra-decoux Sandra Decoux]<br />
#[https://volunteers.joomla.org/joomlers/1143-giovanni-genovino Giovanni Genovino]<br />
<translate><!--T:78--> Graphics for the Joomla posts if not included within the attached article or supplied by the team requesting the posts, are done by Sandra Decoux and Alison Meeks with the image support of our partner 123RF. Graphics for social are done both in horizontal format as recommended by FB/Tw/LinkedIn but also square for Instagram. Shout out thanks to the video team of Sandra and Brian Teeman who have been creating various videos for various special events for use on our social platforms.</translate> <br />
<br />
<translate><br />
<br />
==Guiding Principles== <!--T:79--><br />
</translate><br />
<translate><!--T:80--> #We promote the features and benefits of Joomla! to a worldwide audience of enthusiasts.</translate><br />
<translate><!--T:81--> #The SMT schedule regular posts via HootSuite and as well use it for news posts. Some days there is more news than others. We try to balance it out rather than flooding feeds.</translate> <br />
<translate><!--T:82--> #We strictly avoid controversial links, particularly those which involve Joomla! governance or community politics.</translate><br />
<translate><!--T:83--> #Absolute priority is given to Joomla! Releases. Especially in the event of a security or new version release.</translate><br />
<translate><!--T:84--> #We normally avoid mention of products or services developed by companies in the Joomla! Community that are not direct partners or sponsors.</translate> <br />
<translate><!--T:85--> #We do highlight events and teams in the community. Some of those are Certification, Showcase, JED, Open Source Friday’s, and volunteers.</translate> <br />
<translate><!--T:86--> #We coordinate our work with Joomla's release schedule and the marketing and communications needs of the project as a whole.</translate><br />
<br />
<translate><br />
==Moderation Guidelines== <!--T:87--><br />
</translate> <br />
<translate><!--T:88--> #The Joomla! Volunteer Code of Conduct fully applies to the Joomla! Community gathered on Social Media. Users must conform their behaviour accordingly. At no time will any of our team tolerate harassment or attacks.</translate><br />
<translate><!--T:89--> #Links should posted with the best pictures and images pulled via metadata, if any. Click-through metrics are significantly higher for posts which contain an image.</translate><br />
<translate><!--T:90--> #We direct Social Media participants to ask support questions about Joomla! at the Joomla! Forum or other Joomla support groups located around the web. The official Joomla support is the forum and we always provide a link to it. We do not provide support via any social platforms.</translate> <br />
<br />
== [http://www.facebook.com/joomla Facebook] ==<br />
<translate><br />
===Main Admin=== <!--T:91--><br />
</translate><br />
<translate><!--T:92--> The official Joomla Facebook page is monitored by Alison Meeks with backup support from the rest of the team. Alison is also a member of several Joomla groups on Facebook and shares key posts to them such as updates/security patches etc. The Facebook JoomlaNoSpam Group is not an official Joomla property. Alison is an administrator in this group also. Rules for the NoSpam group are posted within the group. Hans also helps in the group but are not admins.</translate><br />
<br />
== [https://twitter.com/joomla Twitter] ==<br />
<translate><br />
===Main Admin=== <!--T:93--><br />
</translate><br />
<translate><!--T:94--> The official Joomla Twitter account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
<translate><br />
===List of Joomla Twitter channels=== <!--T:15--><br />
</translate><br />
<translate><br />
====The"official" accounts==== <!--T:16--><br />
</translate><br />
<br />
*Twitter: [https://twitter.com/joomla @joomla] - <translate><!--T:18--> This account is for all kinds Joomla news and Joomla.org content. It is the go to Joomla Twitter account.</translate><br />
'''Note:''' Note: As far as possible, the main account follows current board members, team leaders and their assistants, former OSM presidents, JUGs, JoomlaDays, some major active contributors, and some accounts related to the Web.<br />
<br />
<translate><!--T:63--><br />
'''Twitter Accounts run by the Production or Marketing Departments''': </translate><br />
*Developer Network: [https://twitter.com/JoomlaDeveloper @JoomlaDeveloper] <br />
*Joomla! Documentation: [https://twitter.com/joomladocs @joomladocs] <br />
*Joomla! Framework: [https://twitter.com/joomlaframework @joomlaframework]<br />
*Joomla! Bug Squad: [https://twitter.com/JoomlaBugSquad @JoomlaBugSquad]<br />
*Joomla! Translation Centre: [https://twitter.com/JoomlaL10nC @JoomlaL10nC] <br />
*Joomla! GSoC: [https://twitter.com/Joomla_GSoC @Joomla_GSoC] <translate><!--T:95--> (managed by Sandra Decoux)</translate><br />
*Joomla! Volunteers: [https://twitter.com/joomlers @joomlers] <br />
<translate><!--T:19--><br />
There are lists of accounts related to Joomla too </translate><br />
*[https://twitter.com/joomla/lists http://twitter.com/joomla/lists]<br />
<br />
<translate><br />
<br />
====Twitter Accounts run by other parts of the Joomla Project==== <!--T:21--><br />
</translate><br />
<translate><br />
<!--T:22--><br />
Do you know more? We want to get in contact with you to join forces! Join the chat!<br />
</translate><br />
*Twitter: [https://twitter.com/OSMatters @OSMatters]<br />
*Twitter: [https://twitter.com/JoomlaConnect @JoomlaConnect]<br />
*Twitter: [https://twitter.com/JoomlaJUGS @JoomlaJUGS]<br />
*Twitter: [https://twitter.com/Joomla_JED @Joomla_JED]<br />
*Twitter: [https://twitter.com/joomlaevents @joomlaevents]<br />
*Twitter: [https://twitter.com/jworldcon @jworldcon]<br />
*Twitter: [https://twitter.com/JoomlaVel @JoomlaVel]<br />
<br />
==[http://www.linkedin.com/companies/joomla Linkedin]== <br />
<translate><!--T:97--> The official Joomla LinkedIn account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
==[https://www.youtube.com/user/joomla/ YouTube]== <br />
<translate><!--T:98--> The official YouTube account is updated by Sandra Decoux and Alison Meeks.</translate> <br />
<br />
==[https://www.instagram.com/joomlaofficial/ Instagram]== <br />
<translate><!--T:99--> The official Joomla Instagram account is run and monitored by Sandra Decoux with backup by the team. Due to Instagram’s unique operation Sandra manages it and does the scheduled posts per her experience with the platform.</translate><br />
<br />
==[http://www.pinterest.com/joomla/ Pinterest]== <br />
<translate><!--T:100--> The official Joomla Pinterest account is monitored by Giovanni Genovino with backup by the team.</translate><br />
<br />
==MeWe==<br />
<translate><!--T:101--> A Joomla MeWe group account has been created by Alison Meeks to secure the name. Pages there are paid as they don’t do an “ads based” income program but the groups are free. If there gets to a point where there is enough interest we can approach the board for financial approval.</translate> <br />
<br />
<translate><br />
==Want to Join the Social Media Team?== <!--T:102--><br />
</translate><br />
<translate><!--T:103--> If you have the desire and are willing to commit the time we would love to have you join us on the Social Media Team. You can view available positions here: https://volunteers.joomla.org/teams/social-media-team</translate> <br />
<br />
<noinclude><br />
[[Category:Working Groups{{#translation:}}]]<br />
[[Category:Marketing Communication Department{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Social_Media_Working_Group&diff=766611Social Media Working Group2020-11-10T07:09:37Z<p>Sandra97: Change of lead</p>
<hr />
<div><noinclude><languages /></noinclude><br />
<translate><br />
<!--T:1--><br />
This page serves to document the Joomla's social media presence, to explain its content policies and strategies to the Joomla! community, and to collect and share information about the management of Joomla's accounts on the various social media channels.</translate><br />
<br />
<translate><br />
==Official way to contact the Joomla! Social Media Team== <!--T:61--><br />
</translate><br />
<translate><br />
<!--T:54--><br />
To contact the Joomla! Social Media Team please use the “Contact the Social Media Team” on Glip. If you would like to share something from official project's social media channel, or if you have any questions, simply comment in that group and we will answer you as soon as possible. If accepted we may edit and add tags etc as needed then share it. Please feel free to suggest appropriate copy and tags for the post topic.</translate><br />
<br />
<translate><!--T:65--> We created an official repository on [https://github.com/joomla/socialmedia GitHub] to contact the Joomla! Social Media Team. If you would like to share something from official project's social media channel, or if you have any question, simply open an issue in the repo and we will answer you as soon as possible. We will revise the content and if we accept it, we will share it.</translate> <br />
<br />
<translate><br />
==Team== <!--T:66--><br />
</translate><br />
<translate><!--T:67--> With the adaptation of the use of HootSuite, all of our Social Media Team members (SMT) have access to post on all of our platforms. While each platform has a team member/s specifically monitoring them, we have been utilizing the time and work savings of HootSuite to be able to schedule regular news posts. This responsibility is shared with all of the team rather than each post taking time from everyone.</translate> <br />
<br />
<translate><!--T:68--> Remember social media happens every day and our hard working team do their best to keep on top of things while also taking care of their own work and lives. If you see something to be shared or not right, drop a friendly note or tag us. We’re dancing as fast as we can.</translate> <br />
<br />
<translate><br />
== Help Us Help YOU! == <!--T:69--><br />
</translate><br />
<translate><!--T:70--> #Help us see your Joomla content by tagging Joomla</translate><br />
<translate><!--T:71--> #If you have a special event happening contact us and be sure to take photos of your event and supply text of what you want covered (you know your message best). This will allow us to post about your event on our channels.</translate> <br />
<translate><!--T:72--> #Have a group of posts you want to schedule for your team? Contact Alison and learn how to make it happen. We can set you up with our template to do your graphics.</translate> <br />
<translate><!--T:73--> #Did I mention TAG JOOMLA! We want to share your Joomla events out on our channels to show the world all the great things going on within the Joomla community.</translate> <br />
<br />
<translate><br />
==The Joomla Social Media Team== <!--T:74--><br />
</translate><br />
<translate><!--T:75--> The Joomla Social Media Team consists of:</translate><br />
#[https://volunteers.joomla.org/joomlers/232-hans-van-der-meer Hans van der Meer] - <translate><!--T:76--> Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/266-alison-meeks Alison Meeks - <translate><!--T:77--> Assistant Team Lead</translate><br />
#[https://volunteers.joomla.org/joomlers/186-sandra-decoux Sandra Decoux]<br />
#[https://volunteers.joomla.org/joomlers/1143-giovanni-genovino Giovanni Genovino]<br />
<translate><!--T:78--> Graphics for the Joomla posts if not included within the attached article or supplied by the team requesting the posts, are done by Sandra Decoux and Alison Meeks with the image support of our partner 123RF. Graphics for social are done both in horizontal format as recommended by FB/Tw/LinkedIn but also square for Instagram. Shout out thanks to the video team of Sandra and Brian Teeman who have been creating various videos for various special events for use on our social platforms.</translate> <br />
<br />
<translate><br />
<br />
==Guiding Principles== <!--T:79--><br />
</translate><br />
<translate><!--T:80--> #We promote the features and benefits of Joomla! to a worldwide audience of enthusiasts.</translate><br />
<translate><!--T:81--> #The SMT schedule regular posts via HootSuite and as well use it for news posts. Some days there is more news than others. We try to balance it out rather than flooding feeds.</translate> <br />
<translate><!--T:82--> #We strictly avoid controversial links, particularly those which involve Joomla! governance or community politics.</translate><br />
<translate><!--T:83--> #Absolute priority is given to Joomla! Releases. Especially in the event of a security or new version release.</translate><br />
<translate><!--T:84--> #We normally avoid mention of products or services developed by companies in the Joomla! Community that are not direct partners or sponsors.</translate> <br />
<translate><!--T:85--> #We do highlight events and teams in the community. Some of those are Certification, Showcase, JED, Open Source Friday’s, and volunteers.</translate> <br />
<translate><!--T:86--> #We coordinate our work with Joomla's release schedule and the marketing and communications needs of the project as a whole.</translate><br />
<br />
<translate><br />
==Moderation Guidelines== <!--T:87--><br />
</translate> <br />
<translate><!--T:88--> #The Joomla! Volunteer Code of Conduct fully applies to the Joomla! Community gathered on Social Media. Users must conform their behaviour accordingly. At no time will any of our team tolerate harassment or attacks.</translate><br />
<translate><!--T:89--> #Links should posted with the best pictures and images pulled via metadata, if any. Click-through metrics are significantly higher for posts which contain an image.</translate><br />
<translate><!--T:90--> #We direct Social Media participants to ask support questions about Joomla! at the Joomla! Forum or other Joomla support groups located around the web. The official Joomla support is the forum and we always provide a link to it. We do not provide support via any social platforms.</translate> <br />
<br />
== [http://www.facebook.com/joomla Facebook] ==<br />
<translate><br />
===Main Admin=== <!--T:91--><br />
</translate><br />
<translate><!--T:92--> The official Joomla Facebook page is monitored by Alison Meeks with backup support from the rest of the team. Alison is also a member of several Joomla groups on Facebook and shares key posts to them such as updates/security patches etc. The Facebook JoomlaNoSpam Group is not an official Joomla property. Alison is an administrator in this group also. Rules for the NoSpam group are posted within the group. Hans also helps in the group but are not admins.</translate><br />
<br />
== [https://twitter.com/joomla Twitter] ==<br />
<translate><br />
===Main Admin=== <!--T:93--><br />
</translate><br />
<translate><!--T:94--> The official Joomla Twitter account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
<translate><br />
===List of Joomla Twitter channels=== <!--T:15--><br />
</translate><br />
<translate><br />
====The"official" accounts==== <!--T:16--><br />
</translate><br />
<br />
*Twitter: [https://twitter.com/joomla @joomla] - <translate><!--T:18--> This account is for all kinds Joomla news and Joomla.org content. It is the go to Joomla Twitter account.</translate><br />
'''Note:''' Note: As far as possible, the main account follows current board members, team leaders and their assistants, former OSM presidents, JUGs, JoomlaDays, some major active contributors, and some accounts related to the Web.<br />
<br />
<translate><!--T:63--><br />
'''Twitter Accounts run by the Production or Marketing Departments''': </translate><br />
*Developer Network: [https://twitter.com/JoomlaDeveloper @JoomlaDeveloper] <br />
*Joomla! Documentation: [https://twitter.com/joomladocs @joomladocs] <br />
*Joomla! Framework: [https://twitter.com/joomlaframework @joomlaframework]<br />
*Joomla! Bug Squad: [https://twitter.com/JoomlaBugSquad @JoomlaBugSquad]<br />
*Joomla! Translation Centre: [https://twitter.com/JoomlaL10nC @JoomlaL10nC] <br />
*Joomla! GSoC: [https://twitter.com/Joomla_GSoC @Joomla_GSoC] <translate><!--T:95--> (managed by Sandra Decoux)</translate><br />
*Joomla! Volunteers: [https://twitter.com/joomlers @joomlers] <br />
<translate><!--T:19--><br />
There are lists of accounts related to Joomla too </translate><br />
*[https://twitter.com/joomla/lists http://twitter.com/joomla/lists]<br />
<br />
<translate><br />
<br />
====Twitter Accounts run by other parts of the Joomla Project==== <!--T:21--><br />
</translate><br />
<translate><br />
<!--T:22--><br />
Do you know more? We want to get in contact with you to join forces! Join the chat!<br />
</translate><br />
*Twitter: [https://twitter.com/OSMatters @OSMatters]<br />
*Twitter: [https://twitter.com/JoomlaConnect @JoomlaConnect]<br />
*Twitter: [https://twitter.com/JoomlaJUGS @JoomlaJUGS]<br />
*Twitter: [https://twitter.com/Joomla_JED @Joomla_JED]<br />
*Twitter: [https://twitter.com/joomlaevents @joomlaevents]<br />
*Twitter: [https://twitter.com/jworldcon @jworldcon]<br />
*Twitter: [https://twitter.com/JoomlaVel @JoomlaVel]<br />
<br />
==[http://www.linkedin.com/companies/joomla Linkedin]== <br />
<translate><!--T:97--> The official Joomla LinkedIn account is monitored by Hans van der Meer with backup support from the rest of the team.</translate><br />
<br />
==[https://www.youtube.com/user/joomla/ YouTube]== <br />
<translate><!--T:98--> The official YouTube account is updated by Sandra Decoux and Alison Meeks.</translate> <br />
<br />
==[https://www.instagram.com/joomlaofficial/ Instagram]== <br />
<translate><!--T:99--> The official Joomla Instagram account is run and monitored by Sandra Decoux with backup by the team. Due to Instagram’s unique operation Sandra manages it and does the scheduled posts per her experience with the platform.</translate><br />
<br />
==[http://www.pinterest.com/joomla/ Pinterest]== <br />
<translate><!--T:100--> The official Joomla Pinterest account is monitored by Giovanni Genovino with backup by the team.</translate><br />
<br />
==MeWe==<br />
<translate><!--T:101--> A Joomla MeWe group account has been created by Alison Meeks to secure the name. Pages there are paid as they don’t do an “ads based” income program but the groups are free. If there gets to a point where there is enough interest we can approach the board for financial approval.</translate> <br />
<br />
<translate><br />
==Want to Join the Social Media Team?== <!--T:102--><br />
</translate><br />
<translate><!--T:103--> If you have the desire and are willing to commit the time we would love to have you join us on the Social Media Team. You can view available positions here: https://volunteers.joomla.org/teams/social-media-team</translate> <br />
<br />
<noinclude><br />
[[Category:Working Groups{{#translation:}}]]<br />
[[Category:Marketing Communication Department{{#translation:}}]]<br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Pizza,_Bugs_and_Fun_2020/fr&diff=757277Pizza, Bugs and Fun 2020/fr2020-10-17T09:59:07Z<p>Sandra97: Created page with "Si vous ne trouvez pas ce que vous cherchez, voici quelques questions/réponses :<br><br>"</p>
<hr />
<div>[[Image:pbf-2020en.png|1100px]]<br />
<noinclude><languages /></noinclude><br />
{{RightTOC}}<br />
<br />
<br />
Cette année, l'événement Joomla ! Pizza Bug and Fun (PBF) a lieu le '''17 octobre 2020''' et verra des participants du monde entier se joindre à l'événement.<br />
Ce wiki est utilisé comme ressource centrale pour coordonner les efforts et présenter les résultats de cet événement. <br />
Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !<br />
<br />
== Bienvenue ==<br />
{{#ev:youtube|UXFUA70kMqg}}<br />
Video subtitles: [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=en EN] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=DE DE] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=fr FR] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=es ES] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=it IT]<br />
<br />
== Objectifs ==<br />
<br />
Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins jeune, le Pizza Bugs and Fun est fait pour vous. L'événement est destiné à ceux qui travaillent déjà avec Joomla ou qui veulent faire connaissance avec Joomla. Seul votre intérêt pour Joomla est important. Vous êtes toutes et tous les bienvenu(e)s.<br />
Le 17 octobre 2020, nous aimerions inviter tous les utilisateurs enthousiastes de Joomla, quelles que soient vos connaissances préalables, à améliorer encore plus Joomla. Tout soutien est grandement apprécié ! La participation est gratuite, et bien que les boissons non alcoolisées et la pizza soient normalement incluses grâce aux sponsors de l'événement, la COVID-19 nous a contraint à un événement virtuel. <br />
Les tâches du jour sont regroupées en plusieurs catégories, et selon le niveau de compétences. Ainsi, chacun, quel que soit son niveau, peut contribuer à la réalisation de ces tâches :<br />
* '''Joomla 4''': Joomla 4.0 is coming soon, but it still has a lot of bugs and feature requests that are untested, or need additional code, which means they cannot be added into the Joomla core. [[JDOC:Joomla_4_Tutorials_Project|Joomla 4 Documentation]] is also needing lots of work.<br />
* '''Patch Testing''': As a main rule, new functions for Joomla have to be tested before they can be merged into an official release. Usually, it takes only a few minutes and you can help make Joomla better.<br />
* '''[[Pizza,_Bugs_and_Fun_2020#Joomla_Documentation|Documentation]]''': There are lots of Documents that [[JDOC:Maintenance_Tasks|need writing or maintenance]]. Tutorials and Help Screens are needed for Joomla! 4.<br />
* '''[[JDOC:Page Translation Quickstart Guide|Documentation Translation]]''': At the PBF Event we hope to translate lots of English documents into other languages to give Joomla! users as much information as possible in their language.<br />
* '''Language Packs''': Sign up to [[Crowdin|Crowdin]], which Joomla's now using for localisation and translation. From there, you can get started on translating Joomla into your local language. Joomla 4 language packs are ready on Crowdin for translation, and need your help to speed up completion in anticipation of Joomla 4's release.<br />
<br />
== FAQ ==<br />
Si vous ne trouvez pas ce que vous cherchez, voici quelques questions/réponses :<br><br><br />
'''Q:''' Where can I register if I want to join?<br><br />
'''A:''' Search for a [https://community.joomla.org/user-groups.html| Joomla User Group] and contact them to find out if they're doing something. You can also look at [[S:MyLanguage/Portal:Joomla_User_Groups|starting your own Joomla User Group (JUG)]] near you or write an email to the team [mailto:team@pizza-bug-and-fun.com].<br />
<br />
'''Q:''' I can't go to a location - can I join online?<br><br />
'''A:''' Yes! You only need a computer and an internet connection, but unfortunately you have to order or [https://pizza-bugs-fun.com/en/the-pizza make your own pizza].<br />
<br />
'''Q:''' I missed it! Can I still help?<br><br />
'''A:''' You sure can! Since April this year, every Saturday with the world heavily locked down, we've been running [[S:MyLanguage/Bugs & Fun @Home|Bugs & Fun @Home (BF@H)]], where there's been volunteers dropping in when they can to work through the goals outlined in the list above. That's going to continue into the future, so check the BF@H page for details.<br />
<br />
'''Q:''' How can I get more involved?<br><br />
'''A:''' Joomla's after all sorts of skilled volunteers for a wide range of positions. Take a look at the [https://volunteers.joomla.org/ Volunteers Portal], especially the [https://volunteers.joomla.org/help-wanted Help Wanted page] to see how you can help, or just start a conversation during PBF or one weekend during BF@H.<br />
<br />
<br />
== Organization, logistics and communications ==<br />
PBF events are organized by local [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]]. 2020's a bit different as we're doing it virtually, but for future years, we'd love it if more groups came on board to participate.<br />
<br />
If you would like to participate but don't have a user group nearby, or you are Joomla User Group and want to join, this year it's easier than ever to do so online!<br />
There are a few requirements:<br />
<br />
* You need a room with WiFi access.<br />
* You need some Joomlers equipped with a laptop and motivation.<br />
* Do not hesitate to send an email to [mailto:team@pizza-bug-and-fun.com| team@pizza-bug-and-fun.com] or contact the team on [[RingCentral (Glip)|Glip]].<br />
<br />
Of course, you can also join from home, but where is the fun without the community and the pizza?<br />
<br />
==Réseaux Sociaux==<br />
Joomla! is all about community, and so if you're participating in PBF, tell us, and the world, about it.<br />
* For sharing information in the social media please use these hashtags: #pbf20 #joomla<br />
* Also include tags for things you're working on like: #joomla4 #joomladocs #joomlatranslation #a11y #l10n<br />
<br />
=== Illustrations de réseaux sociaux ===<br />
<br />
Right click on the images and choose "Save Image as" to download to your computer to uses these graphics on Social Media<br />
<br />
<div><ul><br />
<li style="display: inline-block;">[[File:Pbf_1200x628.png|200px|thumb|none|Facebook 1200x628]]</li><br />
<li style="display: inline-block;">[[File:Pbf_2020_instagram_1024x1024.png|200px|thumb|none|Instagram 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_1024x1024overlay.png|200px|thumb|none|Instagram Transparent Overlay 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_overlay.png|200px|thumb|none|PBF Bug Transparent Overlay]]</li><br />
</ul></div><br />
<br />
You can use the overlay images, which are transparent PNG files, in other programs to add the PBF Bug to your photos to promote the event.<br />
<br />
== Locations ==<br />
Add your local PBF involvement to the list below (You'll need a JDOCs account, but you're about to contribute to JDOCS during PBF, so that's something you'll have soon if not already!)<br />
<br />
This year everything is different: COVID-19 does not allow us to organize an offline event, or only under very difficult conditions. That's why we decided to create circumstances so that everybody can participate online.<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== Océanie et Australie ===<br />
* Australia - West End, Brisbane - in person event day <br />
* Australia - Other regions - online only<br />
For more information on Australia's 2020 PBF participation visit [https://joomla.org.au/pbf joomla.org.au/pbf]<br />
== Registration ==<br />
=== For Write Access to this Wiki ===<br />
To get write access to this wiki you will need to [[Special:Userlogin|register or login here first]]. (See also the [[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute]] page for more details on getting started on contributing to Joomla documentation.<br />
<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== At a Physical Location ===<br />
If you wish to be present at one of the physical locations listed above then you must register in advance because space is potentially limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.<br />
<br />
=== Taking Bugs, Tasks and Pizza ===<br />
This year PBF aren't supplying the pizza, so order your own from your favourite pizza place or here's a video we've put together [https://pizza-bugs-fun.com/en/the-pizza on how to make your own pizza].<br />
<br />
<br />
==Exigences et conditions de participation==<br />
Pizza, Bugs & Fun is an event that aims to help meet [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Joomla's Mission, Vision & Values]. Contributing to the Joomla! community assumes acceptance of the principles outlined in the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Joomla! Code of Conduct].<br />
<br />
* All code must be made available under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html General Public Licence version 2].<br />
* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]<br />
* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]<br />
* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.<br />
<br />
== Communication Tools ==<br />
That's how teamwork works these days :-)<br />
You can check your [https://kps.fyi/utc local time compared to UTC here].<br />
==== Glip - PBF20 channel ====<br />
In the Glip/RingCentral Chatroom, you can ask questions and exchange ideas. [https://glip.com Glip] and [https://github.com GitHub] For example if you need further clarification for a patch test.<br />
==== Video Chat ====<br />
You can join the [https://pizza-bugs-fun.com/videochat/ PBF20 Video Chat] during the weekend from 2200UTC Friday night (when Australia kicks off PBF20) through to ~0800UTC Sunday Morning (when USA West Coast finishes Saturday night). <br />
<br />
The PBF20 Video Chat uses BigBlueButton, and you can [https://bigbluebutton.org/html5/ watch their tutorials] to see how to use the features of the BigBlueButton platform. <br />
<br />
==== Google Meet - Fallback ====<br />
Just in case you're having issues with getting onto Glip, or the PBF Video Chat, we'll also have the [https://meet.google.com/bke-ufkq-eif Bugs & Fun @Home Google Meet] open from 2200UTC as a fallback.<br />
== Preparations and installations ==<br />
===Outils à utiliser===<br />
There's some other tools to use to get involved as a Bug Tester for Joomla, as well as if you're looking to get involved in the Joomla project overall. The links below take you to pages on JDOCs that will help you get started.<br />
* [[RingCentral_(Glip)|RingCentral (Glip)]] is the communication tool used by the Joomla Project.<br />
** Once you've been added on RingCentral, search for the PBF20 channel to join the conversation.<br />
* [[GitHub|GitHub]] is the tool Joomla uses for managing the code for the CMS, and a login to GitHub also allows you to use the [https://issues.joomla.org|Joomla Issues Tracker].<br />
* [[JDOC:How_to_Contribute_to_Joomla!_Documentation|Joomla Documentation Wiki]] is where all of the Joomla Help documents are created and managed, and to help with documentation, create an account there and you can then help with updating Joomla's help.<br />
* [[Crowdin|Crowdin]] is the translation management tool all of Joomla's official language packs are managed in. Creating an account there will allow you to help with contributing to translations in your own language.<br />
<br />
=== Watch the Training Videos === <br />
[https://www.youtube.com/watch?v=V8hSEDsjsJc Watch this training video], which takes you through a few of the above tools, and how to perform some of the tasks you'll be doing for PBF20. <br />
=== Setting up a Joomla! Installation ===<br />
Required if you want to test patches. There are two ways to get a Joomla! installation at PBF:<br />
* [http://pizza-bugs-fun.com/servers/ Access one of the Pre-installed Joomla 4 installations here.]<br />
** Servers are available in the UK, USA, Germany and Spain.<br />
** To get an instance to test on, click on the domain for a server, log in and change your password to take over the instance.<br />
** After you've changed the password on an instance, set up the pre-installed patch tester to start testing.<br />
** Drop a message in the PBF20 Glip, or in one of the video chats to say which instance you grabbed so others can see what's available next.<br />
** ''Can't access the instance you're trying? Once the password is changed, that instance is taken, so keep trying until you can get into one. Check the PBF20 Glip channel to see what the next available instance may be.''<br />
* Set up a local installation on your device. There's a variety of options you can look at installing. [https://magazine.joomla.org/All-issues/june-2020/github-installing-git Read this Joomla Magazine Article] for a tutorial on installing an environment using XAMPP, as well as configuring the Joomla Patch Tester and Joomla 4.<br />
* Check out the [[Bugs & Fun @Home]] page for a number of other links to resources relating to patch testing and setting up your test environment.<br />
{{tip|title=300 PBF Joomla instances thanks to [https://www.ionos.com/ IONOS]|text=Thanks to PBF sponsor IONOS, there's [http://pizza-bugs-fun.com/servers/ 300 Joomla instances] ready to go for the event, so skip setting up your own for the day.}}<br />
=== Tasks Lists ===<br />
To help you focus in on what needs doing, here's where to find the<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1454163514 '''Explorer'''] - Suitable for beginners. Covers documentation and translation tasks.<br>''The [[JDOC:Maintenance Tasks|Joomla Documentation Maintenance Tasks List]] has plenty of other items for you to consider if you're not confident getting started with the Explorer list.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1748937094 '''Adventurer'''] - Covers patch testing of pull requests for Joomla.<br>''There's always new PR's coming in during the event as code is created to address issues. Check the list of [https://github.com/joomla/joomla-cms/pulls pull requests] later in the day to see if there's new items to test.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=0 '''Conquerer'''] - Advanced tasks - these are issues that require code, consideration and conversation to resolve.<br>''Looking for a problem to resolve? In addition to the Conqueror list, the GitHub [https://github.com/joomla/joomla-cms/issues issues list] has many other issues needing volunteers to create solutions for... is that you?'' <br />
==Documentation Joomla==<br />
=== JDoc Contributions ===<br />
If you don't want to test patches but still want to give back a lot of support to the community, help writing the JDocs for Joomla! 4.<br />
<br />
You will find all information you need to get started here. Please read: <br />
<br />
* Create a JDoc account - read [[JDOC:How_to_Contribute_to_Joomla!_Documentation| How to Contribute to Joomla! Documentation]]<br />
* Read the [[S:MyLanguage/JDOC:Terms_of_Service| Wiki Policy]]<br />
* JDoc Cheatsheet [[S:MyLanguage/JHelp:Cheatsheet| JDoc Wiki formatting codes]]<br />
<br />
=== JDocs Translations ===<br />
If you don't want to test patches but still want to give back and support the community, help to translate the JDocs.<br />
<br />
Here you will find all the information you will need to get started. Please read '''[[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute to Joomla! Documentation]]'''. <br />
<br />
==Merci aux contributeurs du PBF20==<br />
{{#ev:youtube|Kxst-xiF5CQ}}<br />
<br />
Si vous avez contribué pendant le PBF20, assurez-vous de bien enregistrer vos contributions :<br />
[[S:MyLanguage/Pizza Bugs and Fun 2020/Contributors List|Contributors List]]<br />
<br />
==Related Information==<br />
* Organizers website [https://www.pizza-bugs-fun.com pizza-bugs-fun.com]<br />
* Joomla (and by associate PBF20) is registered as a [https://hacktoberfest.digitalocean.com/ Hacktoberfest Event]. Create 4 PR's in October and you can earn a tee or a tree. See website for information.<br />
<br />
<noinclude><br />
<noinclude><br />
[[Category:Bug Squad{{#translation:}}]]<br />
[[Category:Development{{#translation:}}]]<br />
[[Category:Events{{#translation:}}]]<br />
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Pizza,_Bugs_and_Fun_2020/46/fr&diff=757276Translations:Pizza, Bugs and Fun 2020/46/fr2020-10-17T09:59:06Z<p>Sandra97: Created page with "Si vous ne trouvez pas ce que vous cherchez, voici quelques questions/réponses :<br><br>"</p>
<hr />
<div>Si vous ne trouvez pas ce que vous cherchez, voici quelques questions/réponses :<br><br></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Pizza,_Bugs_and_Fun_2020/fr&diff=757275Pizza, Bugs and Fun 2020/fr2020-10-17T09:58:32Z<p>Sandra97: Created page with "Les tâches du jour sont regroupées en plusieurs catégories, et selon le niveau de compétences. Ainsi, chacun, quel que soit son niveau, peut contribuer à la réalisation..."</p>
<hr />
<div>[[Image:pbf-2020en.png|1100px]]<br />
<noinclude><languages /></noinclude><br />
{{RightTOC}}<br />
<br />
<br />
Cette année, l'événement Joomla ! Pizza Bug and Fun (PBF) a lieu le '''17 octobre 2020''' et verra des participants du monde entier se joindre à l'événement.<br />
Ce wiki est utilisé comme ressource centrale pour coordonner les efforts et présenter les résultats de cet événement. <br />
Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !<br />
<br />
== Bienvenue ==<br />
{{#ev:youtube|UXFUA70kMqg}}<br />
Video subtitles: [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=en EN] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=DE DE] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=fr FR] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=es ES] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=it IT]<br />
<br />
== Objectifs ==<br />
<br />
Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins jeune, le Pizza Bugs and Fun est fait pour vous. L'événement est destiné à ceux qui travaillent déjà avec Joomla ou qui veulent faire connaissance avec Joomla. Seul votre intérêt pour Joomla est important. Vous êtes toutes et tous les bienvenu(e)s.<br />
Le 17 octobre 2020, nous aimerions inviter tous les utilisateurs enthousiastes de Joomla, quelles que soient vos connaissances préalables, à améliorer encore plus Joomla. Tout soutien est grandement apprécié ! La participation est gratuite, et bien que les boissons non alcoolisées et la pizza soient normalement incluses grâce aux sponsors de l'événement, la COVID-19 nous a contraint à un événement virtuel. <br />
Les tâches du jour sont regroupées en plusieurs catégories, et selon le niveau de compétences. Ainsi, chacun, quel que soit son niveau, peut contribuer à la réalisation de ces tâches :<br />
* '''Joomla 4''': Joomla 4.0 is coming soon, but it still has a lot of bugs and feature requests that are untested, or need additional code, which means they cannot be added into the Joomla core. [[JDOC:Joomla_4_Tutorials_Project|Joomla 4 Documentation]] is also needing lots of work.<br />
* '''Patch Testing''': As a main rule, new functions for Joomla have to be tested before they can be merged into an official release. Usually, it takes only a few minutes and you can help make Joomla better.<br />
* '''[[Pizza,_Bugs_and_Fun_2020#Joomla_Documentation|Documentation]]''': There are lots of Documents that [[JDOC:Maintenance_Tasks|need writing or maintenance]]. Tutorials and Help Screens are needed for Joomla! 4.<br />
* '''[[JDOC:Page Translation Quickstart Guide|Documentation Translation]]''': At the PBF Event we hope to translate lots of English documents into other languages to give Joomla! users as much information as possible in their language.<br />
* '''Language Packs''': Sign up to [[Crowdin|Crowdin]], which Joomla's now using for localisation and translation. From there, you can get started on translating Joomla into your local language. Joomla 4 language packs are ready on Crowdin for translation, and need your help to speed up completion in anticipation of Joomla 4's release.<br />
<br />
== FAQ ==<br />
If you don't find what you are looking for, here are a few FAQs:<br><br><br />
'''Q:''' Where can I register if I want to join?<br><br />
'''A:''' Search for a [https://community.joomla.org/user-groups.html| Joomla User Group] and contact them to find out if they're doing something. You can also look at [[S:MyLanguage/Portal:Joomla_User_Groups|starting your own Joomla User Group (JUG)]] near you or write an email to the team [mailto:team@pizza-bug-and-fun.com].<br />
<br />
'''Q:''' I can't go to a location - can I join online?<br><br />
'''A:''' Yes! You only need a computer and an internet connection, but unfortunately you have to order or [https://pizza-bugs-fun.com/en/the-pizza make your own pizza].<br />
<br />
'''Q:''' I missed it! Can I still help?<br><br />
'''A:''' You sure can! Since April this year, every Saturday with the world heavily locked down, we've been running [[S:MyLanguage/Bugs & Fun @Home|Bugs & Fun @Home (BF@H)]], where there's been volunteers dropping in when they can to work through the goals outlined in the list above. That's going to continue into the future, so check the BF@H page for details.<br />
<br />
'''Q:''' How can I get more involved?<br><br />
'''A:''' Joomla's after all sorts of skilled volunteers for a wide range of positions. Take a look at the [https://volunteers.joomla.org/ Volunteers Portal], especially the [https://volunteers.joomla.org/help-wanted Help Wanted page] to see how you can help, or just start a conversation during PBF or one weekend during BF@H.<br />
<br />
<br />
== Organization, logistics and communications ==<br />
PBF events are organized by local [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]]. 2020's a bit different as we're doing it virtually, but for future years, we'd love it if more groups came on board to participate.<br />
<br />
If you would like to participate but don't have a user group nearby, or you are Joomla User Group and want to join, this year it's easier than ever to do so online!<br />
There are a few requirements:<br />
<br />
* You need a room with WiFi access.<br />
* You need some Joomlers equipped with a laptop and motivation.<br />
* Do not hesitate to send an email to [mailto:team@pizza-bug-and-fun.com| team@pizza-bug-and-fun.com] or contact the team on [[RingCentral (Glip)|Glip]].<br />
<br />
Of course, you can also join from home, but where is the fun without the community and the pizza?<br />
<br />
==Réseaux Sociaux==<br />
Joomla! is all about community, and so if you're participating in PBF, tell us, and the world, about it.<br />
* For sharing information in the social media please use these hashtags: #pbf20 #joomla<br />
* Also include tags for things you're working on like: #joomla4 #joomladocs #joomlatranslation #a11y #l10n<br />
<br />
=== Illustrations de réseaux sociaux ===<br />
<br />
Right click on the images and choose "Save Image as" to download to your computer to uses these graphics on Social Media<br />
<br />
<div><ul><br />
<li style="display: inline-block;">[[File:Pbf_1200x628.png|200px|thumb|none|Facebook 1200x628]]</li><br />
<li style="display: inline-block;">[[File:Pbf_2020_instagram_1024x1024.png|200px|thumb|none|Instagram 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_1024x1024overlay.png|200px|thumb|none|Instagram Transparent Overlay 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_overlay.png|200px|thumb|none|PBF Bug Transparent Overlay]]</li><br />
</ul></div><br />
<br />
You can use the overlay images, which are transparent PNG files, in other programs to add the PBF Bug to your photos to promote the event.<br />
<br />
== Locations ==<br />
Add your local PBF involvement to the list below (You'll need a JDOCs account, but you're about to contribute to JDOCS during PBF, so that's something you'll have soon if not already!)<br />
<br />
This year everything is different: COVID-19 does not allow us to organize an offline event, or only under very difficult conditions. That's why we decided to create circumstances so that everybody can participate online.<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== Océanie et Australie ===<br />
* Australia - West End, Brisbane - in person event day <br />
* Australia - Other regions - online only<br />
For more information on Australia's 2020 PBF participation visit [https://joomla.org.au/pbf joomla.org.au/pbf]<br />
== Registration ==<br />
=== For Write Access to this Wiki ===<br />
To get write access to this wiki you will need to [[Special:Userlogin|register or login here first]]. (See also the [[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute]] page for more details on getting started on contributing to Joomla documentation.<br />
<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== At a Physical Location ===<br />
If you wish to be present at one of the physical locations listed above then you must register in advance because space is potentially limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.<br />
<br />
=== Taking Bugs, Tasks and Pizza ===<br />
This year PBF aren't supplying the pizza, so order your own from your favourite pizza place or here's a video we've put together [https://pizza-bugs-fun.com/en/the-pizza on how to make your own pizza].<br />
<br />
<br />
==Exigences et conditions de participation==<br />
Pizza, Bugs & Fun is an event that aims to help meet [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Joomla's Mission, Vision & Values]. Contributing to the Joomla! community assumes acceptance of the principles outlined in the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Joomla! Code of Conduct].<br />
<br />
* All code must be made available under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html General Public Licence version 2].<br />
* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]<br />
* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]<br />
* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.<br />
<br />
== Communication Tools ==<br />
That's how teamwork works these days :-)<br />
You can check your [https://kps.fyi/utc local time compared to UTC here].<br />
==== Glip - PBF20 channel ====<br />
In the Glip/RingCentral Chatroom, you can ask questions and exchange ideas. [https://glip.com Glip] and [https://github.com GitHub] For example if you need further clarification for a patch test.<br />
==== Video Chat ====<br />
You can join the [https://pizza-bugs-fun.com/videochat/ PBF20 Video Chat] during the weekend from 2200UTC Friday night (when Australia kicks off PBF20) through to ~0800UTC Sunday Morning (when USA West Coast finishes Saturday night). <br />
<br />
The PBF20 Video Chat uses BigBlueButton, and you can [https://bigbluebutton.org/html5/ watch their tutorials] to see how to use the features of the BigBlueButton platform. <br />
<br />
==== Google Meet - Fallback ====<br />
Just in case you're having issues with getting onto Glip, or the PBF Video Chat, we'll also have the [https://meet.google.com/bke-ufkq-eif Bugs & Fun @Home Google Meet] open from 2200UTC as a fallback.<br />
== Preparations and installations ==<br />
===Outils à utiliser===<br />
There's some other tools to use to get involved as a Bug Tester for Joomla, as well as if you're looking to get involved in the Joomla project overall. The links below take you to pages on JDOCs that will help you get started.<br />
* [[RingCentral_(Glip)|RingCentral (Glip)]] is the communication tool used by the Joomla Project.<br />
** Once you've been added on RingCentral, search for the PBF20 channel to join the conversation.<br />
* [[GitHub|GitHub]] is the tool Joomla uses for managing the code for the CMS, and a login to GitHub also allows you to use the [https://issues.joomla.org|Joomla Issues Tracker].<br />
* [[JDOC:How_to_Contribute_to_Joomla!_Documentation|Joomla Documentation Wiki]] is where all of the Joomla Help documents are created and managed, and to help with documentation, create an account there and you can then help with updating Joomla's help.<br />
* [[Crowdin|Crowdin]] is the translation management tool all of Joomla's official language packs are managed in. Creating an account there will allow you to help with contributing to translations in your own language.<br />
<br />
=== Watch the Training Videos === <br />
[https://www.youtube.com/watch?v=V8hSEDsjsJc Watch this training video], which takes you through a few of the above tools, and how to perform some of the tasks you'll be doing for PBF20. <br />
=== Setting up a Joomla! Installation ===<br />
Required if you want to test patches. There are two ways to get a Joomla! installation at PBF:<br />
* [http://pizza-bugs-fun.com/servers/ Access one of the Pre-installed Joomla 4 installations here.]<br />
** Servers are available in the UK, USA, Germany and Spain.<br />
** To get an instance to test on, click on the domain for a server, log in and change your password to take over the instance.<br />
** After you've changed the password on an instance, set up the pre-installed patch tester to start testing.<br />
** Drop a message in the PBF20 Glip, or in one of the video chats to say which instance you grabbed so others can see what's available next.<br />
** ''Can't access the instance you're trying? Once the password is changed, that instance is taken, so keep trying until you can get into one. Check the PBF20 Glip channel to see what the next available instance may be.''<br />
* Set up a local installation on your device. There's a variety of options you can look at installing. [https://magazine.joomla.org/All-issues/june-2020/github-installing-git Read this Joomla Magazine Article] for a tutorial on installing an environment using XAMPP, as well as configuring the Joomla Patch Tester and Joomla 4.<br />
* Check out the [[Bugs & Fun @Home]] page for a number of other links to resources relating to patch testing and setting up your test environment.<br />
{{tip|title=300 PBF Joomla instances thanks to [https://www.ionos.com/ IONOS]|text=Thanks to PBF sponsor IONOS, there's [http://pizza-bugs-fun.com/servers/ 300 Joomla instances] ready to go for the event, so skip setting up your own for the day.}}<br />
=== Tasks Lists ===<br />
To help you focus in on what needs doing, here's where to find the<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1454163514 '''Explorer'''] - Suitable for beginners. Covers documentation and translation tasks.<br>''The [[JDOC:Maintenance Tasks|Joomla Documentation Maintenance Tasks List]] has plenty of other items for you to consider if you're not confident getting started with the Explorer list.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1748937094 '''Adventurer'''] - Covers patch testing of pull requests for Joomla.<br>''There's always new PR's coming in during the event as code is created to address issues. Check the list of [https://github.com/joomla/joomla-cms/pulls pull requests] later in the day to see if there's new items to test.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=0 '''Conquerer'''] - Advanced tasks - these are issues that require code, consideration and conversation to resolve.<br>''Looking for a problem to resolve? In addition to the Conqueror list, the GitHub [https://github.com/joomla/joomla-cms/issues issues list] has many other issues needing volunteers to create solutions for... is that you?'' <br />
==Documentation Joomla==<br />
=== JDoc Contributions ===<br />
If you don't want to test patches but still want to give back a lot of support to the community, help writing the JDocs for Joomla! 4.<br />
<br />
You will find all information you need to get started here. Please read: <br />
<br />
* Create a JDoc account - read [[JDOC:How_to_Contribute_to_Joomla!_Documentation| How to Contribute to Joomla! Documentation]]<br />
* Read the [[S:MyLanguage/JDOC:Terms_of_Service| Wiki Policy]]<br />
* JDoc Cheatsheet [[S:MyLanguage/JHelp:Cheatsheet| JDoc Wiki formatting codes]]<br />
<br />
=== JDocs Translations ===<br />
If you don't want to test patches but still want to give back and support the community, help to translate the JDocs.<br />
<br />
Here you will find all the information you will need to get started. Please read '''[[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute to Joomla! Documentation]]'''. <br />
<br />
==Merci aux contributeurs du PBF20==<br />
{{#ev:youtube|Kxst-xiF5CQ}}<br />
<br />
Si vous avez contribué pendant le PBF20, assurez-vous de bien enregistrer vos contributions :<br />
[[S:MyLanguage/Pizza Bugs and Fun 2020/Contributors List|Contributors List]]<br />
<br />
==Related Information==<br />
* Organizers website [https://www.pizza-bugs-fun.com pizza-bugs-fun.com]<br />
* Joomla (and by associate PBF20) is registered as a [https://hacktoberfest.digitalocean.com/ Hacktoberfest Event]. Create 4 PR's in October and you can earn a tee or a tree. See website for information.<br />
<br />
<noinclude><br />
<noinclude><br />
[[Category:Bug Squad{{#translation:}}]]<br />
[[Category:Development{{#translation:}}]]<br />
[[Category:Events{{#translation:}}]]<br />
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Pizza,_Bugs_and_Fun_2020/92/fr&diff=757274Translations:Pizza, Bugs and Fun 2020/92/fr2020-10-17T09:58:32Z<p>Sandra97: Created page with "Les tâches du jour sont regroupées en plusieurs catégories, et selon le niveau de compétences. Ainsi, chacun, quel que soit son niveau, peut contribuer à la réalisation..."</p>
<hr />
<div>Les tâches du jour sont regroupées en plusieurs catégories, et selon le niveau de compétences. Ainsi, chacun, quel que soit son niveau, peut contribuer à la réalisation de ces tâches :</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Pizza,_Bugs_and_Fun_2020/fr&diff=757273Pizza, Bugs and Fun 2020/fr2020-10-17T09:57:18Z<p>Sandra97: Created page with "Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins je..."</p>
<hr />
<div>[[Image:pbf-2020en.png|1100px]]<br />
<noinclude><languages /></noinclude><br />
{{RightTOC}}<br />
<br />
<br />
Cette année, l'événement Joomla ! Pizza Bug and Fun (PBF) a lieu le '''17 octobre 2020''' et verra des participants du monde entier se joindre à l'événement.<br />
Ce wiki est utilisé comme ressource centrale pour coordonner les efforts et présenter les résultats de cet événement. <br />
Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !<br />
<br />
== Bienvenue ==<br />
{{#ev:youtube|UXFUA70kMqg}}<br />
Video subtitles: [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=en EN] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=DE DE] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=fr FR] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=es ES] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=it IT]<br />
<br />
== Objectifs ==<br />
<br />
Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins jeune, le Pizza Bugs and Fun est fait pour vous. L'événement est destiné à ceux qui travaillent déjà avec Joomla ou qui veulent faire connaissance avec Joomla. Seul votre intérêt pour Joomla est important. Vous êtes toutes et tous les bienvenu(e)s.<br />
Le 17 octobre 2020, nous aimerions inviter tous les utilisateurs enthousiastes de Joomla, quelles que soient vos connaissances préalables, à améliorer encore plus Joomla. Tout soutien est grandement apprécié ! La participation est gratuite, et bien que les boissons non alcoolisées et la pizza soient normalement incluses grâce aux sponsors de l'événement, la COVID-19 nous a contraint à un événement virtuel. <br />
Tasks for the day are grouped across a number of categories, as well as a range of skill levels, so there's something for everyone at any level to contribute to:<br />
* '''Joomla 4''': Joomla 4.0 is coming soon, but it still has a lot of bugs and feature requests that are untested, or need additional code, which means they cannot be added into the Joomla core. [[JDOC:Joomla_4_Tutorials_Project|Joomla 4 Documentation]] is also needing lots of work.<br />
* '''Patch Testing''': As a main rule, new functions for Joomla have to be tested before they can be merged into an official release. Usually, it takes only a few minutes and you can help make Joomla better.<br />
* '''[[Pizza,_Bugs_and_Fun_2020#Joomla_Documentation|Documentation]]''': There are lots of Documents that [[JDOC:Maintenance_Tasks|need writing or maintenance]]. Tutorials and Help Screens are needed for Joomla! 4.<br />
* '''[[JDOC:Page Translation Quickstart Guide|Documentation Translation]]''': At the PBF Event we hope to translate lots of English documents into other languages to give Joomla! users as much information as possible in their language.<br />
* '''Language Packs''': Sign up to [[Crowdin|Crowdin]], which Joomla's now using for localisation and translation. From there, you can get started on translating Joomla into your local language. Joomla 4 language packs are ready on Crowdin for translation, and need your help to speed up completion in anticipation of Joomla 4's release.<br />
<br />
== FAQ ==<br />
If you don't find what you are looking for, here are a few FAQs:<br><br><br />
'''Q:''' Where can I register if I want to join?<br><br />
'''A:''' Search for a [https://community.joomla.org/user-groups.html| Joomla User Group] and contact them to find out if they're doing something. You can also look at [[S:MyLanguage/Portal:Joomla_User_Groups|starting your own Joomla User Group (JUG)]] near you or write an email to the team [mailto:team@pizza-bug-and-fun.com].<br />
<br />
'''Q:''' I can't go to a location - can I join online?<br><br />
'''A:''' Yes! You only need a computer and an internet connection, but unfortunately you have to order or [https://pizza-bugs-fun.com/en/the-pizza make your own pizza].<br />
<br />
'''Q:''' I missed it! Can I still help?<br><br />
'''A:''' You sure can! Since April this year, every Saturday with the world heavily locked down, we've been running [[S:MyLanguage/Bugs & Fun @Home|Bugs & Fun @Home (BF@H)]], where there's been volunteers dropping in when they can to work through the goals outlined in the list above. That's going to continue into the future, so check the BF@H page for details.<br />
<br />
'''Q:''' How can I get more involved?<br><br />
'''A:''' Joomla's after all sorts of skilled volunteers for a wide range of positions. Take a look at the [https://volunteers.joomla.org/ Volunteers Portal], especially the [https://volunteers.joomla.org/help-wanted Help Wanted page] to see how you can help, or just start a conversation during PBF or one weekend during BF@H.<br />
<br />
<br />
== Organization, logistics and communications ==<br />
PBF events are organized by local [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]]. 2020's a bit different as we're doing it virtually, but for future years, we'd love it if more groups came on board to participate.<br />
<br />
If you would like to participate but don't have a user group nearby, or you are Joomla User Group and want to join, this year it's easier than ever to do so online!<br />
There are a few requirements:<br />
<br />
* You need a room with WiFi access.<br />
* You need some Joomlers equipped with a laptop and motivation.<br />
* Do not hesitate to send an email to [mailto:team@pizza-bug-and-fun.com| team@pizza-bug-and-fun.com] or contact the team on [[RingCentral (Glip)|Glip]].<br />
<br />
Of course, you can also join from home, but where is the fun without the community and the pizza?<br />
<br />
==Réseaux Sociaux==<br />
Joomla! is all about community, and so if you're participating in PBF, tell us, and the world, about it.<br />
* For sharing information in the social media please use these hashtags: #pbf20 #joomla<br />
* Also include tags for things you're working on like: #joomla4 #joomladocs #joomlatranslation #a11y #l10n<br />
<br />
=== Illustrations de réseaux sociaux ===<br />
<br />
Right click on the images and choose "Save Image as" to download to your computer to uses these graphics on Social Media<br />
<br />
<div><ul><br />
<li style="display: inline-block;">[[File:Pbf_1200x628.png|200px|thumb|none|Facebook 1200x628]]</li><br />
<li style="display: inline-block;">[[File:Pbf_2020_instagram_1024x1024.png|200px|thumb|none|Instagram 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_1024x1024overlay.png|200px|thumb|none|Instagram Transparent Overlay 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_overlay.png|200px|thumb|none|PBF Bug Transparent Overlay]]</li><br />
</ul></div><br />
<br />
You can use the overlay images, which are transparent PNG files, in other programs to add the PBF Bug to your photos to promote the event.<br />
<br />
== Locations ==<br />
Add your local PBF involvement to the list below (You'll need a JDOCs account, but you're about to contribute to JDOCS during PBF, so that's something you'll have soon if not already!)<br />
<br />
This year everything is different: COVID-19 does not allow us to organize an offline event, or only under very difficult conditions. That's why we decided to create circumstances so that everybody can participate online.<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== Océanie et Australie ===<br />
* Australia - West End, Brisbane - in person event day <br />
* Australia - Other regions - online only<br />
For more information on Australia's 2020 PBF participation visit [https://joomla.org.au/pbf joomla.org.au/pbf]<br />
== Registration ==<br />
=== For Write Access to this Wiki ===<br />
To get write access to this wiki you will need to [[Special:Userlogin|register or login here first]]. (See also the [[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute]] page for more details on getting started on contributing to Joomla documentation.<br />
<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== At a Physical Location ===<br />
If you wish to be present at one of the physical locations listed above then you must register in advance because space is potentially limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.<br />
<br />
=== Taking Bugs, Tasks and Pizza ===<br />
This year PBF aren't supplying the pizza, so order your own from your favourite pizza place or here's a video we've put together [https://pizza-bugs-fun.com/en/the-pizza on how to make your own pizza].<br />
<br />
<br />
==Exigences et conditions de participation==<br />
Pizza, Bugs & Fun is an event that aims to help meet [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Joomla's Mission, Vision & Values]. Contributing to the Joomla! community assumes acceptance of the principles outlined in the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Joomla! Code of Conduct].<br />
<br />
* All code must be made available under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html General Public Licence version 2].<br />
* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]<br />
* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]<br />
* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.<br />
<br />
== Communication Tools ==<br />
That's how teamwork works these days :-)<br />
You can check your [https://kps.fyi/utc local time compared to UTC here].<br />
==== Glip - PBF20 channel ====<br />
In the Glip/RingCentral Chatroom, you can ask questions and exchange ideas. [https://glip.com Glip] and [https://github.com GitHub] For example if you need further clarification for a patch test.<br />
==== Video Chat ====<br />
You can join the [https://pizza-bugs-fun.com/videochat/ PBF20 Video Chat] during the weekend from 2200UTC Friday night (when Australia kicks off PBF20) through to ~0800UTC Sunday Morning (when USA West Coast finishes Saturday night). <br />
<br />
The PBF20 Video Chat uses BigBlueButton, and you can [https://bigbluebutton.org/html5/ watch their tutorials] to see how to use the features of the BigBlueButton platform. <br />
<br />
==== Google Meet - Fallback ====<br />
Just in case you're having issues with getting onto Glip, or the PBF Video Chat, we'll also have the [https://meet.google.com/bke-ufkq-eif Bugs & Fun @Home Google Meet] open from 2200UTC as a fallback.<br />
== Preparations and installations ==<br />
===Outils à utiliser===<br />
There's some other tools to use to get involved as a Bug Tester for Joomla, as well as if you're looking to get involved in the Joomla project overall. The links below take you to pages on JDOCs that will help you get started.<br />
* [[RingCentral_(Glip)|RingCentral (Glip)]] is the communication tool used by the Joomla Project.<br />
** Once you've been added on RingCentral, search for the PBF20 channel to join the conversation.<br />
* [[GitHub|GitHub]] is the tool Joomla uses for managing the code for the CMS, and a login to GitHub also allows you to use the [https://issues.joomla.org|Joomla Issues Tracker].<br />
* [[JDOC:How_to_Contribute_to_Joomla!_Documentation|Joomla Documentation Wiki]] is where all of the Joomla Help documents are created and managed, and to help with documentation, create an account there and you can then help with updating Joomla's help.<br />
* [[Crowdin|Crowdin]] is the translation management tool all of Joomla's official language packs are managed in. Creating an account there will allow you to help with contributing to translations in your own language.<br />
<br />
=== Watch the Training Videos === <br />
[https://www.youtube.com/watch?v=V8hSEDsjsJc Watch this training video], which takes you through a few of the above tools, and how to perform some of the tasks you'll be doing for PBF20. <br />
=== Setting up a Joomla! Installation ===<br />
Required if you want to test patches. There are two ways to get a Joomla! installation at PBF:<br />
* [http://pizza-bugs-fun.com/servers/ Access one of the Pre-installed Joomla 4 installations here.]<br />
** Servers are available in the UK, USA, Germany and Spain.<br />
** To get an instance to test on, click on the domain for a server, log in and change your password to take over the instance.<br />
** After you've changed the password on an instance, set up the pre-installed patch tester to start testing.<br />
** Drop a message in the PBF20 Glip, or in one of the video chats to say which instance you grabbed so others can see what's available next.<br />
** ''Can't access the instance you're trying? Once the password is changed, that instance is taken, so keep trying until you can get into one. Check the PBF20 Glip channel to see what the next available instance may be.''<br />
* Set up a local installation on your device. There's a variety of options you can look at installing. [https://magazine.joomla.org/All-issues/june-2020/github-installing-git Read this Joomla Magazine Article] for a tutorial on installing an environment using XAMPP, as well as configuring the Joomla Patch Tester and Joomla 4.<br />
* Check out the [[Bugs & Fun @Home]] page for a number of other links to resources relating to patch testing and setting up your test environment.<br />
{{tip|title=300 PBF Joomla instances thanks to [https://www.ionos.com/ IONOS]|text=Thanks to PBF sponsor IONOS, there's [http://pizza-bugs-fun.com/servers/ 300 Joomla instances] ready to go for the event, so skip setting up your own for the day.}}<br />
=== Tasks Lists ===<br />
To help you focus in on what needs doing, here's where to find the<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1454163514 '''Explorer'''] - Suitable for beginners. Covers documentation and translation tasks.<br>''The [[JDOC:Maintenance Tasks|Joomla Documentation Maintenance Tasks List]] has plenty of other items for you to consider if you're not confident getting started with the Explorer list.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1748937094 '''Adventurer'''] - Covers patch testing of pull requests for Joomla.<br>''There's always new PR's coming in during the event as code is created to address issues. Check the list of [https://github.com/joomla/joomla-cms/pulls pull requests] later in the day to see if there's new items to test.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=0 '''Conquerer'''] - Advanced tasks - these are issues that require code, consideration and conversation to resolve.<br>''Looking for a problem to resolve? In addition to the Conqueror list, the GitHub [https://github.com/joomla/joomla-cms/issues issues list] has many other issues needing volunteers to create solutions for... is that you?'' <br />
==Documentation Joomla==<br />
=== JDoc Contributions ===<br />
If you don't want to test patches but still want to give back a lot of support to the community, help writing the JDocs for Joomla! 4.<br />
<br />
You will find all information you need to get started here. Please read: <br />
<br />
* Create a JDoc account - read [[JDOC:How_to_Contribute_to_Joomla!_Documentation| How to Contribute to Joomla! Documentation]]<br />
* Read the [[S:MyLanguage/JDOC:Terms_of_Service| Wiki Policy]]<br />
* JDoc Cheatsheet [[S:MyLanguage/JHelp:Cheatsheet| JDoc Wiki formatting codes]]<br />
<br />
=== JDocs Translations ===<br />
If you don't want to test patches but still want to give back and support the community, help to translate the JDocs.<br />
<br />
Here you will find all the information you will need to get started. Please read '''[[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute to Joomla! Documentation]]'''. <br />
<br />
==Merci aux contributeurs du PBF20==<br />
{{#ev:youtube|Kxst-xiF5CQ}}<br />
<br />
Si vous avez contribué pendant le PBF20, assurez-vous de bien enregistrer vos contributions :<br />
[[S:MyLanguage/Pizza Bugs and Fun 2020/Contributors List|Contributors List]]<br />
<br />
==Related Information==<br />
* Organizers website [https://www.pizza-bugs-fun.com pizza-bugs-fun.com]<br />
* Joomla (and by associate PBF20) is registered as a [https://hacktoberfest.digitalocean.com/ Hacktoberfest Event]. Create 4 PR's in October and you can earn a tee or a tree. See website for information.<br />
<br />
<noinclude><br />
<noinclude><br />
[[Category:Bug Squad{{#translation:}}]]<br />
[[Category:Development{{#translation:}}]]<br />
[[Category:Events{{#translation:}}]]<br />
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Pizza,_Bugs_and_Fun_2020/43/fr&diff=757272Translations:Pizza, Bugs and Fun 2020/43/fr2020-10-17T09:57:18Z<p>Sandra97: Created page with "Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins je..."</p>
<hr />
<div>Que vous soyez débutant ou professionnel, graphiste ou programmeur, que vous ayez une agence ou un site d'association, que vous soyez une femme ou un homme, jeune ou moins jeune, le Pizza Bugs and Fun est fait pour vous. L'événement est destiné à ceux qui travaillent déjà avec Joomla ou qui veulent faire connaissance avec Joomla. Seul votre intérêt pour Joomla est important. Vous êtes toutes et tous les bienvenu(e)s.<br />
Le 17 octobre 2020, nous aimerions inviter tous les utilisateurs enthousiastes de Joomla, quelles que soient vos connaissances préalables, à améliorer encore plus Joomla. Tout soutien est grandement apprécié ! La participation est gratuite, et bien que les boissons non alcoolisées et la pizza soient normalement incluses grâce aux sponsors de l'événement, la COVID-19 nous a contraint à un événement virtuel.</div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Pizza,_Bugs_and_Fun_2020/fr&diff=757270Pizza, Bugs and Fun 2020/fr2020-10-17T09:54:49Z<p>Sandra97: Created page with "Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !"</p>
<hr />
<div>[[Image:pbf-2020en.png|1100px]]<br />
<noinclude><languages /></noinclude><br />
{{RightTOC}}<br />
<br />
<br />
Cette année, l'événement Joomla ! Pizza Bug and Fun (PBF) a lieu le '''17 octobre 2020''' et verra des participants du monde entier se joindre à l'événement.<br />
Ce wiki est utilisé comme ressource centrale pour coordonner les efforts et présenter les résultats de cet événement. <br />
Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !<br />
<br />
== Bienvenue ==<br />
{{#ev:youtube|UXFUA70kMqg}}<br />
Video subtitles: [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=en EN] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=DE DE] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=fr FR] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=es ES] [https://www.youtube.com/embed/UXFUA70kMqg?cc_load_policy=1&cc_lang_pref=it IT]<br />
<br />
== Objectifs ==<br />
<br />
Whether you are a newbie, beginner or professional, graphic designer or programmer, whether you have an agency or a club site, whether female or male, whether young or old, Pizza Bugs and Fun is for you. The event is for those who already work with Joomla! or want to get to know Joomla! first. Only your interest in Joomla! counts. Everyone is welcome.<br />
On '''17th of October 2020''' we would like to invite you all Joomla-enthusiastic users, regardless of your previous knowledge, to make Joomla! even better. We are grateful for any support! Participation is free, and though non-alcoholic drinks and pizza are normally included thanks to sponsors of the event, COVID-19 sees us going virtual instead. <br />
Tasks for the day are grouped across a number of categories, as well as a range of skill levels, so there's something for everyone at any level to contribute to:<br />
* '''Joomla 4''': Joomla 4.0 is coming soon, but it still has a lot of bugs and feature requests that are untested, or need additional code, which means they cannot be added into the Joomla core. [[JDOC:Joomla_4_Tutorials_Project|Joomla 4 Documentation]] is also needing lots of work.<br />
* '''Patch Testing''': As a main rule, new functions for Joomla have to be tested before they can be merged into an official release. Usually, it takes only a few minutes and you can help make Joomla better.<br />
* '''[[Pizza,_Bugs_and_Fun_2020#Joomla_Documentation|Documentation]]''': There are lots of Documents that [[JDOC:Maintenance_Tasks|need writing or maintenance]]. Tutorials and Help Screens are needed for Joomla! 4.<br />
* '''[[JDOC:Page Translation Quickstart Guide|Documentation Translation]]''': At the PBF Event we hope to translate lots of English documents into other languages to give Joomla! users as much information as possible in their language.<br />
* '''Language Packs''': Sign up to [[Crowdin|Crowdin]], which Joomla's now using for localisation and translation. From there, you can get started on translating Joomla into your local language. Joomla 4 language packs are ready on Crowdin for translation, and need your help to speed up completion in anticipation of Joomla 4's release.<br />
<br />
== FAQ ==<br />
If you don't find what you are looking for, here are a few FAQs:<br><br><br />
'''Q:''' Where can I register if I want to join?<br><br />
'''A:''' Search for a [https://community.joomla.org/user-groups.html| Joomla User Group] and contact them to find out if they're doing something. You can also look at [[S:MyLanguage/Portal:Joomla_User_Groups|starting your own Joomla User Group (JUG)]] near you or write an email to the team [mailto:team@pizza-bug-and-fun.com].<br />
<br />
'''Q:''' I can't go to a location - can I join online?<br><br />
'''A:''' Yes! You only need a computer and an internet connection, but unfortunately you have to order or [https://pizza-bugs-fun.com/en/the-pizza make your own pizza].<br />
<br />
'''Q:''' I missed it! Can I still help?<br><br />
'''A:''' You sure can! Since April this year, every Saturday with the world heavily locked down, we've been running [[S:MyLanguage/Bugs & Fun @Home|Bugs & Fun @Home (BF@H)]], where there's been volunteers dropping in when they can to work through the goals outlined in the list above. That's going to continue into the future, so check the BF@H page for details.<br />
<br />
'''Q:''' How can I get more involved?<br><br />
'''A:''' Joomla's after all sorts of skilled volunteers for a wide range of positions. Take a look at the [https://volunteers.joomla.org/ Volunteers Portal], especially the [https://volunteers.joomla.org/help-wanted Help Wanted page] to see how you can help, or just start a conversation during PBF or one weekend during BF@H.<br />
<br />
<br />
== Organization, logistics and communications ==<br />
PBF events are organized by local [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]]. 2020's a bit different as we're doing it virtually, but for future years, we'd love it if more groups came on board to participate.<br />
<br />
If you would like to participate but don't have a user group nearby, or you are Joomla User Group and want to join, this year it's easier than ever to do so online!<br />
There are a few requirements:<br />
<br />
* You need a room with WiFi access.<br />
* You need some Joomlers equipped with a laptop and motivation.<br />
* Do not hesitate to send an email to [mailto:team@pizza-bug-and-fun.com| team@pizza-bug-and-fun.com] or contact the team on [[RingCentral (Glip)|Glip]].<br />
<br />
Of course, you can also join from home, but where is the fun without the community and the pizza?<br />
<br />
==Réseaux Sociaux==<br />
Joomla! is all about community, and so if you're participating in PBF, tell us, and the world, about it.<br />
* For sharing information in the social media please use these hashtags: #pbf20 #joomla<br />
* Also include tags for things you're working on like: #joomla4 #joomladocs #joomlatranslation #a11y #l10n<br />
<br />
=== Illustrations de réseaux sociaux ===<br />
<br />
Right click on the images and choose "Save Image as" to download to your computer to uses these graphics on Social Media<br />
<br />
<div><ul><br />
<li style="display: inline-block;">[[File:Pbf_1200x628.png|200px|thumb|none|Facebook 1200x628]]</li><br />
<li style="display: inline-block;">[[File:Pbf_2020_instagram_1024x1024.png|200px|thumb|none|Instagram 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_1024x1024overlay.png|200px|thumb|none|Instagram Transparent Overlay 1024x1024]]</li><br />
<li style="display: inline-block;">[[File:Pbf20_overlay.png|200px|thumb|none|PBF Bug Transparent Overlay]]</li><br />
</ul></div><br />
<br />
You can use the overlay images, which are transparent PNG files, in other programs to add the PBF Bug to your photos to promote the event.<br />
<br />
== Locations ==<br />
Add your local PBF involvement to the list below (You'll need a JDOCs account, but you're about to contribute to JDOCS during PBF, so that's something you'll have soon if not already!)<br />
<br />
This year everything is different: COVID-19 does not allow us to organize an offline event, or only under very difficult conditions. That's why we decided to create circumstances so that everybody can participate online.<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== Océanie et Australie ===<br />
* Australia - West End, Brisbane - in person event day <br />
* Australia - Other regions - online only<br />
For more information on Australia's 2020 PBF participation visit [https://joomla.org.au/pbf joomla.org.au/pbf]<br />
== Registration ==<br />
=== For Write Access to this Wiki ===<br />
To get write access to this wiki you will need to [[Special:Userlogin|register or login here first]]. (See also the [[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute]] page for more details on getting started on contributing to Joomla documentation.<br />
<br />
Please be aware that the registration process requires you to have a valid email address, and verify the account through an email that's sent to your email.<br />
=== At a Physical Location ===<br />
If you wish to be present at one of the physical locations listed above then you must register in advance because space is potentially limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.<br />
<br />
=== Taking Bugs, Tasks and Pizza ===<br />
This year PBF aren't supplying the pizza, so order your own from your favourite pizza place or here's a video we've put together [https://pizza-bugs-fun.com/en/the-pizza on how to make your own pizza].<br />
<br />
<br />
==Exigences et conditions de participation==<br />
Pizza, Bugs & Fun is an event that aims to help meet [https://www.joomla.org/about-joomla/the-project/mission-vision-and-values.html Joomla's Mission, Vision & Values]. Contributing to the Joomla! community assumes acceptance of the principles outlined in the [https://www.joomla.org/about-joomla/the-project/code-of-conduct.html Joomla! Code of Conduct].<br />
<br />
* All code must be made available under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html General Public Licence version 2].<br />
* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]<br />
* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]<br />
* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.<br />
<br />
== Communication Tools ==<br />
That's how teamwork works these days :-)<br />
You can check your [https://kps.fyi/utc local time compared to UTC here].<br />
==== Glip - PBF20 channel ====<br />
In the Glip/RingCentral Chatroom, you can ask questions and exchange ideas. [https://glip.com Glip] and [https://github.com GitHub] For example if you need further clarification for a patch test.<br />
==== Video Chat ====<br />
You can join the [https://pizza-bugs-fun.com/videochat/ PBF20 Video Chat] during the weekend from 2200UTC Friday night (when Australia kicks off PBF20) through to ~0800UTC Sunday Morning (when USA West Coast finishes Saturday night). <br />
<br />
The PBF20 Video Chat uses BigBlueButton, and you can [https://bigbluebutton.org/html5/ watch their tutorials] to see how to use the features of the BigBlueButton platform. <br />
<br />
==== Google Meet - Fallback ====<br />
Just in case you're having issues with getting onto Glip, or the PBF Video Chat, we'll also have the [https://meet.google.com/bke-ufkq-eif Bugs & Fun @Home Google Meet] open from 2200UTC as a fallback.<br />
== Preparations and installations ==<br />
===Outils à utiliser===<br />
There's some other tools to use to get involved as a Bug Tester for Joomla, as well as if you're looking to get involved in the Joomla project overall. The links below take you to pages on JDOCs that will help you get started.<br />
* [[RingCentral_(Glip)|RingCentral (Glip)]] is the communication tool used by the Joomla Project.<br />
** Once you've been added on RingCentral, search for the PBF20 channel to join the conversation.<br />
* [[GitHub|GitHub]] is the tool Joomla uses for managing the code for the CMS, and a login to GitHub also allows you to use the [https://issues.joomla.org|Joomla Issues Tracker].<br />
* [[JDOC:How_to_Contribute_to_Joomla!_Documentation|Joomla Documentation Wiki]] is where all of the Joomla Help documents are created and managed, and to help with documentation, create an account there and you can then help with updating Joomla's help.<br />
* [[Crowdin|Crowdin]] is the translation management tool all of Joomla's official language packs are managed in. Creating an account there will allow you to help with contributing to translations in your own language.<br />
<br />
=== Watch the Training Videos === <br />
[https://www.youtube.com/watch?v=V8hSEDsjsJc Watch this training video], which takes you through a few of the above tools, and how to perform some of the tasks you'll be doing for PBF20. <br />
=== Setting up a Joomla! Installation ===<br />
Required if you want to test patches. There are two ways to get a Joomla! installation at PBF:<br />
* [http://pizza-bugs-fun.com/servers/ Access one of the Pre-installed Joomla 4 installations here.]<br />
** Servers are available in the UK, USA, Germany and Spain.<br />
** To get an instance to test on, click on the domain for a server, log in and change your password to take over the instance.<br />
** After you've changed the password on an instance, set up the pre-installed patch tester to start testing.<br />
** Drop a message in the PBF20 Glip, or in one of the video chats to say which instance you grabbed so others can see what's available next.<br />
** ''Can't access the instance you're trying? Once the password is changed, that instance is taken, so keep trying until you can get into one. Check the PBF20 Glip channel to see what the next available instance may be.''<br />
* Set up a local installation on your device. There's a variety of options you can look at installing. [https://magazine.joomla.org/All-issues/june-2020/github-installing-git Read this Joomla Magazine Article] for a tutorial on installing an environment using XAMPP, as well as configuring the Joomla Patch Tester and Joomla 4.<br />
* Check out the [[Bugs & Fun @Home]] page for a number of other links to resources relating to patch testing and setting up your test environment.<br />
{{tip|title=300 PBF Joomla instances thanks to [https://www.ionos.com/ IONOS]|text=Thanks to PBF sponsor IONOS, there's [http://pizza-bugs-fun.com/servers/ 300 Joomla instances] ready to go for the event, so skip setting up your own for the day.}}<br />
=== Tasks Lists ===<br />
To help you focus in on what needs doing, here's where to find the<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1454163514 '''Explorer'''] - Suitable for beginners. Covers documentation and translation tasks.<br>''The [[JDOC:Maintenance Tasks|Joomla Documentation Maintenance Tasks List]] has plenty of other items for you to consider if you're not confident getting started with the Explorer list.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=1748937094 '''Adventurer'''] - Covers patch testing of pull requests for Joomla.<br>''There's always new PR's coming in during the event as code is created to address issues. Check the list of [https://github.com/joomla/joomla-cms/pulls pull requests] later in the day to see if there's new items to test.''<br />
* [https://docs.google.com/spreadsheets/d/1lOeSzc2JjUYbjxLI3EVLilYRzg6m8RH8AUBfOtPGWmQ/edit#gid=0 '''Conquerer'''] - Advanced tasks - these are issues that require code, consideration and conversation to resolve.<br>''Looking for a problem to resolve? In addition to the Conqueror list, the GitHub [https://github.com/joomla/joomla-cms/issues issues list] has many other issues needing volunteers to create solutions for... is that you?'' <br />
==Documentation Joomla==<br />
=== JDoc Contributions ===<br />
If you don't want to test patches but still want to give back a lot of support to the community, help writing the JDocs for Joomla! 4.<br />
<br />
You will find all information you need to get started here. Please read: <br />
<br />
* Create a JDoc account - read [[JDOC:How_to_Contribute_to_Joomla!_Documentation| How to Contribute to Joomla! Documentation]]<br />
* Read the [[S:MyLanguage/JDOC:Terms_of_Service| Wiki Policy]]<br />
* JDoc Cheatsheet [[S:MyLanguage/JHelp:Cheatsheet| JDoc Wiki formatting codes]]<br />
<br />
=== JDocs Translations ===<br />
If you don't want to test patches but still want to give back and support the community, help to translate the JDocs.<br />
<br />
Here you will find all the information you will need to get started. Please read '''[[JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute to Joomla! Documentation]]'''. <br />
<br />
==Merci aux contributeurs du PBF20==<br />
{{#ev:youtube|Kxst-xiF5CQ}}<br />
<br />
Si vous avez contribué pendant le PBF20, assurez-vous de bien enregistrer vos contributions :<br />
[[S:MyLanguage/Pizza Bugs and Fun 2020/Contributors List|Contributors List]]<br />
<br />
==Related Information==<br />
* Organizers website [https://www.pizza-bugs-fun.com pizza-bugs-fun.com]<br />
* Joomla (and by associate PBF20) is registered as a [https://hacktoberfest.digitalocean.com/ Hacktoberfest Event]. Create 4 PR's in October and you can earn a tee or a tree. See website for information.<br />
<br />
<noinclude><br />
<noinclude><br />
[[Category:Bug Squad{{#translation:}}]]<br />
[[Category:Development{{#translation:}}]]<br />
[[Category:Events{{#translation:}}]]<br />
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]<br />
[[Category:Volunteer Engagement{{#translation:}}]]<br />
</noinclude><br />
</noinclude></div>Sandra97https://docs.sandbox.joomla.org/index.php?title=Translations:Pizza,_Bugs_and_Fun_2020/91/fr&diff=757269Translations:Pizza, Bugs and Fun 2020/91/fr2020-10-17T09:54:48Z<p>Sandra97: Created page with "Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !"</p>
<hr />
<div>Vous pouvez trouver plus d'informations sur l'événement sur le site [https://www.pizza-bugs-fun.com pizza-bugs-fun.com/fr/], y compris sur l'achat de marchandises PBF !</div>Sandra97