Re: [libreoffice-l10n] emoji uniqueness?

[Németh László]

Hi,

Yes, we need unique keywords. Fortunately, there are only a few duplicates.
Unfortunately, there is no Pootle integration yet, but the update script
found the following ones:

Languages:

duplicate_emoji_bg.txt
duplicate_emoji_ca.txt
duplicate_emoji_da.txt
duplicate_emoji_de.txt
duplicate_emoji_es.txt
duplicate_emoji_fi.txt
duplicate_emoji_fr.txt
duplicate_emoji_hr.txt
duplicate_emoji_hu.txt
duplicate_emoji_it.txt
duplicate_emoji_nl-BE.txt
duplicate_emoji_nl.txt
duplicate_emoji_pt-BR.txt
duplicate_emoji_pt.txt
duplicate_emoji_ro.txt
duplicate_emoji_ru.txt

Words:

== duplicate_emoji_bg.txt =
внимание
телефон
слънце
овен
не
мъж
жена
целувка2
гняв
изчервяване
== duplicate_emoji_ca.txt =
telèfon
fi
no
== duplicate_emoji_da.txt =
advarsel
telefon
glimmer
sol
blomst
is
flag
flag2
fodbold
kylling
mand
kvinde
pære
mappe
diagram
højtaler
nøgle
== duplicate_emoji_de.txt =
Hermesstab
Gewitter
Wal
Faust
Smiley erleichtert
Baby
== duplicate_emoji_es.txt =
caduceo
teléfono
fi
negra
corchea
Tierra
flor
fútbol
no
linterna
sonrisa
== duplicate_emoji_fi.txt =
risti
risti2
puhelin
pata
nuotit
ei
hymy
== duplicate_emoji_fr.txt =
petit carré noir
téléphone
cœur
soleil
fleur
trèfle
riz
étincelle
casque
sac-à-main
empreintes
mariage
livre
portable
caméra
haut-parleur
grimace
sourire
bisou
colère
grimaçant
== duplicate_emoji_hr.txt =
jota
== duplicate_emoji_hu.txt =
növény
== duplicate_emoji_it.txt =
lira
caduceo
telefono
Luna
Luna2
Sole
fiore
== duplicate_emoji_nl-BE.txt =
geen deelverzameling
waarschuwing
telefoon
vijfhoek
wassende maan
wassende maan
rijst
voetbal
beer
vuist
huwelijk
notitie
telefoon
sleutel
lachend
duizelig
lachende kat
tram
vrachtwagen
kabelbaan
toilet
== duplicate_emoji_nl.txt =
geen deelverzameling
waarschuwing
telefoon
vijfhoek
wassende maan
wassende maan
rijst
voetbal
beer
vuist
huwelijk
notitie
telefoon
sleutel
lachend
duizelig
lachende kat
tram
vrachtwagen
kabelbaan
toilet
== duplicate_emoji_pt-BR.txt =
espadas
caduceu
telefone
fi
semínima
colcheia
lua cheia
flor
sorvete
futebol
não
casamento
sorriso
diabinho
beijo
franzido
choroso
tonto
== duplicate_emoji_pt.txt =
espadas
telefone
estrela
fi
lua cheia
sol
flor
não
casamento
câmara de vídeo
sorriso
diabinho
beijo
zangado
franzido
angustiado
choroso
boca aberta
== duplicate_emoji_ro.txt =
liră
triunghi dreptunghic
pătrat mic
== duplicate_emoji_ru.txt =
телефон
трава


The update script doesn't fix automatically these duplicates, only the
second (third etc) occurrences of the same keyword are ignored. If you add
a number to the keyword, the next update will add the missing characters to
the replacement tables.

Many thanks for the great translations and your question!

Best regard,
László






2015-07-20 0:56 GMT+02:00 Donald Rogers :

> Does each emoji string have to be unique? (I suppose so).
> Is there an automated test for uniqueness that will show up in the "Fix
> critical errors" column?
> The reason that I ask is that some of the English terms are so similar in
> meaning that I may have translated them to the same thing. I may need to
> add a digit to one of them.
>
> Regards
> Donaldo
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@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
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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

[libreoffice-l10n] resolving emoji short name conflicts with time format

[Németh László]

Hi,

I have changed the bad

:1:
:2:
...
:12:

en-US emoji short names to

:1 h:
:2 h:
...
:12 h:

ones. After pushing the related commit
(https://gerrit.libreoffice.org/#/c/28756/3), it will be possible to
translate the new short names for the master branch, keeping this
international standard form in the translation, or giving better ones,
if they exist in your languages (for example, using :12.00: instead of
:12 h:)

(In libreoffice-5-2, possibly in the affected older branches the
clockface emoji replacements will be removed completely to solve their
conflict with time format, see
https://bugs.documentfoundation.org/show_bug.cgi?id=97191)

Please, avoid of the usage of middle colon in the translations. This
is exactly the ISO 8601 time format standard, but it doesn't work in
LibreOffice. For example, do not use "12:00" as a translations of the
recent en-US "12.00".

It's the same for the newer "11.30" like short names. I have removed
the never working ":1:30:"-like patterns from the da, en-GB, fr, ko,
nl-BE, lt, nl, ro, sk, sv, tr DocumentList.xml files (these files are
the final place of the translations).

(If I right think, it would be better the change the recent en-US
:11.30: format to the more natural :11 h 30:, but it will be still
possible to translate it to :11.30:. Also you can skip their
translations, using "nil" or to do nothing here.)

Thank you for your great work to translate the big emoji dictionary of LO.

Best regards,
László

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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

[libreoffice-l10n] English and German screencasts about “Grammar By” user dictionary feature

[Németh László]

Hi,

I have linked the following YouTube screencasts in the LO 6.0’s Release
Notes (
https://wiki.documentfoundation.org/ReleaseNotes/6.0#.E2.80.9CGrammar_By.E2.80.9D_spell_checking
):

https://www.youtube.com/watch?v=EsS3gaBTfOo

https://www.youtube.com/watch?v=aYVFDqCUb6I German

I have a question about the German example sentence (“YouTuber liken keine
postfaktischen Vlogeinträge.”).

Is it correct grammatically? If not, I will fix it.

Best regards,
Laszlo

PS. Here are the source of the screencasts to use/move them freely. Mike,
maybe if it’s worth and not too late, you can use it in the LO marketing
video instead of the screenshot.

http://numbertext.org/tmp/Grammar_by_English.webm
http://numbertext.org/tmp/Grammar_by_German.webm

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Re: [libreoffice-l10n] English and German screencasts about “Grammar By” user dictionary feature

[Németh László]

Hi Christian,

2018-01-26 12:21 GMT+01:00 Christian Lohmaier <
lohmaier+ooofut...@googlemail.com>:

> Hi Németh, *,
>
> On Fri, Jan 26, 2018 at 10:13 AM, Németh László 
> wrote:
> >
> > I have linked the following YouTube screencasts in the LO 6.0’s Release
> > Notes (
> > https://wiki.documentfoundation.org/ReleaseNotes/6.0#.E2.80.
> 9CGrammar_By.E2.80.9D_spell_checking
> > ):
> >
> > https://www.youtube.com/watch?v=EsS3gaBTfOo
> >
> > https://www.youtube.com/watch?v=aYVFDqCUb6I German
> >
> > I have a question about the German example sentence (“YouTuber liken
> keine
> > postfaktischen Vlogeinträge.”).
> >
> > Is it correct grammatically? If not, I will fix it.
>
> Yes, is grammatically correct.
>
> PS: add some bgm or voiceover please - completely silent videos are
> always a little awkward... :-)
>

I have added the music "Problems solved by Technology" by EasyAccessMusic,
hoping that is better, than nothing. :)

Thanks for your answer and advice.

Best regards,
László


> ciao
> Christian
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

[libreoffice-l10n] Fixing new spell out numbering styles in LibreOffice 6.1

[Németh László]

Hi,

LibreOffice 6.1 will support “spell out” numbering styles of OOXML (One,
Two...; First, Second..., 1st, 2nd...),
as you can see in the following screen cast (only English, French and
German examples):

 https://youtu.be/c0j4Sjie8t4 

My questions to the native language speakers:

1. Are these numbers correct in your language?

You can check here, too: https://numbertext.github.io/
index.html#testimonials

2. Do we need to change the default format etc. according to the normal
usage of your country/language variant?

For example, in the recent implementation, British English and American
English differ with the “and”

101 -> “One hundred and one”: en-AU, en-GB, en-IE, en-NZ
101 -> “One hundred one”: en-US etc.

3. Is it enough to support only a single gender in Spanish etc. languages
to cover common outline and page number usage in publishing?

Book/Part/Chapter/Section/Page/Paragraph One, or simply One (normal usage
in English outline numbering)
First Book/Part/Chapter/Section/Page/Paragraph (less common in English, but
default numbering styles cover this, too)

Note: there is a plan to use similar spell out formats in currency and date
formats of Writer, typical in contracts and invoices in several
languages. These formats are only supported in Calc yet by the NUMBERTEXT
Calc extension (or also in Writer macros via the new
com.sun.star.linguistic2.NumberText
service).

Best regards,
László

P.S: A recent question (comes from Rene Engelhard) for Hebrew contributors:

Is the Hebrew correct in the next line of resource file of the Numbertext
Calc extension:

NUMBERTEXT() וMONEYTEXT() פונקציות גליון Calc

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Re: [libreoffice-l10n] Fixing new spell out numbering styles in LibreOffice 6.1

[Németh László]

Hi,

New changes based on your great feedbacks:

– complete Bulgarian module by Mihail Balabanov;
– new Icelandic module (without currency support yet);
– new Slovenian ordinal number support;
– better (I hope) Czech ordinal numbers;
– fixing default currency for Lithuanian and Latvian, better ordinal
numbers in Latvian;
– etc.

I am going to update libnumbertext integration with these fixes for
LibreOffice 6.1.

We've got help from Mike Kaganski, who has not only fixed the Russian
language data, but added libnumbertext features to NatNumber native number
formatter of LibreOffice.
This will help to use the different gender functions and other number
formatting features of Numbertext language descriptions in different area
of Writer and Calc.
A Hungarian example in a Writer screencast:
https://www.youtube.com/watch?v=8EqnUOPMfbc – formatting  a variable in
different formats at the same time, as
frequently used in contracts and legal documents.

The new NatNumber12 number formatter is still under development, but based
on this, it will be possible to add new date and other formats to the XML
locale files,
for example, the common English date format "31st December", or the common
Hungarian date formats with affixation: 2018. január 25-e/26-a (plain
date),  24-én/26-án (on 24th/26th).

Using https://numbertext.github.io/Soros.html, you can check/test all
details of the language data more easily.
For the already integrated chapter numbering (with working DOCX
import/export), you can test the default
ordinal numbers and ordinal indicators, too, adding "ordinal" and
"ordinal-number" in the input box "prefix".

For the incoming NatNum12 support, the other gender variants are available
under the prefix cardinal-feminine, ordinal-neuter etc., according to the
"help"
of the end of the modules. With empty prefix input field, the Input "help"
shows the available functions, for example for Slovenian:

helpena, dve, tri
cardinal-feminine: ena, dve, tri
cardinal-masculine: ena, dva, tri
cardinal-neuter: ena, dve, tri
ordinal-feminine: prva, druga, tretja
ordinal-masculine: prvi, drugi, tretji
ordinal-neuter: prvo, drugo, tretjo
ordinal-number: 1., 2., 3.

(Unfortunately, this help misses the available cardinal-adverbial and
ordinal-adverbial, as I just noticed.)

Thanks for your help,

Best regards,
László



2018-05-19 19:35 GMT+02:00 Martin Srebotnjak :

> Hi,
>
> I am reporting back for Slovenian (sl). I am adding other two members of
> the Slovenian localization team (Urška and Robert) to assist in my answer
> and your further questions, if needed.
> Looking at https://numbertext.github.io/index.html#testimonials
> - cardinal number for Slovenian seems ok (used in 1, 2, ...);
> - ordinal numbering for Slovenian is not existent in your system (used
> with modification in 1., 2., ...).
>
> First, for writing only ordinal numbers in Slovenian:
> The beginning is the same as in cardinal number, except for the last word,
> which ends with "i" (this is for ordinal number for masculine, for female
> it should be "a" and for neutrum it should be "o"); but there are different
> endings for 1-4 with modulo 100 (0, 100, 200, 300, 400, 500, 600, 700, 800,
> 900) where endings go like this:
> 1.- prvi
> 2.- drugi
> 3.- tretji
> 4.- četrti
> 5.-100.: cardinal + "i"; example: 5.: peti ("pet"=5 + "i"); 98:
> osemindevetdeseti (osemindevetdeset=98 + "i")
> 101. - stoprvi = 100 "sto" + "prvi"
> 102. - stodrugi =  + "drugi"
> 103. - stotretji
> 104. - sto četrti
> 105. - stopeti = "sto pet" - space + "i"
> So with 10203 we have "deset tisoč dvesto tretji".
>
> For lists with ordinal numbers, however, the ordinal nuber gets appended
> with "č", as form "prvič", "drugič", etc. is used with ordinal numbers, so
> we get:
> 1. = prvič = ordinal number  ("prvi") + "č"
> 2. = drugič
> 3. = tretjič
> ---
> 99. = devetindevetdesetič
> 100. = stotič
> 101. = stoprvič
> 104. = stočetrtič
> 105. = stopetič
> ...
> 423. = štiristotriindvajsetič
>
> Also, if I am correct, in ordinal numbers and ordinal numberings for lists
> the word is written as one, without spaces (whereas the cardinal number has
> spaces where you have them already). Will check about that and report back.
> Maybe I am wrong, Urška can confirm (at lease "101." as an idiom in the
> dictionary exists as "stoprvič").
>
> We have a problem in Slovenian with the "1st, 2nd, 3rd, ..." etc. list
> numbering, we do not have appropriate form for that, must check what MSO
> uses there, maybe a female or neutrum version of ordinal numbering or
> somethi

Re: [libreoffice-l10n] Fixing new spell out numbering styles in LibreOffice 6.1

[Németh László]

Hi Martin, Hi All,

2018-06-19 22:24 GMT+02:00 Martin Srebotnjak :

> Hi, Laszlo,
>
> 2018-05-25 20:26 GMT+02:00 Németh László :
>
>>
>>
>> For the incoming NatNum12 support, the other gender variants are
>> available under the prefix cardinal-feminine, ordinal-neuter etc.,
>> according to the "help"
>> of the end of the modules. With empty prefix input field, the Input
>> "help" shows the available functions, for example for Slovenian:
>>
>> helpena, dve, tri
>> cardinal-feminine: ena, dve, tri
>> cardinal-masculine: ena, dva, tri
>> cardinal-neuter: ena, dve, tri
>> ordinal-feminine: prva, druga, tretja
>> ordinal-masculine: prvi, drugi, tretji
>> ordinal-neuter: prvo, drugo, tretjo
>> ordinal-number: 1., 2., 3.
>>
>> (Unfortunately, this help misses the available cardinal-adverbial and
>> ordinal-adverbial, as I just noticed.)
>>
>> For Slovenian I am missing the "prvič, drugič, tretjič, ..." which is the
> equal of "1." or "first, second, third" as in "third point"; the gender
> ordinal ones you list are correct, but they count in corresponding gender,
> whereas the "prvič, drugič, tretjič" is the spelled-out form of "prislovni
> števnik", of the "adverbial ordinal", which would be needed in the lists,
> like "prvič: this and this; drugič: this and this, ..." ... Maybe this one
> can replace the "1st, 2nd, 3rd" we do not use in Slovenian as a special
> graphic form.
>

The plan is to use the new NatNum12 feature to support genders and other
functions in custom or predefined number formats:

https://wiki.documentfoundation.org/ReleaseNotes/6.1#New_.E2.80.9Cspell_out.E2.80.9D_NatNum_modifier

Moreover, it will be possible to use dozens of suffix functions for
agglutinative languages with vowel harmony (ie. word-dependent suffix
variants), like Estonian, Finnish and Hungarian, see

https://github.com/Numbertext/libnumbertext/commit/cbcc8bbcb63964e4831ee611b22cbaca1f415817

and adding dozens of predefined date formats to the locale files to support
all date variants used in templates and mail merge in these languages (for
example, for Hungarian: https://gerrit.libreoffice.org/#/c/55637/)


>
> Also, I downloaded the LO61b2 from a few days ago and it includes my
> translation of the numbering, but the numberin displayed in Slovenian
> document and language is not the one listed here, I only get: Ordinal 1.,
> Ordinal 2., Ordinal 3. and not "Prvič, Drugič, Tretjič" ... Is this feature
> not yet enabled for Slovenian?
>

Unfortunately, this is the fallback of the feature, when libnumbertext is
not available.

The issue with more information:
https://bugs.documentfoundation.org/show_bug.cgi?id=118261



>
>
>> Thanks for your help,
>>
>
> Thank you for your wonderful work, I hope we get this right for as many
> languages as possible for the 6.1.0 release ;)
>

Thanks, I hope that. :)  Thanks for your bug report!

Best regards,
Laszlo



>
> Best regards,
> Martin
>
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] Note to translators in NatNum12 help files

[Németh László]

Hi,

Thanks, Sophie, forwarding the description. Thanks, Olivier, for the link.
There is the new NatNum12 description at the end of the page.


2018-07-17 14:32 GMT+02:00 Olivier Hallot :

> Hi Sophie, Dear translators
>
> I must admit I got quite confused (and the subject is confusing indeed).
>
> The page is this one:
>
> https://help.libreoffice.org/6.2/en-US/text/shared/01/
> 05020301.html?&DbPAR=CALC
>
> and my master build shows nothing when [NatNum12] is used.
>

It needs a zero at least to get a format code, for example, "[NatNum12
ordinal]0" will spell out the number as an ordinal number. Likely, it's
better to add these zeroes to the translations, and to the English
originals, according to the table header "Formatting code".


>
> Some questions:
> 1) Where are these XML files?
>

source/text/shared/01/05020301.xhp

in helpcontent2

2) Is there a working example?
>

I have just attached the following test document to the issue (
https://bugs.documentfoundation.org/show_bug.cgi?id=115007):

https://bugs.documentfoundation.org/attachment.cgi?id=143595

(Screenshot of the document:
https://bug-attachments.documentfoundation.org/attachment.cgi?id=143596)



> 3) Should the help content give examples?
>

The recent help content lists only the NatNum12 modifier with different
options. We need to add a format code to get a working example, ie. simply
extending them with a 0:

[NatNum12] -> [NatNum12]0
[NatNum12 ordinal-feminine] -> [NatNum12 ordinal-feminine]0
[NatNum12 USD] -> [NatNum12 USD]0
etc.

See the screenshot of the previous test document in the Format number
dialog, spell out format of a money amounts in U.S. dollars with title
case:

https://bug-attachments.documentfoundation.org/attachment.cgi?id=143596

The screenshot shows its number format code: "[NatNum12 title USD]0"

In my translator note, I tried to suggest to list the available functions
of your language, and this is possible in the last paragraph of the text.
For example,  the available functions of Numbertext/NatNum12 for Brazilian
Portuguese are

feminine, masculine, ordinal-feminine, ordinal-masculine,
ordinal-number-feminine and ordinal-number-masculine.

To see these and available functions of other languages, choose menu item
"Functions (help)" in pop-up menu of the page

https://numbertext.github.io/#testimonials

If your language hasn't been supported yet, you don't need to extend the
translated text.

By the way, it's easy to add a new language based on the recent modules and
the Numbertext tutorial, so I encourage you to contribute. I will help,
also I continue to extend the list of the supported languages of
Numbertext, for example, I have just added Galician (developed by Adrián
Chaves), Albanian, Ukrainian and Norwegian Bokmål and Nynorsk.


>
> Help welcome, the numbertext feature is a must and deserves better
> description and usage contents.
>

Thanks again,

I am going to add more examples, test documents and screen casts to the
issue, also to the 6.1 release notes soon, and write to this list.


Best regards,
László


>
> Kind regards
> Olivier
>
>
> Em 10/07/2018 13:11, sophi escreveu:
> >
> > Hi all,
> >
> > In the patch for NatNum12 function's help, there is a note for
> > translators that I copy and paste here (thanks Laszlo for adding it):
> > ---
> > tdf#115007 add NatNum12 help and ask translators for extending
> > language support in number and date formatting by extending
> > the newly integrated libnumbertext (http://www.numbertext.org)
> > and default date formats of LibreOffice:
> >
> > Translators: (1) please, modify the list of NatNum12 functions
> > according to libnumbertext language support of your language.
> > Other arguments could be ordinal-feminine, ordinal-masculine,
> > ordinal-neuter, formal, article, etc. To show the available
> > NatNum12 arguments of your language, open
> > https://numbertext.github.io/#testimonials in a browser, and
> > select "Functions (help)" in the pop-up menu.
> >
> > As you can see in the examples for NatNum12 date formats
> > and in the extended en_US.xml and hu_HU.xml locale data files, it's
> > possible to support also special number formatting needs of your
> > language, including spelling out numbers, money amounts and dates
> > with automatic selection of prepositions [like Catalan "de" or "d'"
> > before month names], articles [Hungarian "a" or "az"] and suffixes
> > [in Hungarian or likely Estonian, Finnish, Turkish etc. languages:
> > "in", "from", "to" etc. suffixes of day and month names], check
> > http://numbertext.org or write your questions on LibreOffice l10n
> > mailing list.
> > 
> >
> > Cheers
> > Sophie
> >
>
> --
> Olivier Hallot
> LibreOffice Documentation Coordinator
> Comunidade LibreOffice
> Rio de Janeiro - Brasil - Local Time: UTC-03:00
> http://

Re: [libreoffice-l10n] Fixing new spell out numbering styles in LibreOffice 6.1

[Németh László]

Hi, Cor,

Cor Nouws  ezt írta (időpont: 2018. szept. 12., Sze,
22:43):

> Hi László,
>
> Németh László wrote on 03-05-18 18:57:
>
> > LibreOffice 6.1 will support “spell out” numbering styles of OOXML (One,
> > Two...; First, Second..., 1st, 2nd...),
> > as you can see in the following screen cast (only English, French and
> > German examples):
> >
> >  https://youtu.be/c0j4Sjie8t4 <https://youtu.be/c0j4Sjie8t4>
> >
> > My questions to the native language speakers:
> >
> > 1. Are these numbers correct in your language?
>
> LibreOffice Versie: 6.1.0.3
> Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
> CPU-threads: 4; Besturingssysteem: Linux 4.15; UI-render: standaard;
> VCL: gtk2;
> Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
>
> The numbering styles appear fine in the list 'Number'
> But the result in the document is broken/wrong.
> Such as Ordinal 1, Ordinal 2... and not 1e / eerste, 2e / tweede, etc.
>
> What is the status of this currently?
>


Missing data file installation was fixed on Windows, so version 6.1.1 will
work well on it, see
https://bugs.documentfoundation.org/show_bug.cgi?id=118261.

But it's possible, this won't fix the problems of the TDF build on Linux.
That uses older GCC, unfortunately, without the requested C++11 regex
support, so it's possible, only LibreOffice versions packaged by the recent
Linux distributions will show "spell out" numbering correctly for a while.

Maybe it's worth to change the fall-back formats of ordinal and ordinal
indicator numbers to simple numbers, as in the case of the cardinal
numbers, to avoid to show "ordinal 1" or "ordinal-number 1" in TDF builds.

What is your opinion?

Best regards,
László



>
> Cheers,
> Cor
>
>
> >
> > You can check here, too: https://numbertext.github.io/
> > index.html#testimonials
> >
> > 2. Do we need to change the default format etc. according to the normal
> > usage of your country/language variant?
> >
> > For example, in the recent implementation, British English and American
> > English differ with the “and”
> >
> > 101 -> “One hundred and one”: en-AU, en-GB, en-IE, en-NZ
> > 101 -> “One hundred one”: en-US etc.
> >
> > 3. Is it enough to support only a single gender in Spanish etc. languages
> > to cover common outline and page number usage in publishing?
> >
> > Book/Part/Chapter/Section/Page/Paragraph One, or simply One (normal usage
> > in English outline numbering)
> > First Book/Part/Chapter/Section/Page/Paragraph (less common in English,
> but
> > default numbering styles cover this, too)
> >
> > Note: there is a plan to use similar spell out formats in currency and
> date
> > formats of Writer, typical in contracts and invoices in several
> > languages. These formats are only supported in Calc yet by the NUMBERTEXT
> > Calc extension (or also in Writer macros via the new
> > com.sun.star.linguistic2.NumberText
> > service).
> >
> > Best regards,
> > László
> >
> > P.S: A recent question (comes from Rene Engelhard) for Hebrew
> contributors:
> >
> > Is the Hebrew correct in the next line of resource file of the Numbertext
> > Calc extension:
> >
> > NUMBERTEXT() וMONEYTEXT() פונקציות גליון Calc
> >
>
>
> --
> Cor Nouws
> GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28  A038 E49D 7365 B134 80A6
> - vrijwilliger https://nl.libreoffice.org
> - volunteer https://www.libreoffice.org
> - Member Board The Document Foundation
> - http://www.nouenoff.nl / https://www.mijnclouoffice.nl
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-l10n] LibreOffice Language Technology – News & Best practices

[Németh László]

Hi,

After releasing Hunspell 1.7
 with several
improvements, including the fast and better spelling suggestion, I
published the extended version of my presentation at LiboCon, Tirana:
LibreOffice
Language Technology – News & Best practices
.
I suggest checking its content especially for members of native language
groups. I have listed several ideas, examples and code pointers to improve
the support of your language in LibreOffice, helping your LibreOffice
users. (I sent this to planet.documentfoundation.org, too, sorry for the
duplication.)

Best regards,
László

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] Para Hyphenation No Last Word

[Németh László]

Hi,

Heiko Tietze  ezt írta (időpont: 2022.
jún. 20., H, 13:50):

> It was requested in
> https://bugs.documentfoundation.org/show_bug.cgi?id=149248 and done by
> Laszlo in https://gerrit.libreoffice.org/c/core/+/134985
>
> And as Martin pointed out this string is used for the SI likewise "Para
> Hyphenation No Caps" for example.
>
> On 20.06.22 09:57, Donald wrote:
> > Source string description: 8BFum
> > Source string location: sw/inc/inspectorproperties.hrc:209
> > Para Hyphenation No Last Word
> >
> > What does this mean?:
> >
> > Does para mean paragraph?
> > Does it mean "Don't hyphenate the last word of a paragraph"?
>

Indeed, this text was created after "Para Hyphenation No Caps".
The other new string is the "Para Hyphenation Zone":

https://wiki.documentfoundation.org/ReleaseNotes/7.4#New_typographic_settings

Thanks,
László





> >
> > Regards
> > Donald
> >
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/l10n/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] Language of LibreLogo commands

[Németh László]

Hi Michael,

Michael Wolf  ezt írta (időpont: 2022. szept. 27., K,
22:13):

> Hi,
>
> I currently translate LibreOffice master Help for LibreLogo.
>

I'm very glad of it! Many thanks for that!


>
> A question: Where are the commands of LibreLogo translated, in
> LibreOffice or externally? I'm afraid that LibreLogo is not in Upper
> Sorbian and Lower Sorbian. But, in the LibreLogo help I have to use the
> LibreLOgo commands in a language that works.
>

https://translations.documentfoundation.org/projects/libo_ui-master/librelogosourcepythonpath/dsb/
https://translations.documentfoundation.org/projects/libo_ui-master/librelogosourcepythonpath/hsb/

It seems, they are translated completely, thanks for the work of the
Sorbian translators!

But with the recent master, only the Upper Sorbian works, as intended:

$ grep -o "hsb': '\w*'" instdir/share/Scripts/python/LibreLogo/LibreLogo.py
| head
hsb': 'oranžowy'
hsb': 'dypk'
hsb': 'absolutny'
hsb': 'naruna'
hsb': 'nakósny'
hsb': 'wudaće'
hsb': 'tupl'
hsb': 'někajki'
hsb': 'złoty'
hsb': 'nic'

$ grep -o "dsb': '\w*'" instdir/share/Scripts/python/LibreLogo/LibreLogo.py

I think the next update of the code will add the Lower Sorbian translations.

Best regards,
László


>
> Thanks and kind regards,
>
> Michael
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/l10n/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] Language of LibreLogo commands

[Németh László]

Hi Michael,

Michael Wolf  ezt írta (időpont: 2022. szept. 28.,
Sze, 15:26):

>
>
> 28.9.2022 14:38 hodź. Németh László napisa:
>
> Hi László,
>
> thank your for your quick reply.
>
> > Michael Wolf  ezt írta (időpont: 2022. szept. 27.,
> K,
> > 22:13):
> >
> >> Hi,
> >>
> >> I currently translate LibreOffice master Help for LibreLogo.
> >>
> >
> > I'm very glad of it! Many thanks for that!
>
> My pleasure! Thank you.
>
> >
> >>
> >> A question: Where are the commands of LibreLogo translated, in
> >> LibreOffice or externally? I'm afraid that LibreLogo is not in Upper
> >> Sorbian and Lower Sorbian. But, in the LibreLogo help I have to use the
> >> LibreLOgo commands in a language that works.
> >>
> >
> >
> https://translations.documentfoundation.org/projects/libo_ui-master/librelogosourcepythonpath/dsb/
> >
> https://translations.documentfoundation.org/projects/libo_ui-master/librelogosourcepythonpath/hsb/
> >
> > It seems, they are translated completely, thanks for the work of the
> > Sorbian translators!
>
> Great, I'll thank myself. :-D
> >
> > But with the recent master, only the Upper Sorbian works, as intended:
> >
> > $ grep -o "hsb': '\w*'"
> instdir/share/Scripts/python/LibreLogo/LibreLogo.py
> > | head
> > hsb': 'oranžowy'
> > hsb': 'dypk'
> > hsb': 'absolutny'
> > hsb': 'naruna'
> > hsb': 'nakósny'
> > hsb': 'wudaće'
> > hsb': 'tupl'
> > hsb': 'někajki'
> > hsb': 'złoty'
> > hsb': 'nic'
> >
> > $ grep -o "dsb': '\w*'"
> instdir/share/Scripts/python/LibreLogo/LibreLogo.py
> >
> > I think the next update of the code will add the Lower Sorbian
> translations.
>
>
> Ah, wonderful. I translated some commands in thought :-) and entered
> them in the LibreLogo window but I got the error message that the
> command is unknown although I set Upper Sorbian in Tools -> Options ->
> Languages -> Western.
>

Indeed, it didn't work! Thanks for your bug report, I was able to fix the
problem:

https://gerrit.libreoffice.org/c/core/+/140796

"LibreLogo: fix ast, gug, hsb and sid language support

Asturian (ast), Paraguayan Guaraní (gug), Sidamo (sid) and Upper-Sorbian
(hsb) localizations did't work despite their existing localization stored
in the language fallback dictionary of LibreLogo.py, because their 3-letter
language identifiers with their country codes trimmed to 2-letter, for
example: "hsb-DE" -> "hs" instead of the correct "hsb".

Missing Upper-Sorbian support was reported by Michael Wolf."

I'll back-port the fix into LibreOffice 7.4 and before. Also I'll add
Lower-Sorbian and other translations to the "language fallback" dictionary
of LibreLogo.py soon.

Many thanks again, also for your translation!

Best regards,
László


>
>
> Kind regards,
>
>
> Michael
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] Language of LibreLogo commands

[Németh László]

Hi Michael,

Michael Wolf  ezt írta (időpont: 2022. nov. 21., H,
19:35):

> Hi,
>
> until now the Libreoffice does not support Lower Sorbian LibreLogo
> commands although they have been translated on Weblate for a long time.
>
> Additionally, I have changed some Upper Sorbian and Lower Sorbian
> translations of LibreLogo commands more than a month ago. Until now the
> new translations are not in Libreoffice, neither in LibreOffice master
> nor in LibreOffice 7.4.*.
>
> Please include Lower Sorbian LibreLogo commands and changed Upper
> Sorbian LibreLogo commands as soon as possible.
>

The last LibreOffice 7.4 release has already included both of them, so the
problem is not the missing translation:

$ ls -lt
/opt/libreoffice7.4/share/Scripts/python/LibreLogo/LibreLogo_*sb.properties
-rw-r--r-- 1 root root 3367 okt   11 01:28
/opt/libreoffice7.4/share/Scripts/python/LibreLogo/LibreLogo_dsb.properties
-rw-r--r-- 1 root root 3340 okt   11 01:28
/opt/libreoffice7.4/share/Scripts/python/LibreLogo/LibreLogo_hsb.properties

As a quick solution for 7.4, I started to back-port the fallback dictionary
patch, which was committed a day before yesterday to the master branch:

https://gerrit.libreoffice.org/c/core/+/143073

So the daily build already uses Lower Sorbian and the last version of Upper
Sorbian, and the next 7.4 bug fix release will do that.

I have tested it this way:

1. Change the language of an empty document to Lower Sorbian.

2. Click on the Start Logo program icon of the Logo Toolbar.

The icon inserts an English language demo program, and translates it to
Lower Sorbian, and runs it:

PISMOWABARWA „ZELENY“
POMJENJENJE „LIBRE“
PISAKGÓRJEJ
SLĚDK 30
WOBRAZ [
POŁNJECABARWA NĚKAKI
KREJZ 40
PISMOWABARWA „CARNY“
POMJENJENJE „LOGO“
NALĚWO 180
DOPRĚDKA 20
PISAKDOŁOJ
BARWAPISAKA NĚKAKI
WJELIKOSĆPISAKA 1
DOPRĚDKA 40
WÓSPJETUJ 20 [
DOPRĚDKA LICAK*2
NAPŠAWO 90
]
]
PISAKGÓRJEJ POZICIJA NĚKAKI PISAKDOŁOJ



For Upper-Sorbian, I've got the following translated demo code:

PISMOWABARBA „ZELENY“
POPIS „LIBRE“
PISAKHORJE
WRÓĆO 30
WOBRAZ [
PJELNJACABARBA NĚKAJKI
KRUH 40
PISMOWABARBA „ČORNY“
POPIS „LOGO“
NALĚWO 180
DOPRĚDKA 20
PISAKDELE
BARBAPISAKA NĚKAJKI
WULKOSĆPISAKA 1
DOPRĚDKA 40
WOSPJETUJ 20 [
DOPRĚDKA LIČAK*2
NAPRAWO 90
]
]
PISAKHORJE POZICIJA NĚKAJKI PISAKDELE


I didn't notice the problem with loading the external Sorbian resource
files before, but I will fix that, too.

Sorry for the inconvenience, and many thanks for the translation and the
bug report!

Best regards,
László



>
> Reagrds,
>
> Michael Wolf
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/l10n/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-l10n] State-of-the-art hyphenation for Danish, Dutch, German, Hungarian, Norwegian and Sweden

[Németh László]

Hi,

As a complement to my ongoing typography developments (
https://numbertext.org/typography/), I work on the extension of the
hyphenation zone to hyphenate compound words at stem boundaries, combining
the pattern based libhyphen hyphenation with morphological analysis of
Hunspell. This would result in state-of-the-art automatic hyphenation in
several languages, which write long or very long non-dictionary compound
words frequently. My plan is to commit the first working version within a
few days, so it will be possible to test it.

No need to extend the Hunspell dictionaries to get some improvement, but
can help (see “Specifying stem boundaries in .dic file”), also it can be an
option to check and fix the bugs of the pattern based libhyphen hyphenation
later.

The explanation of the extension: the hyphenation zone is a custom distance
from the end of the line, where the preferred line break is the last space,
if it exists, despite the possible hyphenation after that. The planned
extension differentiates the possible (libhyphen) hyphenations within the
hyphenation zone, and prefers the last one, which is also a stem boundary
(according to Hunspell), despite the possible hyphenations after that.

Issue with references:
https://bugs.documentfoundation.org/show_bug.cgi?id=158885

I have attached a Hungarian test file to the issue, with a hyphenation zone
(see Text Flow in paragraph settings), and with some explanation. You can
make your OpenDocument test file based on this example, if your Hunspell
dictionary uses COMPOUNDFLAG, COMPOUNDBEGIN etc. compound word features.

It's already possible to test Hunspell compound word decomposition by the
command line Hunspell, using -m (morphological analysis). For example for
Swedish:

~/libreoffice/dictionaries/sv_SE$ hunspell -d sv_SE -m
rättstavningskontroll
rättstavningskontroll  pa:kontroll

This analysis contains only the last stem or part (pa:) of the compound,
yet, but planned to extend Hunspell to get the other parts, too (which can
contain in-word suffixes, e.g. Fuge-elements in German, fogemorphemes in
Swedish).

Compare this with libhyphen hyphenation:

~/libreoffice/dictionaries/sv_SE$
/home/laci/libreoffice/workdir/UnpackedTarball/hyphen/example hyph_sv.dic
<(echo rättstavningskontroll)
rätt=stav=nings=kon=troll

With the existing Hunspell analysis, the upcoming development code can
prefer "rättstavnings-kontroll" instead of the hyphenation
"rättstavningskon-troll" in the specified hyphenation zone. With the
planned extension of Hunspell, to prefer "rätt-stavningskontroll" instead
of "rättstav-ningskontroll".

= Specifying stem boundaries in .dic file =

Using morphological fields, it's possible to add information for the stem
boundaries of a word with the following syntax:

stavningskontroll hy:stavnings|kontroll

or using the index of the character before the hyphenation point:

stavningskontroll hy:9

The first solution allows to specify more stem boundaries:

rättstavningskontroll hy:rätt|stavnings|kontroll

or weightening one of the stem boundaries for the hyphenation zone:

rättstavningskontroll hy:rätt||stavnings|kontroll

(Note: likely the real preference is the opposite, because of the meaning
is good|spelling||control, but I wanted to show an example, when we can
prefer not only the last stem boundary within the hyphenation zone).

See also man 5 hunspell for morphological fields.

I am interested to hear your opinions and welcome any further suggestions,
including for other languages, too.

Best regards and Happy New Year!

László

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-l10n] Translating LibreLogo

[Németh László]

Hi,

András mentioned the (possible) translation of the LibreLogo module in his
previous letter. LibreLogo is a native language, Logo-like (a simplified
procedural language with turtle graphics) programming interface/lightweight
environment to the excellent vector graphics of LibreOffice. More
information: http://extensions.libreoffice.org/extension-center/librelogo

Translations of the LibreLogo commands are defined by property files, for
example the English one: http://numbertext.org/logo/commands_en.txt.
Commands and their alternative and optional abbreviated forms separated by
vertical bars. First item is the non-abbreviated, default form, like
"forward" and its abbreviation, "fd" in the following example:

FORWARD=forward|fd

1. It is recommended (and easier) to use the existing native language
translation of the original Logo programming language, if it exists. Eg.
the Hungarian translation of "forward" and its abbreviated form are the
same as in the closed source, closed platform-dependent Logo environments
used in Hungarian schools:

FORWARD=előre|e

2. Quotation marks to annotate strings and decimal signs are also
localized, eg.

LEFTSTRING="|'
RIGHTSTRING="|'
DECIMAL=.

in Hungarian

LEFTSTRING="
RIGHTSTRING="
DECIMAL=,

3. For agglutinative languages, postfix form(s) of the IN operator are also
supported (starting with hyphen or colon):

IN=in
IN=-ban|-ben  # Hungarian noun case
IN=:ssa|:ssä # suggested for Finnish

FOR a IN b [ ]

In Hungarian:

FUT a b-BEN [ ]

RTL language support hasn't checked yet, but I will make LibreLogo
extensions with the new translations to test it and other features.

Any feedback and questions are welcome,
Best regards,
László

-- 
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] LibreLogo help strings

[Németh László]

Hi,

The referred page contains the first test version of the LibreLogo help,
thanks for the link:
http://wiki.documentfoundation.org/User:Nemeth

The po format is a little bit modified and fixed (eg. non-breaking spaces
removed by András Tímár to avoid the compilation problems of the copied
Logo examples).

(The command list is up to date: http://numbertext.org/logo/commands_en.txt)

A short, but useful introduction with images:
http://www.numbertext.org/logo/librelogo_en.pdf

Named parameters of the “penjoint” command, eg. “miter”, “round”, “bevel”
has already translated in LibreOffice
as “mitered”, “rounded”, “beveled” line corners.

Best regards,
László

2012/12/5 Sérgio Marques 

> 2012/12/4 Sérgio Marques 
>
> >
> >
> > 2012/12/4 Michael Bauer 
> >
> >>
> >> 04/12/2012 07:09, sgrìobh Cor Nouws:
> >>
> >>
> >>> I've still planned a little explaining blog. Sorry that I failed to
> make
> >>> time so far... I've some notes :
> >>>
> >> Ah this does help, thank you, and I'll try the current extension.
> >>
> >>
> >>> But... you can also type a simple command in de toolbar
> >>>
> >> Ok this raises a question in relation to Andras post - how can I tell
> >> which (apart from obvious long, verbose sentences) which are commands
> (and
> >> in my case not to be translated) and which are ... not commands?
> >>
> >>
> > The commands if im not mistaken are in
> > http://numbertext.org/logo/commands_en.txt
> >
> > --
> > Sérgio Marques
> >
>
>
> Some more information about librelogo:
> http://wiki.documentfoundation.org/User:Nemeth
> --
> Sérgio Marques
>
> --
> 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
>
>

-- 
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

Fwd: [libreoffice-l10n] LibreLogo localization

[Németh László]

Hi,

LibreLogo in 4.0.1 will support Asian and CTL languages, depending
from the language of the user interface, and (Western, Asian, CTL)
languages of the document. You have to change the Western language of
the document/paragraph to [None], if the user interface of LibreOffice
is in this Western language, for example, to test Japanese Logo
commands in LibreOffice with English UI. (See
https://bugs.freedesktop.org/show_bug.cgi?id=61376, where I have
attached a simple Japanese test file with these language settings.)

Especially CTL and Asian languages may have special problems or
requirements, so, please, inform me about them.
By the way, here is an interesting article about the importance of
native language programming, thanks to Kim Bastin for the link:

http://www.newscientist.com/blogs/onepercent/2013/02/arabic-programming-language.html

Best regards,
László

2013/1/14 Németh László :
> Hi Naruhiko,
>
> It seems, the main problem is the western based language detection. I'm
> afraid, there is no  method to detect the direction of the translation here.
> We can detect the language of the LibreOffice installation, and use
> Japanese. I will test it with RC1, and report the result.
> Many thanks for your mail.
>
> Best regards,
> László
>
> 2013/1/14 Naruhiko Ogasawara 
>>
>> Hi everyone,
>>
>>
>> I'm very sorry that I had misunderstood about "magic" icon feature of
>> LibreLogo.
>>
>> --
>> Dear Németh László,
>>
>> Please remove "ja" in your LibreLogo.py if you have already added.
>>
>> Now we, Japanese community decided we'll postpone to support LibreLogo
>> "magic" icon translation feature.
>>
>> --
>> Details:
>>
>> We, Japanese community has two problem:
>>
>> Problem 1: Which is primary: English or Japanese? (maybe Japanese)
>> Problem 2: How we can select document language is Japanese?
>>
>>
>>
>> The help [1] tell us:
>>
>> "It expands and upper case Logo commands in the Writer document. Change
>> the
>> language of the document (Tools » Options » Language Settings » Languages
>> » Western) and click on this icon to translate the Logo program to the
>> selected
>> language."
>>
>>
>> * Problem 1 *
>>
>> My big misunderstanding is translation direction: I thought this button
>> let
>> local-language command or short aliases TO English, primary language.
>> But it's not correct.
>>
>> Please let me confirm, if we have:
>>
>> FORWARD=すすむ|forward|fd
>>
>> and the document language is Japanese, all of following Logo code:
>>
>> すすむ 10
>> forward 10
>> fd 10
>>
>> should be changed:
>>
>> すすむ 10
>> すすむ 10
>> すすむ 10
>>
>> In the other words, the first word should be chosen.  Correct?
>> It means Japanese command is primary, and others are alias.
>>
>>
>> If so, according to difference of syntax of English and Japanese,
>> it's very hard to use Logo in Japanese only word-by-word translation.
>>
>> Small example; operator NOT is prefix, but in Japanese, directly
>> translated word "ではない" is postfix (a > 10 ではない).  That's
>> why we have to choose to translate NOT very declarative words like
>> "the following expression is not correct."
>>
>> It's deep problem, not only the translation issue, that's why
>> we want to postpone to apply "magic" icon feature for Japanese.
>>
>>
>> So, what caused if we'll use below?
>>
>> FORWARD=forward|すすむ|fd
>>
>> If the line means "forward" is a primary ("magic" icon changes
>> "すすむ" to FORWARD), our problem will be small.
>> Because young flexible brain can easily accept English command
>> if they have good entrypoints, Japanese localization might be.
>>
>>
>>
>> * Problem 2:
>>
>> It's not so serious.  Just a question.
>>
>> As help [1] says, LibreLogo choose their language to see "western,"
>> but, you might know, some languages (Japanese also) is in "Asian"
>> or "CTL."
>> How LibreLogo knows our document is in Japanese?
>>
>>
>>
>> [1]
>> https://translations.documentfoundation.org/ja/libo_help/swriter/librelogo.po/translate/#unit=33620860
>>
>>
>> Sorry to spend long time to read my long mail.
>> Thanks,
>> --
>> Naruhiko Ogasawara (naru...@gmail.com)
>
>

Re: [libreoffice-l10n] Problem with dic file

[Németh László]

 Dear Jānis,

Your dictionary (version 0.1.2 from
http://extensions.libreoffice.org/extension-center/latgalian-spell-checking-and-hyphenation-module/releases/0.1.2/ltg_lv-0.1.2.oxt/view)
works well with the recent LibreOffice master branch. There was no
changes on the spelling checker side, but the language
code/localization handling has been changed, and there was a bug in
the dictionary registration:

https://bugs.freedesktop.org/show_bug.cgi?id=58503

I believe, using the recent development
version or older LibreOffice versions _or_ (if I right know)
installing system-wide dictionaries into the /usr/share/hunspell on
Linux can solve this problem. I suggest to check different LibreOffice
versions (removing temporarily also the user profiles before the
installation, eg. on Linux ~/.libreoffice or ~/.config/libreoffice)
and set the working versions on your dictionary site of
extensions.libreoffice.org. Or is this problem related to the
integrated dictionary?

Best regards,
László

2013/4/15 Jānis :
> Hi!
>
> I found that for some reason the spell checking dic for Latgalian language
> in not working anymore
>
> the dic can be found here:
>
> http://extensions.libreoffice.org/extension-center/latgalian-spell-checking-and-hyphenation-module
>
> The dic is shown in the list of extensions, in character formatting dialogue
> the availability of spelling dic is indicated, but spell schecking is gone
> and there are no suggestions also.
>
> To add more to the confusion - the very dictionary is working in Mozilla
> products without any problems.
>
> Where is a problem? The other dic developed by me for Latvian languge is
> working as expected.
>
> Janis
> --
> http://dict.dv.lv
> http://tehvi.dv.lv
>
>
>
> --
> 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

-- 
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] Understanding the hunspell

[Németh László]

Hi Kruno,

2013/7/27 Krunoslav Šebetić :
> Hi,
>
> I'm not sure if I'm doing it right by sending this mail do l10n, but hopping
> someone will point me to right direction. Even tried to subscribe to
> hunspell mailing list, but with no success.

This is the right place for your questions.

>
> I've done reading Hunspell help/documentation pdf from the internet but
> still have few questions. From what stands in that document I can't be
> certain in some specific things which are actually very important when we
> talk about morphology of highly flective language like Croatian.
>
> Here we go:
>
> Let's say that .aff contain:
>
> FLAG long
> SFX Y A1 1
> SFX Y 0 a .
>
> FLAG long
> SFX Y A2 1
> SFX Y A2 0 e .
>
> Now, A1 and A2 needs to be applied to word "jezik" (eng. language). So if
> .dic file contain "jezik/A1" I should expect forms like "jezik" and
> "jezika". If .dic file contain entery like "jezik/A2" expected forms are
> "jezik", "jezike", but if the entery is
>
> jezik/A1A2
>
> I can expect forms like "jezik", "jezika", "jezike", but will hunspell try
> to combine A1 and A2 together like "jezikae" or "jezikea"? Form "jezikae"
> and "jezikea" are not valid in Croatian. I know it can be prevented by doing
>
> FLAG long
> SFX Y A2 1
> SFX Y A2 0 e [^a]
>
> but question is - will hunspell combine (aglutinate) suffixes if suffix
> statements doesn't prevent it explicitly (and allows it implicitly)? Wasn't
> able to solve this by reading the manual from
> http://hunspell.sourceforge.net nor by looking into other .aff files from
> git repository.

The second field in the header of a suffix class means only allowed
combination with prefix flags (from a class with similar allowed
prefix-suffix combination), so your first example will work (with
syntax corrections) well:

FLAG long
SFX A1 Y 1
SFX A1 0 a .

SFX A2 Y 1
SFX A2 0 e .

>
> Also if .dic file contains only form "PDF" will the word "pdf" in LO be
> underlined as misspelled?

Yes, "pdf" won't be accepted, only "PDF" (by the way, it's possible to
set this feature for lower case words, eg. names of the measurements
or currencies have to be lower case words in capitalized text, too).

> Can .dic file contain two words in one line?

Only in space separated form, and in LibreOffice this is only for
better suggestions.

>
> Further more - have trouble with understanding the REP section in .aff file.
> Can I do:
>
> REP 1
> Plitvička_Jezera Plitvička_jezera
>
> will that automatically correct capital letter in word "Jezera"?

No, there is that autocorrect list in the file DocumentList.xml of
acor_hr-HR.dat ZIP archive.

Best regards,
László

>
> I hope someone will give me a hand here...
>
> Kruno
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@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

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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] Romanian hyphenation dictionary

[Németh László]

Hi Ákos,

First, check the hyphenation settings in the paragraph style (Text
Flow->Hyphenation->Automatically). Move "UTF-8" into the first line of
the pattern file, convert the patterns by substrings.pl (it is better
to remove the comments during the conversion), check the registration
of the Romanian hyphenation patterns in
http://cgit.freedesktop.org/libreoffice/dictionaries/tree/ro/dictionaries.xcu.

More information:
http://wiki.openoffice.org/wiki/Documentation/SL/Using_TeX_hyphenation_patterns_in_OpenOffice.org

Best regards,
László


2013/10/2 Nagy Ákos :
> Hi,
>
> in LibreOffice don't work the hyphenation for romanian language. I verify
> the dictionary, and it seem that is installed correctly, and probably the
> rules is correct too.
> This is the dictionary file
> https://dl.dropboxusercontent.com/u/55468772/lo/hyph_ro_RO.dic
> Can you help me in how I start the debugging, and how can I find the
> problem?
>
> --
> Ákos
>
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@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
>

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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] IN in librelogo

[Németh László]

Hi,

Using the the same name for different keywords results name conflict,
but this is an exception, because IN and INCH are used in different
ways, so this is not problem:

[num]in for measurements, eg. 10in

and single

"in" for the operator. The translator („magic wand”) icon also can
handle this difference.

Best regards,
László


2013/12/10 dmtrs32 :
> I noticed  that there is a in (for inch) and a in (for i in & in) could  be
> any problem there?
>
> --
> To unsubscribe e-mail to: l10n+unsubscr...@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

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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] IN in librelogo

[Németh László]

Yes, it is, ROUNDED is a parenthesized constant, eg.

PENCAP 'ROUND'

ROUND is a numerical function:

PRINT ROUND 5.6

Best regards,
László

> 2013/12/10 dmtrs32 :
>>
>> Στις 10/12/2013 11:13 πμ, ο/η Németh László έγραψε:
>>
>>> Hi,
>>>
>>> Using the the same name for different keywords results name conflict,
>>> but this is an exception, because IN and INCH are used in different
>>> ways, so this is not problem:
>>>
>>> [num]in for measurements, eg. 10in
>>>
>>> and single
>>>
>>> "in" for the operator. The translator („magic wand”) icon also can
>>> handle this difference.
>>>
>>> Best regards,
>>> László
>>>
>>>
>>> 2013/12/10 dmtrs32 :
>>>>
>>>> I noticed  that there is a in (for inch) and a in (for i in & in) could
>>>> be
>>>> any problem there?
>>>>
>>>> --
>>>> To unsubscribe e-mail to: l10n+unsubscr...@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
>>
>> Is it the same with round?

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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] IN in librelogo

[Németh László]

Yes, it is, ROUNDED is a parenthesized constant, eg.

PENCAP 'ROUND'

ROUND is a numerical function:

PRINT ROUND 5.6

Best regards,
László

2013/12/10 dmtrs32 :
>
> Στις 10/12/2013 11:13 πμ, ο/η Németh László έγραψε:
>
>> Hi,
>>
>> Using the the same name for different keywords results name conflict,
>> but this is an exception, because IN and INCH are used in different
>> ways, so this is not problem:
>>
>> [num]in for measurements, eg. 10in
>>
>> and single
>>
>> "in" for the operator. The translator („magic wand”) icon also can
>> handle this difference.
>>
>> Best regards,
>> László
>>
>>
>> 2013/12/10 dmtrs32 :
>>>
>>> I noticed  that there is a in (for inch) and a in (for i in & in) could
>>> be
>>> any problem there?
>>>
>>> --
>>> To unsubscribe e-mail to: l10n+unsubscr...@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
>
> Is it the same with round?

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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

[libreoffice-l10n] Re: TYPOS?

[Németh László]

Hi,

Unpaired ASCII quoation mark is the original Logo syntax for a single
word literals (it is strange, but true).

Best regards,
László



2013/12/11 dmtrs32 :
> Hi,
> LABEL “text” ; print text in the turtle position LABEL 'text' ; see
> above LABEL "text ; see above (only for single words)
> nwEgR  LibreLogo.xhp
> LibreLogo.xhp
> par_1370
> help.text
> or
> LABEL “text” ; print text in the turtle position LABEL 'text' ; see
> above LABEL "text" ; see above (only for single words)

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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

[libreoffice-l10n] Re: State-of-the-art hyphenation for Danish, Dutch, German, Hungarian, Norwegian and Sweden

[Németh László]

Hi all,

I've extended the compound-constituent based hyphenation last year, thanks
to the support of FSF.hu Foundation, and there is a new option in paragraph
hyphenation setting to set the minimum compound constituent boundary
distance left before the hyphenation, too (also on the sidebar:
https://numbertext.org/typography/#__RefHeading___Toc2799_2584835629,
thanks to the support of NLnet Foundation).

I realized that this feature is much more important than I thought before.
I wrote a (yet Hungarian) article about it, see its English abstract:
https://numbertext.org/typography/automatikus_magyar_elv%C3%A1laszt%C3%A1s_a_LibreOffice-ban.pdf

For example, hyphenation is forbidden in headings traditionally, allowed
only e.g. at compound constituent boundary. Recent pattern based automatic
hyphenation can result in really annoying problems in the languages with
very long compound words, which need manual interaction (proofreading), or
stylistic constraints (very small font sizes in headings). The other
similar area is column/page/spread boundaries, where hyphenation is often
forbidden, which is the default setting in MSO, but its recent
implementation (shifting full lines to the next column/page/spread (spread
= visible page pair) is ugly and imperfect solution for the problem in
several languages, comparing to the compound constituent based hyphenation,
because it did not guarantee the elimination of the hard-to-read or ugly
hyphenation on the last line (if the previous line was also hyphenated).

My plan is to continue to extend the support for compound constituent-based
hyphenation, which can be applicable for fully automatic line breaking of
headings, also across columns, pages, spreads in German, and languages with
German-type orthography, e.g. Danish, Dutch, Hungarian, Norwegian and
Sweden.

Recent LibreOffice ODF extension:

loext:hyphenation-compound-left-char-count (now
loext:hyphenation-compound-remain-char-count)

Minimum hyphenation distance from the left compound constituent boundary.
The default setting is 2, which means that 1-character distance is
forbidden. Setting it to 3, also the 2-character distance is forbidden:
e.g. "counter-intelligence", but not "counterin-telligence". Value 0 means
maximal distance, i.e. no hyphenation after the left compound constituent
boundary (except in constituent boundaries). This setting doesn't affect
the hyphenation in the first compound constituent, and in the suffixation
of the compound word.

The planned improvements:

loext:hyphenation-compound-right-char-count

Minimum hyphenation distance from the right compound constituent boundary.
The default setting is 2, which means that 1-character distance is
forbidden. Setting it to 3, also the 2-character distance is forbidden:
e.g. "honeybee", but not "hon-eybee". Value 0 means maximal distance, i.e.
no hyphenation before the right compound constituent boundary (except in
constituent boundaries). This setting affects the hyphenation of the first
compound constituent.

Setting this option and loext:hyphenation-compound-left-char-count to 0,
the hyphenation is only allowed at compound constituent boundary and in
suffix of the compound word, but not within the (stem of the) compound
constituents.

loext:hyphenation-remain-char-count-compound

The minimum number of characters in a compound word before the hyphenation
character, if the word is hyphenated at compound constituent boundary. This
is the minimum number of characters in the compound constituent(s) left on
the line ending with the hyphenation character. The default value 0 has a
special meaning: apply the setting of fo:hyphenation-remain-char-count.

loext:hyphenation-push-char-count-compound

The minimum number of characters in a compound word after the hyphenation
character, if the word is hyphenated at compound constituent boundary. This
is the minimum number of characters in the compound constituent(s) pushed
to the next line after the line ending with the hyphenation character. The
default value 0 has a special meaning: apply the setting of
fo:hyphenation-push-char-count.

Example: forbidding the hyphenation in the suffix, but not at compound
boundary of compound words, set fo:hyphenation-push-char-count to the size
of the largest suffix, and set loext:hyphenation-push-char-count-compound
to a non-zero lower value.

I am interested to hear your opinions, especially from experts of the
listed languages and welcome any further suggestions, including for other
languages, too.

Best regards and Happy New Year!

László


Németh László  ezt írta (időpont: 2023. dec. 27.,
Sze, 13:43):

> Hi,
>
> As a complement to my ongoing typography developments (
> https://numbertext.org/typography/), I work on the extension of the
> hyphenation zone to hyphenate compound words at stem boundaries, combining
> the pattern based libhyphen hyphenation with morphological analysis of
> Hunspell. T