How to distribute translated manuals as a part of distribution?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

How to distribute translated manuals as a part of distribution?

Yasuhiko Kamata
Hello doc,

Finally we have completed translations of openSUSE-manual to Japanese
(already uploaded to opensuse-doc SVN).
So I want them to be distributed via opensuse official repository and
make them available online (doc.opensuse.org).

.spec file (for .rpm) was already created at OBS home project
(OBS > Projects > home:belphegor_belbel) and outputs were checked by
myself.

What should I do after that?

Anyway, some tweaks needed for Japanese PDF (not neededed for HTML);
1. Need italic/bold fonts.

   Since FOP cannot generate italic(oblique)/bold style from existing
   fonts (and all existing Japanese fonts does not contain them),
   I've decided to generate them (by fontforge scripting) before
   making PDFs.

   These fonts are packaged with name IPAGothic_BoldItalic
   in OBS home project (OBS > Projects > home:belphegor_belbel).
   (This package's publish flag is now off, because this package is not
    essential one.)

2. Special FOP configs.

   For Japanese fonts, special configs are needed for FOP (even if
   normal (not bold/italic) font). This config is now located at
   opensuse-doc SVN
   (/svn/opensuse-doc/trunk/documents/distribution/ja/fop-suse-ja.xml).
   DC-* and ENV-* files were adjusted accordingly.

Thanks,

--
Yasuhiko Kamata <[hidden email]>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to distribute translated manuals as a part of distribution?

Karl Eichwalder
Yasuhiko Kamata <[hidden email]> writes:

> So I want them to be distributed via opensuse official repository and
> make them available online (doc.opensuse.org).

The first goal should be to build it in the Documentation project of
OBS.  There we already have the English book, which builds with "daps":

https://build.opensuse.org/package/show?package=opensuse-manuals_en&project=Documentation

Thus far, I did not try building translated books with daps, but it
should be straightforward--you just need tar of the sources:

    daps -d DC-opensuse-html package-src --def-file=DEF-opensuse-manuals

(Edit DEF-opensuse-manuals according to your needs.)

Then adjust the en.spec file for your language.

(There is a shell script that does all these steps automatically for the
English book:
trunk/tools/susedoc-buildbook/daps-prep-source-and-spec.sh
We must test whether it also works for translated books out-of-the-box;
especially the osc commands that deal with the OBS are probably broken.)

--
Karl Eichwalder                              SUSE LINUX Products GmbH
R&D / Documentation                          Maxfeldstraße 5
                                             90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to distribute translated manuals as a part of distribution?

Thomas Schraitle-3
In reply to this post by Yasuhiko Kamata
Hi Yasuhiko Kamata,

>
> Finally we have completed translations of openSUSE-manual to Japanese
> (already uploaded to opensuse-doc SVN).
> So I want them to be distributed via opensuse official repository and
> make them available online (doc.opensuse.org).

Thanks for your efforts! Regarding translation, Karl already answered
that part.

 
> Anyway, some tweaks needed for Japanese PDF (not neededed for HTML);
> 1. Need italic/bold fonts.
>
>    Since FOP cannot generate italic(oblique)/bold style from existing
>    fonts (and all existing Japanese fonts does not contain them),
>    I've decided to generate them (by fontforge scripting) before
>    making PDFs.

Cool!
Yes, as far as I remember, italic/bold is unusual in Japanese
typography, isn't it?

 
>    These fonts are packaged with name IPAGothic_BoldItalic
>    in OBS home project (OBS > Projects > home:belphegor_belbel).
>    (This package's publish flag is now off, because this package is
> not essential one.)

It may be worth to branch the original ipa-fonts package from
M17N:fonts and submit your changes back. That way, we have it in _one_
package and it's in an official repository.

 
> 2. Special FOP configs.
>
>    For Japanese fonts, special configs are needed for FOP (even if
>    normal (not bold/italic) font). This config is now located at
>    opensuse-doc SVN
>    (/svn/opensuse-doc/trunk/documents/distribution/ja/fop-suse-ja.xml).
>    DC-* and ENV-* files were adjusted accordingly.

Our latest daps version contains a bugfix which lets you set the FOP
config file. However, this is not available in the current released daps
package.

The latest version supports the FOP_CONFIG_FILE environment variable.
Move your FOP configuration file to your SVN working copy and set the
above variable to your file, (re)build the book and it will use the
correct file.

If you are unsure, you can check the value, if you use daps with this
options:

 $ daps -d YOUR_DC_FILE showvariable VARIABLE=FOP_CONFIG_FILE

We will release a new package soon which supports this feature.


--
Gruß/Regards,
    Thomas Schraitle

----------------------------------------------------------------------
SUSE LINUX Products GmbH     (o<  
Maxfeldstrasse 5             /\\      Documentation Specialist
90409 Nuernberg, Germany    _\_v      http://www.suse.com
http://lizards.opensuse.org/author/thomas-schraitle/
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild,
Felix Imendörffer, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to distribute translated manuals as a part of distribution?

Yasuhiko Kamata
In reply to this post by Karl Eichwalder
Hi Karl,

I have already prepared opensuse-manuals_ja.spec file
and tested at OBS in my home project
(https://build.opensuse.org/package/show?package=opensuse-manuals_ja&project=home%3Abelphegor_belbel).

So I think it's time to "Request role addition" and
create new package in OBS Documentation project, right?

On Thu, 19 Apr 2012 15:00:22 +0200
Karl Eichwalder <[hidden email]> wrote:

> Yasuhiko Kamata <[hidden email]> writes:
>
> > So I want them to be distributed via opensuse official repository and
> > make them available online (doc.opensuse.org).
>
> The first goal should be to build it in the Documentation project of
> OBS.  There we already have the English book, which builds with "daps":
>
> https://build.opensuse.org/package/show?package=opensuse-manuals_en&project=Documentation
>
> Thus far, I did not try building translated books with daps, but it
> should be straightforward--you just need tar of the sources:
>
>     daps -d DC-opensuse-html package-src --def-file=DEF-opensuse-manuals
>
> (Edit DEF-opensuse-manuals according to your needs.)
>
> Then adjust the en.spec file for your language.
>
> (There is a shell script that does all these steps automatically for the
> English book:
> trunk/tools/susedoc-buildbook/daps-prep-source-and-spec.sh
> We must test whether it also works for translated books out-of-the-box;
> especially the osc commands that deal with the OBS are probably broken.)
>
> --
> Karl Eichwalder                              SUSE LINUX Products GmbH
> R&D / Documentation                          Maxfeldstraße 5
>                                              90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

Best regards,

--
Yasuhiko Kamata <[hidden email]>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to distribute translated manuals as a part of distribution?

Karl Eichwalder
Yasuhiko Kamata <[hidden email]> writes:

> I have already prepared opensuse-manuals_ja.spec file
> and tested at OBS in my home project
> (https://build.opensuse.org/package/show?package=opensuse-manuals_ja&project=home%3Abelphegor_belbel).

Yes, looks good.

> So I think it's time to "Request role addition" and
> create new package in OBS Documentation project, right?

Yes, I added you as a maintainer.  Cheers,
Karl

--
Karl Eichwalder                              SUSE LINUX Products GmbH
R&D / Documentation                          Maxfeldstraße 5
                                             90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to distribute translated manuals as a part of distribution?

Yasuhiko Kamata
In reply to this post by Thomas Schraitle-3
Hi Thomas,

> Yes, as far as I remember, italic/bold is unusual in Japanese
> typography, isn't it?

Surely it was unusual in the past.
But now frequently used; I think computing culture makes it usual
(HTML tags, word processing softwares etc.).

> It may be worth to branch the original ipa-fonts package from
> M17N:fonts and submit your changes back. That way, we have it in _one_
> package and it's in an official repository.

Ok, I'll try.

On Thu, 19 Apr 2012 16:02:57 +0200
Thomas Schraitle <[hidden email]> wrote:

> Hi Yasuhiko Kamata,
>
> >
> > Finally we have completed translations of openSUSE-manual to Japanese
> > (already uploaded to opensuse-doc SVN).
> > So I want them to be distributed via opensuse official repository and
> > make them available online (doc.opensuse.org).
>
> Thanks for your efforts! Regarding translation, Karl already answered
> that part.
>
>  
> > Anyway, some tweaks needed for Japanese PDF (not neededed for HTML);
> > 1. Need italic/bold fonts.
> >
> >    Since FOP cannot generate italic(oblique)/bold style from existing
> >    fonts (and all existing Japanese fonts does not contain them),
> >    I've decided to generate them (by fontforge scripting) before
> >    making PDFs.
>
> Cool!
> Yes, as far as I remember, italic/bold is unusual in Japanese
> typography, isn't it?
>
>  
> >    These fonts are packaged with name IPAGothic_BoldItalic
> >    in OBS home project (OBS > Projects > home:belphegor_belbel).
> >    (This package's publish flag is now off, because this package is
> > not essential one.)
>
> It may be worth to branch the original ipa-fonts package from
> M17N:fonts and submit your changes back. That way, we have it in _one_
> package and it's in an official repository.
>
>  
> > 2. Special FOP configs.
> >
> >    For Japanese fonts, special configs are needed for FOP (even if
> >    normal (not bold/italic) font). This config is now located at
> >    opensuse-doc SVN
> >    (/svn/opensuse-doc/trunk/documents/distribution/ja/fop-suse-ja.xml).
> >    DC-* and ENV-* files were adjusted accordingly.
>
> Our latest daps version contains a bugfix which lets you set the FOP
> config file. However, this is not available in the current released daps
> package.
>
> The latest version supports the FOP_CONFIG_FILE environment variable.
> Move your FOP configuration file to your SVN working copy and set the
> above variable to your file, (re)build the book and it will use the
> correct file.
>
> If you are unsure, you can check the value, if you use daps with this
> options:
>
>  $ daps -d YOUR_DC_FILE showvariable VARIABLE=FOP_CONFIG_FILE
>
> We will release a new package soon which supports this feature.
>
>
> --
> Gruß/Regards,
>     Thomas Schraitle
>
> ----------------------------------------------------------------------
> SUSE LINUX Products GmbH     (o<  
> Maxfeldstrasse 5             /\\      Documentation Specialist
> 90409 Nuernberg, Germany    _\_v      http://www.suse.com
> http://lizards.opensuse.org/author/thomas-schraitle/
> SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild,
> Felix Imendörffer, HRB 21284 (AG Nürnberg)
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>

Thanks,

--
Yasuhiko Kamata <[hidden email]>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]