Re: [libreoffice-l10n] beta2 - media wiki text doesn't show translation
2011/12/28 Lior Kaplan kaplanl...@gmail.com: On Fri, Dec 23, 2011 at 1:56 AM, Mihkel Tõnnov mihh...@gmail.com wrote: Hi Lior, *, 2011/12/23 Lior Kaplan kaplanl...@gmail.com Hi, For Beta2 Hebrew had 100% for the media wiki extension, and while testing writer I see the media wiki dialogs in English. Could someone text for other languages ? The same with Estonian and also the key-ID build. Andras, is this issue known and will be taken care of ? All extensions built with gbuild have localization problems. Hopefully they can be fixed in next betas or RCs. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] l10n bugs to fix for LibreOffice 3.5.0 beta3
On 20/12/2011, at 2:59 AM, Andras Timar wrote: Hi, Today I exported updated po files from Pootle and pushed them to git to the translations module. The next push will take place three weeks from, for LibreOffice 3.5.0 beta3. Meanwhile, could you all please fix bugs in your translations? :) Fatal errors: de eo eu fi nl pt pt-BR tr vi I corrected them in git as I could, but please correct them in Pootle, too. Non-fatal errors: bg cs da de en-GB eo eu fi ne nl pl pt-BR pt ru sk tr vi Log files (from all tools) and error files (from gsicheck tool): http://dev-www.libreoffice.org/l10n/errorlog/ Hi Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters. For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err: vidigi la alÅutitan vikipaÄon should be vidigi la alŝutitan vikipaĝon Donald -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] l10n bugs to fix for LibreOffice 3.5.0 beta3
Hi, 2011/12/28 Donald Rogers donr2...@clear.net.nz On 20/12/2011, at 2:59 AM, Andras Timar wrote: Hi, Today I exported updated po files from Pootle and pushed them to git to the translations module. The next push will take place three weeks from, for LibreOffice 3.5.0 beta3. Meanwhile, could you all please fix bugs in your translations? :) Fatal errors: de eo eu fi nl pt pt-BR tr vi I corrected them in git as I could, but please correct them in Pootle, too. Non-fatal errors: bg cs da de en-GB eo eu fi ne nl pl pt-BR pt ru sk tr vi Log files (from all tools) and error files (from gsicheck tool): http://dev-www.libreoffice.org/l10n/errorlog/ Hi Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters. For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err: vidigi la alÅ utitan vikipaÄ on should be vidigi la alŝutitan vikipaĝon It’s shown correctly here. Your browser/text-editor probably chooses the wrong encoding -- I got the result you described when I manually set the encoding to ISO 8859-1 (i.e. Western European), UTF-8 displayed everything fine. Best regards, Mihkel -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] l10n bugs to fix for LibreOffice 3.5.0 beta3
Hi Donald, On Wed, Dec 28, 2011 at 8:37 PM, Donald Rogers donr2...@clear.net.nz wrote: Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters. They are. For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err: vidigi la alÅ utitan vikipaÄ on should be vidigi la alŝutitan vikipaĝon Make sure your browser uses the UTF-8 charset to display the file. As it is a plain textfile and no html file, the browser is not told explicitly what charset to use, so it uses whatever is configured as the default charset in the browser. ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] l10n bugs to fix for LibreOffice 3.5.0 beta3
On 29/12/2011, at 9:17 AM, Mihkel Tõnnov wrote: Hi, 2011/12/28 Donald Rogers donr2...@clear.net.nz On 20/12/2011, at 2:59 AM, Andras Timar wrote: Hi, Today I exported updated po files from Pootle and pushed them to git to the translations module. The next push will take place three weeks from, for LibreOffice 3.5.0 beta3. Meanwhile, could you all please fix bugs in your translations? :) Fatal errors: de eo eu fi nl pt pt-BR tr vi I corrected them in git as I could, but please correct them in Pootle, too. Non-fatal errors: bg cs da de en-GB eo eu fi ne nl pl pt-BR pt ru sk tr vi Log files (from all tools) and error files (from gsicheck tool): http://dev-www.libreoffice.org/l10n/errorlog/ Hi Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters. For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err: vidigi la alÅ utitan vikipaÄ on should be vidigi la alŝutitan vikipaĝon It’s shown correctly here. Your browser/text-editor probably chooses the wrong encoding -- I got the result you described when I manually set the encoding to ISO 8859-1 (i.e. Western European), UTF-8 displayed everything fine. Thanks, Mihkel and Christian. I should have thought of that. Donald -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] compound strings
Hi Milos, Martin, *, 2011/12/29 Martin Srebotnjak mi...@filmsi.net: 2011/12/28 Martin Srebotnjak mi...@filmsi.net 2011/12/28 Milos Sramek sramek.mi...@gmail.com Hi, I have in the new Header/Footer feature of 3.5 for the first time noticed compound strings consisting of two separately translated strings. For example, Format Header is composed of strings Format (KeyId _XDs) and Header (b4n3). Slovak (and other languages) have cases - the Header word must be in the accusative case here. Are we sure that the b4n3 Header string is used only in such context and not in other, where for example, the nominative case should be used? I would prefer to not to compound strings of other strings. What do you think about that? Can we send this message to the developers? Hi, I haven't noticed that, this should be marked, explained in notes, if sdf had those... Will check, but why is this not a single string? Does that mean that also Format Footer is formed from two strings? This is unacceptable and anglo-saxon-centric, really does not work well for other languages. OMG, now I saw it, this is horrible - each context menu command must be a separate string, you cannot format context menu commands in the same manner for 100+ languages! Thanks, Milos, for noticing this. See also this thread: http://listarchives.libreoffice.org/global/l10n/msg03406.html I agree that composing strings in such a manner is not okay, and should it become a habit with the devs, it's a disaster waiting to strike. Another such case: 7yKt + btRK = Insert + Rows 7yKt + xGzB = Insert + Columns (make a table in Writer, right-click in it, choose Row - Insert or Column - Insert, and behold the dialog title.) I'm not sure if there are more. Greetings, Mihkel The Estonian team -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] compound strings
On 29/12/2011, at 2:52 PM, Mihkel Tõnnov wrote: Hi Milos, Martin, *, 2011/12/29 Martin Srebotnjak mi...@filmsi.net: 2011/12/28 Martin Srebotnjak mi...@filmsi.net 2011/12/28 Milos Sramek sramek.mi...@gmail.com Hi, I have in the new Header/Footer feature of 3.5 for the first time noticed compound strings consisting of two separately translated strings. For example, Format Header is composed of strings Format (KeyId _XDs) and Header (b4n3). Slovak (and other languages) have cases - the Header word must be in the accusative case here. Are we sure that the b4n3 Header string is used only in such context and not in other, where for example, the nominative case should be used? I would prefer to not to compound strings of other strings. What do you think about that? Can we send this message to the developers? Hi, I haven't noticed that, this should be marked, explained in notes, if sdf had those... Will check, but why is this not a single string? Does that mean that also Format Footer is formed from two strings? This is unacceptable and anglo-saxon-centric, really does not work well for other languages. OMG, now I saw it, this is horrible - each context menu command must be a separate string, you cannot format context menu commands in the same manner for 100+ languages! Thanks, Milos, for noticing this. See also this thread: http://listarchives.libreoffice.org/global/l10n/msg03406.html I agree that composing strings in such a manner is not okay, and should it become a habit with the devs, it's a disaster waiting to strike. Another such case: 7yKt + btRK = Insert + Rows 7yKt + xGzB = Insert + Columns (make a table in Writer, right-click in it, choose Row - Insert or Column - Insert, and behold the dialog title.) I'm not sure if there are more. Yes, the same happens in the Esperanto version. It does not even put a space between the two words, and the case of the second is wrong (naturally). On the other hand, is this a mechanism for developers to save us lots of work, retranslating the same strings over and over, e.g. OK, Cancel? Donald -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
