From Fedora Project Wiki
Page title matches
- {{lang|cs|en|es|it|ko|nl|pt|pt-br|ru|sk|zh-cn|zh-tw|page=Help:Editing}}71 bytes (16 words) - 17:08, 7 April 2021
Page text matches
- {{lang|cs|en|es|it|ko|nl|pt|pt-br|ru|sk|zh-cn|zh-tw|page=Help:Editing}}71 bytes (16 words) - 17:08, 7 April 2021
- ** [[Help:Editing#Writing Example Commands]] ** [[Help:Editing#Marking Technical Terms]]4 KB (640 words) - 08:12, 26 February 2012
- * ''make LANG'': builds the pages in a specific language, where LANG is the two-letter abbreviation for the translation. * ''make LANG test'': builds a test instance at http://localhost:5000/ in a specific lang9 KB (1,478 words) - 02:02, 8 October 2018
- * Publican and Fedora/GNOME lang codes not consistent 1 * Not at all clear how login lang selected is used8 KB (1,259 words) - 08:06, 18 September 2016
- ...class="text" style="color: #407a40">popularity and ease of mediawiki does help</td><td class="time">[[#t15:29|15:29]]</td></tr> ...the new wiki's much faster response time and consistent "up-ness" is a big help</td><td class="time">[[#t15:29|15:29]]</td></tr>40 KB (6,220 words) - 21:37, 25 February 2009
- * without editing personal .css or .js files ...ion == 'submit' || wgPageName == 'Special:Upload') { //scripts specific to editing pages17 KB (1,683 words) - 18:38, 27 April 2011
- ...<td class="text" style="color: #42427e">I don't have membership on the per-lang lists, but I can certainly send an email to f-trans-l with a summary</td><t ...class="text" style="color: #818144"><dreaming>1 e-mailadress to all lang-lists</dreaming></td><td class="time"><a href="#t09:09" class="time">39 KB (6,389 words) - 21:41, 25 February 2009
- * Publican and Fedora/GNOME lang codes not consistent 1 * Not at all clear how login lang selected is used10 KB (1,567 words) - 08:13, 19 August 2010
- ** commons-lang-2.4.jar -> jakarta-commons-lang Etherpad is the pinnacle of online, collaborative text editing. If you're not familiar with EtherPad, take a look at [http://www.viddler.c6 KB (871 words) - 23:52, 17 October 2010
- * Editing based on the tickets/issues status changes. (For example, Latam Ambassadors * Move everything under old translation schema ''LANG/OriginalPageName/SomethingElse'' to present way to work on translation: ''P5 KB (775 words) - 10:50, 11 February 2011
- ...ground-color:#ffe9d4">/GNOME</span><span style="background-color:#fbc759"> lang codes not consistent</span><span style="background-color:#befde2"> </span>< </span><span style="background-color:#fbc759">* Not at all clear how login lang selected is used</span><span style="background-color:#ffe9d4"><br />25 KB (3,616 words) - 10:03, 18 September 2016
- Recent versions of <code>Emacs</code> and <code>vi</code> have .spec file editing modes which will also bring up a similar template upon creating a new file. The fields in our <code>.spec</code> file need slight editing. Please follow the [[How_to_create_an_RPM_package#Spec_file_pieces_explaine10 KB (1,609 words) - 09:14, 22 February 2018
- Maybe a GUI tool to set the LANG= variable? (A panel applet?) * GUI for editing RPM sources (for yum/apt/up2date)(?)8 KB (1,229 words) - 16:32, 24 May 2008
- project, including configuration, build, internationalization, help files, etc. This is an iterative process: after editing the <code>.spec</code> file, rerun <code>rpmbuild</code>.12 KB (1,362 words) - 16:39, 8 September 2016
- {{lang|en|es|pt-br|page=FAD Documentation Managua 2013}} ...mong other stuff. We like to spand the abilities of local collaborators to help Fedora Project. One of the voids that we have is local knowledge of documen7 KB (965 words) - 23:30, 24 June 2013
- Recenti versioni di <code>Emacs</code> e <code>vi</code> hanno modalità di editing del file .spec che ripropongono modelli simili durante la creazione di un n project, including configuration, build, internationalization, help files, etc.10 KB (1,485 words) - 15:52, 27 January 2016
- '''Proposed solution''': adopt Uniscribe solution; editing old PS1 fonts is a pointless exercise. With a corrected external mapping, a ...e> with <code>ROM/locl</code> enabled but the default English UI is: <code>LANG=ro_RO.UTF-8 LC_MESSAGES=C gedit</code>. See Pango [http://bugzilla.gnome.or11 KB (1,750 words) - 18:19, 25 June 2009
- ...s to follow, the current way is by editing a PHP file, adding content to a LANG array. We do not actually see the “context” in which this string gets u Each element pulled from the LANG array has an ID associated with it.22 KB (3,711 words) - 11:52, 2 May 2013
- * Add support to the UI for recognizing and displaying BTRFS volumes, but not editing. * The meaning of the lang-table columes has changed.12 KB (1,952 words) - 18:03, 15 February 2012
- rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet rd_LVM_LV=VG_CentOS/LV_CentOS_root rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun1621 KB (3,579 words) - 21:24, 26 February 2012