Peter,
keep in mind that this frame must accommodate also the translation of the
text into other languages - and the translations are usually longer than
the original (at least in Slovenian they usually are).
So the solution must offer some flexibility for (even) longer translations
...
Lp, m.
V
You raise an important issue, Jean.
There should be some other very easy way. These are not programmers, they
are not used to filling in bug reports.
What about having a special simple "post" report-form that would be
moderated and only true reports would be then forwarded to the new
discussion s
The LO74a1 is coming out probably next week (was officially scheduled May
9-15), and its builds are already available on the dev-builds website:
https://dev-builds.libreoffice.org/pre-releases/
See also : https://wiki.documentfoundation.org/ReleasePlan/7.4
Lp, m.
V V ned., 22. maj 2022 ob 12:10
se.
>
> Regards
> Peter Schofield
> psaut...@gmail.com
> Technical Writer, LO Documentation Team
>
> On 21 May 2022, at 11:14, Martin Srebotnjak wrote:
>
> Hi,
>
> I do not know about the future, but the TDF board should inform the teams
> (esp. the documentation
Hi,
I do not know about the future, but the TDF board should inform the teams
(esp. the documentation team) at least one version prior of such a change
(if being planned for 7.5/(=8.0?), the LO teams should be informed by the
time of the 7.4 release) - so everyone can prepare accordingly (maybe th
Hello,
In the previous months I have asked several times for the cleanup of the GS
Guide for LO73 odt files to start translating them.
Could someone please take care of that task?
Lp, m.
--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
Problems? https://www.libreof
Please, next time discuss the issue of not cleaning the odt files, which is
stopping the l10n process of guides.
Therefore none of the 7.3 guides is yet "completed".
Lp, m.
V V pet., 1. apr. 2022 ob 00:23 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:
> Documentation Team Me
Hello,
V sob., 26. mar. 2022 ob 21:01 je oseba Jean Weber
napisala:
>
> The chapter and book files also need to be “cleaned” using that Python
> script.
>
The same goes for the GS 7.3 guide and its chapters, otherwise localization
cannot start.
Lp, m.
--
To unsubscribe e-mail to: documentati
There is a formatting issue with the template shown by the heading
> at the bottom of
>
> https://documentation.libreoffice.org/assets/Uploads/Documentation/en/GS7.3/GS73-GettingStarted.pdf#page=258
>
>
> V V tor., 22. feb. 2022 ob 16:16 je oseba Martin Srebotnjak <
> mi...@fi
Hi,
V V tor., 22. feb. 2022 ob 16:16 je oseba Martin Srebotnjak <
mi...@filmsi.net> napisala:
> Could now someone please clean the final chapter files + whole guide?
> Olivier, could you please make a 7.3 GS odm file for automatic book
> generation of translated guides?
>
anyo
Hello,
great!
Could now someone please clean the final chapter files + whole guide?
Olivier, could you please make a 7.3 GS odm file for automatic book
generation of translated guides?
Thanks,
Martin
V V tor., 22. feb. 2022 ob 12:28 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> nap
Hello, Peter,
V V tor., 25. jan. 2022 ob 09:56 je oseba Peter Schofield <
psaut...@gmail.com> napisala:
>
> • Should the Options command menu path be treated the same way in the
> guides' texts (Options-win/linux-path (macOS Options-macos-path)?
> The options shortcut modifier will be treated the
Hello,
I propose to discuss this and decide on a solution for all the guides and
all the writers, via the list and/or the documentation team weekly meeting.
And then to document the approach in the documentation-writing
guidelines/guide.
The questions that pop to my mind:
- How often do such
Hello,
Peter, it would be great if you could update both chapters for the GS
guide, so that the project can move forward as it is the basic guide in the
series.
Lp, m.
V V čet., 13. jan. 2022 ob 09:13 je oseba Peter Schofield <
psaut...@gmail.com> napisala:
> I have started updating the Impress
Hello, Peter,
maybe all this needs to be first discussed thoroughly before a lot of work
is instilled into adding things into the current form of the guide(s).
So I suggest to first have a consensus of the Doc Team about this.
Best regards,
m.
V V čet., 6. jan. 2022 ob 12:40 je oseba Peter Schof
.
V V ned., 2. jan. 2022 ob 19:39 je oseba Ilmari Lauhakangas <
ilmari.lauhakan...@libreoffice.org> napisala:
> On 2.1.2022 20.27, Martin Srebotnjak wrote:
> > Ilmari, could you please elaborate: what do you intend to patch
> regarding
> > the help build?
>
> Ignoring
Jean et.. al.,
I took a look at the complete pdf and it looks good. As a macOS user I
would prefer this guide than the Linux/Windows-oriented "generic" guide ...
I do see where Jean is trying to help the user (which is what documentation
is about) - macOS users are a bit left out by using guides
Hello, Jean et. al.,
thanks for taking care of this guide. Just the blog announcement is missing
now ...
Lp, m.
V V tor., 21. dec. 2021 ob 20:57 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:
> HI Jean, All
>
> I have updated the documentation website with the latest public
The problem is that Calc help content now links to wiki for additional
information about the functions (and will probably in the end link to all
function descriptions there), so wiki is becoming a part of LO help (which
is problematic for organizations/companies that do not want/approve
accessing e
Notes for LO 7.3 and accidentally
> duplicated
> > entry 263. This was the only one I edited and now it is fixed.
> >
> > I did not check if there are any other duplicate IDs though.
> >
> > Rafael
> >
> >
> > On Tue, Nov 23, 2021 at 8:32 AM Martin Sreb
kan...@libreoffice.org> napisala:
> On 22.11.2021 22.54, Martin Srebotnjak wrote:
> > Hello,
> >
> > just want to report, the wiki page
> > https://wiki.documentfoundation.org/ReleaseNotes/7.3
> > has errors (the name of the translation unit 263 has several instanc
Hello,
just want to report, the wiki page
https://wiki.documentfoundation.org/ReleaseNotes/7.3
has errors (the name of the translation unit 263 has several instances) and
thus cannot be marked for translation in the latest version.
Please fix this and mark the latest version available for transla
From my experience localizing the chapters of GS and the Math guide in
OmetgaT: the Math guide is very similar to Math chapter in GS guide (it is
only extended in some parts) - but GS chapter got thoroughly revised by the
reviewers (regarding wording) from 7.0 (I think), while the Math guide
remain
Thanks for noticing, Jean.
I think they should be replaced, yes, to be in line with all the Community
editions of the software they refer to.
Lp, m.
V V sob., 20. nov. 2021 ob 05:21 je oseba Jean Weber
napisala:
> Peter, Olivier, and team--
>
> Apologies for not noticing this before, but the t
Hello, Peter,
why do you not take Jean's files? This way there will be no difference
between them, otherwise some errors might persist or new can be introduced
...
Lp, m.
V V pet., 19. nov. 2021 ob 11:03 je oseba Peter Schofield <
psaut...@gmail.com> napisala:
> Hello Jean
>
> I am checking all
+ * shortcut to the
given range.
Please notify the author of the help text so that she/he does not repeat
the error on other strings.
Lp, m.
V V sob., 6. nov. 2021 ob 13:17 je oseba Martin Srebotnjak
napisala:
> Hello,
>
> the help string JT47J in calc/01.po is not properly caseinline-d:
>
Hello,
the help string JT47J in calc/01.po is not properly caseinline-d:
This is an experimental feature and is disabled by default. To enable it,
go to Tools - Options - Advanced and check the option
Enable experimental features (may be unstable).
It should have "%PRODUCTNAME -
PreferencesTools
Hi, Steve et. al.,
V V tor., 2. nov. 2021 ob 16:44 je oseba Mike Saunders <
mike.saund...@documentfoundation.org> napisala:
>
> > 2. On Windows, the *Help > Search Commands* option in the Menu bar
> > identifies a shortcut for the interaction (that is, Shift+Esc). Is
> > there a correspon
;ll publish the fix for the strings you mentioned.
>
> Regards
> Rafael
>
> On Tue, Oct 19, 2021 at 1:36 PM Martin Srebotnjak
> wrote:
>
> > Hi, Olivier,
> >
> > as I wrote, these errors are in the master, they were on October 15, four
> > days ago (that
introducing some of these errors... Now I see that
> > this is troublesome for translators and future help pages won't have
> these
> > embedvars.
> >
> > Let me know whenever you come across issues like these.
> >
> > Regards,
> > Rafael Lima
>
Hello,
for some time now I notice that help writers keep using embedvars to
simplify their work. These not only make help unreadable for localizers
(and thus prone to errors in localization), but introduce errors, as the
use of embedvars in sentences is not allowed for languages with cases (like
As with the latest changes to finished 7.2 GS files I urge to not use these
changed files and remain with the previous ones as the changes make the
localization for some languages impossible (it cannot be grammatically
correct in Slavic languages and probably many more).
Lp, m.
V V sre., 8. sep.
y wrong.
Please, remove these changes ASAP.
Lp, m.
V V sre., 8. sep. 2021 ob 23:01 je oseba Martin Srebotnjak
napisala:
> Hi, Olivier,
>
> please undo all your changes from these files to renaming figure to
> as this causes unwanted problems with OmegaT - translation of
> word
Hi, Olivier,
please undo all your changes from these files to renaming figure to
as this causes unwanted problems with OmegaT - translation of
word Figure (in Slovenian "slika") gets printed in the guide with capital
"Slika", although set to "slika" in OmegaT. Since it is a field, it cannot
be e
Hi all,
Dave helped me to locate it:
https://wiki.documentfoundation.org/File:Automobile.odb#file
<https://listarchives.libreoffice.org/global/documentation/2021/msg00047.html>
Lp, m.
V V pon., 6. sep. 2021 ob 15:17 je oseba Dave Barton
napisala:
> On 06/09/2021 13:55, Martin Srebotn
Hello,
for localization purposes I would need the (English or localized) databases
(odb) appearing/used in the Base chapter.
I can't find them on the nextcloud site, maybe I am missing something.
Best regards,
Martin
--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
Hi , Ilmari,
it it is off it still pastes the content; In both ways the settings and
formatting does not get copied (i,e. the font color), but the values do get
copied. Only if you check Formats in the Paste Special window also the
formatting gets pasted.
Lp, m.
V V ned., 8. avg. 2021 ob 09:08 j
Hi, Jean,
it is really ambiguous. The tooltip says:
Inserts the contents of the clipboard into the current file in a
format that you can specify.
But this is the default tooltip for the Paste Special window (it also shows
upon the Cancel or OK button etc.).
I still cannot see the point in it. I
Hi,
Draw guide does not have its master document for automatic book assembly
which simplifies the procedure for translated guides, so that would be
great, Olivier.
Lp, m.
V pon., 26. jul. 2021 03:56 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:
> Hello Peter
>
> Do you need
Hi, Olivier,
could you please clean also the finished 7.1 GS guide chapters?
Best regards,
Martin
V pon., 26. jul. 2021 04:06 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:
> HI Team
>
> Em 22/07/2021 16:02, Olivier Hallot escreveu:
> > Topics and Discussion:
> > * Update
Please do not make any massive help page changes after beta1 release of
7.2, because that makes it hard to be localized in time for a 7.2 release.
The 7.2 release in itself requires a big effort from the l10n community
with many new help strings and help updates.
Lp, m.
V V tor., 8. jun. 2021 ob
Sure, I have several.
This means changing around 200 strings in English * 100 l10ns = 2
strings need to be updated by localization teams.
Lp, m.
V V sre., 2. jun. 2021 ob 09:39 je oseba Peter Schofield
napisala:
> There are several examples of two words being put together as a single
> wor
Great work again!
Please do not forget to clean the files as well.
Best regards,
Martin
V V sob., 22. maj 2021 ob 10:19 je oseba Jean Weber
napisala:
> Congratulations to everyone who worked on this update.
> I’ll try to find time to produce the print edition this coming week.
>
> Jean
>
> On
Hello, Felipe,
congrats on your dedicated work!
Please update the "Publication date and software version" subchapter of the
Copyright chapter (page 2) of all chapter files and the book by adding the
following disclaimer as proposed by Jean and used in the 7.1 Writer guide:
Other versions of Libre
Hello,
to prevent chaos, I suggest to update the 7.1 template's "Copyright "
chapter under the "Publication date and software version" subchapter (as
did Jean with the Writer 7.1 guide) as well:
"Published (month) 2021. Based on LibreOffice 7.1."
changes to:
"Published (month) 2021. Based on Libr
> declare what the guides do not cover, I think it is clear enough when we
> >> say that the document is based on LibreOffice Community. Mentioning so
> many
> >> times the term LibreOffice Enterprise could lead the user to believe
> that
> >> TDF is working on
Hello,
V V pet., 9. apr. 2021 ob 11:19 je oseba Jean Weber
napisala:
> I agree with Felipe that a long Disclaimer is not necessary, but .perhaps
> we might add a short sentence like, “Other versions of LibreOffice may
> differ in appearance and functionality.”
>
Jean, I find your proposal great
Hello, Jean,
great to hear about the progress on the 7.1 guides.
As you work on the covers etc. - this leads to the question of properly
naming and tagging these guides, along with the Community/Professional
naming scheme the TDF has decided on.
Just adding "Community" tag to the small LibreOffi
Hi,
since work already started on updating to 7.1, I guess in this case it is
best to go for 7.1.
Lp, m.
V V tor., 16. mar. 2021 ob 07:03 je oseba Jean Weber
napisala:
> I had started earlier this year on updating the Writer Guide from v6.4
> to v7.0, but as that was delayed I changed to updati
Community version should be omitted on the back cover.
Lp, m.
V V sre., 24. feb. 2021 ob 11:28 je oseba Martin Srebotnjak <
mi...@filmsi.net> napisala:
> I agree,
>
> the artwork on the front page (and the wording either in the prologue of
> the guides/chapters) must clearly s
I agree,
the artwork on the front page (and the wording either in the prologue of
the guides/chapters) must clearly state and visualize, what version the
guides (and the localization community effort) refer to.
Lp, m.
V V ned., 21. feb. 2021 ob 06:23 je oseba Jean Weber
napisala:
> Where can I
I agree with Jean,
this means also additional work for all translation teams, when updating
guides' translation from older versions to 7.1 ...
Lp, m.
V V ned., 21. feb. 2021 ob 06:19 je oseba Jean Weber
napisala:
> I've apparently missed previous discussion on this new (5th) character
> style.
Hi,
I can see the "cleaned" subfolder in the GS70 published folder - were these
files already manually cleaned up and has the python script been run on
these?
Could someone please also update the LO70 master document to generate the
full guide from individual chapter files?
Thanks,
m.
V V pet.,
Hi, Olivier,
there is no "LibreOffice" anymore, from LO71 there is only "LibreOffice
Community" - shouldn't the covers reflect which actual product they refer
to?
Or do they refer to the LibreOffice spin-offs by the eco-system companies,
which have additional features and/or different appearance?
So at the moment only Base chapter needs some love?
What is the status?
Lp, m.
V V ned., 22. nov. 2020 ob 08:56 je oseba Jean Weber
napisala:
> Thank you to the people reviewing updated chapters of GS70.
> I have taken Ch12 (HTML pages) to update. PeterS will do 6 (Impress)
> and 7 (Draw).
> Th
Just reminding of this suggestion by Milos from August 2020.
+1
Lp, m.
V V čet., 6. avg. 2020 ob 14:39 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:
> Forwarding to the documentation mailing list
>
> Important topic.
>
>
> Mensagem encaminhada
> Assunto:
So, Miloš,
this is probably the place with your updated script odtcleant:
https://github.com/milossramek/translation-scripts/tree/master/odtclean
Lp, m.
V V pet., 18. dec. 2020 ob 09:42 je oseba Milos Sramek <
sramek.mi...@gmail.com> napisala:
> Hi,
> I have a new version - I'll put it on githu
Hi, Milos,
I completely agree with you and +1 from me.
There were some reports about the script not working on GNU/Linux, maybe
someone can elaborate?
Lp, m.
V V čet., 17. dec. 2020 ob 20:42 je oseba Milos Sramek <
sramek.mi...@gmail.com> napisala:
> Hi,
>
> I suggest to include file cleaning
Hello,
could this guide's chapters - as well as other guides' chapters upon being
finished - be cleaned with the odtclean script my Milos to remove unwanted
formatting code and help l10n teams?
I suggest this becoming a part of the official procedure, as documented in
the guide for writing guides
Hi, Dave,
the GS exists for LO6.4, so all you need is to gather all the new stuff
that landed in LO 7.0 - which should be in the LO70 release notes on wiki.
Lp, m.
V V čet., 24. sep. 2020 ob 19:15 je oseba DaveB
napisala:
> Hi All,
>
> I have been doing some preparation for the 7.0 edition of
.
> Perhaps we can add a new directory "for_cleaning" where finished documents
> would be put. From there the document would go to Published
>
> Milos
>
>
> On 8/3/20 8:44 PM, Martin Srebotnjak wrote:
>
> Hi, Miloš,
>
> I guess the Feedback dir was empti
nd the directories you have mentioned, I've checked
> https://nextcloud.documentfoundation.org/apps/files/?dir=/LibreOffice%20Documentation/English/Writer%20Guide/6.4
>
> Milos
>
> On 7/31/20 7:16 PM, Martin Srebotnjak wrote:
>
> Hi, Jean et. al.,
>
> I cleaned the files with the
Hi, Jean et. al.,
I cleaned the files with the odtclean.py script downloaded from
"English/Contributor Resources" map (uploaded 2 years ago).
I hope this is the latest script, as some styles have been recently renamed
etc. Maybe Miloš can confirm. The files seem bigger, but that might be
because
Hi, Peter et. al.,
just a quick explanation: the important thing is NOT to make the word
"Figure" part of the reference, because then there are problems with
translation (one needs to manually edit/translate the reference in LO
Writer, it cannot be localized in i.e. OmegaT).
Lp, m.
V V sre., 15.
then name
> the guide accordingly. Also, If we go with the second option then we will
> have to do something about the Personal/Community edition tag as the
> enterprise edition will not contain them.
> Pulkit Krishna
>
>
> On Fri, Jul 10, 2020 at 12:22 PM Martin Srebotnjak
> wr
h the second
>> option then we will have to do something about the Personal/Community
>> edition tag as the enterprise edition will not contain them.
>> Pulkit Krishna
>>
>>
>> On Fri, Jul 10, 2020 at 3:14 AM Martin Srebotnjak
>> wrote:
>>
>>>
Hi,
on Windows I see that the title of modules is in LO7RC1 also appended (with
"Personal", just like the suite itself, where "Personal Edition" is
appended), so open document in Writer has "NameOfTheDocument.odt -
LibreOffice Personal Writer) stated in the title bar.
Of course, the "Personal" /
Jean, here it is:
https://wiki.documentfoundation.org/SI-GUI
Otherwise prereleases and latest versions of builds can always be directly
downloaded from here:
https://dev-builds.libreoffice.org/pre-releases/
Must warn macOS users on this list of a LO7RC1 bug I noticed on macOS (and
reported) - for
n of
> month names. Having worked with multiple languages -MM-DD works very
> well.
>
> Regards
> Peter Schofield
> psaut...@gmail.com
>
>
>
> > On 5 Jul 2020, at 09:34, Martin Srebotnjak wrote:
> >
> > Hi, Jean,
> >
> > I have one re
Hi, Jean,
I have one request:
please remove date fields for month of publication (page 2): languages with
cases are not supported properly in LO and LO does not properly adjust
month names (e.g. in Slovenian, LO replaces "January" with nominative
"januar", but in this sentence it should be genitiv
Hello, Peter,
I think it is reasonable to make user guides as functional and readable as
possible - they are not books for young children but technical guides.
As such the design of the text should be unified and - IMHO - the colors of
application should only be used on covers to distinguish the
I totally agree, Peter.
Design should be left to professionals. The points you raise are 101 design
axioms.
Lp, m.
V sob., 6. jun. 2020 12:21 je oseba Peter Schofield
napisala:
> I have just created a draft version of the Preface Impress Guide Version
> 7.0 using the new 7.0 templet that Olivie
Since the site is not only for English documentation teams, it hosts also
localization teams and they should probably use the same procedure for
localisation as is set for updating/reviewing original guides, I suggest to
use the universal date format 2020-05-28. This way dates in all status
sheets
Hi,
there is some confusion, yes, as can be seen on the page
https://documentation.libreoffice.org/en/english-documentation/
Covers for guides of same-release modules or suite (i.e. 6.4) seem not
follow the same cover template (just looking at the size of "6.4" on those
preview pics).
Some desig
Hi, all,
I think that GS chapter still hasn't had its styles updated.
Lp, m.
V V pon., 4. maj 2020 ob 05:05 je oseba Pulkit Krishna <
pulkitkrishn...@gmail.com> napisala:
> Hello Jean,
> I have taken chapter 8 of GS for its fourth review. After that you can
> compile that book also.
> Pulkit Kr
Well, the Base chapter still needs 2nd review, it is in the Drafts folder
...
See the guide status.
Lp, m.
V V sre., 29. apr. 2020 ob 12:46 je oseba Jean Weber
napisala:
> OK, I’ll do that tomorrow.
>
> On Wed, 29 Apr 2020 at 19:49 randolph gamo
> wrote:
>
> > Hi Jean,
> > All drafts have now
Thanks, Peter, for noting that.
It seems that we need a wiki page with all the thing that are not funcional
in macOS.
Since most programmers of LO write/say what Regina wrote here, it would
maybe help if TDF could buy one mac and have it available to LO programmers
and testers via remote desktop
Hello,
if so, all videos should be available for translation, because help is
localized :)
I cannot find the script of this particular video to translate on wiki:
https://wiki.documentfoundation.org/Marketing/Videos
Could it be possible that such video subtitles would be merged into help
files to
Hi, Luke,
V V čet., 16. apr. 2020 ob 20:43 je oseba Luke (gmail) <
luke.kend...@gmail.com> napisala:
> Why not export ODG to SVG, as vector components will stay high res and
> scalable, and image parts will stay as images, and it's supported by EPUB?
>
for pure screenshots of UI and its elements
. 2020 ob 12:58 je oseba Peter Schofield
napisala:
> I reviewed both chapters and did several changes. They need someone else
> to give them both a once over and they will be ready for publishing.
>
> Regards
>
> Peter Schofield
> Sent from my iPad Mini
>
> On 5
Hi, Peter,
you took out two chapters of the LO64 GS guide (Impress and Draw) for
review and those are the only chapters still waiting for 1st review. Do you
plan to review them in the near future or should someone else take them
over for 1st review?
Thanks,
m.
V V ned., 5. apr. 2020 ob 11:48 je
;
> On Wed, Mar 25, 2020 at 1:09 PM Martin Srebotnjak
> wrote:
>
> > Thanks, Drew.
> >
> > If this isn't already a part of LOOL guide (at least it seems to me), it
> > could be added (Chapter 3 or 8?).
> >
> > As well as guidelines about finding and
Pulkrit,
we are volunteers.
Please be patient and do not use words like "should" nor give orders to the
members of the documentation team.
It is rude.
Lp, m.
V čet., 26. mar. 2020 06:24 je oseba Pulkit Krishna <
pulkitkrishn...@gmail.com> napisala:
> Hello Drew,
> Are you done with the review
Thanks, Drew.
If this isn't already a part of LOOL guide (at least it seems to me), it
could be added (Chapter 3 or 8?).
As well as guidelines about finding and installing language packs for LOOL
(to support UI in other languages and the
spell-checking/hyphenation/thesaurus). Info is needed for n
Hi, Pulkit,
decisions as to what the official Documentation-team-produced documentation
will be is decided on Doc team meetings.
Maybe it would be best to discuss this there before you start working on it.
Lp, m.
V V tor., 24. mar. 2020 ob 07:35 je oseba Pulkit Krishna <
pulkitkrishn...@gmail.c
Hello, Roman,
I am not sure that will work for all languages. Also, sometimes toolbars,
keys or icons are localized in more informal way, like the status bar, Ctrl
etc. and as such are used with cases in sentences, which poses a problem
for using static stings in Nominative, at least for languages
Hi, Jean et. al.,
I prefer waiting for reviews and publishing them cleaned with odtcleaner
script so translation can go from there on.
In the GS64 status spreadsheet it says that chapter 8 (Base) hasn't had
style updated yet. That is probably a mistake?
Thanks, m.
V V sre., 5. feb. 2020 ob 08:4
Hi, Dimona,
I suggest you base your updates on LO6.4 (LO6.4 RC2 is out for testing, and
it's feature- and string-frozen), as it will be officially released in
about three weeks.
Lp, m.
V V sre., 15. jan. 2020 ob 20:39 je oseba Dimona Delvere <
dimonadelv...@outlook.com> napisala:
> Hello Everyo
Hi, Robert,
yesterday the wiki translation plugin also did not work anymore for me. It
must bw a problem of the wiki, I tried several browsers.
Lp, m.
V sob., 4. jan. 2020 09:14 je oseba Robert Großkopf <
rob...@familiegrosskopf.de> napisala:
> Hi *,
>
> sometimes ago I had translated most of
Hi, Jean (& Olivier),
Olivier made a master document for GS60 that is useful for automatically
creating a full guide from chapter files, maybe this can be also done for
Calc60guide?
Lp, m.
V V pon., 25. nov. 2019 ob 22:16 je oseba Cathy Crumbley
napisala:
> That sounds like a good plan. I am g
Hi,
the GS was last updated with LO6.0 and since this is the main general guide
for LO, I think it is worth of regular updates. It is also the most
translated of the guides and thus an always updated version could trigger
even more localizations.
Since GS60 update was quite thorough I believe the
Hi,
the page is now fully localized into Slovenian, except for the screenshots.
So, what needs to be done that LO63 with Slovenian UI will offer the sl
link of this wiki page? Is it already coded that way or should we enter a
bug report?
Lp, m.
V V sre., 17. jul. 2019 ob 17:47 je oseba Robert
Hi,
I am cross-posting this also to l10n list, as this needs to be localized
for 6.3 release as well (at least for languages that want it localized).
Will this page get under a l10n wiki plug-in for translation or should we
translate this wiki page manually?
Will links to localized wiki page in
Hi,
the link should point to a localized wiki page in the ui language, if
available.
Thanks, m.
V pet., 7. jun. 2019 19:17 je oseba Drew Jensen
napisala:
> Howdy,
>
> In the ESC meeting yesterday the question of including the Migration
> Assistant (MA) feature by default in the pending 6.3 relea
Want to move a column in Calc in-between two others in a single step? Click
the header of a column, then a cell in this column, while pressing Alt key
keep mouse button pressed and move it to the desired position.
Not totally grammatically correct, but probably makes more sense.
But this has furt
my Simple-Chinese version book:
>>
>>- The contents of the copyright are exactly the same as the original
>>English version, including contributors (current edition and previous
>>edition), no changes.
>>- And, the copyright page number is the same as
Hi,
you cannot delete the GPL3 license (or change a license, even if it is very
very similar), as the previous iterations (now parts) of the text were
published under those terms and conditions. Unless you get direct approval
from *all* the authors of those previous versions (published under those
Well, the strings landed in Pootle and are subject for translation.
Also, translators cannot wait indefinitely. There are quite a number of new
longer help strings that require a lot of translating (more than 500 of
those if not even more). The alpha comes out in the beginning of May the
200+ new
Hello Olivier et. al.,
will the editor in any way change underlying string/text
non-changed-with-editing code (i.e. if a small edit of one word is
performed, does the whole chunk of help page save/change (regarding also
xml checks and corrections and beautification?).
Did you try any tests, how m
Hi,
please, could you further explain:
+ Supporting minor updates to published guides (pdf file)
What is the agreed notification workflow with every guide update for all
l10n teams translating these guides (content-wise, i.e. notifying "this
sentence in this chapter/page was changed from this t
1 - 100 of 154 matches
Mail list logo
