Re: Failed pipeline for latest | debian-reference | 51c0df57

[Beatrice Torracca]

Hi again!

On 04/12/21 19:01, Beatrice Torracca wrote:

Hi everyone!

I received the following message from Salsa (I obfuscate my email 
address and name in the text).


On 04/12/21 12:43, Debian GitLab wrote:

✖ Pipeline #323842 has failed!



I think it was because I used a URL with "%" signs. If it is for that, I 
see Xiao already fixed the problem; so my thanks to Xiao.



Good weekend,


beatrice

Re: Failed pipeline for latest | debian-reference | 51c0df57

[Beatrice Torracca]

Hi everyone!

I received the following message from Salsa (I obfuscate my email 
address and name in the text).


On 04/12/21 12:43, Debian GitLab wrote:

✖   Pipeline #323842 has failed!

Project 	Debian  / debian-reference 


Branch  
latest 


Commit  
	51c0df57 
 



Partial update of the Italian translation
Commit Author   

[snip my name]

Pipeline #323842 
 
triggered by 		< my name and salsa ID>


had 1 failed build.
Failed builds
✖   test

	html-tests 



I have no idea if it is because I tried the command "make test" as 
suggested in the readme or if my translation has errors.


It is the first time that I receive something like this.

I can of course revert the commit if there is a problem with my partial 
Update of the Italian translation.


Sadly trying to build locally it is very difficult for me with all the 
entities declarations missing, and I never managed to make it work 
properly to see the document build.


Thanks,

beatrice

Re: I took liberty to update po for debian-faq

[Beatrice Torracca]

On venerdì 15 marzo 2019, at 18:45 +0100, Holger Wansing wrote:
> Hi,

Hi,

> 
> Today I committed a French translation update from 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920492
> 
> However, this translation seems outdated as Beatrice mentions above.
> When I now call "make update-po", all po files (!) are changed again because
> of changings like this:
> 
> 
> @@ -3185,7 +3185,7 @@ msgid ""
>  "management system (dpkg) will send an error message that it also needs "
>  "binutils, and stop installing "
>  "gcc. (However, this facility can be overridden by the "
> -"insistent user, see .) See more in  "
> +"insistent user, see .) See more in  "
>  "id=\"depends\"> below."

In the past when I saw that with make update-po all the resulting
changes were like the one you mention, I just reverted the
changes. With my first update-po, at least for Italian, there were
some real "updates" with new messages and changed messages, not only
this kind of changes with just a different order of the items in the
tags.

After all, you only need one "make update-po" after some changes in the
original text. Then you won't need to run it again until the original
text changes. But, yes, it is an annoying problem.

> Means the "section=xxx" and "name=yyy" parts within  are swapped,
> leading to 18 fuzzy strings :-((
> 
> I remember such issue from years ago. But is this still an unfixed issue?
> 
> This way we cannot get the translations up-to-date, h ...
> 
> Is this known? How to deal with this?

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725931

Anyway as far as I can see, the proposed work around is already implemented
in the Makefile of the faq that already contains "PERL_PERTURB_KEYS=0
PERL_HASH_SEED=0".

> Beatrice: which Debian version are you using? I wonder if the tools in Debian
> unstable behave different from those in Debian stable (I'm trying to explain,
> what happens here).
> I am using Debian stable.

I am using testing.

Ciao,

beatrice

Re: I took liberty to update po for debian-faq

[Beatrice Torracca]

Hi,

> > In case I made the wrong move, please tell me if I should not do this
> > again, or if I need to revert the changes (or keep them only for
> > Italian).
> 
> It looks fine to me; thanks!  I've just recorded your commit in a new entry 
> for
> debian/changelog.

So now that I have updated the Italian translation, can I simply commit that or 
should I make a record in debian/changelog. (I am inclined to think only 
maintainer should touch the debian/changelog file).

Thanks,

beatrice

I took liberty to update po for debian-faq

[Beatrice Torracca]

Hi!

In the debian-faq repo the original version has been updated several
times, but the .pot and .po files (and the corresponding translations,
I imagine) were stuck at 2017 (IIRC).
 
Having commit rights on salsa for my translation work, I took the
liberty to update the po files ("make update-po"). As a result several
.po files are to be updated: de, fr, it, ja, nl, ru, zh_CN.

In case I made the wrong move, please tell me if I should not do this
again, or if I need to revert the changes (or keep them only for
Italian).

Thanks,

beatrice


signature.asc
Description: PGP signature

Re: [Debian-Reference] Updating po translations of Debian Reference - correct work flow?

[Beatrice Torracca]

On venerdì 22 settembre 2017, at 08:47 +0200, Holger Wansing wrote:
> > My doubt is that in this process I get lots of messages about unused
> > Entities. Messages like this one:
> > 
> > debian-reference.en.xml:17278: parser error : Entity 'freetype' not defined
> >   FreeType 2.0 font 
> > rasteriza
> >^
> 
> I don't see such messages here when testing your translation. Italian builds
> fine and without errors.
> Also when looking at your latest commit
> https://anonscm.debian.org/cgit/ddp/debian-reference.git/commit/?id=14c4a31705c521825c1250b2d0b41b0f770db7c8
> everything looks fine. There are no messages deleted from the po files or
> the like.
> 
> If you still see such messages on your PC, I suspect there might be some 
> software missing? The toolchain to build such documents is rather ambitious
> sometimes...
> 'apt-get build-dep debian-reference' should install everything that's needed,
> or look at https://packages.debian.org/source/stretch/debian-reference

Hi,

thanks for your reply.

I did install dctrl-tools that I was missing; that seemed to have helped thanks.

Those messages were removed from the file I committed locally.

> > Right now I committed my last translation after the make wrap / make
> > test commands, but if I don't get any comment I will revert that
> > commit.
> 
> No need for such reverting.

Sorry, I should make more clear that I committed the file but I did
not push the commit in the Debian git repo. So I reverted it locally.

thanks for the help,

beatrice

Re: [Debian-Reference] Updating po translations of Debian Reference - correct work flow?

[Beatrice Torracca]

On venerdì 22 settembre 2017, at 09:21 +0800, atzlinux wrote:
>     On my notebook, git pull the newest version,I use "make test
> LANGPO=it" ,it can compile the it html success,no any errors display.
> 
> Can you try "make distclean",then "make test LANGPO=it" ?

Hi!

thanks for the reply. I tried that.

Now I don't get all those errors but I have a different message:


sed -e 's/@-@amp@-@/\&/g' -e 's/@-@\([^@]\+\)@-@/\&\1;/g' > 
debian-reference.en.xml
 You are missing ENTITY files ***
datadatepop.ent datadatesize.ent popcon.ent pkgsize.ent
*
 run "make entity"
*
Makefile:171: set di istruzioni per l'obiettivo "datadatepop.ent" non riuscito
make: *** [datadatepop.ent] Errore 1

I will try the make entity command then ... I need to install some
packages for that so I have to wait. I will report the results :)

I found out another problem though.

The command "make dist clean" erased the temporary directory in my
home folder. ~/.tmp .

Not the content, the whole directory itself, which made other programs
start to complain or behaving badly since they were using the
temporary directory. I think the Makefile script could be corrected to
not delete the directory itself. Actually I think that even deleting
the whole content is bad enough, since some other program could have
stored some temporary valuable data there.

Maybe just not using $(TMPDIR) at all but just $(CURDIR)/tmp  ?

Thanks for the help,

beatrice.

[Debian-Reference] Updating po translations of Debian Reference - correct work flow?

[Beatrice Torracca]

Hi all!

I have a doubt about the proper way to update the translations of the
Debian Reference.

I followed the instructions in the README.sources and used

"make wrap" and "make test" to test my translation (recently Osamu had
to fix a syntax mistake in my translation and I would prefer to avoid
giving work to others and check my translation myself)

It looks though like the "make test" action also updates the po
files. Every po file, but that is not a problem because I can commit
only the Italian one.

My doubt is that in this process I get lots of messages about unused
Entities. Messages like this one:

debian-reference.en.xml:17278: parser error : Entity 'freetype' not defined
  FreeType 2.0 font rasteriza
   ^
   
and it looks to me like (almost) all messages related to entity
translations in the .po file become commented and unused.

I don't think this is what is supposed to happen.

I see there is also a "make entity" target. I am not sure that is
supposed to be used.

But mostly I am not sure what is the right .po file for me to
commit. The one before the make test action or the one I get
afterwards? I think that once the generation of the translation
documentation is carried out in the Debian server those entity
messages will turn out to be needed.

Right now I committed my last translation after the make wrap / make
test commands, but if I don't get any comment I will revert that
commit.

Thanks for any help or pointers,

beatrice

yay just wönderful

[Beatrice Torracca]

I föund sömething  really wönderful, it impressed me  a great deal,  it's 
really sömething  interesting. Take a peek here  
http://coopbeds.com/jump.php?UE9yZWZjYXJkQHBhY2thZ2VzLmRlYmlhbi5vcmc-

See you around, Beatrice Torracca


-

The content of the pages of this website is for your general information and 
use only. It is subject to change without notice. This website uses cookies to 
monitor browsing preferences. If you do allow cookies to be used, the following 
personal information may be stored by us for use by third parties.

Re: [Ddp-commits] [debian-reference] 50/50: Translated using Weblate (German)

[Beatrice Torracca]

HI,

as far as I understood, German too was one of those languages which
has the Debian-Reference already translated and for which the weblate
interface should be disabled. Maybe I am mistaken and Holger (in CC:)
which was the previous German translator can prove me wrong.

Thanks,

beatrice.

P.S.: resending this message for problems in delivery due to my
mistake in address, please forgive the noise if you get double
messages.

On venerdì 28 luglio 2017, at 05:20 +, Faris Xiao wrote:
> This is an automated email from the git hooks/post-receive script.
> 
> atzlinux-guest pushed a commit to branch master
> in repository debian-reference.
> 
> commit 4b7db268c4340a1450beadbf2f12926056c4fe54
> Author: ssantos 
> Date:   Thu Jul 27 23:00:26 2017 +
> 
> Translated using Weblate (German)
> 
> Currently translated at 100.0% (7642 of 7642 strings)
> ---
>  po/de.po | 34 --
>  1 file changed, 24 insertions(+), 10 deletions(-)
> 
> diff --git a/po/de.po b/po/de.po
> index a9f76d1..4738cc9 100644
> --- a/po/de.po
> +++ b/po/de.po
> @@ -9,15 +9,15 @@ msgid ""
>  msgstr ""
>  "Project-Id-Version: debian-reference v2\n"
>  "POT-Creation-Date: 2016-12-31 18:12+0900\n"
> -"PO-Revision-Date: 2016-12-26 00:35+0100\n"
> -"Last-Translator: Holger Wansing \n"
> +"PO-Revision-Date: 2017-07-27 23:00+\n"
> +"Last-Translator: ssantos \n"
>  "Language-Team: German \n"
>  "Language: de\n"
>  "MIME-Version: 1.0\n"
>  "Content-Type: text/plain; charset=UTF-8\n"
>  "Content-Transfer-Encoding: 8bit\n"
>  "Plural-Forms: nplurals=2; plural=n != 1;\n"
> -"X-Generator: Lokalize 1.5\n"
> +"X-Generator: Weblate 2.16-dev\n"
>  

Re: Installation guide is not updated in some languages

[Beatrice Torracca]

On sabato 10 giugno 2017, at 18:09 +0200, Cyril Brulebois wrote:
> 
> Given we're already building docs to ship in binary packages, it seems
> reasonable to re-use those build results on www-master indeed. There's
> maybe some history behind building it there but I'm not aware of it. So
> working on an update of the “build” process looks good to me. Any takers
> on the debian-boot side?
> 

Hi all,

isn't there also the fact that binary packages are created only so
often, while the sources in the VCS maybe more up-to-date?

Would not the documentation on the website be more up-to-date if they
were generated from the VCS sources?

I think I see something like that happening with the Debian FAQ that,
as far as I know, has the documentation online taken from the Debian
packages.

Hope I am not missing something obvious.

Thanks for the work on this,

beatrice



signature.asc
Description: PGP signature

Re: manpages.debian.org has been modernized!

[Beatrice Torracca]

On mercoledì 18 gennaio 2017, at 18:23 +0100, Michael Stapelberg wrote:

Hi!

> https://manpages.debian.org has been modernized! We have just launched
> a major update to our manpage repository. What used to be served via a
> CGI script is now a statically generated website, and therefore
> blazingly fast.

I tried a couple of "random" pages and indeed it was very fast.

> Furthermore, the design of the site has been updated and now includes
> navigation panels that allow quick access to the manpage in other
> Debian versions, other binary packages, other sections and other
> languages. Speaking of languages, the site serves manpages in all
> their available languages and respects your browser’s language when
> redirecting or following a cross-reference.

I like it a lot. Indeed it showed me the Italian version, but it was
very easy to switch to the English one.

> We’d love to hear your feedback and thoughts. Either contact us via an
> issue on https://github.com/Debian/debiman/issues/, or send an email
> to the debian-doc mailing list (see
> https://lists.debian.org/debian-doc/).

I am just writing to say thanks to all those who worked on this new
and improved manpages.debian.org. You did a very useful job.

Thanks,

beatrice

Re: Info request on how documentation is built for the website - FAQ example

[Beatrice Torracca]

On Sunday 05 June 2016, at 23:20 +0900, victory wrote:
> On Sun, 5 Jun 2016 15:00:32 +0200
> Beatrice Torracca wrote:
> 
> > In the past I had to try to understand part of this mechanism to try to
> > validate my translations or to move a translation from sgml to po, or
> > just for curiosity and to be able to be more involved in the process.
> 
> first, use your own system to test, do not try it on the server :)
> no real hardware needed for that :)

Yes, of course. :)

I did not mean that I wanted to test my translation on the server. I
never did that.

Still I need to know what "make" command to use on my system too if I
want to create the documentation locally and check that the translated
version compiles correctly.

Also if the translated version does not show on the website correctly it
is necessary to understand what is going wrong if I want to be able to help.

> > I imagine the top-level Makefile in the svn ddp repo gets called and
> > then the 7doc script in cron/parts of the debwww git repo should somehow
> > publish the doc online. But then what is going wrong here? Or am I
> > missing something obvious? (It might very well be because my
> > understanding of those scripts is very limited).
> 
> see SUBDIRS in the ddp's top level Makefile which you mentioned;
> it does not contain any "debian-faq"
> so the answer is:
> yes, you overlooked what the Makefile does;
> nothing on the server scripts was the factor

That is a starting point for me to understand, thanks. 

So I guess the webpages for debian-faq are gathered from the debian-faq
packages. 

> note: 7doc_manuals (not 7doc) handles svn versions
> 
> 7doc handles files in ftpdir/pool/ pulled from ftp, 
> which means it cares "packaged" manuals

OK, thanks again. debian-faq is indeed a packaged manual.

beatrice


signature.asc
Description: PGP signature

Info request on how documentation is built for the website - FAQ example

[Beatrice Torracca]

Hi all,

Since I work a lot on translations I would like to understand more how
the built system works to get the documentation from its sources in the
ddp repo to the webpages.

There are some things that I still can not understand. One very
stupid/simple example, using the Debian FAQ is this.
The sgml file is updated and correct (decision vs. decission).
The pot file is correct.
Both Italian and German translation are 100% completed in the po file.

But then you get this 3 pages:

English one with the mistake still present (last line of the question)
https://www.debian.org/doc/manuals/debian-faq/ch-ftparchives.en.html#s-codenames
 
German one with no sign at all of the sentence, and without some of the
codenames (no orgiginal version shown in their place)
https://www.debian.org/doc/manuals/debian-faq/ch-ftparchives.de.html#s-sourceforcodenames

Italian page with the sentence (with the mistake) and other codenames in
the original untranslated version.
https://www.debian.org/doc/manuals/debian-faq/ch-ftparchives.it.html#s-sourceforcodenames

The mistake was fixed in the repo the 15th of April.

In the past I had to try to understand part of this mechanism to try to
validate my translations or to move a translation from sgml to po, or
just for curiosity and to be able to be more involved in the process.

I imagine the top-level Makefile in the svn ddp repo gets called and
then the 7doc script in cron/parts of the debwww git repo should somehow
publish the doc online. But then what is going wrong here? Or am I
missing something obvious? (It might very well be because my
understanding of those scripts is very limited).

So I would be grateful if someone can explain me this, or point me to
some info, even if maybe it would be obvious for many of you.

Thanks,

beatrice


signature.asc
Description: PGP signature

Re: Last part of the proposed changes to debian-faq

[Beatrice Torracca]

On Saturday 04 June 2016, at 21:45 +0200, Holger Wansing wrote:

Hi!

I incorporated all the proposed corrections and suggestions in this
thread and I attach an updated version of my proposed patch.

I also updated the example of the flow of packages from unstable to
testing to reflect the 5 days waiting period (instead of the old 10 days
period).

Aside the discussed changes I modified one change I made in the
ftparchives.sgml file. In my first version I added the codenames of
jessie and stretch, but I did not notice that the question was: "What
OTHER codenames have been used?". Indeed jessie and stretch were
mentioned in the previous question.

So I now changed that paragraph to:
«Aside  and , other 
codenames that have been already used are: buzz for
release 1.1, rex for release 1.2, bo for releases 1.3.x,
hamm for release 2.0, slink for release 2.1,
potato for release 2.2, woody for release 3.0,
sarge for release 3.1, etch for release 4.0,
lenny for release 5.0,
squeeze for release 6.0, and
wheezy for release 7.»

Thanks,

beatrice
Index: basic_defs.sgml
===
--- basic_defs.sgml	(revisione 11198)
+++ basic_defs.sgml	(copia locale)
@@ -120,8 +120,9 @@
 information about the GNU/Hurd in general, and http://www.debian.org/ports/hurd/;>
 for more information about Debian GNU/Hurd.
 
-A second effort is the port to a BSD kernel.  People are working with both
-the NetBSD and the FreeBSD kernels.
+
+A second effort is the port to a BSD kernel.  People are working with
+  the FreeBSD kernels.
 
 See http://www.debian.org/ports/#nonlinux;> for more information
 about these non-linux ports.
Index: choosing.sgml
===
--- choosing.sgml	(revisione 11198)
+++ choosing.sgml	(copia locale)
@@ -29,7 +29,8 @@
 in. You can easily switch to the more modern unstable (or testing) once you are a little
 more confident.
 
-If you are a desktop user with a lot of experience in the operating system and does not mind
+If you are a desktop user with a lot of experience in the
+operating system and do not mind
 facing the odd bug now and then, or even full system breakage, use unstable. It has all the latest and
 greatest software, and bugs are usually fixed swiftly.
 
@@ -62,9 +63,9 @@
 even without subscribing. The archives can be read
 through http://lists.debian.org/debian-user/;>. Information regarding
 subscribing to the list can be found at the location of archives. You are
-strongly encouraged to post your questions on the mailing-list than on http://www.debian.org/support; name="irc">.  The mailing-list messages are
-archived, so solution to your problem can
+archived, so the solution to your problem can
 help others with the same issue. 
 
 Will there be different versions of packages in different distributions? 
@@ -89,7 +90,7 @@
 servers which have to work 24 hours a day, 7 days a week.
 
 On the other hand, packages in testing or unstable can have hidden bugs,
-security holes etc., Moreover, some packages in testing and unstable might not
+security holes etc. Moreover, some packages in testing and unstable might not
 be working as intended. Usually people working on a single desktop prefer
 having the latest and most modern set of packages. Unstable is the solution for
 this group of people.
@@ -109,13 +110,13 @@
 time and if you are real careful and if you know what you are doing,
 then it might be possible to go from unstable to testing and then to
 stable. The installer scripts are not designed to do that. So in the
-process, your configuration files might be lost and 
+process, your configuration files might be lost and...
 
 Could you tell me whether to install stable, testing or unstable?
 
 No, this is a rather subjective issue. There is no perfect answer
-as it depends on the software needed, the users' needs 
-and the experience of its system administrator. Here are some tips:
+as it depends on your software needs and
+your experience in system administration. Here are some tips:
 
 
 
@@ -160,14 +161,14 @@
 
 The bug fixes and improvements introduced in the unstable distribution
 trickle down to testing after a certain number of days. Let's say this
-threshold is 10 days. The packages in unstable go into testing only when there
+threshold is 5 days. The packages in unstable go into testing only when there
 are no RC-bugs reported against them. If there is a RC-bug filed against a
-package in unstable, it will not go into testing after the 10 days.
+package in unstable, it will not go into testing after the 5 days.
 
 The idea is that, if the package has any problems, it would be discovered by
 people using unstable and will be fixed before it enters testing.  This keeps
-the testing in an usable state for most period of the time.  Overall a
-brilliant concept, if you ask me. But things are always not so simple. Consider
+testing in a usable state for most of the time.  Overall a

Re: Last part of the proposed changes to debian-faq

[Beatrice Torracca]

On Saturday 04 June 2016, at 12:23 +0100, Justin B Rye wrote:

Hi!

thanks again for the corrections. I will apply them to my patch so that
I can suggest to Holger a cleaner patch.

> >  Could you tell me whether to install stable, testing or unstable?
> >  
> >  No, this is a rather subjective issue. There is no perfect answer
> >  as it depends on the software needed, the users' needs 
> > -and the experience of its system administrator. Here are some tips:
> > +and the experience of their system administrator. Here are some tips:
> >  
> 
> I'm not sure I follow this.  What "needs" does the user have (that
> Debian can help with) other than software?  Are we imagining the
> sysadmin as a different person from the user?  If so then that's who
> they should probably be asking for advice.  I suspect this may have
> been originally intended to mean:
> 
>No, this is a rather subjective issue. There is no perfect answer
>as it depends on your software needs and your experience in system
>administration. Here are some tips:
> 
> Or maybe:
> 
>No, this is a rather subjective issue. There is no perfect answer
>as it depends on your software needs, your willingness to deal with 
> possible
>breakage, and your experience in system administration. Here are some tips:

Yes, I imagined it was including the scenario where there are several users
and one sysadmin (even in a house PC there could be someone more PC-savy,
I guess) who of course would be the one asking the question.

I will use your first suggestion in my proposed patch and Holger or the
maintainer of the document can decide on this.

> > @@ -166,8 +167,8 @@
> >  
> >  The idea is that, if the package has any problems, it would be 
> > discovered by
> >  people using unstable and will be fixed before it enters testing.  This 
> > keeps
> > -the testing in an usable state for most period of the time.  Overall a
> > -brilliant concept, if you ask me. But things are always not so simple. 
> > Consider
> > +the testing in an usable state for most of the time.  Overall a
> 
> No article before the quasi-name "testing"; and "usable" begins with a
> consonant (you can't trust English orthography):
> 
>testing in a usable state for most of the time.  Overall a

True! I did not spot those errors. I imagine that the whole document
would benefit from an overall English review from a native speaker.

> > @@ -253,15 +254,15 @@
> >  After some time testing becomes frozen. But it will still be 
> > called
> >  testing. At this point no new packages from unstable can migrate to 
> > testing
> >  unless they include release-critical (RC) bug fixes.
> > -When testing is frozen, all the new bugfixes introduced, have to 
> > be
> > +When testing is frozen, all the new bugfixes introduced have to 
> > be
> >  manually checked by the members of the release team. This is done to 
> > ensure
> > -that there won't be any unknown severe problems in the frozen
> > +that there won't be any unknown severe problem in the frozen
> >  testing.
> 
> You've been changing "(not) any Xs" to "(not) any Y", enforcing a
> grammar rule that modern English speakers generally ignore.  Usually
> it does no harm,  but here it seems to me that it changes the sense
> from "it won't have whatever-sort-of errors" to "it will have
> absolutely no errors".  Keep it as
> 
>that there won't be any unknown severe problems in the frozen

I did not know that grammar rule was not used. Anyway I really thought it
wanted to say that it will try to guarantee that there will be zero
unknown severe problems.
I guess you never can be 100% sure, anyway

I will apply your correction, of course.

> [...]
> 
> >  linux system 'feels' etc., Knoppix is good for demonstration purposes while
>^
> Linux has a capital letter.  In these days of Linux-based Android
> devices I would prefer to credit the "feel" to "GNU/Linux".

On this (GNU/Linux) I will let others decide.


> > @@ -47,10 +47,9 @@
> >  
> >  
> >  The development of binary distributions of Debian for 
> > - >   >   > - > +and
> >   >  is currently underway.
> 
> Is it really?

I was as "conservative" as I could in my corrections on this, since I
have no first hand experience. I checked some Debian web pages. Those I
removed here I did remove because they are now included in the released
architectures or I added a note when I found it in the Release Notes.

The page https://www.debian.org/ports/ indeed says that avr32 (not
arv32 as it was spelled here) and m32 have been suspended/abandoned. Sh is
listed as currently underway. 

Looking at that page I could propose to change that paragraph to
«The development of binary distributions of Debian for hurd-i386 (for GNU
Hurd kernel on i386 32 bit PCs), mips64el (for 64 bit MIPS in
little-endian mode), or1k (for OpenRISC 1200 open source CPUs),
powerpcspe (port for the "Signal Processing Engine" hardware), sparc64
(for 64 bit SPARC processors), 

Re: More proposed changes to debian-faq

[Beatrice Torracca]

On Friday 03 June 2016, at 15:53 +0100, Justin B Rye wrote:

Hi,

> >  
> > +<
> >  The AAA component identifies the processor for which
> > -the package was built.  This is commonly i386, which refers to
> > -chips compatible to Intel's 386 or later versions.  For other
[snip]
 
> The content's good, but what's that extra "<"?

Something that slipped unintentionally. I will correct it.

> [...]
> > @@ -196,7 +200,7 @@
> >package foo once foo has been unpacked from its Debian
> >archive (".deb") file. Often, 'postinst' scripts ask the user for input,
> >and/or warn the user that if he accepts default values, he should 
> > remember
> > -  to go back and re-configure that package as the situation warrants.
> > +  to go back and re-configure that package as needed.
> >Many 'postinst' scripts then execute any commands necessary to start or
> >restart a service once a new package has been installed or upgraded.
> 
> I'd like to suggest a change to the start of that sentence:
> 
> Often, 'postinst' scripts ask users for input,
>  and/or warn them that if they accept default values, they should remember
>  to go back and re-configure that package as needed.
>   

I will incorporate this and your other suggestions/corrections in a new
patch, so that Holger can work on a cleaner patch.

> > @@ -275,7 +283,7 @@
> >  A virtual package is a generic name that applies to any one of a group
> >  of packages, all of which provide similar basic functionality. For example,
> >  both the tin and trn programs are news readers, and
> > -should therefore satisfy any dependency of a program that required a news
> > +should therefore satisfy any dependency of a program that requires a news
> >  reader on a system, in order to work or to be useful.
> >  They are therefore both said to provide the "virtual package" called
> >  news-reader.
> 
> Given that trn is non-free, I would suggest instead mentioning slrn or
> knews.  Or given that twentyfirst-century newbies may never have heard
> of USENET news groups, perhaps we should use a different example
> virtual package, such as "editor" or "www-browser".

OK. I will change the example to use www-browser and
konqueror/firefox-esr as packages.

> [...]
> > Index: redist.sgml
> > ===
> > --- redist.sgml (revisione 11198)
> > +++ redist.sgml (copia locale)
> > @@ -36,9 +36,9 @@
> >  
> >  Yes. Debian-derived distributions are being created both in close
> >  cooperation with the Debian project itself and by external parties.  One 
> > can
> > -use the http://cdd.alioth.debian.org/; name="Custom Debian
> > -Distributions"> framework to work together with Debian;  > -id="http://www.skolelinux.org/; name="Skolelinux"> is one such project.
> > +use the https://www.debian.org/blends/; name="Debian
> > +Pure Blends"> framework to work together with Debian;  > +id="https://wiki.debian.org/DebianEdu/; name="DebianEdu/Skolelinux"> is 
> > one such project.
> >  
> >  There are several other Debian-derived distributions already on the 
> > market,
> >  such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at 
> > a
>^^  
> "Progeny Linux" vanished nine years ago, and "Linspire" eight years
> ago.  Maybe Linux Mint and Raspbian?  Or grml?

based on the info in
https://www.debian.org/misc/children-distros.en.html, I will change my
proposal to "...such as grml, LMDE (Linux Mint Debian Edition), Knoppix
and Ubuntu..."

> [...]
> > @@ -168,11 +168,11 @@
> >  engine for newsgroups.
> >  
> >  For example, to find out what experiences people have had with
> > -finding drivers for Promise controllers under Debian, try searching on
> > +finding drivers for Promise controllers under Debian, try searching
> >  the phrase Promise Linux driver. This will show you all the
> > -postings that contain these strings, i.e. those where people discussed
> > +posts that contain these strings, i.e. those where people discussed
> >  these topics. If you add Debian to those search strings, 
> > you'll
> > -also get the postings specifically related to Debian.
> > +also get the posts specifically related to Debian.
> 
> This is distinctly cobwebby - when I ask Google I find ten-year-old
> books advising me that the best way to use Promise RAID controllers
> even then was to use the standard open-source drivers in the mainline
> kernel.
> 
> Plus, advising people to use Google Groups seems cruel.

"cobwebby" is a new word for me :)

maybe changing "Promise controllers" with NVIDIA graphic card? anyway I
don't think that the object of the search counts much, but rather the
suggestion on how to do the search.

As for the cruelty of suggesting Google Groups, I imagine Google Groups
(and USENET in general) are not as used today as they were in the
past. Still I think Google Groups indexes many newsgroups. I 

More proposed changes to debian-faq

[Beatrice Torracca]

Hi!

This is the second part of my proposed changes to debian-faq. Aside
minor changes in the English language (which probably need a review from
a native speaker) I changed some contents, specifically:

 - mention amd64 (and not i386) as the common architecture
 - I updated the example control file from the hello package (took it
   from stable)
 - In the discussion about package priorities, I took out some reference
   to packages like w3m, mutt or exim4 which as far as I can tell no longer
   have "Standard" priority but they are now with priority "Optional".
 - I changed the reference to Custom Debian Distributions and Skolelinux
   to Debian Pure Blends and DebianEdu/Skolelinux, respectively; the new
   links are those the old links redirect to, anyway.
 - I added a reference to the "Guide for Debian Maintainers" which is
   more up to that than the New Maintainers' Guide.

Thanks,

beatrice
Index: pkg_basics.sgml
===
--- pkg_basics.sgml	(revisione 11198)
+++ pkg_basics.sgml	(copia locale)
@@ -15,7 +15,7 @@
   Binary packages, which contain executables, configuration
   files, man/info pages, copyright information, and other documentation.
   These packages are distributed in a Debian-specific archive format
-  (see ); they are usually distinguished by having
+  (see ); they are usually characterized by having
   a '.deb' file extension. Binary packages can be unpacked using the Debian
   utility dpkg (possibly via a frontend like .diff.gz file that contains the Debian-specific changes to the
   original source.  The utility dpkg-source packs and unpacks
   Debian source archives; details are provided in its manual page.  (The
-  program dpkg-source.)
+  program dpkg-source.)
 
 
 Installation of software by the package system uses "dependencies" which
@@ -69,9 +69,9 @@
 The Debian binary package file names conform to the following convention:
 foo_VersionNumber-DebianRevisionNumber_DebianArchitecture.deb
 
-Note that foo is supposed to be the package name. As a check,
-one can learn the package name associated with a particular Debian archive
-file (.deb file) in one of these ways:
+Note that foo is supposed to be the package name. Checking
+the package name associated with a particular Debian archive file
+(.deb file) can be done in one of these ways:
 
   inspect the "Packages" file in the directory where it was stored
   at a Debian FTP archive site.  This file contains a stanza describing
@@ -94,9 +94,10 @@
 file (debian/control), the installation or removal scripts
 (debian/p*), or in the configuration files used with the package.
 
+<
 The AAA component identifies the processor for which
-the package was built.  This is commonly i386, which refers to
-chips compatible to Intel's 386 or later versions.  For other
+the package was built.  This is commonly amd64, which refers to
+AMD64, Intel 64 or VIA Nano chips.  For other
 possibilities review Debian's FTP directory structure at .
 For details, see the description of "Debian architecture" in the  manual page
 .
@@ -109,17 +110,20 @@
 Briefly, a sample control file is shown below for the Debian package hello:
 
 Package: hello
+Version: 2.9-2+deb8u1
+Architecture: amd64
+Maintainer: Santiago Vila 
+Installed-Size: 145
+Depends: libc6 (>= 2.14)
+Conflicts: hello-traditional
+Breaks: hello-debhelper (<< 2.9)
+Replaces: hello-debhelper (<< 2.9), hello-traditional
+Section: devel
 Priority: optional
-Section: devel
-Installed-Size: 45
-Maintainer: Adam Heath doo...@debian.org
-Architecture: i386
-Version: 1.3-16
-Depends: libc6 (>= 2.1)
-Description: The classic greeting, and a good example
+Homepage: http://www.gnu.org/software/hello/
+Description: example package based on GNU hello
  The GNU hello program produces a familiar, friendly greeting.  It
-
- allows nonprogrammers to use a classic computer science tool which
+ allows non-programmers to use a classic computer science tool which
  would otherwise be unavailable to them.
  .
  Seriously, though: this is an example of how to do a Debian package.
@@ -186,7 +190,7 @@
 The individual files are:
 
 This script executes before that package will be unpacked from its
+  This script is executed before the package it belongs to is unpacked from its
   Debian archive (".deb") file. Many 'preinst' scripts stop services for
   packages which are being upgraded until their installation or upgrade is
   completed (following the successful execution of the 'postinst' script).
@@ -196,7 +200,7 @@
   package foo once foo has been unpacked from its Debian
   archive (".deb") file. Often, 'postinst' scripts ask the user for input,
   and/or warn the user that if he accepts default values, he should remember
-  to go back and re-configure that package as the situation warrants.
+  to go back and re-configure that package as needed.
   Many 'postinst' scripts then execute any commands necessary to start or
   restart a service 

Re: proposed changes to debian-faq

[Beatrice Torracca]

On Sunday 29 May 2016, at 17:48 +0100, Justin B Rye wrote:

Hi!

> And almost all of them look to me like definite improvements in the
> English.  But:

I should have added that I am not a native English speaker, although I
think it is quite obvious :)

Thanks for the corrections!

> 
> > @@ -238,8 +238,8 @@
> >  synaptic
> >  
> >   > install,
> > -upgrade and remove software packages in a user friendly way.   Next to all
> > -features offered by aptitude, it also has a feature for editing the list of
> > +upgrade and remove software packages in a user friendly way.   Next to
> > +all the features offered by aptitude, it also has a feature for editing 
> > the list of
> >  used repositories, and supports browsing all available documentation 
> > related to
> >  a package. See the http://www.nongnu.org/synaptic/; name="Synaptic
> >  Website"> for more information.
> 
> What is "next to" trying to say here?  Something like "alongside",
> "along with"?  But more importantly, Synaptic doesn't in fact have
> *all* the features offered by aptitude (like for instance the debtags
> browser view).  Could we change it to something like:
> 
>upgrade and remove software packages in a user friendly way.  Along with
>most of the features offered by aptitude, it also has a feature for 
> editing the list of

The meaning (I imagine) was the one you guessed. Your suggestion is
definitely better than mine. I am sure Holger will take it into account.

By the way, I could do the commit but I did not want to disrupt the
workflow of Holger who is reorganizing the FAQ. (But I am willing to do
it if instead it's time-saving for him).

> > Index: uptodate.sgml
> > ===
> > --- uptodate.sgml   (revisione 11195)
> > +++ uptodate.sgml   (copia locale)
> > @@ -1,8 +1,8 @@
> > -
> > +vn
> >  
> >  Keeping your Debian system up-to-date
> 
> Is that deliberate?

no. my bad, sorry.

beatrice


signature.asc
Description: PGP signature

proposed changes to debian-faq

[Beatrice Torracca]

Hi!

I updated the Italian translation of the Debian FAQ. In doing so I
notice a couple of minor things that I think can be changed (nothing
substantial!).

Since Holger is doing such an extensive great job in
reorganizing/updating the FAQ I thought this might be a good moment to
re-read the FAQs as a "low-level" reviewer. The changes I propose are
mostly minor typos and such.

The only change related to actual contents is about the use of
httpredir.

I attach a suggested patch for 4 of the sgml files in the source tree.

Holger can decide what to change or not change of course.

I plan to read the rest of the files in the repo too, unless someone
objects to my suggestions.

Thanks,

beatrice
Index: nexttime.sgml
===
--- nexttime.sgml	(revisione 11195)
+++ nexttime.sgml	(copia locale)
@@ -31,7 +31,7 @@
 
 All of these are done in an ongoing basis. For the first item, a set of security hardening
 build flags that try to prevent known attacks such as stack smashing,
-predictable locations of values in memory, etc. The target is to cover at least
+predictable locations of values in memory, etc. is used. The target is to cover at least
 all packages that are part of the basic installation as well as packages that
 had to be updated through a Security Advisory since 2006. As of this writing,
 around 400 packages have been modified since this effort was first started. All the issues
@@ -94,7 +94,7 @@
 More architectures
 
 Complete Debian system on other architectures. Notice that even though some
-architectures are dropped for a given the release there still might be a way to
+architectures are dropped for a given release, there still might be a way to
 install and upgrade using the latest sid.
 
 More kernels
Index: pkgtools.sgml
===
--- pkgtools.sgml	(revisione 11195)
+++ pkgtools.sgml	(copia locale)
@@ -22,7 +22,7 @@
 for more information about the Debian package management utilities.
 This document is available in various languages and formats, see http://www.debian.org/doc/user-manuals#quick-reference; name="the Debian
-Reference entry on the DDP Users' Manuals overview">.
+Reference entry in the DDP Users' Manuals overview">.
 
 
@@ -66,14 +66,14 @@
 
 APT is the Advanced Package Tool, an advanced interface to the
 Debian packaging system which provides the /usr/share/doc/apt-doc/guide.html/index.html (you will have to install
-the apt-doc package).
+the apt-doc package).
 
 Starting with Debian Jessie, some frequently used
-Some common ways to use 
-   To update the list of package known by your system, you can run:
+   To update the list of packages known by your system, you can run:
apt update
(you should execute this regularly to update your package lists)
 
@@ -148,11 +148,11 @@
 
 
 Note that you must be logged in as root to perform any commands that
-modify any packages.
+modify packages.
 
-Note that Note that The apt tool suite also includes the To print the packages a given package depends on:
apt-cache depends package
 
-   To print detailed information of the versions available
+   To print detailed information on the versions available
for a package and the packages that reverse-depends on
it:
apt-cache showpkg package
@@ -181,7 +181,7 @@
 For more information, install the ,
 , 
-and install the  /usr/share/doc/apt-doc/guide.html/index.html.
 
 aptitude
@@ -218,7 +218,7 @@

 
@@ -229,9 +229,9 @@
 aptitude install foo.
 
 Note that For more informations, read the manual page For more information, read the manual page  and install the synaptic
 
 http://www.nongnu.org/synaptic/; name="Synaptic
 Website"> for more information.
@@ -273,7 +273,7 @@
 
 dpkg-deb
 
-This program manipulates Debian archive(.deb) files.
+This program manipulates Debian archive (.deb) files.
 Some common uses are:
 
   Find out all the options:  dpkg-deb --help.
@@ -321,8 +321,8 @@
 status symbol (explained in the header), the package name, the version
 which is installed, and a brief description.
 
-To learn the status of packages whose names match the string any
-pattern beginning with "foo" by executing the command:
+To learn the status of packages whose names match any
+pattern beginning with "foo", run the command:
   dpkg --list 'foo*'
 
 To get a more verbose report for a particular package, execute the
@@ -329,7 +329,7 @@
 command:
   dpkg --status packagename
  
-How to display the files of a package installed?
+How to display the files of an installed package?
 
 To list all the files provided by the installed package foo
 execute the command
@@ -372,13 +372,13 @@
 If you install the apt-file, similar to the above, it
 searches files which contain the substring or regular expression
 foo in their full path names. The
-advantage over the sample above is that 

Re: debian-faq: Patch2 to improve wording or meaning, remove superfluous words, consistentency ...

[Beatrice Torracca]

On Tuesday 29 March 2016, at 19:20 +0200, Holger Wansing wrote:

Hi,

thanks for working on updating this and other documents. I have some minor 
comments:

> ===
> --- ftparchives.sgml  (Revision 10939)
> +++ ftparchives.sgml  (Arbeitskopie)
> @@ -61,14 +61,14 @@
>sarge was the sergeant of the Green Plastic Army Men,
>etch was the toy blackboard (Etch-a-Sketch),
>lenny was the toy binoculars,
> -  squeeze was the name for the three-eyed aliens,
> -  wheezy was the name of the rubber toy penguin with 
> +  squeeze was the three-eyed aliens,

I think this should be either "squeeze was the name of the three-eyed
aliens" or "squeeze were the three-eyed aliens" , but I think the first
one sounds better.

> Index: pkgtools.sgml
> ===
> --- pkgtools.sgml (Revision 10939)
> +++ pkgtools.sgml (Arbeitskopie)
> @@ -64,7 +64,7 @@

>Execute the command dpkg-split --split foo.deb.
> -This will produce N files each of approximately 460 KBytes long in the
> +This will produce N files each of approximately 460 KBytes file size in 
> the
>  current directory.

The part "file size" sounds strange to me (not a English native
speaker). I would simply say "of approximately 460 KBytes", or "N files
each with a file size of approximately 460 KByte" (but it is maybe an
unnecessary complication) or "each with an approximate size of 460 KBytes".

> Index: uptodate.sgml
> ===
> --- uptodate.sgml (Revision 10939)
> +++ uptodate.sgml (Arbeitskopie)
> @@ -57,7 +57,7 @@
>   
>  Yes. You can use cron-apt, this tool updates the system at
>  regular interval by using a cron job. By default it just updates the package
> -list and downloads new packages without installing.
> +list and downloads new packages, but without installing.
>   

I think it is more common to use the plural "intervals" in the phrase
"at regular intervals". Also maybe adding "them" as in "but without installing 
them."?

Ciao,

beatrice


signature.asc
Description: PGP signature

Translation of Debian Progeny Guide aka kow to translate documentation with no localization structure available

[Beatrice Torracca]

Hi!

some Italian translators have translated the Debian Progeny guide which
is in the Debian DDP repository and it is published on the website among
the obsolete documentation, here
https://www.debian.org/doc/obsolete#users-guide 

Never the less, since there is a published version I think it would be
nice to publish the Italian version too.

The problem for me is that right now there is no i18n/l10n structure
available in the repo (po files, or localized directories).

I am trying to understand more on the process of going from the
files in the ddp repo to the published version of the documentation on
the website.

What would it take to have the Italian version published? (dirs to
create? maybe a makefile?? ) I would really be thankful for any help on
this. Please also note that I cross-posted to debian-doc and debian-i18n
mailing lists because I am not sure which team takes care of this kind
of aspects (and maybe debian-www is involved too for the website page
creation). I am subscribed to both lists so feel free to set the
reply-to field to the more appropriate one.

Thanks a lot in advance,

beatrice

Updating pot (and po) files for debian-faq and debian project-history

[Beatrice Torracca]

Hi!

I noticed that on the repository the pot files for the Project history
manual is older than the .sgml source , and I think the same is true for
the debian-faq manual.

I wanted to update the Italian translations, but the only way I know how
to do that with po4a includes updating the .pot model files and all the
.po files for all the languages, thus making them (possibly) all
incomplete.

I am not sure I am allowed to do that and also I don't know if I should
just update the .pot and it.po file and leave the other languages
untouched... or if things are normally done in another way.

any help by those with more experience are really welcome.

Thanks,

beatrice


signature.asc
Description: Digital signature

Debian Reference - IT translation

[Beatrice Torracca]

Hi!

I saw Osamu did this commit to the debian-reference git repository

=
commit 560a64ee5d9b755cc155c92e7cd25e93157d4b9e
Author: Osamu Aoki os...@debian.org
Date:   Sat Nov 29 21:05:02 2014 +0900

IT: unfuzzy

Since I got no response on this change, I am temporary unfuzzy this in the
similar way as French case.  This may be reverted or chenged by the proper
translator later.
=

The unfuzzy action for Italian is OK.

I replied both privately and on the Italian-l10n mailing list to Osamu
but I am afraid my mails could be blocked by some spam filter or
something like it.

Anyway I simply wanted to inform him that the Italian translation is OK
like that.

Thanks,

beatrice


signature.asc
Description: Digital signature

[Debian-reference] possible minor error

[Beatrice Torracca]

Hi,

I am updating the italian .po for the debian-reference.

I see this new msg:

In ulink url=systemd;systemd/ulink, si può usare ulink 
url=logind;logind/ulink per gestire il login degli utenti. Vedere 
citerefentryrefentrytitlesystemd-networkd/refentrytitlemanvolnum8/manvolnum/citerefentry.

I think it should refer to the manpage of systemd-logind (not networkd).

That is all.

Thanks,

beatrice


-- 
To UNSUBSCRIBE, email to debian-doc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141018131627.gc1...@aebea.it.invalid

Re: [Debian-reference] possible minor error

[Beatrice Torracca]

On Saturday 18 October 2014, at 15:16 +0200, Beatrice Torracca wrote:

 
 In ulink url=systemd;systemd/ulink, si può usare ulink 
 url=logind;logind/ulink per gestire il login degli utenti. Vedere 
 citerefentryrefentrytitlesystemd-networkd/refentrytitlemanvolnum8/manvolnum/citerefentry.
 
 I think it should refer to the manpage of systemd-logind (not networkd).

Sorry,

I was sure I copied the original string. which is:

Under ulink url=\systemd;\systemd/ulink, ulink url=\logind;
\logind/ulink may be used to manage user logins.  See 
citerefentryrefentrytitlesystemd-networkd/refentrytitlemanvolnum8/
manvolnum/citerefentry.


beatrice


-- 
To UNSUBSCRIBE, email to debian-doc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141018133206.gd1...@aebea.it.invalid

Re: CSS style for the documentation pages?

[Beatrice Torracca]

On Sunday 27 April 2014, at 17:17 +0200, Stéphane Blondon wrote:

Hi!

I can not help directly with the issue but...

 Is publican-debian currently used in a project (whatever it is)?
 It could be useful to read the configuration files and the way it
 works for this project.

publican-debian is used for the Debian Handbook guide and thus the
debian-handbook package.
https://packages.debian.org/source/sid/debian-handbook

the Git source repository has the publican.cfg file and everything else of
course.

(I used publican only to generate docs from the translations).

Ciao,

beatrice


signature.asc
Description: Digital signature