PDF creation: element errors

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

PDF creation: element errors

Marguerite Su
Hi, all,

I tried to produce a pdf, but I got these errors:

$ daps --docconfig=DC-opensuse-startup color-pdf
MAIN.opensuse.xml:211: element filename: validity error : Element
filename is not declared in filename list of possible children
MAIN.opensuse.xml:15: element abstract: validity error : Element
abstract content does not follow the DTD, expecting (title? , para+),
got ()
MAIN.opensuse.xml:46: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)
MAIN.opensuse.xml:78: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)
MAIN.opensuse.xml:81: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)
MAIN.opensuse.xml:84: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)
MAIN.opensuse.xml:112: element keycombo: validity error : Element
keycombo content does not follow the DTD, expecting (keycap)+, got
(keycap CDATA keycap)
MAIN.opensuse.xml:126: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)
MAIN.opensuse.xml:173: element guimenu: validity error : Element
guimenu was declared #PCDATA but contains non text nodes
MAIN.opensuse.xml:173: element guimenu: validity error : Element
guimenu was declared #PCDATA but contains non text nodes
MAIN.opensuse.xml:173: element guimenu: validity error : Element
guimenu was declared #PCDATA but contains non text nodes
MAIN.opensuse.xml:11: element xref: validity error : Element xref was
declared EMPTY this one has content
MAIN.opensuse.xml:482: element xref: validity error : IDREF attribute
linkend references an unknown ID "ex.welt.zone"
MAIN.opensuse.xml:578: element xref: validity error : IDREF attribute
linkend references an unknown ID "sec.basicnet.manconf.hosts"
MAIN.opensuse.xml:33: element xref: validity error : IDREF attribute
linkend references an unknown ID "sec.apparmor.start.update"

when I tried to fix them, I found MAIN.opensuse.xml:XX actually does
not have the error it warned, eg:

MAIN.opensuse.xml:46: element menuchoice: validity error : Element
menuchoice content does not follow the DTD, expecting (shortcut? ,
guimenu+), got (guimenu CDATA guimenu)

but MAIN.opensuse.xml:46 is:

<!ENTITY gnomecc "&gnome; Control Center">

I can't see anything wrong.

Any ideas?


Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
Hi Marguerite,

sorry, missed your mail and with all the public holidays in between, it
vanished...

> I tried to produce a pdf, but I got these errors:
>
> $ daps --docconfig=DC-opensuse-startup color-pdf
> MAIN.opensuse.xml:211: element filename: validity error : Element
> filename is not declared in filename list of possible children
> MAIN.opensuse.xml:15: element abstract: validity error : Element
> abstract content does not follow the DTD, expecting (title? , para+),
> got ()

This means, you haven't inserted neither title nor at least one para.


> MAIN.opensuse.xml:46: element menuchoice: validity error : Element
> menuchoice content does not follow the DTD, expecting (shortcut? ,
> guimenu+), got (guimenu CDATA guimenu)
                          ^^^^^

There is some non-space character between your consecutive guimenus.
Inside menuchoice only other elements are allowed, no text.



> MAIN.opensuse.xml:173: element guimenu: validity error : Element
> guimenu was declared #PCDATA but contains non text nodes

You can't add other elements inside guimenu. Only text is allowed.


> MAIN.opensuse.xml:11: element xref: validity error : Element xref was
> declared EMPTY this one has content

The <xref/> element is empty, neither text nor elements, even spaces are
not allowed. Just use <xref linkend="..."/>


> MAIN.opensuse.xml:482: element xref: validity error : IDREF attribute
> linkend references an unknown ID "ex.welt.zone"
> MAIN.opensuse.xml:578: element xref: validity error : IDREF attribute
> linkend references an unknown ID "sec.basicnet.manconf.hosts"
> MAIN.opensuse.xml:33: element xref: validity error : IDREF attribute
> linkend references an unknown ID "sec.apparmor.start.update"

You need to insert an id attribute into example and section (or sect1,
sect2, ...) elements.


> when I tried to fix them, I found MAIN.opensuse.xml:XX actually does
> not have the error it warned, eg:
> [...]
> I can't see anything wrong.

If I remember correctly, some old xmllint parser couldn't deal with
correct line numbering. Usually this happens when a XML file is
splitted up into different files and the references are resolved later.

Use the "daps bigfile" command. This creates an XML file where
everything is resolved. You can find it under "build/.tmp/". This
makes it a bit easier for debugging.



--
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: PDF creation: element errors

Marguerite Su
Hi, Thomas,

Great appreciated your help!

Can I just create a single pdf for DC-opensuse-startup:

daps --docconfig=DC-opensuse-startup color-pdf bigfile

These errors come from that command.

But the number doesn't match, eg:

/home/marguerite/opensuse-doc/zh_CN/build/.profiled/x86-amd64-em64t_osuse_/MAIN.opensuse.xml:94:
element keycombo: validity error : Element keycombo content does not
follow the DTD, expecting (keycap)+, got

Actually build/.tmp/book.opensuse.startup.xml:94 is:

  <varlistentry>

not the error. even no keycombo in it.


Greetings

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
Hi Marguerite,

On Tue, 21 May 2013 20:21:16 +0800
Marguerite Su <[hidden email]> wrote:

> Can I just create a single pdf for DC-opensuse-startup:
>
> daps --docconfig=DC-opensuse-startup color-pdf bigfile

You can either create the PDF (with the color-pdf subcommand) or
validate and create a bigfile. You can't have both. ;)

Do you use the source from our SVN repository?


> But the number doesn't match, eg:
>
> /home/marguerite/opensuse-doc/zh_CN/build/.profiled/x86-amd64-em64t_osuse_/MAIN.opensuse.xml:94:
> element keycombo: validity error : Element keycombo content does not
> follow the DTD, expecting (keycap)+, got

According to the above error message, you have something like this:

  <keycombo> ... </keycombo>

Unfortunately, you've cut the important part after the "got ..." ;) No
problem, we can deal without it.

However, the DTD expects at least one keycap like this:

  <keycombo>
     <keycap>F2</keycap>
  </keycombo>

Well, one keycap in keycombo doesn't really make sense, so keycombo is
only useful for more than one. The reason for this is, a keycombo
represents a key press of two or more keys. Something like this:

  <keycombo>
     <keycap>Alt</keycap>
     <keycap>F2</keycap>
  </keycombo>


> Actually build/.tmp/book.opensuse.startup.xml:94 is:
>
>   <varlistentry>
>
> not the error. even no keycombo in it.

I know, the numbers can be a pain.

I've looked at the zh_CN source and there seem to be some validation
errors. Usually it's best to run a "daps --docconfig=DC-opensuse-startup
validate" and go through all the error messages.

For example, I got the following validation error (like you):

  nm.xml:78: element menuchoice: validity error : Element menuchoice
  content does not follow the DTD, expecting (shortcut? , guimenu+), got
  (guimenu CDATA guimenu)

That means, it's in the nm.xml file under the subdirectory "xml/".
Unfortunately, you can't rely on the line number. A better(?) approach
could be to first generate the so-called "bigfile" (everything is in
one file) and then validate it again. Something like this:

1. Run "daps --docconfig=DC-opensuse-startup bigfile"
   => Gives you the complete file, saved under
   build/.tmp/book.opensuse.startup.xml

2. Load that file into a editor (Emacs, vi, ...)

3. Validate separately with the command:
   $ xmllint --valid --noout build/.tmp/book.opensuse.startup.xml \
     2> validation-errors.txt

4. Open the validation-errors.txt files and fix the errors step by step.


If I do that, I get same error, but with a correct line number:

  build/.tmp/book.opensuse.startup.xml:37766: element menuchoice:
  validity error : Element menuchoice content does not follow the DTD,
  expecting (shortcut? , guimenu+), got (guimenu CDATA guimenu)
  <guimenu>网络设备</guimenu>⏎ <guimenu>网络设置</guimenu></menuchoice>

If I now open the build/.tmp/book.opensuse.startup.xml file, I can jump
to the respective line.

There is a "⏎ " between each guimenu. That's not allowed, the
stylesheets inserts a character automatically (actually, it's a
different one).

Notice, don't fix the error in the temporary file, fix it in the
original(!) file. If you scroll up to the first section, you see a sect1
element with the id="sec.nm.activate".

Use that information for your grep command to find all the occurances
of this ID:

  $ grep "sec.nm.activate" xml/*.xml

The only file which contains an id=... line is xml/nm.xml. Open that
file, jump to the same structure (line numbers are different!), fix the
problem and validate it again. The error should disappear.



--
Gruß/Regards,
    Thomas Schraitle

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

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
Hi, Thomas,

Thank you very much for the long detailed reply.

These days I gradually fixed all the errors in my xml files.

They mostly comes from typos and transifex ("⏎").

And now I run into a new trouble (maybe a bug of daps or docbook):

It didn't assign a Chinese font.

In the color pdf I generated, all Chinese characters are replaced with "#".

When I fresh install daps (long time ago), I noticed it "recommends" a
font called "FZSongTi".

"FZSongTi" is a commercial font only available to SLE series (we have
a contract with them).

In an openSUSE box, it should be "WenQuanYi Zen Hei" or "WenQuanYi
Micro Hei" unless SuSE wants to share the commercial font with us as
before.

But now even on an openSUSE box with open source Chinese fonts
installed, I stilll get the "#" replacment.

So would you mind where I can find the definition of font-family?

Then maybe I can help fixing the bug (no one noticed that because
there was no Chinese documentation branch before)


Greetings

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
On Mon, May 27, 2013 at 6:05 PM, Marguerite Su <[hidden email]> wrote:
> In the color pdf I generated, all Chinese characters are replaced with "#".

After some searching, I found it's a common problem with fop.

I'll share some infos later.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
fop replace Chinese characters with "#" because it has no metrics for
Chinese fonts.

So I have to make one:

fop -fontmetrics -ttcname "WenQuanYi Zen Hei"
/usr/share/fonts/truetype/wqy-zenhei.ttc ./zh_CN/wqy-zen-hei.xml

Then add the xml to /etc/fop.xconf

<font metrics-url="file:///home/marguerite/opensuse-doc/zh_CN/wqy-zen-hei.xml"
kerning="yes" embed-url="file:///usr/share/fonts/truetype/wqy-zenhei.ttc">
          <font-triplet name="WenQuanYi Zen Hei" style="normal"
weight="normal"/>
          <font-triplet name="WenQuanYi Zen Hei" style="normal" weight="bold"/>

          <font-triplet name="WenQuanYi Zen Hei" style="italic"
weight="normal"/>
          <font-triplet name="WenQuanYi Zen Hei" style="italic" weight="bold"/>
</font>

between <fonts>

Then the tutorial I found tells me to "configure xsl" and set
"body/title/sans/monospace.font.family"

I changed /usr/share/xml/docbook/stylesheet/suse/pocket/fo/fonts.xsl

lines after "The fonts are from the RPM package freefont"

<xsl:param name="body.font.family">
  <xsl:call-template name="genfont">
    <xsl:with-param name="font-family">WenQuanYi Zen Hei</xsl:with-param>
  </xsl:call-template>
</xsl:param>

then `daps --docconfig=DC-opensuse-startup color-pdf

but I get:

五月 27, 2013 8:49:29 下午 org.apache.fop.hyphenation.Hyphenator getHyphenationTree
SEVERE: Couldn't find hyphenation pattern for lang="zh_cn".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
INFO: Rendered page #1.
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "版" (0x7248) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "权" (0x6743) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "所" (0x6240) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "有" (0x6709) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "及" (0x53ca) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "其" (0x5176) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "贡" (0x8d21) not available in font "LiberationSans".
五月 27, 2013 8:49:30 下午 org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "献" (0x732e) not available in font "LiberationSans".

The `Couldn't find hyphenation pattern for lang="zh_cn".` is about
word-wrapping. that's okay.

But the `Glyph "版" (0x7248) not available in font "LiberationSans".`
error seems to tell me that I didn't set font right.

Any ideas?

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
Hi, Thomas,

I did it!

1. pick an open source Chinese font
2. create metrics for it using fop-fontmetrics
3. edit /etc/fop.xconf as mentioned before. (Chinese has no "italic"
so you have to bind it to normal)
4. edit /usr/share/xml/docbook/stylesheet/suse/common/l10n/zh_cn.xml

add "WenQuanYi Micro Hei" and "WenQuanYi Micro Hei Mono" to relevant tags.

now: daps --docconfig=DC-opensuse-startup color-pdf

it works amazing!

And I found a potential bug:

both zh_cn.xml and zh_tw.xml use a "Chinese" and a "ChineseMono" as their fonts.

I don't know if they're alias (I didn't find anything definitions in
/usr/share/xml for them), but if they are real, it will be a bug.
Because there's no actual font named "Chinese". Actually Simplified
Chinese and Tranditional one are totally different in font industry.

And there's also a bug in susedoc:

Because there's no "FZSongTi" available in openSUSE at all.


Can you confirm these? I'm preparing fixes.


Greetings

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
Hi Marguerite,

>
> I did it!

Cool, congratulations!


> 1. pick an open source Chinese font
> 2. create metrics for it using fop-fontmetrics
> 3. edit /etc/fop.xconf as mentioned before. (Chinese has no "italic"
> so you have to bind it to normal)
> 4. edit /usr/share/xml/docbook/stylesheet/suse/common/l10n/zh_cn.xml
>
> add "WenQuanYi Micro Hei" and "WenQuanYi Micro Hei Mono" to relevant
> tags.

Do we have a package for them?

 
> now: daps --docconfig=DC-opensuse-startup color-pdf
>
> it works amazing!

Perfect! Many thanks!

If I'm not mistaken, this is the "old approach" to define and use fonts
in FOP. I had the impression that you don't have to create metrics
files anymore. FOP searches all fonts for you.

Could you try to do the same, but without any metrics? I would propose
to read the following link first:

  http://xmlgraphics.apache.org/fop/1.1/fonts.html

Also make sure to use the correct font name in your FO file, otherwise
it won't work. If your Chinese font contains spaces (like the one
above), you need to put them in single quotes. For example, this could
look like this:

  <fo:inline font-family="FreeSerif,'WenQuanYi Micro Hei',serif">...

If the font name is correct, FOP should find them. To avoid guessing,
better install fontforge (a font editor), load the font, and click the
"Element" > "Font Info..." menu item. There you should see the font
name and family name. I think, you need the string in "Family Name",
but I'm not sure.


> And I found a potential bug:
>
> both zh_cn.xml and zh_tw.xml use a "Chinese" and a "ChineseMono" as
> their fonts.

Ahh, right. This is a mistake.

 
> I don't know if they're alias (I didn't find anything definitions in
> /usr/share/xml for them), but if they are real, it will be a bug.

I think, we can consider it as a bug. :)
This originates from XEP; it allows using alias names and define
the aliases in the XEP configuration file. The advantage of this is,
that you don't have to transform your XML file again and again just to
test another Chinese font. With an alias name, you can just change the
definition.

Unfortunately, this works only for XEP, not FOP. I guess, it was a copy
and paste error.


> Because there's no actual font named "Chinese". Actually Simplified
> Chinese and Tranditional one are totally different in font industry.

Right.


> And there's also a bug in susedoc:
>
> Because there's no "FZSongTi" available in openSUSE at all.
 
These are commercial fonts. As I'm not familiar with Chinese and its
typography, could you recommend a good Chinese font? Preferably open
source. :))

 
> Can you confirm these? I'm preparing fixes.

I think your analysis is correct. Maybe you should try the
configuration without the metrics. They should work as well.

Could you send us your fixes? Just to let you know, tomorrow is a
public holiday in Germany and I'm not here for the next 3 weeks.
Probably one of my collegues will take and submit your patches.


Thanks for your efforts, well done!


--
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: PDF creation: element errors

Marguerite Su
Hi, Thomas,

On Wed, May 29, 2013 at 2:25 PM, Thomas Schraitle <[hidden email]> wrote:
>> add "WenQuanYi Micro Hei" and "WenQuanYi Micro Hei Mono" to relevant
>> tags.
>
> Do we have a package for them?
>

Yes, package name "wqy-microhei-fonts` in OSS, developed at M17N:fonts

> If I'm not mistaken, this is the "old approach" to define and use fonts
> in FOP. I had the impression that you don't have to create metrics
> files anymore. FOP searches all fonts for you.
>
> Could you try to do the same, but without any metrics?

Oh yes, I commented fop.xconf and they still work well.

> I think, we can consider it as a bug. :)
> This originates from XEP; it allows using alias names and define
> the aliases in the XEP configuration file. The advantage of this is,
> that you don't have to transform your XML file again and again just to
> test another Chinese font. With an alias name, you can just change the
> definition.
>
> Unfortunately, this works only for XEP, not FOP. I guess, it was a copy
> and paste error.

I see, then I'll SR a patch to suse-xsl-stylesheets. As they're not on
git, I can just open a ticket on sf.

> These are commercial fonts. As I'm not familiar with Chinese and its
> typography, could you recommend a good Chinese font? Preferably open
> source. :))
>

I recommend wqy-*-fonts.

wqy(文泉驿) is the main open source project for Chinese fonts:

http://wenq.org/wqy2/index.cgi?Home

led by Chinese students in MIT. They provided an easy to use web
interface to create fonts. Every user can contribute, thus their fonts
covered a lot more glyphs than any commerical fonts. BTW, the Chinese
part of Google Droid fonts are based on this project.

Actually modern linux (sles needs to be stable, so it's a little
"old") all use their fonts as default.

And using wqy can avoid the problem that you have to install
"FZSongTi", then openSUSE automatcially set it as your ugly display
font. FZ fonts are used for printing, they didn't display well on
LC/EDs.

> Could you send us your fixes? Just to let you know, tomorrow is a
> public holiday in Germany and I'm not here for the next 3 weeks.
> Probably one of my collegues will take and submit your patches.

Sure. I'll fix suse-xsl-stylesheets and susedoc.

Holiday is the 1st priority, so just enjoy life. fixes can wait.

Greeting

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
Hi Marguerite,

On Wed, 29 May 2013 16:03:24 +0800
Marguerite Su <[hidden email]> wrote:

> > Do we have a package for them?
>
> Yes, package name "wqy-microhei-fonts` in OSS, developed at M17N:fonts

This is good news!

 
> > If I'm not mistaken, this is the "old approach" to define and use
> > fonts in FOP. I had the impression that you don't have to create
> > metrics files anymore. FOP searches all fonts for you.
> >
> > Could you try to do the same, but without any metrics?
>
> Oh yes, I commented fop.xconf and they still work well.

Brilliant! According to the link that I've sent you, FOP 1.1 doesn't
need metrics anymore. So I guess it's better to avoid them altogether.


> > [...] it was a copy and paste error.
>
> I see, then I'll SR a patch to suse-xsl-stylesheets. As they're not on
> git, I can just open a ticket on sf.

Please do. :) We could add that as a requirement/recommendation for the
suse-xsl-stylesheet package.

 
> > These are commercial fonts. As I'm not familiar with Chinese and its
> > typography, could you recommend a good Chinese font? Preferably open
> > source. :))
> >
>
> I recommend wqy-*-fonts.

Good. I guess we need all, right?


> wqy(文泉驿) is the main open source project for Chinese fonts:
>
> http://wenq.org/wqy2/index.cgi?Home
>
> led by Chinese students in MIT. They provided an easy to use web
> interface to create fonts. Every user can contribute, thus their fonts
> covered a lot more glyphs than any commerical fonts. BTW, the Chinese
> part of Google Droid fonts are based on this project.
>
> Actually modern linux (sles needs to be stable, so it's a little
> "old") all use their fonts as default.
>
> And using wqy can avoid the problem that you have to install
> "FZSongTi", then openSUSE automatcially set it as your ugly display
> font. FZ fonts are used for printing, they didn't display well on
> LC/EDs.

Thanks for the information, I didn't know. :)


> > Could you send us your fixes? Just to let you know, tomorrow is a
> > public holiday in Germany and I'm not here for the next 3 weeks.
> > Probably one of my collegues will take and submit your patches.
>
> Sure. I'll fix suse-xsl-stylesheets and susedoc.

You can omit susedoc as this is really too old and we don't support
that anymore. Any fixes should go into daps or suse-xsl-stylesheets
packages now.



> Holiday is the 1st priority, so just enjoy life. fixes can wait.

:-)) Thanks.
If you submit your changes today, I can look at them and approve them.



--
Gruß/Regards,
    Thomas Schraitle

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

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
In reply to this post by Marguerite Su
Hi Marguerite,

> [...]
> Holiday is the 1st priority, so just enjoy life. fixes can wait.

Sorry, I forgot to add:

If it doesn't create you too much hassle for you, could you create the
patch from our SVN repository, if possible?
As we are upstream we could apply this patch directly and create a new
package in OBS.
Or just send me the files that you've changed by mail and I will
integrate that into our SVN.

Checkout or update from http://svn.code.sf.net/p/daps/svn/trunk/daps

Thanks!

--
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: PDF creation: element errors

Marguerite Su
In reply to this post by Thomas Schraitle-3
Hi, Thomas,

>> Oh yes, I commented fop.xconf and they still work well.
>
> Brilliant! According to the link that I've sent you, FOP 1.1 doesn't
> need metrics anymore. So I guess it's better to avoid them altogether.
>

Yes, then we just have to fix suse-xsl-stylesheets, XD.

SR 176918 and SR 176919 were just sent.


>> I see, then I'll SR a patch to suse-xsl-stylesheets. As they're not on
>> git, I can just open a ticket on sf.
>
> Please do. :) We could add that as a requirement/recommendation for the
> suse-xsl-stylesheet package.
>

I just sent the SRs, now still a ticket with the patch upstream?
(seems we're upstream)

>> I recommend wqy-*-fonts.
>
> Good. I guess we need all, right?

Nope. Just wqy-microhei-fonts will be enough. We have all in M17N:fonts.

>
> You can omit susedoc as this is really too old and we don't support
> that anymore. Any fixes should go into daps or suse-xsl-stylesheets
> packages now.

Oh sorry I hit send before I see this...feel free to reject...

>> Holiday is the 1st priority, so just enjoy life. fixes can wait.
>
> :-)) Thanks.
> If you submit your changes today, I can look at them and approve them.
>

DONE.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
In reply to this post by Thomas Schraitle-3
Hi, Thomas,

On Wed, May 29, 2013 at 4:25 PM, Thomas Schraitle <[hidden email]> wrote:
> If it doesn't create you too much hassle for you, could you create the
> patch from our SVN repository, if possible?

Sure I can.

> Checkout or update from http://svn.code.sf.net/p/daps/svn/trunk/daps

Doing.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
In reply to this post by Marguerite Su
Hi Marguerite,

On Wed, 29 May 2013 16:45:25 +0800
Marguerite Su <[hidden email]> wrote:

> [...]
> Yes, then we just have to fix suse-xsl-stylesheets, XD.
>
> SR 176918 and SR 176919 were just sent.
 
I've just accepted both.


> [...]
> I just sent the SRs, now still a ticket with the patch upstream?
> (seems we're upstream)

Yes, we are. :)


> >> I recommend wqy-*-fonts.
> >
> > Good. I guess we need all, right?
>
> Nope. Just wqy-microhei-fonts will be enough. We have all in
> M17N:fonts.

Ok, perfect!


> > You can omit susedoc as this is really too old and we don't support
> > that anymore. Any fixes should go into daps or suse-xsl-stylesheets
> > packages now.
>
> Oh sorry I hit send before I see this...feel free to reject...

No problem. I'll integrate your patch into our SVN.

Just one question: The font name contains spaces. Does it still work if
you quote them with single quotes?


--
Gruß/Regards,
    Thomas Schraitle

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

Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Marguerite Su
Hi, Thomas,

> No problem. I'll integrate your patch into our SVN.
>

Patch for svn attached. patch -p1 in the svnroot.

> Just one question: The font name contains spaces. Does it still work if
> you quote them with single quotes?

Yes. this patch for svn has single quotes, XD.

Marguerite

daps-fop-chinese.patch (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PDF creation: element errors

Thomas Schraitle-3
Hi,

> > No problem. I'll integrate your patch into our SVN.
> >
>
> Patch for svn attached. patch -p1 in the svnroot.

Many thanks! Great! :))


> > Just one question: The font name contains spaces. Does it still
> > work if you quote them with single quotes?
>
> Yes. this patch for svn has single quotes, XD.

Ok, applied and committed.

I will release another package after lunch. ;)


--
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: PDF creation: element errors

Thomas Schraitle-3
In reply to this post by Marguerite Su
Hi,

> [...]
> > No problem. I'll integrate your patch into our SVN.
> >
>
> Patch for svn attached. patch -p1 in the svnroot.
>
> > Just one question: The font name contains spaces. Does it still
> > work if you quote them with single quotes?
>
> Yes. this patch for svn has single quotes, XD.

OBS contains now version 1.9.21 of the suse-xsl-stylesheets in the
Documentation:Tools repository. If you want to give it a try, please
update to the latest version.

Many thanks for your contribution!


--
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]