headers
Jonathan A. Kollasch | 1 Jan 2006 06:28
Gravatar

please convert page to docbook

Hi,
	I'd like it if someone with access to the converter would
docbookify htdocs/Documentation/network/ipv6/index.list so I can
provide diffs against that rather than the .list.

	Jonathan Kollasch
Permalink | Reply | 2 comments |
headers
rudolf | 10 Jan 2006 15:57
Picon

guide: 15.2.2 atactl dkctl

Hi,

in section 15.2.2 of The NetBSD Guide is mentioned atactl(8) command in 
the context of setting disk caches, but this feature is provided by 
dkctl(8) command. Maybe the Guide should be corrected?

r.

--- chap-rf.xml-orig 2006-01-05 19:41:07.000000000 +0100
+++ chap-rf.xml   2006-01-10 15:48:23.000000000 +0100
 <at>  <at>  -180,7 +180,7  <at>  <at> 
  /dev/rsd0d: caching parameters are savable</screen>

        <para>For drives on non-SCSI buses (EIDE, SATA, USB, IEEE1394),
-       &man.atactl.8; may be available or a virtual SCSI bus may be
+       &man.dkctl.8; may be available or a virtual SCSI bus may be
         attached which should allow for access.</para>
      </sect2>
    </sect1>
Permalink | Reply | 0 comments |
headers
Klaus Heinz | 16 Jan 2006 22:30
Picon

character sets in XML documents

 [ moved to netbsd-docs ]

Rui Paulo wrote:

> I think he should set the enconding in the first line of the XML files
> and then use the native language accents/punctuation/etc.

So far, I always use character entities for German umlauts instead of
ISO-8859-1. Since NetBSD's localization features still leave a lot to
be desired I felt this would make it easier for everybody.

Should we encourage people to use their native character sets or leave
it up to them?

ciao
     Klaus
Permalink | Reply | 7 comments |
headers
Rui Paulo | 16 Jan 2006 22:37

Re: character sets in XML documents

On 2006.01.16 22:30:36 +0100, Klaus Heinz wrote:
|  [ moved to netbsd-docs ]
| 
| Rui Paulo wrote:
| 
| > I think he should set the enconding in the first line of the XML files
| > and then use the native language accents/punctuation/etc.
| 
| So far, I always use character entities for German umlauts instead of
| ISO-8859-1. Since NetBSD's localization features still leave a lot to
| be desired I felt this would make it easier for everybody.
| 
| Should we encourage people to use their native character sets or leave
| it up to them?

Let's leave it up to them. It works fine for pt_BR and pt_PT (and I've
been encouraging them) but it may not for other languages.

		-- Rui Paulo
Permalink | Reply | 0 comments |
headers
Emil Hessman | 17 Jan 2006 09:48
Picon

Re: character sets in XML documents

Thus wrote Klaus Heinz:

> [ moved to netbsd-docs ]
> 
> Rui Paulo wrote:
> 
> > I think he should set the enconding in the first line of the XML 
> > files and then use the native language accents/punctuation/etc.
> 
> So far, I always use character entities for German umlauts instead of
> ISO-8859-1. Since NetBSD's localization features still leave a lot to
> be desired I felt this would make it easier for everybody.
> 
> Should we encourage people to use their native character sets or leave
> it up to them?

   For portability reasons, I'd prefer use of either UTF-8 or XML
entities. According to the NetBSD guide, XML entities are preferable to
national characters;

http://www.netbsd.org/guide/en/ap-contrib.html#ap-contrib-translating-writing-docbook

	-- ceh
Permalink | Reply | 5 comments |
headers
Rui Paulo | 19 Jan 2006 22:50

Re: character sets in XML documents

Emil Hessman <ceh <at> otaku.se> writes:

> Thus wrote Klaus Heinz:
>
>> [ moved to netbsd-docs ]
>> 
>> Rui Paulo wrote:
>> 
>> > I think he should set the enconding in the first line of the XML 
>> > files and then use the native language accents/punctuation/etc.
>> 
>> So far, I always use character entities for German umlauts instead of
>> ISO-8859-1. Since NetBSD's localization features still leave a lot to
>> be desired I felt this would make it easier for everybody.
>> 
>> Should we encourage people to use their native character sets or leave
>> it up to them?
>
>    For portability reasons, I'd prefer use of either UTF-8 or XML
> entities.

What portability reasons are you talking about ?

> According to the NetBSD guide, XML entities are preferable to
> national characters;
>
> http://www.netbsd.org/guide/en/ap-contrib.html#ap-contrib-translating-writing-docbook

Yes, but we were discussing if this is the correct way or not. It's
PITA to write documentation using XML entities.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Hubert Feyrer | 19 Jan 2006 23:27
Picon
Favicon

Re: character sets in XML documents


On Thu, 19 Jan 2006, Rui Paulo wrote:
> Yes, but we were discussing if this is the correct way or not. It's
> PITA to write documentation using XML entities.

Seconded.

  - Hubert
Permalink | Reply | 0 comments |
headers
Emil Hessman | 21 Jan 2006 11:03
Picon

Re: character sets in XML documents

Thus wrote Rui Paulo:

> >    For portability reasons, I'd prefer use of either UTF-8 or XML
> > entities.
> 
> What portability reasons are you talking about ?

> > According to the NetBSD guide, XML entities are preferable to
> > national characters;
> >
> > http://www.netbsd.org/guide/en/ap-contrib.html#ap-contrib-translating-writing-docbook

> Yes, but we were discussing if this is the correct way or not. It's
> PITA to write documentation using XML entities.

   Ah, yes - and as you wrote in an earlier message; leaving the
decision up to the people who's doing the actual work sounds like the
best idea. 
   Enforcing use of national characters isn't a good idea whilst XML
character entities are preferable in the sense of "portability" between
different languages and their corresponding character encodings, et
cetera.

   As for writing documentation using XML entities; there's simple
methods like editing the files with national characters and let sed
scripts convert the national characters back and forth to their
equivalent XML character entities.

   If it's worth the time and effort, perhaps the www team could
overlook the possibility of developing simple tools to simplify the
(Continue reading)

Permalink | Reply | 2 comments |
headers
Rui Paulo | 21 Jan 2006 16:44

Re: character sets in XML documents

Emil Hessman <ceh <at> otaku.se> writes:
>    If it's worth the time and effort, perhaps the www team could
> overlook the possibility of developing simple tools to simplify the
> task of writing documents with XML entities in mind?

I don't know. While writing XML documents in non-English languages
using entities is a pain, reading them is also painful. I'm ok for
local charsets in htdocs.

>    On another note, has there been any discussions at all regarding use
> of UTF-8 as a prefered character encoding for *all* documentation?

Not that I recall. But this could be considered a bloat, I think.

--

-- 
Rui Paulo - rpaulo <at> fnop.net
Permalink | Reply | 1 comment |
headers
James K. Lowden | 21 Jan 2006 18:55
Gravatar

Re: character sets in XML documents

Rui Paulo wrote:
Emil Hessman <ceh <at> otaku.se> writes:
> >    On another note, has there been any discussions at all regarding
> >    use
> > of UTF-8 as a prefered character encoding for *all* documentation?
> 
> Not that I recall. But this could be considered a bloat, I think.

I should hope not.  Unicode is the default encoding for XML and even HTML
these days.  UTF-8 has a byte density very close to ISO 8859-1 for
languages that use Roman characters.  Moving everything (even man pages?)
to UTF-8 would be the Right Thing (tm).  

If document authors prefer to operate in other encodings for their
convenience, why not let them convert with iconv(1), edit, re-convert, and
commit?  Eventually UTF-8 will be better supported than its obsolete
predecessors, so the road will only get easier.  

Is there some technical obstacle I'm overlooking?  

--jkl
Permalink | Reply | 0 comments |

Gmane