| Summary: | sys-apps/portage: russian translation of manpages | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Vladimir Romanov (RETIRED) <blueboar> |
| Component: | Documentation | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | mva, pinkbyte, totktonada.ru |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=420577 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild(1) man page
ebuild(1) man page env-update.1 ebuild.1 env-update.1 fixpackages.1 etc-update.1 etc-update.1 english ebuild.5 english ebuild.1 english env-update.1 english ebuild.1 apply changes to russian version also env-update.1 add changes to russian version also ebuild.1.diff apply changes to russian version also env-update.1.diff apply changes to russian version also diff to english dispatch-conf man page Russian translation of dispatch-conf man page color.map.5 russian Ebuild.1 diff |
||
|
Description
Vladimir Romanov (RETIRED)
2013-01-05 12:46:34 UTC
File separate bugs each package (equery/gentoolkit and eselect are not part of sys-apps/portage). For sys-apps/portage, you can attach the man pages to this bug, and we'll add them to a man/ru directory like suggested in bug #420577, comment #2. You can find the latest english versions of the man pages here: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=tree;f=man;hb=refs/heads/master and feel free to poke some russian gentoo devs[1] to double-check your work. [1] maksbotan pinkbyte tetromino Thanks. I think, this will be not fast, so you can close this bug (i will open another when complete). About double-checking - yes, i know this, i translate handbook, and they're checking all for 2-3 weeks :D And one more question - at link http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=tree;f=man;hb=refs/heads/master, portage.5, in page http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d9fc4acc572c6647a4f27b838d35d27d805d190e (very first commit to git) written "Migration (without history) of the current stable line to subversion. svn path=/main/branches/2.0/; revision=1941" Is that svn still can be found somewhere? I want to see this 1941 revisions... I can't believe, it all was simply deleted. The main repository is located at <uri>svn+ssh://cvs.gentoo.org/var/svnroot/portage/main</uri>, please note that it is subject to strict access controls, only people listed in the developers section on this page are able to commit to it.</p> :(. So, i can't view it anyhow? Hmm... it seems, first portage man is here http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-src/portage/man/portage.5?hideattic=1&view=log - from very beginning. But then... why migration to subversion... why 1941?! Or... it being CVS initially (sources.gentoo.org), then is was moved to SVN (without history), and then it was moved to GIT, but with history from SVN? git history goes back to 2005: commit d9fc4acc572c6647a4f27b838d35d27d805d190e Author: Jason Stubbs <jstubbs@gentoo.org> Date: Sun Aug 28 08:37:44 2005 +0000 Migration (without history) of the current stable line to subversion. svn path=/main/branches/2.0/; revision=1941 Yes. To 2005. Where history BEFORE 2005? It can be seen in CVS, but comment in GIT (2005) said 'move to... subversion'? "Migration (without history)" So your own conclusion was right: "Or... it being CVS initially (sources.gentoo.org), then is was moved to SVN (without history), and then it was moved to GIT, but with history from SVN?" Thanks. Bug can be closed. Created attachment 335352 [details]
ebuild(1) man page
Here is first translated man-page. Please check it and make a decision - is it worth continue?
(In reply to comment #11) It looks good to me, but I don't understand Russian. If you want to continue, then I'll commit and release it. Yes, i want to continue, and i want you to commit it. I will be glad, if anyone can check it, but if it can't be done... well, if you may commit, commit it Okay, I'll commit it. Should it go in man/ru, man/ru_RU.UTF-8, or what? I'm not really familiar with how the man page locales work, but your man page does appear to be UTF-8 encoded. Well, i have it simply in man/ru, and it works. But i don't know, if this is right way. But, yes, it is UTF-8 encoded. ebuild manpage translation looks good and up-to-date (In reply to comment #15) > Well, i have it simply in man/ru, and it works. But i don't know, if this is > right way. Okay, we'll go with man/ru. I've committed it with after doing sed 's: $::' to remove trailing spaces: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=15ec6256f3156b241346d2bc25970ec44ee43d3e (In reply to comment #17) > ebuild manpage translation looks good and up-to-date Thanks for reviewing it. In portage-2.1.11.41 and 2.2.0_alpha152, with USE=linguas_ru, /usr/share/man/ru/man1/ebuild.1.bz2 is installed. Will continue translating then By the way, why ebuild(1) man page contains references only to md5-sum, md5-digest, and so on? Isn't is SHA and WHIRLPOOL now? (In reply to comment #21) Yes, I've updated the english version: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a8d775aeb0256e8fbde687ea44749b81bfd2b509 Heh :). Now i need to change the translation also. I suggest to don't use verbal translations. I bet, that it is better to repeat "низкоуровневый" (low-level), used in NAME section, that using crappy "прямой" (which commonly causes to think "straight", than "direct", used in orignal man). Also. DO NOT USE PLURAL on portage!! And it'd be better to do not translate it ever. When I read "портежей" (<smth> of portages) I want to kill the author! IMHO. Anyway, I'd wait for your update (that you men in last comment) of translation file and then try to fix such cases, if nobody has objections ;) Created attachment 335814 [details]
ebuild(1) man page
Updated man page, removed "портежей". Don't know, how i miss this.
Please, don't kill the translator, i do, what i can :D Thanks, committed: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=01b3e21f2f0df390ec64e88a3dc5de4f124dc8b5 Sad, i forgot to change Dec 2012 to Jan 2013. I think, it is not a big error? Will continue now to translate ebuild(5) I don't worry about the date headers. I often forget to update them too. In env-update.1 in first paragraph, env-update first encountered in bold (\fBenv-update\fR), then in italic (\fIenv-update\fR). What standards say about this? And, then in options ldconfig and ld.so is not in bold or italic. And, finally, "ld.so cache", need to be "ld.so.cache" Also, .SH (such as NAME, SYNOPSIS, DESCRIPTION, etc...) in ebuild.1 is in quotes ("DESCRIPTION", "SYNOPSIS"), but in env-update.1 AUTHORS, OPTIONS, SYNOPSIS and DESCRIPTION are not in quotes (by the way, OPTIONS in ebuild.1 also not quoted)
Created attachment 337012 [details]
env-update.1
Created attachment 337014 [details]
ebuild.1
Added forgotten .fi at end
Created attachment 337016 [details]
env-update.1
Changed a little
Created attachment 337018 [details]
fixpackages.1
By the way, from the man page of fixpackages i can't even determine, what it is do. I think, this man page need to be seriously reworked - it is only 2-3 lines now. Same for etc-update man page. It is written "etc-update will prompt user for decision", but there is no explanation about what decisions can be, what user need to press, what he can expect. In etc-update.1, in NAME SECTION etc-update \- handle configuration file updates second \- is escaped, but - in etc-update is not escaped By the way, dash in etc-update is not escaped all through the text of man page Also, in etc-update.1, each etc-update is on separate line, such as .I etc-update But for italic is much better just enquote etc-update such as \fIetc\-update\fR, and there is no need to start new line each time In env-update, automode option, -3, -5, -7, -9 need to be "quoted" \-3, \-5, \-7, \-9 Created attachment 337020 [details]
etc-update.1
In ebuild.5 at the end, in EXAMPLES, Copyright 1999-2009 Gentoo Foundation need to be changed to 2013 Em... i just went out of man directory in git and went to doc dir. Is that docbook can be translated also? Thanks, all of your attachments are now in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=512452ad3a8081d81f0eab279d119db98e52bc5c (In reply to comment #30) > In env-update.1 in first paragraph, env-update first encountered in bold > (\fBenv-update\fR), then in italic (\fIenv-update\fR). What standards say > about this? I think we should be using bold for all command names. I don't know about standards. (In reply to comment #31, comment #32, etc...) > And, then in options ldconfig and ld.so is not in bold or italic. And, > finally, "ld.so cache", need to be "ld.so.cache" Please feel free to submit patches to the English man pages. (In reply to comment #44) > Em... i just went out of man directory in git and went to doc dir. Is that > docbook can be translated also? It could, but I don't know if it's worth the effort. Do i need to open new bugs for english manpages, or may i put it here? You may put them here. Created attachment 337316 [details]
etc-update.1 english
Created attachment 337318 [details]
ebuild.5 english
May be other errors exists here, will check carefully later
Created attachment 337320 [details]
ebuild.1 english
Created attachment 337322 [details]
env-update.1 english
This is fixes for english manpages. If this will be comitted, will update Russian accordingly Thanks, your changes are in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=39786370fe836cdedac653cc6d0e0de48b88e8b4 I forgot to commit your ebuild.5 change in the first commit. Here it is now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=66f2f2df36df6fc7b2702694e7bddd56d0149051 It will be easier if you submit your changes in unified diff format. If you just want to use diff on two separate folders, you can use a command like this: diff -Nur man.orig man > man.diff Or clone the git repo and use git. The git repo URL is displayed on the gitweb summary page: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=summary By the way, what's the difference between "doc-other/portage documentation" area and this - "portage development/documentation"? (In reply to comment #56) > By the way, what's the difference between "doc-other/portage documentation" > area and this - "portage development/documentation"? I am not part of GDP, but i think so: doc-other/portage documentation - documentation on gentoo.org site about portage portage development/documentation - documentation that's a part of sys-apps/portage package(manpages in /usr/share/man, doc entries in /usr/share/doc, etc.) Created attachment 339120 [details]
ebuild.1 apply changes to russian version also
Created attachment 339122 [details]
env-update.1 add changes to russian version also
Sorry, can't apply diff, as cvs update does not working (shows 'cvs [update aborted]: end of file from server (consult above messages if any) Em... Sorry. I forgot, that man pages in GIT, not in CVS. Will add diffs now Created attachment 339124 [details]
ebuild.1.diff apply changes to russian version also
Created attachment 339126 [details]
env-update.1.diff apply changes to russian version also
Em... Why are my attachments made obsolete? (In reply to comment #64) > Em... Why are my attachments made obsolete? It looks like there was an upgrade or config change for our bugzilla, and it just displays things differently. It shows that you marked obsolete the attachments from comment #58 and comment #59, which was intended, since you attached the corresponding diffs in comment #62 and comment #63. I've applied the diffs now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cb194e041de0c63281e23c802dd42cda4bfbd44 http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=44274bd7ee71a2de0d62d0a73c963c23a56bac6a Created attachment 346096 [details]
diff to english dispatch-conf man page
Created attachment 346098 [details]
Russian translation of dispatch-conf man page
Thanks, you changes are now in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=45e0fa1f556eaf66678a4f78ed003d3f8cfb892a http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9993992fc36839fa0eec60b8750b614e819c3f1c Created attachment 351820 [details]
color.map.5 russian
(In reply to Vladimir from comment #69) > Created attachment 351820 [details] > color.map.5 russian Thanks, this is in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d64259b25757f0564aecaaba78f0591190c1e0d4 Sorry for so long delay. Here is updated ebuild.1 man page Created attachment 366840 [details, diff]
Ebuild.1 diff
Thank you. Applied in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=8fa39c6cc49cfabfae41225a6228c6f34cd18903 If possible, please use git format-patch from the base portage directory of the checkout. I had to edit the patch to adjust the path. There was also a couple whitespace errors that it introduced. Both easy fixes. Thank you again. Bug status is outdated Vladimir, as you have commit rights for quite long time, please clarify if we should close this No, no, no, don't close this. I will translate something in december/february. And i don't have rights to do this by myself, as this is in GIT, and i have right to SVN only |