Hi Dwayn and Samuel --

Thanks for your kind responses.  You are not the first to tell me to
slow down and really say what I mean.  My wife, if she were privy to
this conversation, would be saying: See?? I'm not the *only* one who's
complaining about this. :)

So, let me try again.

- It sounds like you have the ability to do the abbreviation support in
terms of associating them with a particular phrase.

- String length cap: What I was trying to say is that it would be nice
to be able to allow a translation vendor access to the screens that the
strings will appear in, so that they can visually verify that the
translated strings will fit.  There are two criteria here, I think.

- Keeping track of where a string is used.

Regards,
 
Paul E. Ourada
Principal Software Engineer
Covidien
Energy-based Devices
5920 Longbow Dr
Boulder, CO 80301
USA
Office: 303-581-6940
[EMAIL PROTECTED]
http://www.covidien.com
 
> -----Original Message-----
> From: [EMAIL PROTECTED]
[mailto:translate-
> [EMAIL PROTECTED] On Behalf Of Samuel Murray
> Sent: Tuesday, October 23, 2007 6:14 AM
> To: translate-pootle
> Subject: Re: [translate-pootle] Embedded Systems Support? Or the rest
of
> the story...
> 
> 
> G'day Dwayne and Paul
> 
> I'm not a programmer or a Pootle expert, but here are my thoughts.
> Paul's introductory e-mail was a little cryptic for me, but I hope
> Dwayne's interpretation of it is correct.  If not, please tell.
> 
> Dwayne Bailey het geskryf:
> 
> > On Mon, 2007-10-22 at 17:51 -0400, Ourada, Paul wrote:
> 
> >> - abbreviation support: in embedded systems we tend to have
> >> fixed text fields, so translators often have to come up with
> >> abbreviations in various languages.
> 
> > I assume what you really mean is that the system should limit the
entry
> > to N characters?  We don't do that, its never emerged as a
requirement
> > in the non-embedded world, so its never been coded.
> 
> I have encountered this in the translation of user interfaces for cell
> phones and medical auxiliary equipment.  I have also had this in the
> mobile edition of Opera web browser.  There is a limit on the text
> length and it would be great if a Pootle user can be alerted of it.
> 
> The Pootle UI is HTML/JavaScript, and there are free JavaScript
scripts
> that count the characters in a text box in real time.  The character
> count of the source text can be handled by pocount, not?  So all you
> need is some kind of comparison, and perhaps a counter box that turns
> red if the one exceeds the other.
> 
> As for pofilter... isn't there a way to check the msgid char length
> against the msgstr char length?  Dwayne?  Can a smart regex do this
with
> the existing pofilter?
> 
> >> - about those fixed fields: font and screen support: it would
> >> be really really nice to be able to hand a list of words/phrases to
be
> xlated along with a
> >> tool which would render those xlations into a bitmap of the target
> screen/popup/window
> >> in a pre-determined font.
> 
> > Its the... tool which would... that is missing here.  Since the
> > translations are platform agnostic you would need a tool for each
> > toolkit that could render the results.
> 
> This is the way I also see it.
> 
> The current workflow in Pootle is:
> 
> Vendor format -> (POT) -> PO.
> 
> In other to show how the translation looks in the app, you'd need to
do
> the following for each segment:
> 
> PO -> (pomerge) -> Vendor format -> vendor format resource viewer
> 
> In other words, it won't be impossible, but it would have to work on a
> vendor format specific basis and you'd need a resource viewer that can
> already convert the vendor format string into a screenshot of it.
> 
> >> - more about abbreviation support: the abbreviations would be
> >> associated with a particular word or phrase.
> 
> > Well the terminology lists that we currently support can easily be
used
> > for that.
> 
> What would be nice would be some way to add to the glossaries from
> within Pootle, so that users who create abbreviations can add them to
> the glossary.
> 
> There is currently no pofilter that checks to see if a word occurs in
> the source, that a certain other word must occur in the target.  Such
a
> check would be great (also for checking correct usage of terminology).
> 
> >> - String usage:  it would be useful to have a way to keep track
> >> of where a particular word or phrase was used.
> 
> > We don't do that now.
> 
> True, but can't you use pogrep to get a list of strings where the term
> occurs, and check the comments of those strings to get some sort of
clue
> about where they were used?
> 
> Samuel
> 
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Translate-pootle mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/translate-pootle

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle

Reply via email to