Also, I still can't readily find on LO sites the
authoritative description of the .PO based L10N
process. Pootle isn't acceptable for the
languages with the comparatively weak
terminological base . In such cases it's common
for everybody to translate just as one sees
fit. Sasha's
On 03/04/2011 09:53 AM, Sophie Gautier wrote:
3) The .PO technological cycle isn't documented comprehensively on LO
sites.
What do you mean by technological cycle? I've begin to write some
...
In this context, I'd expect something on the
lines of:
(Provided your work is based on the .PO
Many thanks, Andras!
-Yury
On 03/04/2011 01:16 PM, Andras Timar wrote:
...
Initially we thought that l10n of LibreOffice 3.3 will be as simple as
...
--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to
Also, same word in English may indeed relate to
a different words in translation depending on
context.
-Yury
On 04/19/2011 03:21 PM, Andras Timar wrote:
...
This is not a false positive. You need to translate Heading and Title
to different words, otherwise you'll have troubles with default
Will there be KeyID builds, possibly?
On 10/27/2011 12:38 PM, Thorsten Behrens wrote:
...
for 3.4.4 rc1, we're now uploading builds to a public (but
...
--
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems?
On 10/27/2011 06:35 PM, Andras Timar wrote:
No, 3.4.4 is stable. You can use an older KeyID build (3.4.0beta2),
strings are 99.99% percent the same.
Thanks. You should note, that that KeyID build
can't be used directly on some systems:
$ ldd -r libpyuno.so
ldd: warning: you do not have
On 11/01/2011 10:08 AM, Andras Timar wrote:
...
You can still expect string changes, string freeze is due to Dec 19. Let
me know, if you have questions.
...
New templates are for 3.5. Do you expect a
significant string changes in 3.4 series, though?
Yury
--
Unsubscribe instructions:
Would it be possible to maintain a custom
comments in PO files of the template set? Sort
of what translate-toolkit utils add, # (pofilter)?
The use I have in mind for that right now is
keeping meta-information, e.g., hints for
translators. Sort of: the term XYZ in this
record relates to
I was rather referring to the possibility of
'just' having extra comments associated with
certain 'strings' and kept there.
Would this be equivalent to the introduction of
extra source code? What serves as a master-copy
of (en-US) templates then, actually, a Pootle or
PO set?
Yury
--
On 11/08/2011 01:52 PM, Yury Tarasievich wrote:
I was rather referring to the possibility of
...
Just after sending, saw Andras' answer to
Martin. Scratch my questions, as the problem is
of another scale than I thought.
Yury
--
Unsubscribe instructions: E-mail to l10n+h
If you ask for the meaning, it's:
In OOO internal representation, a cell which
spans the rows is represented by nested table.
In wiki representation, a cell which spans the
rows is represented by column and row spans.
That's the reason why you can't export cells
which span the rows to a
For Belarusian, D.M with no more than two digits
per part might do (is the two-digit limit
enforcable?).
Actually, it'd be better to have possibility of
switching off the feature altogether, across
the installation, as the traditional fractional
part separator /comma/ tends quite often to
On 01/17/2012 05:23 PM, Eike Rathke wrote:
On Tuesday, 2012-01-17 07:41:42 +0200, Yury Tarasievich wrote:
Actually, it'd be better to have possibility of switching off the
feature altogether, across the installation, as the traditional
fractional part separator /comma/ tends quite often
On 01/18/2012 03:50 PM, Eike Rathke wrote:
...
But it would be ever so better to have a possibility for computer to
not second-guess at all, as such guesses might even be culturally
irrelevant.
... I'm confused now, does be-BY want incomplete date patterns, yes or
no?
Yes. Sorry.
And also
On 01/19/2012 11:46 PM, Eike Rathke wrote:
And also it wants a possibility to switch off incomplete date
recognition completely? Is this doable?
No (not yet?) Best would be to implement an editable list of not
auto-generated patterns, so the user could add/remove to her likes.
...
Well, I
Generally speaking, producing the quality
translation is as much a function of
formal (self-)training and hard work as
producing the quality code.
Just being native speaker (and I'm sort of
sadly privileged to know the emptiness of terms
such as this) is not enough.
Least of all is it a
Right, thank you.
On 08/26/2012 07:24 PM, Rimas Kudelis wrote:
I just gave Mikalai admin rights on /be/. Now
there are two users with such privileges: him
and sasha.
Yury
--
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems?
I'd appreciate a quick answer on l10n-related
aspect of bibliography index (not involving
exhaustive source digging):
The default set of bib entries types (Article,
Book etc.), with their default formattings -- is
it programmed in or, possibly, put as a xml-form
somewhere in a system
Will there be a pot files set for a download and
non-pootle work?
On 11/19/2012 07:59 PM, Andras Timar wrote:
We have two LibreOffice branches, and there is no automatic migration
...
--
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems?
Thanks. BTW and FWIW, since 2.0 times, I was
doing the migration with the pot2po.
On 11/19/2012 09:35 PM, Andras Timar wrote:
Yes,
http://dev-www.libreoffice.org/l10n/latest-pot/libreoffice-4.0-en-US-2012-11-18.pot.zip
I recommend that you download your migrated po files from Pootle.
...
Building OpenOffice these days isn't SO
difficult. Of course, you'd have to be prepared
to spend some GBs and some bandwidth and some
time building. Several gigs of storage, about 1
gig of downloads, several hours on a fairly
modern desktop.
Not a negligible effort, yes. I also wouldn't
Well, yes, kinda, provided you can spare the cycles.
I'm somewhat surprised, though, that nobody else
replied to that.
Yury
On 02/25/2013 08:31 AM, Baurzhan Muftakhidinov
wrote:
Hello,
I kinda solved this issue by making a nightly builds of LO 4.0,
at each build I pull zip file for my
In a modern world, I think it might even be the
time to do away with the locale-language
connection. Even the locale data regulation span
might be reduced somewhat.
More, with the major culture-data-employing
entities (CLDR, Google, what-have-you) all
having their outlooks competitively
I understand this isn't the first time the
question comes up, but:
Everybody knows any template file may be set 'as
default'.
Is there any way to access the 'default default'
template, the one which the documents with empty
'template' property refer to? All those
undeletable style
Might be the English descriptions for Calc
functions were initially translated, at least
partially, from German.
-Yury
On 07/20/2013 11:31 PM, Mihovil Stanic wrote:
Dana 20.7.2013. 18:31, Mirosław Zalewski je
...
Personally, I favor precise and hermetic
language. People who need certain
But what about providing some clues in the help
for those who know what they want but are
unacquainted with the developing system in the
first place? Your approach leaves too high entry
threshold.
Continuing with the Calc functions, I might know
what statistical distributions are but to
That's a difficult one to keep track of. With no
meta-info in POT/PO base. E.g., this has been
corrected in /be/ for years, but after the
recent massive changes sort of crept in again.
Indeed, what do we do now?
-Yury
On 07/22/2013 11:04 PM, Sophie wrote:
egrep -A3
Just change the *_HEADLINE_BASE one to something
like *, main one.
You do not commonly use that style from UI,
anyway, that's the root node for the headings
settings.
-Yury
On 07/22/2013 11:40 PM, Mihovil Stanic wrote:
...
I can try to change translation on one of those
strings but it will
23, 2013 at 7:48 AM, Yury Tarasievich
yury.tarasiev...@gmail.com wrote:
Just change the *_HEADLINE_BASE one to something like *, main one.
You do not commonly use that style from UI, anyway, that's the root node for
the headings settings.
Yes, but main one is misleading and IMHO wrong
Or, even better (?), rename it to the tune of
Heading Base Style.
-Yury
On 07/23/2013 12:11 PM, Niklas Johansson wrote:
Hi
For future versions of LibreOffice wouldn't it
be a good idea to change the English string from
Title to Main Title? Or is it wrong to call it
...
--
To unsubscribe
.
Should it be a question for UX-advise?
/Niklas
Yury Tarasievich skrev 2013-07-23 11:32:
Or, even better (?), rename it to the tune of
Heading Base Style.
-Yury
On 07/23/2013 12:11 PM, Niklas Johansson wrote:
Hi
For future versions of LibreOffice wouldn't it
be a good idea to change the English
Better comprehensibility would also be good.
The Title-Name of the document variant might
also be considered for (2).
-Yury
On 07/23/2013 02:42 PM, Sérgio Marques wrote:
2013/7/23 Yury Tarasievich
Actually, I mean changing both:
1) Heading - Heading Base Style
2) Title - Document
Would such comment be a solution, really?
For one, PO fileset is local. Work put there is
being constantly lost, if slowly.
Now, is there a POT fileset serving as the root
source of English strings?
Is one Andras publishes such root source?
Or is there one more root-ish than that?
-Yury
set deliberately.
-Yury
On 07/23/2013 04:46 PM, Sérgio Marques wrote:
2013/7/23 Yury Tarasievich
yury.tarasiev...@gmail.com
mailto:yury.tarasiev...@gmail.com
Better comprehensibility would also be good.
The Title-Name of the document variant
might also be considered for (2).
I
On 07/23/2013 06:48 PM, Sophie wrote:
...
Now, is there a POT fileset serving as the
root source of English strings?
Is one Andras publishes such root source?
Or is there one more root-ish than that?
The latest pot file is published here by Andras
On 07/23/2013 07:23 PM, Martin Srebotnjak wrote:
SDF is deprecated - POT files are generated directly from code, and PO
files are directly checked back into code.
So where would the comment come from after the
re-generation?
-Yury
--
To unsubscribe e-mail to:
on this string.
-Yury
On 07/23/2013 08:50 PM, Christian Lohmaier wrote:
On Tue, Jul 23, 2013 at 5:48 PM, Yury Tarasievich
yury.tarasiev...@gmail.com wrote:
'Title', 'Heading', 'Name of the document' -- all these are good and bad.
No - in this context Name of the document is simply wrong for either
On 07/23/2013 07:40 PM, Martin Srebotnjak wrote:
2013/7/23 Yury Tarasievich yury.tarasiev...@gmail.com:
So where would the comment come from after the re-generation?
I have written that already in another mail - from the code, from the
same place where the string comes. There should be some
That's a term from lead blocks typography times.
Means always add fixed amount *between* the text
lines. As that sort of the specialized
terminology went out of use somewhat, yes, it's
rather hard to translate meaningfully and tersely.
-Yury
On 07/26/2013 11:48 AM, Mihovil Stanić wrote:
Hi
Make it Source cells, better.
-Yury
On 09/02/2013 12:41 AM, Mirosław Zalewski wrote:
...
LibreOffice Calc, main pivot table window (Data → Pivot table →
Create... with at least two cells selected; skip first window), in
expandable part of window (More button) .
What:
Label for very first
On 10/11/2013 11:26 PM, Tom Davies wrote:
...
OmegaT sounds like the main tool i was looking for.
...
I feel I still ought to warn you from my own
experience.
Yes, OmegaT is, /de facto/, the only serious
tool of description available open-sourcely (and
not tied-in into some specific
In fact, I believe I've seen an OOO/LO add-on
for parallel (segment-by-segment) translation.
It was called translator's friend or in the
similar vein. I didn't try it.
-Yury
On 10/12/2013 09:49 AM, Tom Davies wrote:
...
Firefox has a lot of different add-ons that are quite good MTs. Quite
Ah, I found the reference to this add-on in my
notes. It's named 'translation table' :), and
it's function isn't exactly CAT (for which
functionality authors refer to Anaphraseus
add-on for OmegaT :), just a two-column segment
layout helper (still very useful for what you
seem to have in
Tom, Thomas,
From what I can see in the code, Anaphraseus
seems to be at least partially self-contained
CAT (relying on OO for UI functionality (?)),
and so the OmegaT reference in the 'Translation
table' annotation looks somewhat bogus.
On the other hand, Anaphraseus definitely knows
The translate-toolkit which I suppose is used in
Pootle, is intelligent enough to migrate the
content based on the combination of msgid and
identifier (in msgcomment), but not intelligent
to pass on the result as a 'sure thing', only as
a fuzzy hit. You'd still have to go through the
fuzzies
That is all fine, but be advised that OT if used
incautiously may insert lots of untranslated
strings into the result. First it's all dandy,
next moment you're looking at 20% of English
strings in your product.
After all, OT isn't the specialised UI
translation tool like kbabel, poedit, and
Integrals have top/bottom indices (upper and
lower integration limits, strictly speaking);
these are aligned with 'int' sign.
Super-/sub- scripts indices denote other things
and are drawn to the side of what they are
indexes of.
Yury
On 01/04/2014 05:14 AM, Sérgio Marques wrote:
And
These look like standard names for stick-on
labels (?).
In harmonisation practive, the standards' codes
(cyphers) usually are only transcribed, indeed,
but titles *are* translated. How else? :)
Yury
On 03/31/2014 08:18 AM, Andras Timar wrote:
You will see strings like CIL-W227 Diskette
On 11/30/2014 05:13 AM, Adolfo Jayme Barrientos
wrote:
...
In case you guys didn’t know, Apple [1], Microsoft [2] and GNOME [3]
are all recommending the use of typographical apostrophes and
quotation marks, among other characters that have been historically
...
Said recommendations, while
On 11/30/2014 11:23 AM, Rimas Kudelis wrote:
2014.11.30 07:38, Yury Tarasievich rašė:
...
And if you use Windows and want to make inputting these characters even
more convenient, you can always customize your keyboard layout adding
missing typographical symbols to the AltGr (or any other
On 11/30/2014 12:07 PM, Yury Tarasievich wrote:
...
What's strictly incorrect in straight
apostrophe, anyway?
...
Anyway, here's an idea for you guys about to
suffer from this: diff the en_US source before
and after apostrophe nice-fication, then create
a program which looks
On 11/30/2014 02:33 PM, Jesper Hertel wrote:
Just because you do not like an idea or are
afraid of its consequences there is no reason to
shoot it down with sarcasm or other violent
methods. That is never helpful.
Oh dear. What to do then, if one doesn't like
the idea and does NOT in fact
On 11/30/2014 09:30 PM, Akerbeltz.org wrote:
...
Yes, we're translating pro bono publico but it's still a callous way of treating
donated lifetime.
...
Did you notice how I've left out that angle? :)
And 'callous' is the right word here (incorrect
apostrophes!).
Yury
--
To unsubscribe
In fact, this is a good idea, not in sarcastic
way whatsoever. Point the translation origin to
the uncorrcted, un-nicefied English (updated
only if the semantics change). Make production
en_US a 'translation' of this.
Yury
On 11/30/2014 08:13 PM, Olivier Hallot wrote:
...
I suggest to
On 12/01/2014 07:07 AM, Donald wrote:
In the UI: svx/source/dialog.po there are some colors to be translated:
Tango green, Tango red and others with Tango in the name. What is the
significance of the word Tango? Is it part of the color name or is it
software or something else?
Tango scheme.
On 12/01/2014 01:11 PM, Christian Lohmaier wrote:
On Mon, Dec 1, 2014 at 5:58 AM, Yury Tarasievich
yury.tarasiev...@gmail.com wrote:
On 11/30/2014 11:52 PM, Rimas Kudelis wrote:
And why is not anyone (besides me) discussing automation, of that same
problem, too?
Probably because
I may be completely misunderstanding this, but
it seems to me the point is the en_US strings
should be translations as well. That would put
much needed damper on the changes introduced
just because they can be introduced. As a
secondary gain, translations are (hopefully)
created by folks
Those changes, while possibly worthwhile from
en_US perspective, are not related to what
localised interface looks like. Since version 2
the workload in ui strings might easily
constitute +100% of initial 25k. Did the ui
change that much? No.
Yury
On 12/13/2014 03:22 AM, Khaled Hosny
Not so feasible, I think.
Work based on another translation would very
likely mean missing important nuances.
Ironically, this was the case with English (!)
in times of OO 2.0, when it was somewhat more
instructive to look into German strings
(originating from StarOffice) for the precise
On 12/14/2014 09:19 AM, Khaled Hosny wrote:
...
But that was not my point, I was complaining about people who think that
consistency, following linguistic rules and proper typography are usless
cosmetics. Regardless of how localisation will be done or what language is
...
Then you completely
On 12/14/2014 11:07 AM, Sophie wrote:
...
And I have yet to see those technical marvels we've been promised will
compensate for this problem (promised with lot of eff-ing at silly
localisers, by the way).
Hey, those scripts are done by people to help us, so don't shout on
them. We will discuss
On 12/14/2014 11:59 AM, Rimas Kudelis wrote:
2014.12.14 02:43, jonathon wrote:
...
The more fundamental error is assuming that what is in source is
consistently en_US, or any other en_* variant.
It should be. You can look at it the other way around: anything that
gets in the source should
On 12/14/2014 12:47 PM, Khaled Hosny wrote:
I have been localising software for much longer
than I have been making fonts (or even writing
software) and I know that reviewing a few
hundred strings that were trivially changed is
not the end of the world. Usually the tool I'm
using (be it Pootle
I won't pretend I understood the Chinese and
Japanese cases, however, seems to me ALL this,
or at least the most representative parts,
should go into help, all languages, possibly not
into the specific Basic function but into some
separate subclause (handling the multi-byte
codings?).
This
wrote:
On Mon, Jun 1, 2015 at 9:54 AM, Cor Nouws oo...@nouenoff.nl wrote:
Yury Tarasievich wrote on 28-05-15 07:50:
E.g., in Writer's 'Edit paragraph style' dialog, 'Alignment' tab, 'Last
line' combobox (activated if 'alignment' is set to 'Justified'), the 1st
variant is 'Default'.
I happen
Hello all,
What is the correct (and productive) workflow
procedure if the UI string is just vaguely
formulated? Not incorrect as such, just vague,
inconcrete, overly cryptic?
E.g., in Writer's 'Edit paragraph style' dialog,
'Alignment' tab, 'Last line' combobox (activated
if 'alignment'
On 06/29/2015 04:13 PM, Christian Lohmaier wrote:
On Mon, Jun 29, 2015 at 1:01 PM, Yury Tarasievich
yury.tarasiev...@gmail.com wrote:
Regardless of non-trivial effort and commendable result,
I think trivial effort :-)
Not that trivial, surely.
I'm aghast, guys.
So that's how manpower
On 06/29/2015 11:53 AM, Mihkel Tõnnov wrote:
2015-06-29 11:40 GMT+03:00 Serg Bormant borm...@gmail.com:
emoji autocorrect file, what is it exactly? Do we need to translate
See here ;) https://wiki.documentfoundation.org/Emoji
Regardless of non-trivial effort and commendable
result, I'm
Apologies, all, but shouldn't we "use the
source" at this juncture?
All this sounds like guessing, and the likely
outcome would be another wild-guess translation
(well, translationS) -- in the spirit of MSword
localisations, anyway. :)
-Yury
PS I don't have the blob in question on hand at
On 13/06/16 11:58, Eike Rathke wrote:
On Friday, 2016-06-10 07:40:36 +0300, Yury Tarasievich wrote:
*Safer* to have no space there at all, and for Belarusian, too.
...
Anyway, programs neither help with entering the glyph, nor highlight its
non-breakability.
It's for display purposes only
Your explanation, while lingually flawless,
would confuse the askers, too, I guess. :)
The string means that for updates to take effect
one must press/click something (button?)
labelled 'Apply'.
-Yury
On 01/18/2016 07:43 PM, anne-ology wrote:
Well, whoever typed this must have
My apologies, but I'd like to offer some
corrections to this -- assuredly off-topic --
thread.
On 01/21/2016 01:15 AM, Charles-H. Schulz wrote:
Interesting reaction but I am afraid we are bothing peope doing real work here.
Anne-ology, you and I are the ONLY three people top posting in this
There are (still) lots of artifacts of a string
kind in LO, I believe.
However, if you do not know the string is
actually displayed, how do you know there is
nothing appropriate to click?
Generally -- is there any way to mark the
actually unused strings, so as to waste not the
effort?
By my estimates -- I'm looking at the kbabel
stats, which aren't perfect, -- last three years
(half 2013--end 2015) brought about 100% overall
"change" (untranslatedness) in UI strings corpus
(up to 30K units). Of course, this includes
strings going fuzzy without real change in the
content,
On 20/08/16 13:07, MENGUAL Jean-Philippe wrote:
I would like to know if Libreoffice can be translated without Pottle. I
Yes, it's doable, and there are precedents of it
being done that way.
or upload. Can the translation be done continuously? Or it is "block"
per release (a cycle)?
Does keyboard layout actually affect the (new)
text paragraphs language setting?
On my Linux system I have three keyboard layouts
set up and no check in the 'Ignore...' box and
LO sets the text language just as it's set in
the config.
On 16/11/16 13:20, Michael Bauer wrote:
...
Ok so it
That would be 4.5 points, in typographic
measure, so no, shouldn't convert that (and
please nobody start on there being two kinds of
typographic points )).
Only I wonder what's measured that precisely, in UI?
On 22/12/16 22:39, Olivier Hallot wrote:
I found some measurements in inches in
2016-12-23 13:07 keltezéssel, Yury Tarasievich írta:
That would be 4.5 points, in typographic measure, so no, shouldn't
convert that (and please nobody start on there being two kinds of
typographic points )).
Only I wonder what's measured that precisely, in UI?
On 22/12/16 22:39, Olivier Hallot
Totally no need to bother with deeper sense of
it, really.
Just translate it literally.
Same story with 'oblique'/'italic' dichotomy.
On 21/06/17 16:50, Olivier Hallot wrote:
"Book" font style seems to be a term/jargon used by the printing
industry, and careless translation may lead to
I've used the .PO based workflow from the
beginning of my OOO/LO L10N stint, and yes,
you'd get those problems in such environment.
You'd just have to keep the IDs for strings
translations' variants/exceptions/etc. separately.
That was how I was dealing with the problem,
anyway -- last
Seconding this. The project just throws away the
l10n people man-hours (but just you try to get
them dev guys to fix something in the code!).
That's not right, and in OSS you'd definitely
want to pay attention to putting things right
(the crypto-currency here!).
On 13/10/17 15:10, Michael
On 16/10/17 16:00, Adolfo Jayme Barrientos wrote:
...
Because they have a better model [...]
...
Yes.
It might be helpful to know that there are plans to build automated
Pootle pushes [2], which in turn should give us much more frequent
...
I'd say things ought to be organised so that
You are talking wisely
On 16/10/17 13:47, Adolfo Jayme Barrientos wrote:
2017-10-13 7:45 GMT-05:00 Yury Tarasievich <yury.tarasiev...@gmail.com>:
Seconding this. The project just throws away the l10n people man-hours (but
just you try to get them dev guys to fix something in the code!).
.
On 17/10/17 11:14, Krunose wrote:
On 17.10.2017 09:39, Yury Tarasievich wrote:
shortcut=autochange (change just the marker in
the translated)
You mean that system automatically replace
shortcut position or just character: _New : ~New
: N_ew : N~ew.
This could be tricky.
--
To unsubscribe e
Some thoughts for guys capable of implementing.
Of course, I have no idea whether any of these
are feasible.
So, change in English string (tEh original)
brings some checks with the previous value:
1) capitalisation changed? set flag 1
2) shortcut markup changed (like _ to &)? set flag 2
3)
Well, I'm 'out of loop' ATM, but thank you for
your effort, the organising team, *really*. I
understand all this's a difficult undertaking.
The problem (on which guys are commenting) is --
certain kinds of changes should never
generate/cause an obligatory workload.
In your place (I know,
On 18/10/17 12:31, Sveinn í Felli wrote:
I guess changes in quotation marks ('→" "→ˮ)
inside of text strings would fall into category 3)?
I'd say those, as culture-dependent, would merit
a separate category. OTOH, ellipsis vs.
three-dots is implementation-specific (so, #3).
One frequent
On 03/12/17 17:46, Chris Leonard wrote:
I know this is off-topic for this list, but I assume many of you are also
Well, I know this is off-topic for this list,
but I assume many of you are also wishing all
kids of the world well, right?
So, is this such a good idea to hand kids a
computer
The idea of handing a kid 'from 3 to 12'
something like this is the sole reason for
'shuddering'.
Of course, such outbursts as mine aren't really
proper, so my apologies, all.
-Yury
On 04/12/17 15:46, Tom Davies wrote:
I haven't looked into it much so I don't know
...
--
To unsubscribe
On 29/01/19 12:25, Mike Saunders wrote:
> Sure -- I've added full section names to the EN version:
One good turn deserves another, could you please
redo with continued numbering? :)
>> without the context. E.g., #16: the
> "After this commit: * The initial search time went down from ~40 seconds
Guys, please add the components names to the
list points. E.g., I couldn't understand right
away the importance of #24, and I still don't
know what's #25 about.
#8--#10 are about the same change
Not all features/changes are comprehensible
without the context. E.g., #16: the
personalization
The AOO wiki link (from where the term
supposedly came):
https://wiki.openoffice.org/wiki/Sidebar#Decks
clearly shows that that 'deck' has the meaning
as in the 'deck of cards' (well, 'of panels').
So you might translate it as if it was a 'set
(of panels)' or a 'spread (of panels)' or
On
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?
There was a lot of talk about how certain fonts
look good or bad in certain writing systems.
Maybe I'm missing something, but were there any
actual comments from people sort of representing
those (non-Latin-based) writing systems?
-Yury
--
To unsubscribe e-mail to:
94 matches
Mail list logo
