[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: Translation issues with the calligraplan documentation
From:       Dag <danders () get2net ! dk>
Date:       2020-03-26 8:57:25
Message-ID: 45a2d494a5a25c2c31aed13d926b0ce2 () get2net ! dk
[Download RAW message or body]

I have adjusted the structure so now xml2po extracts all texts, at
least. 

Haven't tested if xml2po works. 

Also noted there are problems with keycode/keycap, but let's see if my
changes is enough to generate translated docs.

---
Cheers, Dag 

Luigi Toscano skrev den 2020-03-24 23:33:

> Hi,
> 
> it seems that the translations system does not work with the calligraplan
> documentation. I believe the problem is connected with the way the split is
> done: only the first top-level tag in each document is extract. If I remember
> correctly we hit this problem in the past and we ended up with restructing the
> documentation, but I can't investigate right now.
[Attachment #3 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" \
/></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'> <p>I \
have adjusted the structure so now xml2po extracts all texts, at least.</p> \
<p>Haven't tested if xml2po works.</p> <p>Also noted there are problems with \
keycode/keycap, but let's see if my changes is enough to generate translated \
docs.</p> <div>---<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Cheers, \
Dag</div> </div>
<p>Luigi Toscano skrev den 2020-03-24 23:33:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; \
margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored --> <div \
class="pre" style="margin: 0; padding: 0; font-family: monospace">Hi,<br /> <br /> it \
seems that the translations system does not work with the calligraplan<br /> \
documentation. I believe the problem is connected with the way the split is<br /> \
done: only the first top-level tag in each document is extract. If I remember<br /> \
correctly we hit this problem in the past and we ended up with restructing the<br /> \
&nbsp;documentation, but I can't investigate right now.</div> </blockquote>
</body></html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic