headers
Mike M. Volokhov | 4 Feb 2005 16:18
Picon

Lost messages to www <at> 

Greetings!

More than one month ago I have sent the following two mails to www <at> , but
got no reply:

	Date: Thu, 16 Dec 2004 16:19:32 +0200
	Subject: Submission: NetBSD in action: productivity tools
	Synopsis: The screenshot of documentation framefork based on XXE2
		driven by Java 1.5 and NetBSD 2.99

	Date: Wed, 29 Dec 2004 16:56:59 +0200
	Subject: NetBSD main page validation
	Synopsis: A patchset to htdocs/index.html and other laguages to
		make them compliant to HTML 4.01 Transitional.

Does anoybody know what happens with my mails?

Excuse me please for annoying.

--
Best wishes,
Mishka.
Permalink | Reply | 1 comment |
headers
Klaus Heinz | 5 Feb 2005 15:15
Picon

Re: Lost messages to www <at> 

Hi Mishka,

> 	Date: Thu, 16 Dec 2004 16:19:32 +0200
> 	Subject: Submission: NetBSD in action: productivity tools
> 	Synopsis: The screenshot of documentation framefork based on XXE2
> 		driven by Java 1.5 and NetBSD 2.99
> 
> 	Date: Wed, 29 Dec 2004 16:56:59 +0200
> 	Subject: NetBSD main page validation
> 	Synopsis: A patchset to htdocs/index.html and other laguages to
> 		make them compliant to HTML 4.01 Transitional.
> 
> Does anoybody know what happens with my mails?

I missed responding to at least one of the above :-/.

> Excuse me please for annoying.

Obviously, I needed someone to remind me, so you're not annoying at
all. I will take care of both messages.

Regards.
     Klaus
Permalink | Reply | 0 comments |
headers
Jan Schaumann | 7 Feb 2005 15:03
Favicon
Gravatar

updating the flyer

Hi,

Is there somebody here who could help us out and update the NetBSD flyer
we usually use for our booths at conferences?  It's the first flyer at
http://www.netbsd.org/gallery/advocacy/, the .tex sources are available
in several languages.

If somebody could send me a patch to update the flyer for the 2.0
release, that would be great!

Thanks,
-Jan

--

-- 
Life," said Marvin, "don't talk to me about life."
Permalink | Reply | 0 comments |
headers
Mike M. Volokhov | 12 Feb 2005 13:36
Picon

More XSL Guide customization

Greetings!

I'm working on build process of Russian translation of The NetBSD Guide.
The problem is chunked HTML output is always ISO-8859-1 encoded, which
is not acceptable for Russian (and I believe some other languages too).
There are no "chunker.output.encoding" parameter defined for XSLT
processor. Thus, I've enforce this parameter by providing additional
XSL_DBX_WITH_CHUNKER_OUTPUT_ENCODING variable in doc.docbook.xsl.mk
file.

However, previously I've tried to add it to another settings, i.e.:

	XSL_DBX_WITH_CHUNKER_OUTPUT_ENCODING=UTF-8
	XSL_DBX_HTML_SPLIT_PARAMS+=XSL_DBX_WITH_CHUNKER_OUTPUT_ENCODING

and found that all other settings was flushed, so as we have the
following in a make logic:

	.if !defined(XSL_DBX_HTML_SPLIT_PARAMS) || empty(XSL_DBX_HTML_SPLIT_PARAMS)
	XSL_DBX_HTML_SPLIT_PARAMS+= ......
	.endfi

So this cause to inability to simply add user's own parametres (like
I've did before). The patch below will fix this (and mentioned encoding)
problems.

--
Best wishes,
Mishka.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Hiroki Sato | 12 Feb 2005 19:08
Picon

Re: More XSL Guide customization

"Mike M. Volokhov" <mishka <at> apk.od.ua> wrote
  in <20050212143641.68108446.mishka <at> apk.od.ua>:

m> I'm working on build process of Russian translation of The NetBSD Guide.
m> The problem is chunked HTML output is always ISO-8859-1 encoded, which
m> is not acceptable for Russian (and I believe some other languages too).

 I think $XML_ENCODING in the Makefile in the language dependent directory
 is enough.  Didn't it work?

--

-- 
| Hiroki SATO
Permalink | Reply | 2 comments |
headers
Mike M. Volokhov | 14 Feb 2005 10:30
Picon

Re: More XSL Guide customization

On Sun, 13 Feb 2005 03:08:35 +0900 (JST)
Hiroki Sato <hrs <at> NetBSD.org> wrote:

> "Mike M. Volokhov" <mishka <at> apk.od.ua> wrote
>   in <20050212143641.68108446.mishka <at> apk.od.ua>:
> 
> m> I'm working on build process of Russian translation of The NetBSD Guide.
> m> The problem is chunked HTML output is always ISO-8859-1 encoded, which
> m> is not acceptable for Russian (and I believe some other languages too).
> 
>  I think $XML_ENCODING in the Makefile in the language dependent directory
>  is enough.  Didn't it work?

Unfortunately, no. XML_ENCODING is used within three cases:

1. When generating *.xsl files (seems doesn't really used, alas).
2. When producing work *.xml files (as <?xml encoding="FOO"?>).
3. And when producing *.txt files (as w3m option).

The best way to done this within cases above is a very first point, if
master*.xsl files would contain something like:

	<xsl:param name="chunker.output.encoding"> <at>  <at> HTML_ENCODING <at>  <at> </xsl:param>
	<xsl:output encoding=" <at>  <at> HTML_ENCODING <at>  <at> "/>

Yes, I've used HTML_ENCODING so as XML_ENCODING doesn't set *output*
encoding at all, but default output encoding is always ISO-8859-1.

Moreover, XML_ENCODING and SX_ENCODING seems cannot be set to different
values, so as XML_ENCODING sets the encoding in "<?xml?>" tag, when
(Continue reading)

Permalink | Reply | 1 comment |
headers
Radek Kujawa | 15 Feb 2005 12:39
Picon

"PCI Hardware Supported by NetBSD"

Hello.
   I think that page http://www.netbsd.org/Hardware/pci.html is listing 
some non-PCI devices.
   AFAIR there cards are just plain ISA:
- Sierra's Aria chipset (aria(4))
- ESS Technology ES1777/1868/1869/1887/1888/888 (ess(4), NOT eso(4), 
esa(4) which are used to drive PCI ESS boards - Maestro and Solo)
- Personal Sound System (pss(4))
- ProAudio Spectrum (pas(4))
- Windows Sound System (wss(4))

Radek

--
Radek Kujawa	- unix sysadmin / artist extraordinaire
streamer <at> myrealbox.com
Permalink | Reply | 0 comments |
headers
Hiroki Sato | 16 Feb 2005 18:53
Picon

Re: More XSL Guide customization

"Mike M. Volokhov" <mishka <at> apk.od.ua> wrote
  in <20050214113026.15c55a94.mishka <at> apk.od.ua>:

m> >  I think $XML_ENCODING in the Makefile in the language dependent directory
m> >  is enough.  Didn't it work?
m> 
m> Unfortunately, no. XML_ENCODING is used within three cases:

 Ah, right, I misunderstood your problem.

m> The best way to done this within cases above is a very first point, if
m> master*.xsl files would contain something like:
m> 
m> 	<xsl:param name="chunker.output.encoding"> <at>  <at> HTML_ENCODING <at>  <at> </xsl:param>
m> 	<xsl:output encoding=" <at>  <at> HTML_ENCODING <at>  <at> "/>

 These sort of settings can be customized by using <lang>/share/default-*.xsl.
 Please define $chunker.output.encoding in these files as done
 in ko/share/default-html-chunk.xsl.

 I am still not sure XML_ENCODING and SP_ENCODING problem you mention.
 Do you need conversion of the encoding during XSLT processing?
 Could you please show me a more specific case?

--

-- 
| Hiroki SATO
Permalink | Reply | 0 comments |
headers
Brian A. Seklecki | 17 Feb 2005 04:42

Re: Patch against the Guide's RAIDFrame chapter

On Sat, 2004-12-11 at 08:42, Ceri Davies wrote:
> One spellchecker error, one misuse of an apostrophe, one rewording.
> 

Thanks for these.  It looks like they were commited.  I've been in the
cut for about 5 months.

~BAS

> Cheers,
> 
> Ceri
> 
> PS If I should be send-pring these instead, just let me know ;-)
Permalink | Reply | 0 comments |

Gmane