'Re: kde-info2html: can't translate messages'

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

List:       kde-i18n-doc
Subject:    Re: kde-info2html: can't translate messages
From:       Burkhard =?utf-8?q?L=C3=BCck?= <lueck () hube-lueck ! de>
Date:       2010-08-31 20:13:23
Message-ID: 201008312213.23802.lueck () hube-lueck ! de
[Download RAW message or body]

Am Dienstag, 31. August 2010, um 20:22:00 schrieb Marta Rybczynska:
> On 31/08/10 20:44, Albert Astals Cid wrote:
> > A Dimarts, 31 d'agost de 2010, Marta Rybczynska va escriure:
> >> On 30/08/10 23:15, Albert Astals Cid wrote:
> >>> As far as i know, the info kioslave just shows in a html form what the
> >>> info command line utility returns, so you'd have to look how info pages
> >>> are translated (no idea if that is even possible).
> >>> 
> >>> Albert
> >> 
> >> I understand this. But what about the pages that are internally
> >> generated inside that script (not using anything from info)?
> > 
> > Are there any of these? Can you give an example?
> > 
> > Albert
> > 
> >> Marta
> 
> Sure.
> http://websvn.kde.org/trunk/KDE/kdebase/runtime/kioslave/info/kde-info2html
> ?revision=1055438&view=markup from line 96. You get it when you type
> something like info:blah in Dolphin's or Konqueror's address bar:
> 96 <head>
> 97 $STYLESHEET_KDE
> 98 <title>Info: (no page found)</title>
> 99 </head>
> 100 <body>
> 101 <h1>KDE Info Pages Viewer Error</h1>
> 102 No info page for topic <code>"$FileName"</code> found.<br>
> 103 You may find what you are looking for at the <a
> href="man:$FileName">$FileName manpage</a>.
> 104 </body>
> 
The man kioslave has similar (translatable) messages, but that is completely 
written in C++ using i18n calls.

-- 
Burkhard Lück

[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic