Date: prev next · Thread: first prev next last
2024 Archives by date, by thread · List index


Hi Prasanta,

On Tue, Oct 15, 2024 at 11:53 AM Eike Rathke <erack@redhat.com> wrote:

Q. Which component should be given the most priority (Ascending to
Descending) ?

Your approach of {cui,svx,sw,sc} sounds about right to me, first cui and
svx for most common dialogs and then the applications. Maybe shift
svtools and sfx2 and vcl up in priorities, so
{cui,svx,sfx2,svtools,vcl,sw,sc,sd,chart2,dbaccess,starmath} would cover
the most used core modules.


officecfg contains most of the menu items, button tooltips etc.


-- Any documentation link, I'm giving priority based on the increasing
order of string numbers, as below:

Btw, you can completely ignore dictionaries/*, there's nothing to
translate from other languages' dictionaries.


 dictionaries/* are mainly for the installer (only a few strings to
describe the module).

Probably it's a sane approach to translate UI elements first, which are
usually shorter strings, and leave error messages, long tooltips, Calc
formula descriptions, installer strings, etc. for later.

Best regards,
Andras

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.