Re: Sarge release Notes
* Frans Pop <aragorn@tiscali.nl> [2005-05-29 19:57] :
> Hello,
>
> I have been coordinating the efforts to get the Release Notes for Sarge
> up-to-date and translated over the last few weeks.
>
> There have been several "Calls for translation" on debian-i18n. I have
> also sent reminders for individual languages. Unfortunately, although you
> both have existing translations in CVS, I missed both fi and sk because
> they were not in my CVS checkout (stupid cvs does not add new directories
> automatically).
>
> There have been major changes to the release notes, and therefore your
> (outdated) translations currently are not published on the website.
>
> The release is likely to happen next weekend. Therefore the deadline for
> translations is currently set for Thursday June 2.
> This deadline is _only_ important for translations to be included on the
> Installation CDs. Translations that are completed after June 2 will of
> course be published on the _website_ [1] as soon as they are received.
Hello,
The French translation is now up-to-date.
I have also noticed two minor mistakes while doing my last update:
Index: en/release-notes.en.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml,v
retrieving revision 1.50
diff -u -u -r1.50 release-notes.en.sgml
--- en/release-notes.en.sgml 28 May 2005 17:06:14 -0000 1.50
+++ en/release-notes.en.sgml 29 May 2005 22:12:46 -0000
@@ -1087,7 +1087,7 @@
often provides additional information on why the package was
removed. You should review both the archived bug reports for the
package itself and the archived bug reports for the <url
- id="&url-bts;/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes"
+ id="&url-bts;/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes"
name="ftp.debian.org pseudo-package">.</p>
<sect1 id="dummy"><heading>Dummy packages</heading>
@@ -1503,7 +1503,7 @@
<![ %mips-mipsel [
<item>
- <p><em>with apt</em>; if you not yet have done so,
+ <p><em>with apt</em>: if you not yet have done so,
change your <file>sources.list</file> file to point
to &releasename; as described in <ref id="upgrade-process">,
update your packages lists and install the kernel-image for
The first one is needed to include a '?' in this URL (it won't work with
& in either HTML or PDF output).
Greetings,
Fred
Reply to: