summaryrefslogtreecommitdiff
path: root/po/zh_CN.po
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.6~alpha11.6_alpha1Julian Andres Klode2017-10-231-2/+2
|
* zh_CN.po: Update Simplified Chinese programs translationMo Zhou2017-10-081-6/+6
|
* Release 1.51.5Julian Andres Klode2017-09-241-1/+4
|
* Release 1.5~rc21.5_rc2Julian Andres Klode2017-09-091-4/+5
|
* Release 1.5~beta21.5_beta2Julian Andres Klode2017-08-171-23/+34
|
* Merge pull request Debian/apt#44 from willismonroe/patch-1Julian Andres Klode2017-07-171-1/+1
|\ | | | | | | | | | | Minor grammar fix [jak@d.o: Fixed up po/]
* | zh_CN.po: update Simplified Chinese programs translationZhou Mo2017-07-041-19/+16
| |
* | Release 1.5~beta11.5_beta1Julian Andres Klode2017-07-031-2/+2
| |
* | Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode2017-06-281-13/+61
|/
* Release 1.4~rc11.4_rc1Julian Andres Klode2017-02-061-9/+9
|
* po: update Simplified Chinese program translationZhou Mo2017-01-261-8/+5
|
* Release 1.4~beta31.4_beta3Julian Andres Klode2017-01-051-48/+48
|
* expand -f to --fix-broken in error messagesDavid Kalnischkies2016-12-311-23/+23
| | | | | | | | | | | | | | | | | | | | Users end up believing that this is a --force mode as -f is common for that, but apt doesn't have such a mode and --fix-broken is really not about forcing something but actually trying to fix the breakage which tends to be the result of a user forcing something on its system via low-level forced dpkg calls. Example: The "common" pattern of "dpkg -i ./foo.deb; apt install -f" is nowadays far better dealt with via "apt install ./foo.deb". And while at it the two places handing out this suggestion are changed to use the same strings to avoid needless translation work in the future and the suggestion uses 'apt' instead of 'apt-get' as this will be run interactively by a user, so its a good opportunity to showcase what we can do and will allow us to be more helpful to the user. Closes: #709092 Thanks: Kristian Glass for initial patch!
* Release 1.4~beta11.4_beta1Julian Andres Klode2016-11-251-1/+3
|
* Release 1.3~rc31.3_rc3Julian Andres Klode2016-08-301-1/+2
|
* zh_CN.po: update simplified Chinese translationZhou Mo2016-08-201-23/+18
|
* Release 1.3~rc21.3_rc2Julian Andres Klode2016-08-171-5/+5
|
* Release 1.3~rc11.3_rc1Julian Andres Klode2016-08-111-1872/+1887
| | | | | | | | This commit looks heavy. Most of that comes from the fact that the ordering of files in the translations changed with the switch to CMake. I could have gone the extra mile to figure out the original ordering and replicate it, but I have chosen to re-order everything by file and line number, as that's easier.
* Release 1.3~pre31.3_pre3Julian Andres Klode2016-08-041-11/+45
|
* zh_CN.po: update simplified chinese translationZhou Mo2016-06-271-6/+6
|
* show right binary name in simulation noticeDavid Kalnischkies2016-06-231-5/+7
| | | | Closes: 825216
* Release 1.3~exp31.3_exp3Julian Andres Klode2016-06-221-30/+38
| | | | Quite a huge churn of new strings.
* zh_CN.po: update simplified chinese translationZhou Mo2016-06-211-3/+7
|
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-111-7/+21
|
* zh_CN.po: update simplified Chinese translation.Zhou Mo2016-05-141-2/+2
|
* Release 1.3~exp11.3_exp1Julian Andres Klode2016-05-111-25/+29
|
* support Signed-By in Release files as a sort of HPKPDavid Kalnischkies2016-05-011-7/+2
| | | | | | | | | | | | Users have the option since apt >= 1.1 to enforce that a Release file is signed with specific key(s) either via keyring filename or fingerprints. This commit adds an entry with the same name and value (except that it doesn't accept filenames for obvious reasons) to the Release file so that the repository owner can set a default value for this setting effecting the *next* Release file, not the current one, which provides a functionality similar "HTTP Public Key Pinning". The pinning is in effect as long as the (then old) Release file is considered valid, but it is also ignored if the Release file has no Valid-Until at all.
* drop empty line from fetch errorDavid Kalnischkies2016-04-251-8/+3
| | | | | | | | This is a duplicate of sorts of 0efb29eb36184bbe6de7b1013d1898796d94b171 which is the a lot more frequent case of this error – and also a duplicate of this error message, just without the \n at the end. Git-Dch: Ignore
* Release 1.2.111.2.11Julian Andres Klode2016-04-251-1/+1
|
* zh_CN.po: update simplified Chinese translation. (100%)Zhou Mo2016-03-271-4/+4
|
* drop confusing comma from no strong hash messageDavid Kalnischkies2016-03-251-2/+2
|
* Release 1.2.81.2.8Julian Andres Klode2016-03-241-15/+14
|
* zh_CN.po: update simplified Chinese translation. (Closes: #818639)Zhou Mo2016-03-191-4/+4
| | | | | 100% translated. Note: this commit contains a message from the future. #818639
* zh_CN.po: update simplified chinese translation.Zhou Mo2016-03-191-39/+41
| | | | Note, 0 untran, 1 fuzzy, and the fuzzy string remains at Bug#818639.
* Release 1.2.71.2.7Julian Andres Klode2016-03-151-1/+7
|
* zh_CN.po: fix translation bug. (Closes: #818177)Zhou Mo2016-03-151-1/+1
|
* Release 1.2.31.2.3Julian Andres Klode2016-02-101-75/+63
| | | | | Build system messed up the 1.2.2 commit by not updating the .po files properly, so they are now.
* Release 1.2.11.2.1Julian Andres Klode2016-01-251-8/+6
|
* po: update zh_CN programs translationZhou Mo2016-01-221-56/+62
|
* Release 1.21.2Julian Andres Klode2016-01-151-14/+11
|
* po: update simplified chinese programs translationZhou Mo2016-01-151-76/+83
|
* Release 1.2~exp11.2_exp1Julian Andres Klode2016-01-081-13/+18
|
* Release 1.1.101.1.10Julian Andres Klode2015-12-301-5/+6
|
* Release 1.1.91.1.9Julian Andres Klode2015-12-271-1/+6
|
* 1.1.6 Christmas releaseJulian Andres Klode2015-12-241-9/+9
|
* Release 1.1.51.1.5Julian Andres Klode2015-12-141-6/+20
|
* Release 1.1.41.1.4Julian Andres Klode2015-12-071-34/+34
|
* release 1.1.31.1.3Michael Vogt2015-11-301-105/+105
| | | | Git-dch: ignore
* Release 1.1.21.1.2Julian Andres Klode2015-11-281-1/+6
|
* Run ./prepare-release pre-exportMichael Vogt2015-11-251-44/+43
|
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-05 08:30:13 +0000