List Info

Thread: Welcome Page Localization Patch
Welcome Page Localization Patch
user name
 2006-11-27 12:04:51 

  


  

    
> Support for different types of files is kind of harcoded in intltool, so
> for .cs files it will look for GetString, but it won't do the same for
> xsl files. I'm not an expert in intltool, but I don't think that can be
> changed.
>
> Lluis. 

I posted an email on the intltool mailing list asking for help on this issue, and if it is possible to extract GetStrings from an Xsl file. Waiting to hear back from them, and will report back on this issue.

Another possible way of solving this problem would be to generate an Xml file containing all the text that needs to be translated, and merge this xml with the
 generated xml that contains the history and etc. This will allow us to use intltool-update to extract the phrases that needs to be translated, but still use the Extension Object to display the correct string for the current language at runtime. I'll work on getting this working in the meantime.

Any thoughts, suggestions on other work arounds?

Gideon



		
 
All New Yahoo! Mail – Tired of Vigr! come-ons? Let our SpamGuard protect you.		
  

  
  
   
     
    

  

    Welcome Page Localization Patch
  


  

     user name

     2006-11-27 13:00:38
  


  

    
Gideon de Swardt escribió:
> I posted an email on the intltool mailing list asking
for help on this 
> issue, and if it is possible to extract GetStrings from
an Xsl file. 
> Waiting to hear back from them, and will report back on
this issue.

But an XSL file is also an XML file. Doesn't it work with
adding the 
file to POTFILES and adding the attribute
"translatable" (as the glade 
files have) in the tag that contains the localizable string?

Regards,

	Andrés	[ knocte ]

-- 

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st


  


  

    
  

  
  
   
     
    

  

    Welcome Page Localization Patch
  


  

     user name

     2006-11-27 13:17:14
  


  

    
The problem is: in which xml namespace the 'translatable'
attribute
should go, for it to be recognized by intltool and still
work as xslt?
Some step may force schema/dtd validation on the xslt and
can break on
extended attributes.

I would prefer to create a simple tool that extracts the
translatable
strings from the xslt and insert/update them directly in the
.pot file
after it is updated by intltool and before it is further
processed.

Fun,

On 11/27/06, "Andrés G. Aragoneses [ knocte ]"
<knoctegmail.com> wrote:
> Gideon de Swardt escribió:
> > I posted an email on the intltool mailing list
asking for help on this
> > issue, and if it is possible to extract GetStrings
from an Xsl file.
> > Waiting to hear back from them, and will report
back on this issue.
>
> But an XSL file is also an XML file. Doesn't it work
with adding the
> file to POTFILES and adding the attribute
"translatable" (as the glade
> files have) in the tag that contains the localizable
string?
>
> Regards,
>
>         Andrés  [ knocte ]
>
> --
>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
>


-- 
Rafael "Monoman" Teixeira
---------------------------------------
"The reasonable man adapts himself to the world; the
unreasonable one
persists in trying to adapt the world to himself. Therefore
all
progress depends on the unreasonable man." George
Bernard Shaw
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st


  


  

    
  

  
  
   
     
    






 [1-3]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )