[Etoys-notify] [JIRA] Updated: (SQ-75) Context comment in POs too long for Pootle

[jira at immuexa.com]

     [ http://tracker.immuexa.com/browse/SQ-75?page=all ]

Scott Wallace updated SQ-75:
----------------------------

    Fix Version: M2: second alpha (june)
                     (was: triage)

> Context comment in POs too long for Pootle
> ------------------------------------------
>
>          Key: SQ-75
>          URL: http://tracker.immuexa.com/browse/SQ-75
>      Project: squeakland
>         Type: Improvement
>   Components: etoys
>     Reporter: team
>     Priority: Eventual
>      Fix For: M2: second alpha (june)

>
>
> From TRAC 5135 (korakurider)
> gettext exporter of EToys sometimes generate very long context comment because of the format that exporter assumes (only one line even with multiple occurrences) Pootle decides column width of online editor simply by the longest information in the first column, so screen layout become very ugly and difficult to use for some phrases.
> Maybe we can work around by adjusting format with one comment line for each occurrence.
> (xavi) s far as I can tell, this is a browser issue not Pootle.
> http://lists.laptop.org/pipermail/etoys/2007-November/001559.html
> Using a comma-space (', ') separator between each of the 'sources' in the comment string would allow the browsers do a better job when dealing with long-continuous lines. IOW, I don't think it's necessary to tweak the extractor to generate multi-line, length limited comments.
> (korakurider) Original motivation to omit white spaces in comment (and replace them with underscore) was that "gettext tool might replace a space to a new line some times, and it makes difficult to take a diff". (excerpts from squeak code comment: maybe Takashi experienced that...) So I still think multi-line format would be better for real use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://tracker.immuexa.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira