User talk:SwifT

thanks for the locale how to migration. can you do me a favor and cut out the acknowledgements. acknowledgements are bad on multiple levels. i would not want my good name tied to something, if it has gone rouge and destroyed anything, or used in crimes and me being an accessory in aiding to that. 666threesixes666 (talk) 23:01, 11 December 2013 (UTC)


 * We can only do that if the user requests that. The document license requires attribution. As we do not have edit history for migrated documents, this needs to remain. --SwifT (talk) 12:18, 12 December 2013 (UTC)


 * sorry about the translation number thing, i was almost positive i screwed that up 666threesixes666 (talk) 18:57, 20 December 2013 (UTC)

"Not sure what advantage of kernel linking is here, or using bzImage as name. Switching to additional information about running lilo" re-symlink, no need to touch conf files. 3.10.1 to 3.12.4 same configs, unlink, relink, re lilo, done... leaving old section pointing at 3.10.1.old as it probably works. thanks for translation setup. if i were better at bash i would of inserted commands to link / unlink latest kernel versions. it was setup to evade problems that easily occur with the configuration files, and auto complete linking complex kernel names with version numbers while keeping it simple in the config files. i try to keep my wiki entries as close to sutras as possible, because they work for me. step 1 do this step 2 do this step 3 do this... extend option 1, option 2, option 3....  intro step explanation with step hidden in between verbosity doesn't work well for me, ill skim right past the step and be back at square 1. thanks again =D 666threesixes666 (talk) 05:39, 22 December 2013 (UTC)

Small question about File template
Hi!

You add double whitespace in empty line inside File template (/etc/conf.d/cpufrequtils in AMD64/FAQ article) with reason “to keep translation blocks together”. But without these whitespaces block still together, and if you copy-paste config it will not contail leading spaces. Maybe you confused with markdowd syntax?

--Totktonada (talk) 18:48, 1 April 2014 (UTC)


 * The spaces in the block shouldn't hurt copy/paste. However, the spaces are needed because otherwise the wiki translation plugin will mark the top part of the listing as one block, and the bottom part of another. This then breaks wiki syntax, because the pre-start and pre-end are needed in a single block, making translations impossible (as the translation plugin itself will detect the breakage and refuse translation of "half" blocks) --SwifT (talk) 18:53, 1 April 2014 (UTC)


 * Spaces at end of line (even if line contain only spaces) looks like bad thing. Copyed from rendered article to a file text includes this spaces. But if this is workaround for translation plugin, then I agree with necessarity of this approach. --Totktonada (talk) 19:16, 1 April 2014 (UTC)

REQUEST ENABLE TRANSLATION
Hi!

Please, enable translation for these pages: I can't get the link for do that. I can't editing neither.
 * Handbook:MIPS/Full/Installation
 * Handbook:PPC64/Full/Installation
 * Handbook:SPARC/Full/Installation
 * Handbook:X86/Full/Installation

Quilosaq (talk) 18:26, 21 December 2014 (UTC)