Re: [Libreoffice] Nonsense comments?

2011-03-01 Thread Christina Roßmanith

To summarize:

Andras isn't interested in keeping the comments.
Christian could tell the meaning of '~'.
Nobody votes for keeping the ACHTUNG/ATTENTION comments. So I conclude, 
we can start to remove them. I guess they aren't of any help if gettext 
might be used someday?!?


Christina

Am 28.02.2011 16:37, schrieb Andras Timar:

2011/2/28 Christina Roßmanithchrrossman...@web.de:

Hi,

I admit, I can't follow the discussion. But during translation: are the '~'
important?

Some lines of a diff for translation of comments:

-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
~Grafik kopieren */
-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
~Grafik kopieren */
-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
~Grafik kopieren */
+/* ### ATTENTION: new text in resource? copy graphic : copy
graphic */
+/* ### ATTENTION: new text in resource? copy graphic : copy
graphic */
+/* ### ATTENTION: new text in resource? copy graphic : copy
graphic */

And it seems that there is a certain redundancy. Or is it important to keep
three copies of the same line. Is ACHTUNG a keywort which is searched for?
Or is it safe to translate it to ATTENTION?

Thank you for any low-level explanation  :-)

Hi,

I don't think we need /* ### ACHTUNG: comments at all in resource
files. Probably they were inserted by a script long time ago, when the
source language was German. They do not look useful now. They can be
removed.

Just my 2 cents...

Cheers,
Andras
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Nonsense comments?

2011-02-28 Thread Christina Roßmanith

Hi,

I admit, I can't follow the discussion. But during translation: are the 
'~' important?


Some lines of a diff for translation of comments:

-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren : ~Grafik 
kopieren */
-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren : ~Grafik 
kopieren */
-/* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren : ~Grafik 
kopieren */
+/* ### ATTENTION: new text in resource? copy graphic : copy 
graphic */
+/* ### ATTENTION: new text in resource? copy graphic : copy 
graphic */
+/* ### ATTENTION: new text in resource? copy graphic : copy 
graphic */

And it seems that there is a certain redundancy. Or is it important to 
keep three copies of the same line. Is ACHTUNG a keywort which is 
searched for? Or is it safe to translate it to ATTENTION?


Thank you for any low-level explanation  :-)

Christina

Am 27.02.2011 10:27, schrieb Andras Timar:

Hi,

2011/2/25 Caolán McNamaracaol...@redhat.com:

On Fri, 2011-02-25 at 20:37 +0100, Christina Roßmanith wrote:
timar: po files can have translator-comments in them to help translators
about ambiguous terms/words, while the .src/.sdf format doesn't though,
right ? I recall a problem with trying to get the Spanish translation of
an obscure paper size (8.5 x 13 ) set as Oficio given that this
paper size is known as that in the handful of Latin American nations
that use it, rather than some literal Spanish translation of Long Bond
as the size is known in e.g. the Philippines. Would it be helpful to
have a medium-level hack to add translator-comment support to the
translation tools to help flag that sort of thing ?

In fact it is possible to add comments to strings, there is the
special language code x-comment. Alas, it is not extracted to SDF so
it is not very useful for translators. It would be helpful, if it
worked.

Best regards,
Andras
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Nonsense comments?

2011-02-28 Thread Andras Timar
2011/2/28 Christina Roßmanith chrrossman...@web.de:
 Hi,

 I admit, I can't follow the discussion. But during translation: are the '~'
 important?

 Some lines of a diff for translation of comments:

 -            /* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
 ~Grafik kopieren */
 -            /* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
 ~Grafik kopieren */
 -            /* ### ACHTUNG: Neuer Text in Resource? Grafik ~kopieren :
 ~Grafik kopieren */
 +            /* ### ATTENTION: new text in resource? copy graphic : copy
 graphic */
 +            /* ### ATTENTION: new text in resource? copy graphic : copy
 graphic */
 +            /* ### ATTENTION: new text in resource? copy graphic : copy
 graphic */

 And it seems that there is a certain redundancy. Or is it important to keep
 three copies of the same line. Is ACHTUNG a keywort which is searched for?
 Or is it safe to translate it to ATTENTION?

 Thank you for any low-level explanation  :-)

Hi,

I don't think we need /* ### ACHTUNG: comments at all in resource
files. Probably they were inserted by a script long time ago, when the
source language was German. They do not look useful now. They can be
removed.

Just my 2 cents...

Cheers,
Andras
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice] Nonsense comments?

2011-02-25 Thread Christina Roßmanith

Hi,

while reviewing a patch I came across a lot of comments like

CheckBox CB_USE_PASSWD
{
/* ### ATTENTION: New text in resource? ~password : ~password */
Text [ en-US ] = ~Password ;
};

String STR_LINKEDIT_TEXT
{
/* ### ATTENTION: New text in resource? edit links : edit links */
Text [ en-US ] = Edit links ;
};

The message doesn't sound very exciting - so why all those ATTENTION? 
I'd suggest to remove the comments. It always follows the pattern


/* ### ATTENTION: New text in resource? msg : msg */
Text [ en-US ] = msg ;


One of these messages is Subpoints per level which should be subitems. 
May I change this (sw/source/ui/dialog/abstract.src)?


Christina Rossmanith
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Nonsense comments?

2011-02-25 Thread Caolán McNamara
On Fri, 2011-02-25 at 20:37 +0100, Christina Roßmanith wrote:
 I'd suggest to remove the comments. It always follows the pattern

Seems reasonable, though this reminds me...

timar: po files can have translator-comments in them to help translators
about ambiguous terms/words, while the .src/.sdf format doesn't though,
right ? I recall a problem with trying to get the Spanish translation of
an obscure paper size (8.5 x 13 ) set as Oficio given that this
paper size is known as that in the handful of Latin American nations
that use it, rather than some literal Spanish translation of Long Bond
as the size is known in e.g. the Philippines. Would it be helpful to
have a medium-level hack to add translator-comment support to the
translation tools to help flag that sort of thing ?

 One of these messages is Subpoints per level which should be subitems. 

FWIW, this connects to file-send-create autoabstract/autoabstract to
presentation. e.g. source document of heading 1, followed by three
paragraph of foo, file-send-autoabstract to presentation, 1 subpoint
per level ends up with heading 1 with the first foo turned into a
subpoint of the heading 1. Subitems doesn't really grab me, while
subpoint sort of fits the output presentation. Don't really have an
opinion, but at least this is the dialog it appears in.

C.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Nonsense comments?

2011-02-25 Thread Pierre-André Jacquod
On 02/25/2011 09:46 PM, Caolán McNamara wrote:

 po files can have translator-comments in them to help translators
 about ambiguous terms/words, while the .src/.sdf format doesn't though,
translation with gettext would support this with comment using key-words
/ tags. Key words are configurable, maybe a convention has been set with
### as marker...

 right ? I recall a problem with trying to get the Spanish translation of
 an obscure paper size (8.5 x 13 ) set as Oficio given that this

with gettext, it would be roughly something like
coding in file.cxx:
/* TRANSLATORS paper size (8.5 x 13 ) */
printf(Long Bond);

with xgettext --add-comments TRANSLATORS
the po-file for this language would then looks (after translation) like

#. paper size (8.5 x 13 )
#src: file.cxx 123
msgid Long Bond
msgstr Oficio


in crazy idea to go to gettext, when really time available : -)
regards
Pierre-André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice