Localization derived from Walsh styles

[Vitaly Ostanin]

Hello.

I'm trying to use db2latex-0.7 for our documentation project
(docs.altlinux.ru)

Dir "xsl/common" contain localization files derived from original
DocBook stylesheets but it's unmaintained. Now original styles
is more localized for more languages.

db2latex styles can use original DocBook localization, using full
URI's for l10n files. This scheme depends on XML Catalogs [1]
setup and XML tools for processing it.

Tools with support XML Catalogs:
libxml2
http://xmlsoft.org

XIncluder
http://xincluder.sourceforge.net/

and more.

Question:

Do you want to add:

1. Dependence on DocBook xsl-styles
2. Dependence on XML Catalogs support

for correct localization ?

Links:
[1] http://www.oasis-open.org/committees/entity/spec.html
--
Regards, Vyt
mailto: ***@vzljot.ru
JID: ***@vzljot.ru


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

[James Devenish]

Post by Vitaly Ostanin
I'm trying to use db2latex-0.7 for our documentation project
(docs.altlinux.ru)

I recommend using a more-recent DB2LaTeX version such as the daily
snapshots: <http://db2latex.sourceforge.net/snapshot>. These snapshots
contain a large number of fixes to make DB2LaTeX work better with
existing DocBook documents.

Post by Vitaly Ostanin
Dir "xsl/common" contain localization files derived from original
DocBook stylesheets but it's unmaintained. Now original styles
is more localized for more languages.

They are not exactly unmaintained, as we make changes to them on
occasion. However, you would be correct is saying that they have not
been recently synchronised with information from Norman Walsh's DocBook
XSL stylesheets. Perhaps Ramon can look into that. Thanks for mentioning
it.
Sure. We use usually use xsltproc (and sometimes Xalan)
with catalogue support.

Post by Vitaly Ostanin
1. Dependence on DocBook xsl-styles
2. Dependence on XML Catalogs support
for correct localization ?

The DB2LaTeX localisation files contain more keys than Norman's
stylesheets. Thus, I think DB2LaTeX needs to use its own
localisation files.




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

[Vitaly Ostanin]

On Fri, 27 Jun 2003 07:53:04 +0800

Post by James Devenish

Post by Vitaly Ostanin
I'm trying to use db2latex-0.7 for our documentation project
(docs.altlinux.ru)

I recommend using a more-recent DB2LaTeX version such as the
daily snapshots: <http://db2latex.sourceforge.net/snapshot>.
These snapshots contain a large number of fixes to make
DB2LaTeX work better with existing DocBook documents.

Ok, thanks.

<skipped/>

Post by James Devenish
The DB2LaTeX localisation files contain more keys than Norman's
stylesheets.

For example, what keys are not exists in Norman's stylesheets ?

Anyway, it's possible to import keys from Norman's styles
into your localization files. This can be done with XML
Inclusions [1]. With this schema manual synchronization not
needed.

I look into db2latex-xsl-0.7+20030622 snapshot:
localization files in xsl/common is not well-formed XML. It's
normal ?

Links:
[1] http://www.w3.org/TR/xinclude/

<skipped/>
--
Regards, Vyt
mailto: ***@vzljot.ru
JID: ***@vzljot.ru


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

[James Devenish]

Post by Vitaly Ostanin
For example, what keys are not exists in Norman's stylesheets ?

LaTeX-specific ones :)

Post by Vitaly Ostanin
Anyway, it's possible to import keys from Norman's styles
into your localization files. This can be done with XML
Inclusions [1]. With this schema manual synchronization not
needed.

I understand that, but I don't think we should have XInclude Candidate
support as a prerequisite for DB2LaTeX (even though it's fairly common
these days).

Post by Vitaly Ostanin
I look into db2latex-xsl-0.7+20030622 snapshot: localization files in
xsl/common is not well-formed XML. It's normal ?

Thanks for pointing this out. I would imagine that when the
localisations are modernised, this will in time get corrected.
Ramon will have to get back to you about it.

Thanks for alerting us to these problems.




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

[James Devenish]

Anyway, you can use XInclude for synchronization at build time,
not in normal using.

An interesting idea!

At preparing time for release this file must be parsed for
inclusion and final output will used by release styles.

I expect that we would actually keep a generated copy in the CVS
repository, rather than only putting it into releases, but I
understand your sentiment.

For it I write xsl-style (attached) for parsing DocBook and
DB2LaTeX localization files. See comments in style.

Thanks, we will definitely look into this!

l10n.dtd
l10n.xsl
l10n.xml

Part of the reason I have not personally done any revamping of the
DB2LaTeX localisation is that we have modified those files since our
last sync with Norman's stylesheets. Therefore, his are no longer
drop-in replacements. Obviously that is our problem, but it exists
nevertheless.

BTW, localization files in DocBook is generated too

True.




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

[Vitaly Ostanin]

On Mon, 30 Jun 2003 07:56:01 +0800

Post by James Devenish

Anyway, you can use XInclude for synchronization at build
time, not in normal using.

An interesting idea!

At preparing time for release this file must be parsed for
inclusion and final output will used by release styles.

I expect that we would actually keep a generated copy in the
CVS repository,

For what? This way keep information twice and not synced :(

Post by James Devenish
rather than only putting it into releases, but
I understand your sentiment.

For it I write xsl-style (attached) for parsing DocBook and
DB2LaTeX localization files. See comments in style.

Thanks, we will definitely look into this!

I found bug, but it not affect current localization in DB2LaTeX.
Fixed style is attached.

Post by James Devenish

l10n.dtd
l10n.xsl
l10n.xml

Part of the reason I have not personally done any revamping of
the DB2LaTeX localisation is that we have modified those files
since our last sync with Norman's stylesheets.

Please, give me an example.

Post by James Devenish
Therefore, his are no longer drop-in replacements. Obviously
that is our problem, but it exists nevertheless.

I don't see any problem. Attached style find any DB2LaTeX addons
and keeps their in result output.

If you not just add keys but modified their values, it's strange.

<skipped/>

[James Devenish]

Post by Vitaly Ostanin

Post by James Devenish
I expect that we would actually keep a generated copy in the
CVS repository,

For what? This way keep information twice and not synced :(

It is quite common for projects to have a number of generated files that
are kept in CVS along with their source files. For a start, this allows
casual developers to avoid requiring peculiar dependencies or extremely
long bootstrap processes when using the CVS files. Moreover, it provides
the `diff` and revision history advantages of CVS.




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

[Vitaly Ostanin]

On Mon, 30 Jun 2003 16:36:54 +0800

Post by James Devenish

Post by Vitaly Ostanin

Post by James Devenish
I expect that we would actually keep a generated copy in
the CVS repository,

For what? This way keep information twice and not synced :(

It is quite common for projects to have a number of generated
files that are kept in CVS along with their source files. For a
start, this allows casual developers to avoid requiring
peculiar dependencies or extremely long bootstrap processes
when using the CVS files. Moreover, it provides the `diff` and
revision history advantages of CVS.

Ok.

Please, tell me - do you want to do syncronization with current
DocBook l10n ?

I have patch for l10n.xml for escaping l10n values to LaTeX valid
text. But ru.xml is really old :((