Re: [libreoffice-l10n] LibreOffice download page: Two short strings to translate

2018-03-16 Thread Mihail Balabanov
Hi,

On Fri, Mar 16, 2018 at 3:48 PM, Mike Saunders <
mike.saund...@documentfoundation.org> wrote:

> reply here (and mention the language), then I'll add them to the
>
>
Bulgarian:

To choose another language, click here.
>
За да изберете друг език, щракнете тук.


> Older versions of LibreOffice (may be unsupported!) are available in the
> archive.
>
По-стари версии на LibreOffice (евентуално неподдържани!) можете да
намерите в архива.

Cheers,
Mihail

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

2018-05-04 Thread Mihail Balabanov
Hi,

On Thu, May 3, 2018 at 7:57 PM, Németh László  wrote:

> LibreOffice 6.1 will support “spell out” numbering styles of OOXML (One,
> Two...; First, Second..., 1st, 2nd...),
>

Great!


> 1. Are these numbers correct in your language?
>

There is no Bulgarian; I used the Soros IDE to create a module and it is
now almost complete (only the currency part is remaining) but I could not
find how to add it to the list when it is ready. What is the procedure?


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

The only similar issue for Bulgarian that comes to my mind is that some
numbers have alternative names, for example 15 may be "петнадесет" (more
formal) or "петнайсет" (less formal but also OK in writing). These are not
dependent on language variants though, just style preference. My module
currently uses the formal ones.


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

In Bulgarian, spelled out numerals in chapter numbering are almost always
ordinal ("First chapter" rather than "Chapter one"). Both ordinal and
cardinal numerals have gender that must agree with the gender of the noun,
so all genders must be supported:

първа книга/част/глава/страница (first book/part/chapter/page, feminine)
първи раздел/абзац (first section/paragraph, masculine)
един долар (one dollar, masculine)
една лира (one pound, feminine)
едно евро (one euro, neuter)

Since apparently many languages are like this, maybe we need an option for
the user to select a particular Soros macro (probably through a
user-friendly name rather than things like "ordinal-feminine") for each
numbering level. This can also be used to switch between alternative number
names like the ones described above.

Cheers,
Mihail

-- 
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] Note to translators in NatNum12 help files

2018-08-01 Thread Mihail Balabanov
Hi László, all,

Where are the [NatNum12 xxx]0 format specifiers supposed to work currently?
I loaded the example document from Bugzilla in 6.1.0.1, 6.1.0.2, and a
recent build of 6.2; it appeared OK at first but as long as I updated the
field, it updated to "USD -12345" (just digits, no 'spelled out' number)
and I was unable to make any NatNum12 code work in the Number Format
dialog, even the original example in the document. I tried several
languages and 'subspecifiers' (ordinal, cardinal, etc.), also changing the
language of the text containing the field to match the language of the
formatting code. Nothing worked.
Should I install an extension? Is it supposed to work in Writer, Calc, or
both?

TIA,
Mihail

-- 
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] Libre Libraries?

2019-01-19 Thread Mihail Balabanov
Hello,

In the most recent batch of strings on Pootle, there is a translation unit,
see it for example here:

https://translations.documentfoundation.org/bg/libo_help/translate/sbasic/shared.po#filter=incomplete&unit=168427652&offset=0

that reads:

Libre Libraries: GetPathSeparator function

The corresponding  entry two TUs below is just

GetPathSeparator Function

so it looks a bit like a mistake. Should it be there? What does the 'Libre
Libraries:' prefix mean? Should it be translated, or is it a name of a
module or something similar?

Cheers,
Mihail

-- 
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] Weblate: copy XML tags to translated text

2019-09-12 Thread Mihail Balabanov
I hope this is a joke. :-)
One can also always walk to the next city instead of using transport. It
just takes a bit more time.
Automatic transfer of untranslatable items is an important feature.
Painstakingly selecting, copying, and pasting each tag is much, much slower
and prone to errors.
If there actually is such a feature, I haven't managed to locate it yet.

Cheers,
Mihail

On Sat, Sep 7, 2019 at 9:54 AM  wrote:

> Olivier Hallot schreef op 03.09.2019 15:43:
> > Pootle have a nice feature that weblate miss, -> future improvement...
> >
> > In pootle, clicking on a source XML tag copies it to the cursor
> > position
> > in the translation area. Handy to prevent mistakes when typing source
> > tags (links specially).
>
> You can always use copy past :-)
> >
> > regards
> > --
> > Olivier Hallot
> > LibreOffice Documentation Coordinator
> > Comunidade LibreOffice
> > Rio de Janeiro - Brasil - Local Time: UTC-03:00
> > http://tdf.io/joinus
>
> --
> 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] Weblate: copy XML tags to translated text

2019-09-14 Thread Mihail Balabanov
Hmm… Then maybe it is broken or turned off for us?
I just tried it again. XML tags are not highlighted in any way, the Ctr+1…9
shortcuts do nothing and clicking on the tags themselves also does nothing
(Firefox 69.0 64-bit on Windows 10 build 18362).
See this segment for example:
https://weblate.documentfoundation.org/translate/libo_help-master/textshared02/bg/?type=todo&offset=7

BTW clicking on tags as opposed to using Ctr+n-type shortcuts is important
because when there are more than a few tags (think long paragraphs in the
Help), it becomes cumbersome to count them to select the correct shortcut
for transfer instead of just clicking on it.


On Sat, Sep 14, 2019 at 11:40 PM Adolfo Jayme Barrientos <
f...@libreoffice.org> wrote:

> But Weblate DOES have this feature, it’s even tied to keyboard
> shortcuts: Ctrl+1 will insert the first XML tag, Ctrl+2 the second
> one, and so on… I don’t know what you all are arguing about…
>

-- 
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] How to report problems with original strings in Weblate?

2019-12-22 Thread Mihail Balabanov
Hi,

Pootle had a feature that let me report a typo or other issue with the
original string directly in the web interface while translating. What will
be the respective workflow in Weblate?

Case in question: I suspect the English string for ID "SEFWn" in 6.4 should
be "Color" rather than "Filter". Its context is "
notebookbar_groupedbar_compact|ColorButton" and in 6.3 the text was
"C_olor".

Cheers,
Mihail

-- 
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] Help strings for LO Online in Weblate - lost translations?

2020-01-10 Thread Mihail Balabanov
Hello,

The Suggested Translations feature of Weblate directed me towards
translating a large quantity (~200) of 'new' help strings for LibreOffice
Online (in loleaflet-help) but when I started going through them, they
stroke me as very familiar. I'm almost certain I have translated them in
the past but none of them pop up in the translation memory.

Can somebody confirm what happened with those texts? Am I wrong about them
being previously translated, or do we actually have to re-translate ~200
texts w/o TM because of some technical change?

All the best in the new year,
Mihail

-- 
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] TM not working in Weblate

2020-01-14 Thread Mihail Balabanov
Hello,

I'm unable to access translation memory in Weblate: the Machine Translation
tab is empty and the Translation Memory tab shows 'The request for machine
translation has failed: error:'. Is this a known problem? Is it only for
Bulgarian, or also for other languages?

Cheers,
Mihail

-- 
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] Questions about a couple of strings in UI master

2020-01-23 Thread Mihail Balabanov
Hello,

I have questions about a couple of UI strings in LO master.

Q1: Does  this source string contain a typo? It ends on " instead of a
period:
permalink:
https://weblate.documentfoundation.org/translate/libo_ui-master/svxmessages/bg/?checksum=44cab1dbdbe2c4e7
string: Properties for the task that you are performing are not available
for the current selection"

Q2: What is the meaning of ‘f.’ and ‘ff.’ in the string below? Is it
‘folio’ from Latin or something like that? Should it be translated? (was
‘p’ and ‘pp’ before)
permalink:
https://weblate.documentfoundation.org/translate/libo_ui-master/swmessages/bg/?checksum=e863138aa87c376e
string: Combine identical entries with f. or _ff.

TIA,
Mihail

-- 
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] Alerts in Weblate

2020-03-10 Thread Mihail Balabanov
Hello,

I noticed that all files in the "LibreOffice Help master" project for
Bulgarian have an alert saying

"The VCS repository has many changes compared to the upstream. Please merge
the changes manually or set up push to automate this."

Is this normal?

Cheers,
Mihail

-- 
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] LibreOffice 7.0 banner for translation

2020-07-30 Thread Mihail Balabanov
 Hi Mike,

In Bulgarian these would be

Производителност - Съвместимост - Ползваемост

Cheers,
Mihail

On Wed, Jul 29, 2020 at 7:01 PM Mike Saunders <
mike.saund...@documentfoundation.org> wrote:

> Hello,
>
> I've created this banner, that we can use for social media and other
> things around the LibreOffice 7.0 launch:
>
>
> https://blog.documentfoundation.org/wp-content/uploads/2020/07/LO70_banner_tagline_hires.png
>
> If anyone wants me to make a localised version, just post your
> translation of the three words "Performance - Compatibility - Usability"
> and I'll put them into the dark blue bar. Here's what I did for German,
> for instance:
>
>
> https://de.blog.documentfoundation.org/wp-content/uploads/sites/7/2020/07/LO70_banner_tagline_hires_DE.png
>
> Note that the English uses nouns, and the German version adjectives, so
> feel free to play around and use whatever's best for your language. The
> main goal is to show those three focal points of the release!
>
> --
> Mike Saunders, Marketing and Community Coordinator
> The Document Foundation
>
> --
> 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] What is ‘Show outline content visibility button’?

2020-08-11 Thread Mihail Balabanov
Hello,

What is ‘Show outline content visibility button’? The same text is used as
a label (ID: jtLiA, link: [1]) and as a tooltip (ID: 9DzFr, link: [2]) of a
corresponding control with an internal ID of
ShowOutlineContentVisibilityButton.

Is it
1. A command that shows/hides a button labeled ‘Outline content visiblity’?
2. A button called ‘Show outline content visibility’? In this case, what is
meant by ‘Show X’s visibility’? Does it mean to show/hide an icon that
shows some ‘Visibility’ status of X?
3. A button that shows/hides the outline content itself?
…or something else?

Also, the label and the tooltip should probably differ, otherwise we don’t
need a tooltip. For example, if it is 3, the texts should be something
along the lines of
Label: Toggle outline content
Tooltip: Shows/hides the contents of the outline.

Cheers,
Mihail

[1]
https://weblate.documentfoundation.org/translate/libo_ui-master/officecfgregistrydataorgopenofficeofficeui/en/?checksum=623c362bafdaaa41
[2]
https://weblate.documentfoundation.org/translate/libo_ui-master/officecfgregistrydataorgopenofficeofficeui/en/?checksum=755381f228f08f37

-- 
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] Is it possible to remove automatic suggestions?

2020-12-19 Thread Mihail Balabanov
Hello,

I just managed (again) to submit a half-translated string by misclicking. I
fixed it right away but now the Automatic suggestions tab contains both the
correct and the incorrect translation. (Sometimes it fails to remember
correct translations and I have to repeat them by hand later but it never
fails to remember any wrong ones; emergent artificial intelligence, I guess
:) ).

Is it possible to remove such incorrect translations from the automatic
suggestions when I spot them?

Cheers,
Mihail

-- 
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] "Translation temporarily closed"?

2021-03-11 Thread Mihail Balabanov
Hello,

I’m currently working on the new strings on master but I occasionally
update strings in the older branches. At the moment, I cannot translate any
help files in the 7.1 branch. The project "LibreOffice Help - 7.1" is
marked with a lock icon in the list of projects and when I open any
translation unit from it, Weblate shows the following error banner:

The translation is temporarily closed for contributions due to maintenance,
please come back later.
The translation was automatically locked due to following alerts: Could not
merge the repository.
<https://translations.documentfoundation.org/projects/libo_help-7-1/textsdatabase/#alerts>

Any help will be appreciated. :)

TIA,
Mihail Balabanov

-- 
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] "Translation temporarily closed"?

2021-03-12 Thread Mihail Balabanov
Hi Sophi,

7.1 is OK now but the master help project started exhibiting similar
behavior. :) I see lock icons for all languages but the message is a bit
different. It reads only:

The translation is temporarily closed for contributions due to maintenance,
please come back later.

(without the part about 'automatically locked'). Is this due to a routine
update in progress, or is it also out of the ordinary?

Cheers,
Mihail


On Thu, Mar 11, 2021 at 4:40 PM sophi  wrote:

> Hi Mihail,
>
> It should be back now
> Cheers
> Sophie
>
> Le 11/03/2021 à 15:19, sophi a écrit :
> > Hi Mihail,
> > Le 11/03/2021 à 15:04, Mihail Balabanov a écrit :
> >> Hello,
> >>
> >> I’m currently working on the new strings on master but I occasionally
> >> update strings in the older branches. At the moment, I cannot translate
> any
> >> help files in the 7.1 branch. The project "LibreOffice Help - 7.1" is
> >> marked with a lock icon in the list of projects and when I open any
> >> translation unit from it, Weblate shows the following error banner:
> >>
> >> The translation is temporarily closed for contributions due to
> maintenance,
> >> please come back later.
> >> The translation was automatically locked due to following alerts: Could
> not
> >> merge the repository.
> >> <
> https://translations.documentfoundation.org/projects/libo_help-7-1/textsdatabase/#alerts
> >
> >
> > Thanks for your feedback, there is a merge conflict and Cloph is looking
> > at it.
> > Cheers
> > Sophie
> >
>
>
> --
> Sophie Gautier so...@libreoffice.org
> GSM: +33683901545
> IRC: sophi
> Foundation coordinator
> The Document Foundation
>
> --
> 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] Can we delete entries from TM?

2021-04-15 Thread Mihail Balabanov
Hi,

Is there any way to edit Weblate's TM to remove erroneous or obsolete
translations? Sometimes we change terminology, or punctuation, or spaces,
making translations obsolete. More often than not, I click Save and after
that I realize that I have made a typo or that the translation should be
changed to match something that comes up several strings later.

Nevertheless, the old version of every translation I entered stays in the
TM. These obsolete translations gradually pile up and seriously increase my
cognitive load because I have to read them all carefully to decide what to
use every time I use the TM for a similar string (or the string gets
cosmetically changed *again*).

So, is there any way to delete unnecessary entries, or to 'reset' the TM to
only the strings that are currently used in the projects on Weblate,
discarding all strings that are not currently used in any project?

Cheers,
Mihail

PS Also, it would be a great help if it was possible to highlight the
differences between the English version of the current string and TM's
suggestions. Currently, I have to do that manually by copying them to a
diff app for every single string.

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


Fwd: [libreoffice-l10n] Can we delete entries from TM?

2021-05-06 Thread Mihail Balabanov
Hi,

With yet another batch of several hundred slightly changed long segments,
this feature cannot come soon enough! :) In the meantime, I resorted to
re-translating them with Virtaal which has this feature but hasn't been
updated for almost 10 years.

Nevertheless, what about the possibility of cleaning up the TM? I would
very much like to replace the one for Bulgarian with the current set of
translations from LO 7.1 and master.

Best regards,
Mihail

On Thu, Apr 15, 2021 at 11:30 PM Stanislav Horáček <
stanislav.hora...@gmail.com> wrote:

> Hi,
>
> Dne 15. 04. 21 v 21:22 Mihail Balabanov napsal(a):
> > Hi,
> >
> > Is there any way to edit Weblate's TM to remove erroneous or obsolete
> > translations? Sometimes we change terminology, or punctuation, or spaces,
> > making translations obsolete. More often than not, I click Save and after
> > that I realize that I have made a typo or that the translation should be
> > changed to match something that comes up several strings later.
> >
> > Nevertheless, the old version of every translation I entered stays in the
> > TM. These obsolete translations gradually pile up and seriously increase
> my
> > cognitive load because I have to read them all carefully to decide what
> to
> > use every time I use the TM for a similar string (or the string gets
> > cosmetically changed *again*).
> >
> > So, is there any way to delete unnecessary entries, or to 'reset' the TM
> to
> > only the strings that are currently used in the projects on Weblate,
> > discarding all strings that are not currently used in any project?
> >
> > Cheers,
> > Mihail
> >
> > PS Also, it would be a great help if it was possible to highlight the
> > differences between the English version of the current string and TM's
> > suggestions. Currently, I have to do that manually by copying them to a
> > diff app for every single string.
> >
>
> regarding the highlighting of differences, this issue is about it:
> https://github.com/WeblateOrg/weblate/issues/4368
>
> I agree that this would speed up translating a lot.
>
> Best regards,
> Stanislav
>
>
>
>
> --
> 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] Change in the documentation of the Format function (LO BASIC)

2021-05-06 Thread Mihail Balabanov
Hello,

I noticed that in documentation of the Format function, the name of the
first parameter had been changed from "Number" to "expression". (Starts
around
https://translations.documentfoundation.org/translate/libo_help-master/textsbasicshared/bg/?checksum=b7bf473e14ccdc22,
tens of strings are affected).

Why this change? The Format function does not convert an *expression* to a
string, it actually does convert a *number*; Format (1 + 2 + 3) returns
"6", not "1 + 2 + 3". It does not care about how the number is produced
before being passed to it. The next segments mention things like "if
*expression* contains a digit in this position" and "where *expression*
appears in the *format* code" which do not make sense; the thing that
contains a digit at position X to be formatted is the *number* produced by
the expression and being formatted by the function; the expression itself
cannot appear anywhere in the format code.

If we mean this naming to convey the idea that any argument to any function
call may be the result of an expression nested in the call, we should
change all arguments of all functions to read "numeric_expression",
"start_date_expression", "format_code_expression", etc. It appears to me
that a better solution would be to have a general explanation about nesting
expressions on an introductory page about programming in Basic.

If the reader is unfamiliar with basic programming concepts, either name
may confuse them: "number" may be misunderstood to mean only literal
numbers (1, 7.68, .78E5) and "expression" may be misunderstood to mean that
the function actually formats expressions. If the reader is familiar with
nesting expressions in function calls, they would expect the parameter name
to denote the role of the respective value in the calculation, not the way
it may be produced before passing it to the function.

As a quick fix, maybe changing the parameter to something like
"numericvalue" (following the latest convention of "all lowercase, no
spaces/underscores" for the parameter names) would be slightly better than
both "number" and "expression"?

Best regards,
Mihail

-- 
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] Change in the documentation of the Format function (LO BASIC)

2021-05-13 Thread Mihail Balabanov
Hi Sophie,

Thanks for relaying my question, Alain's explanation clarifies the matter.

I didn't consider that parameter names can be used as keywords in Basic.

This would also mean that in contrast to parameter names of Calc functions,
parameter names for Basic functions should not be translated.

Cheers,
Mihail

On Wed, May 12, 2021 at 7:04 PM sophi  wrote:

> Hi Mihail,
>
> Alain asked me to post this answer he was not able to send via Nabble:
>
> Hi Mihail,
>
> The rationale behind this change is detailed in
> https://bugs.documentfoundation.org/show_bug.cgi?id=141474 which I
> invite you to read thoroughly
>
> VBA Format help doc -
>
> https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/format-function-visual-basic-for-applications
>
> Your recommendations for an increased expressiveness of parameter names
> are highly valid. However libO Basic keyword names support - aka VBA
> named arguments - combined with LibO Basic compatibility with VBA
> prevents from changing parameter names to the extent you suggest.
>
> In the case of 'Format function', this leads to insert 'expression' and
> 'format' as "compulsory" parameter names as well as introducing multiple
> occurrences of literals in the help page.
>
> In order to better describe what 'Numeric expression' stands for, it is
> possible to provide extra Basic scripts that'll illustrate this
> terminology.
> Besides, description improvements for parameters are more than welcome!
>
> Alain
>
> PS: One may expect more Basic functions page updates intended to reflect
> 'exact' keyword names.
>
>
> Cheers
> Sophie
> Le 07/05/2021 à 08:07, Mihail Balabanov a écrit :
> > Hello,
> >
> > I noticed that in documentation of the Format function, the name of the
> > first parameter had been changed from "Number" to "expression". (Starts
> > around
> >
> https://translations.documentfoundation.org/translate/libo_help-master/textsbasicshared/bg/?checksum=b7bf473e14ccdc22
> ,
> > tens of strings are affected).
> >
> > Why this change? The Format function does not convert an *expression* to
> a
> > string, it actually does convert a *number*; Format (1 + 2 + 3) returns
> > "6", not "1 + 2 + 3". It does not care about how the number is produced
> > before being passed to it. The next segments mention things like "if
> > *expression* contains a digit in this position" and "where *expression*
> > appears in the *format* code" which do not make sense; the thing that
> > contains a digit at position X to be formatted is the *number* produced
> by
> > the expression and being formatted by the function; the expression itself
> > cannot appear anywhere in the format code.
> >
> > If we mean this naming to convey the idea that any argument to any
> function
> > call may be the result of an expression nested in the call, we should
> > change all arguments of all functions to read "numeric_expression",
> > "start_date_expression", "format_code_expression", etc. It appears to me
> > that a better solution would be to have a general explanation about
> nesting
> > expressions on an introductory page about programming in Basic.
> >
> > If the reader is unfamiliar with basic programming concepts, either name
> > may confuse them: "number" may be misunderstood to mean only literal
> > numbers (1, 7.68, .78E5) and "expression" may be misunderstood to mean
> that
> > the function actually formats expressions. If the reader is familiar with
> > nesting expressions in function calls, they would expect the parameter
> name
> > to denote the role of the respective value in the calculation, not the
> way
> > it may be produced before passing it to the function.
> >
> > As a quick fix, maybe changing the parameter to something like
> > "numericvalue" (following the latest convention of "all lowercase, no
> > spaces/underscores" for the parameter names) would be slightly better
> than
> > both "number" and "expression"?
> >
> > Best regards,
> > Mihail
> >
>
>
> --
> Sophie Gautier so...@libreoffice.org
> GSM: +33683901545
> IRC: sophi
> Foundation coordinator
> The Document Foundation
>
> --
> 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] Can we delete entries from TM?

2021-05-15 Thread Mihail Balabanov
Hi Sophie,

I searched one more time but my findings were the same as before:

* Weblate’s automatically filled TM is separated into scopes: personal,
per-project, and shared.

* I can manage my personal TM by downloading, uploading, and deleting TM
files. Individual strings cannot be edited or deleted, so the most
practical way to clean up the TM is to delete everything Weblate has
collected and upload a TMX file generated from the latest translations.

* I cannot change project-level TM though. I can only download JSON/TMX
files from it. Also, I seem to have no direct access to the shared scope at
all.

Apparently, while translating, each new entry is added separately to each
scope, so to remove the obsolete entries one has to be able to change the
TM data in all scopes. There is a permission called 'Managing translation
memories' which may or may not help. Judging by the name, it may allow
deleting and uploading per-project and shared TMs. OTOH, if there is no way
to restrict access only to the respective team's language, the server
admins may be reluctant to give it to just any l10n team member. :)

A workaround that comes to mind is to have some automated way to reset TMs
(all scopes) at the server side so that a language team may request
resetting the entire TM for that language without causing too much manual
work on the part of the server maintainer. I assume it is currently
possible (but maybe non-trivial) to purge the entire TM for a language and
regenerate it from the existing translations at the backend because I have
some dim recollection of someone requesting such a thing on this list.

Cheers,
Mihail

PS Unfortunately, the Weblate feature request about highlighting
differences in fuzzy matches remains in the 'help wanted' status since
September 2020.


On Fri, May 7, 2021 at 1:39 PM sophi  wrote:

> Hi Mihail,
> Sorry for the delay to answer your question
> Le 15/04/2021 à 21:22, Mihail Balabanov a écrit :
> > Hi,
> >
> > Is there any way to edit Weblate's TM to remove erroneous or obsolete
> > translations? Sometimes we change terminology, or punctuation, or spaces,
> > making translations obsolete. More often than not, I click Save and after
> > that I realize that I have made a typo or that the translation should be
> > changed to match something that comes up several strings later.
> >
> > Nevertheless, the old version of every translation I entered stays in the
> > TM. These obsolete translations gradually pile up and seriously increase
> my
> > cognitive load because I have to read them all carefully to decide what
> to
> > use every time I use the TM for a similar string (or the string gets
> > cosmetically changed *again*).
> >
> > So, is there any way to delete unnecessary entries, or to 'reset' the TM
> to
> > only the strings that are currently used in the projects on Weblate,
> > discarding all strings that are not currently used in any project?
>
> You can manage your entries into the TM under your profile. I didn't
> test it, but you can download files and upload them. There is not much
> more information in the Weblate help. Maybe you can give it a try and
> let us know your findings.
> Note that there are interesting (for us :) issues reported to Weblate:
>
> https://github.com/WeblateOrg/weblate/issues?q=is%3Aissue+is%3Aopen+translation+memory
>
> Cheers
> Sophie
>
> --
> Sophie Gautier so...@libreoffice.org
> GSM: +33683901545
> IRC: sophi
> Foundation coordinator
> The Document Foundation
>
> --
> 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] Weblate: help ranking what you need :)

2022-02-23 Thread Mihail Balabanov
Hi Sophie,

I am very happy to learn about this effort! My most wanted enhancements
among the mentioned ones would be these three:

https://github.com/WeblateOrg/weblate/issues/6440
Translation Memory Maintenance - Delete Entries

https://github.com/WeblateOrg/weblate/issues/4368
Improved presentation of differences in machine translations

https://github.com/WeblateOrg/weblate/issues/1861
Search should ignore hotkey symbols

Cheers,
Mihail


On Wed, Feb 23, 2022 at 10:49 AM sophi  wrote:

> Hi all,
>
> The Board would like to dedicate a budget to fund some Weblate
> issues/enhancements and I'd like to have your feedback on what would be
> the most important for your team.
>
> Below is a list of tickets that I monitor on Weblate project. This is
> what I think would help l10n teams to work faster but you may have
> others in mind. So please review and rank the list. If you have other
> tickets, also add them in the ranking. Thanks a lot in advance!
>
> https://github.com/WeblateOrg/weblate/issues/7205
> unchanged translation flag notwithstanding glossary term marked as
> untranslatable
>
> https://github.com/WeblateOrg/weblate/issues/6440
> Translation Memory Maintenance - Delete Entries
>
> https://github.com/WeblateOrg/weblate/issues/5898
> Allow to update translation comments from UI
>
> https://github.com/WeblateOrg/weblate/issues/5854
> Autofix Bangla/Bengali sentence ender to ।
>
> https://github.com/WeblateOrg/weblate/issues/5842
> Shortcut for suggest
>
> https://github.com/WeblateOrg/weblate/issues/5792
> Component lists in the selected language
>
> https://github.com/WeblateOrg/weblate/issues/5447
> Per-language translation workflow setting
>
> https://github.com/WeblateOrg/weblate/issues/4368
> Improved presentation of differences in machine translations
>
> https://github.com/WeblateOrg/weblate/issues/4160
> Allow to filter on language in reports
>
> https://github.com/WeblateOrg/weblate/issues/3455
> add Document Foundation identity provider
>
> https://github.com/WeblateOrg/weblate/issues/3242
> Ability to download all translation memory from a given project in a
> per-language basis
>
> https://github.com/WeblateOrg/weblate/issues/3166
> Translation propagation
>
> https://github.com/WeblateOrg/weblate/issues/2241
> Search who translates the same language
>
> https://github.com/WeblateOrg/weblate/issues/2127
> Create Group Administration Permissions
>
> https://github.com/WeblateOrg/weblate/issues/1994
> Check if two different strings share same translation
>
> https://github.com/WeblateOrg/weblate/issues/1661
> Suggestion rejection reason: possibility of explaining why you reject a
> suggestion
>
> https://github.com/WeblateOrg/weblate/issues/263
> Nested projects or project grouping
>
> Cheers
> Sophie
> --
> Sophie Gautier so...@libreoffice.org
> GSM: +33683901545
> IRC: soph
> Foundation coordinator
> The Document Foundation
>
> --
> 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] Support for a new feature in weblate

2022-07-15 Thread Mihail Balabanov
I would definitely sponsor that.

On Fri, Jul 15, 2022 at 11:20 PM Milos Sramek 
wrote:

> Hi,
>
> would it be possible to somehow support development of a new feature in
> weblate by the TDF?
>
> Specifically, this one: https://github.com/WeblateOrg/weblate/issues/4368
>
> When translating, I usually use Automatic suggestions. These are sorted
> by similarity. If similarity is higher than 90%, a string is usually
> usable, but I still need to know where the difference is. It would be
> great if these differences were highlighted. Currently I have to compare
> the English string and source of the suggestion visually, which is quite
> cumbersome and slow.
>
> Milos
>
>
> --
> email: sramek.mi...@gmail.com, jabber: milos.sra...@jabber.sk
>
>
> --
> 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] Unusual behavior of Weblate

2023-02-06 Thread Mihail Balabanov
Hello,

I noticed two unusual things working with Weblate lately:
- There are sporadic 'Delete entry' buttons. Why do they appear only for a
small percentage of the entries and what do they actually do? I would very
much like to delete erroneous or obsolete entries but the button never
appears on any of them.
- Sometimes there is no similarity percentage. This hampers productivity
noticeably because when I know that a string is a 100% match, I can just
click through, otherwise I have to copy and compare in an external program.

This link illustrates both:

https://translations.documentfoundation.org/translate/libo_help-master/textscalc01/bg/?q=state%3A
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] Unusual behavior of Weblate

2023-02-06 Thread Mihail Balabanov
Thanks for the clarifications; I'm aware of the three-tier TM but I did not
pay attention that the "Delete entry" buttons are shown only where the
"Personal" tier is present in the Origin list. Unfortunately, the obsolete
entries and the ones containing typos and such gradually pile up and they
are too many and too scattered to collect them manually. It would be better
to be able to delete them as I stumble upon them in the suggestion list or
immediately after I realize I have just saved a translation containing a
typo.

I guess regenerating Weblete's TM from the latest one or two project
versions (7.4 and master) would be a good way to clean it up. Can I request
such a thing for Bulgarian?

Also, I'm sorry about the broken link, here is a permalink to an entry:

https://translations.documentfoundation.org/translate/libo_help-master/textscalc01/bg/?checksum=6ea269b7376bb4cb

For me, the Similarity column is empty for the last 4 suggestions.



On Mon, Feb 6, 2023 at 2:13 PM Christian Lohmaier 
wrote:

> Hi Mihail,
>
> On Mon, Feb 6, 2023 at 11:46 AM Mihail Balabanov 
> wrote:
> >>
> > I noticed two unusual things working with Weblate lately:
> > - There are sporadic 'Delete entry' buttons. Why do they appear only for
> a
> > small percentage of the entries and what do they actually do?
>
> I assume you refer to the entries in the "Automatic Suggestion" area
> from the weblate translation memory.
>
> Weblate has a three-tier translation memory:
> * the project's translation memory, that can also optionally create
> all new entries into an
> * instance-wide shared translation memory
> * and finally a user-specific translation memory
>
> So you'll see delete entry buttons for the strings coming from your
> user translation memory, for strings that you translated in the past
> within weblate.
>
> > I would very
> > much like to delete erroneous or obsolete entries but the button never
> > appears on any of them.
>
> If you point me to those invalid entries, I can remove them.
>
> > - Sometimes there is no similarity percentage. This hampers productivity
> > noticeably because when I know that a string is a 100% match, I can just
> > click through, otherwise I have to copy and compare in an external
> program.
>
> Also please provide a link for that.
>
> > This link illustrates both:
> >
> >
> https://translations.documentfoundation.org/translate/libo_help-master/textscalc01/bg/?q=state%3A
> > 
> Those kind of links are not stable, what it points to is depending on
> what you translate, better use the "copy permalink" option (the little
> chain-link icon at the top-right of the translation area)
>
> Looking at
> https://translations.documentfoundation.org/translate/libo_help-master/textscalc01/bg/?checksum=6ea269b7376bb4cb
> I see it has entries from weblate's translation memory as well as from
> the amagama server, the tmserver entries. That contains old strings
> from pootle, from the time before weblate was used. So old strings
> from tmserver, new strings from weblate's translation memory.
> And I guess weblate just doesn't return amagama's quality score
> (Levenshtein distance), but all results returned by amagama have at
> least a 75% confidence (from amaGama's POV), but that's just comparing
> against the source string, so not sure whether it is suitable to also
> show it
>
> curl http://localhost:/api/v1/en/bg/unit/is%20less%20than
>
> [{"quality": 75.0, "rank": 100.24, "source": "less than",
> "target": "по-малко"}, {"quality": 75.0, "rank": 100.24,
> "source": "less than", "target": "По-малко"}, {"quality": 75.0,
> "rank": 100.24, "source": "less than", "target": "по-малка
> от"}, {"quality": 75.0, "rank": 100.24, "source": "Is Less
> Than", "target": "По-малко"}, {"quality": 71.42857142857143, "rank":
> 100.24, "source": "Much less than", "target": "Много
> по-малко"}]
>
> (ignore rank, that was always flagged as internal flag that can
> disappear in future)
>

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

2023-09-03 Thread Mihail Balabanov
Hi,
When I thought about it, 'simulated' also sounds weird. The manually
formatted headings, list numbers, captions and other items are neither
fake, nor simulated. They are *actual* list headings, numbers, captions,
etc., just done manually, in a way we don't recommend. The software may not
recognize them as such but any reader would.
So I think a more precise description would be 'manually added list
numbers', 'manually formatted headings' or something along these lines.
Cheers,
Mihail

On Thu, Aug 31, 2023 at 12:05 PM Milos Sramek 
wrote:

> Hi Ilmari,
>
> thank you for the link.
>
> I can see that you have changed "label from Fakes to Simulated captions".
>
> That makes sense, thank you
>
> Let's wait for Webate update
>
> Best
>
> Milos
>
>
>
>
> On 29.08.23 11:28, Ilmari Lauhakangas wrote:
> > On 29.8.2023 9.43, Martin Srebotnjak wrote:
> >> I would call it "imitation" or "simulated"/"simulation", it just
> >> imitates/simulates the "proper" numbering.
> >>
> >> In the days of OOo every new feature needed first a confirmed design
> >> document where even the UI-mock-up was presented.
> >> Now we just code - and take care of the UI-repercussions later.
> >>
> >> And as Miloš wrote, it doesn't work for me (macOS 7.6.0.1), while others
> >> do. It is a "fake" check :)
> >>
> >> Lp, m.
> >>
> >> V V tor., 29. avg. 2023 ob 07:17 je oseba Yury Tarasievich <
> >> yury.tarasiev...@gmail.com> napisala:
> >>
> >>> That kind of use of the word feels singularly
> >>> inappropriate in the modernworld.
> >>> Likely to cause confusion, even indignation.
> >>>
> >>> I mean, how come your program calls my manual
> >>> numbering 'fake'?? It is 'unautomated'
> >>> numbering, certainly, but 'fake'?
> >>>
> >>> Isn't this taking a bit too much on ourselves?
> >>>
> >>> On 28/08/2023 18:44, Milos Sramek wrote:
> >>>
> >
> >>>
> https://help.libreoffice.org/latest/en-US/text/swriter/01/accessibility_check.html
> >>>
> >
> > Sorry, I quoted the help page incorrectly. The help page does not
> > currently mention that there is a check for simulated *captions*.
> >
> > I have submitted a change to the string:
> > https://gerrit.libreoffice.org/c/core/+/156238
> >
> > See the code for the checking logic:
> >
> https://opengrok.libreoffice.org/xref/core/sw/source/core/access/AccessibilityCheck.cxx?r=8386d8e5#978
> >
> >
> > To see the string in the UI, open the accessibility sidebar panel.
> > Type text that starts with Caption, Illustration, Table, Text, Drawing
> > or Figure
> > Immediately insert an image.
> >
> > Now you should see "Fakes" in the sidebar (without my patch).
> >
> > The check also works, if the image is anchored to the paragraph with
> > the text.
> >
> > Ilmari
> >
>
> --
> email: sramek.mi...@gmail.com, jabber: milos.sra...@jabber.sk
>
>
> --
> 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] Abbreviation for Drag 'n Drop

2024-01-08 Thread Mihail Balabanov
Hi,
Since there is no commonly accepted Bulgarian abbreviation for drag and
drop, I would translate "DnD+Shift" as "Shift+плъзгане" (Shift+drag),
leaving "and drop" to be only implied. Maybe something similar would be
suitable for other languages?

On Mon, Jan 8, 2024 at 10:34 AM Heiko Tietze <
heiko.tie...@documentfoundation.org> wrote:

> Some effort is currently made by Jim to allow drag'n drop from the
> Navigator not
> just as link but also to get cross-references into the document. Users can
> trigger the function via pup-up menu or per accelerator. And to give a
> clue
> about the latter we should add some text to the menu, which could be
> "Insert as
> Text Reference (DnD+Shift)" (for the full list of commands see attachment
> to
> https://bugs.documentfoundation.org/show_bug.cgi?id=36310#c21).
>
> Now I wonder if DnD for Drag'n Drop is well-known and easy to translate.
> German
> could be "Ziehen & Ablegen" abbreviated to "Z&A" - which users would never
> understand. Any idea?
> --
> Dr. Heiko Tietze, UX-Designer and UX-Mentor
> Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
> The Document Foundation, Winterfeldtstraße 52, 10781 Berlin, DE
> Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
> Legal details: https://www.documentfoundation.org/imprint
>
> --
> 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] Placeholder string instead of tooltip?

2024-01-24 Thread Mihail Balabanov
Hello,

This extended tooltip looks like a forgotten placeholder:

https://translations.documentfoundation.org/translate/libo_ui-master/sfx2messages/bg/?checksum=a5e915a57b801969

Cheers,
Mihail

-- 
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] LibreOffice 24.2 "New Features" video script for translations

2024-02-04 Thread Mihail Balabanov
Hi,
The Bulgarian translation is ready.
Cheers,
Mihail

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