summaryrefslogtreecommitdiff
path: root/po/fi.po
AgeCommit message (Collapse)Author
2015-11-25Run ./prepare-release pre-exportMichael Vogt
2015-11-21review of new/changed translatable program stringsJustin B Rye
Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
2015-11-04revamp all tools help messagesDavid Kalnischkies
The general idea is: A small paragraph on the tool itself as a description, a list of the most used (!= all) commands available in the tool, a remark where to find more information on the tool and its commands (aka: in the manpage) and finally a common block referring to even more manpages. In exchange options are completely omitted from the output as well as deprecated or obscure commands. (Better) Information about them is available in the manpages anyway and the few options which were listed before were also the least interesting ones (-o -c -q and co are hardly of interest for someone totally new looking to find info by asking for help and anyone with a bit of experience doesn't need this short list. Those would need a list of options applying to the command they call, but they are too numerous and command specific to list them sanely in this context.
2015-11-04split up help messages for simpler reuseDavid Kalnischkies
That is one huge commit with busy work only: Help messages used to be one big translateable string, which is a pain for translators and hard to reuse for us. This change there 'explodes' this single string into new string for each documented string trying hard to split up the translated messages as well. This actually restores many translations as previously adding a single command made all of the bug message fuzzy. The splitup also highlighted that its easy to forget a line, duplicate one and similar stuff. Git-Dch: Ignore
2015-11-04suggest 'apt autoremove' to get right of unneeded packagesDavid Kalnischkies
The bugreport is more conservative in asking for a conditional, but given that this is a message intended to be read by users to be run by users we should suggest using a command intended to be used by users. And while we are at, add sudo to the message – conditional of course. Closes: 801571
2015-10-05Run "./prepare-release pre-export"Michael Vogt
Git-dch: ignore
2015-09-14implement apt-get source msg 'Please use: $vcs' for gitDavid Kalnischkies
A bit unfair that only Bzr had this message. Lets at least print it for git as well with the option of adding more later without string changes.
2015-09-11releasing package apt version 1.1~exp121.1.exp12Michael Vogt
2015-08-27Release 1.11~exp111.1.exp11Julian Andres Klode
2015-08-24releasing package apt version 1.1~exp101.1.exp10Michael Vogt
2015-08-10implement a more generic ShowList methodDavid Kalnischkies
apt-get is displaying various lists of package names, which until now it was building as a string before passing it to ShowList, which inserted linebreaks at fitting points and showed a title if needed, but it never really understood what it was working with. With the help of C++11 the new generic knows not only what it works with, but generates the list on the fly rather than asking for it and potentially discarding parts of the input (= the non-default verbose display). It also doubles as a test for how usable the CacheSets are with C++11. (Not all callers are adapted yet.) Git-Dch: Ignore
2015-06-15show item ID in Hit, Ign and Err lines as wellDavid Kalnischkies
Again, consistency is the main sellingpoint here, but this way it is now also easier to explain that some files move through different stages and lines are printed for them hence multiple times: That is a bit hard to believe if the number is changing all the time, but now that it keeps consistent.
2015-03-16properly implement pkgRecord::Parser for *.deb filesDavid Kalnischkies
Implementing FileName() works for most cases for us, but other frontends might need more and even for us its not very stable as the normal Jump() implementation is pretty bad on a deb file and produce errors on its own at times. So, replacing this makeshift with a complete implementation by mostly just shuffling code around.
2015-03-16merge debian/sid into debian/experimentalDavid Kalnischkies
2015-01-16prepare 1.0.9.61.0.9.6Michael Vogt
2014-12-23release 1.0.9.51.0.9.5David Kalnischkies
2014-12-03release 1.0.9.41.0.9.4David Kalnischkies
2014-11-06Run ./prepare-release pre-exportMichael Vogt
Git-dch: ignore
2014-09-27correct the error messages to refer to apt-key instead of gpgvDavid Kalnischkies
Git-Dch: Ignore
2014-09-27fix progress output for (dist-)upgrade calculationDavid Kalnischkies
Previously, we had a start and a done of the calculation printed by higher-level code, but this got intermixed by progress reporting from an external solver or the output of autoremove code… The higherlevel code is now only responsible for instantiating a progress object of its choosing (if it wants progress after all) and the rest will be handled by the upgrade code. Either it is used to show the progress of the external solver or the internal solver will give some hints about its overall progress. The later isn't really a proper progress as it will jump forward after each substep, but that is at least a bit better than before without any progress indication. Fixes also the 'strange' non-display of this progress line in -q=1, while all others are shown, which is reflected by all testcase changes.
2014-09-09prepare 1.0.81.0.8Michael Vogt
2014-08-28releasing 1.0.71.0.7Michael Vogt
2014-07-10prepare 1.0.6Michael Vogt
2014-06-18releasing package apt version 1.0.51.0.5Michael Vogt
2014-06-10really release 1.0.41.0.4Michael Vogt
2014-06-10release 1.0.4Michael Vogt
2014-05-05prepare release 1.0.31.0.3Michael Vogt
2014-04-25prepare release 1.0.21.0.2Michael Vogt
2014-04-10prepare 1.0.1 release1.0.1Michael Vogt
2014-04-01releasing package apt version 1.01.0Michael Vogt
2014-04-01prepare releaseMichael Vogt
2014-04-01refresh po/pot and unfuzzy apt-extracttemplate changeMichael Vogt
2014-03-15Release 0.9.16.10.9.16.1Julian Andres Klode
2014-03-14prepare 0.9.16 release0.9.16Michael Vogt
2014-03-13msgstr with elipses need three dotsDavid Kalnischkies
fixes some messages and their translation so that all of them have three dots for messages with an elipse. Many translations already had this.
2014-02-28releasing package apt version 0.9.15.50.9.15.5Michael Vogt
2014-02-23releasing package apt version 0.9.15.40.9.15.4Michael Vogt
2014-02-20releasing package apt version 0.9.15.3Michael Vogt
2014-02-13releasing package apt version 0.9.15.20.9.15.2Michael Vogt
2014-02-06releasing package apt version 0.9.15.1Michael Vogt
2014-01-25releasing package apt version 0.9.150.9.15Michael Vogt
2014-01-24releasing package apt version 0.9.14.3~exp50.9.14.3.exp5Michael Vogt
2014-01-24make update-poMichael Vogt
2014-01-22releasing package apt version 0.9.14.3~exp4Michael Vogt
2014-01-18releasing package apt version 0.9.14.3~exp30.9.14.3.exp3Michael Vogt
2014-01-05prepare 0.9.14.3~exp10.9.14.3.exp1Michael Vogt
2013-12-29prepare release0.9.14.2Michael Vogt
2013-12-12releasing package apt version 0.9.14.1Michael Vogt
2013-12-07really release 0.9.140.9.14Michael Vogt
2013-08-01unset LANGUAGE for showing [Y/n] answer hintsDavid Kalnischkies
nl_langinfo is used to acquire the YESEXPR of the language used, but it will return the one from LC_MESSAGES, which might be different from the language chosen for display of the question (based on LANGUAGE) so this commit removes the [Y/n] help text from the questions itself and moves it to the prompt creation in which the usage of LC_MESSAGES is forced for it, so that the helptext shown actually represents the characters accepted as input for the question. There is still room for problems of course starting with an untranslated "[Y/n]" but a translated YESEXPR or the problem that the question is asked in a completely different language which might have a conflicting definition of [Y/n] input or the user simple ignores the helptext and assumes that an answer matching the question language is accepted, but the mayority of users will never have this problem to begin with, so we should be fine (or at least a bit finer than before). Closes nothing really, but should at least help a bit with bugs like deb:194614, deb:471102, lp:1205578, and countless others.