Re: [libreoffice-documentation] Doc Team Meeting Minutes

[Drew Jensen]

Hi Martin,

Thanks for joining in the conversation.

On Wed, Nov 14, 2018 at 4:36 PM Martin Srebotnjak  wrote:

> Hi,
>
> please, could you further explain:
>   + Supporting minor updates to published guides (pdf file)
>

In fact further examination of what this would encompass the purpose behind
adding it to the call agenda.

The second or third week I joined in on the calls it happened that Olivier
and myself were the only two on board that day. Olivier shared some
thoughts, at length, on treating the Guide publication process more closely
to how a software package is released. With an important goal, among a few
others, of bringing Guide publishing dates closer releases of the software.
The idea has been bounced around between others on a few subsequent calls.

What I've taken away from these discussion would be to have a work flow
which supports major and a minor publication of a Guide.

A major publication of a Guide would involve updates to every document
(master document and all chapter/appendix documents) along with other
components such, cover art for one example.
It could add or remove chapters or make other changes in chapter structure.
It includes the production of two set of documents, one including an ODF
master document, ODF text documents for each chapter or appendix and the
other set pdf files created from the first set.
The publication process includes then the production of an official print
master, including ISBN registration as a final update, which is then sent
to a print service.
This represents the current publication process.

Publishing a minor version of a Guide could, but may not, require a change
to the master document beyond generating new TOC/Alpha Index tables, it
would include updates of some subset of chapter or appendix documents.
A minor publication process produces both sets of files, ODF and PDF.
No print master is produced for the minor publication, therefore no
registration of a new ISBN is needed.
***I have some open questions regarding the last point about the ISBN and
if there might be some legal requirement of a clearly distinct name from
the registered printed book, even if true it is just something to account
for in the workflow.
These minor publishing events would happen between the full, major, Guide
releases.

This change would require us to change the file names to include a document
release number in addition to the software release number, only those files
which actually change would increment the document release number so that
at a macro level you could easily see which of the constituent files
actually changed based on the file names in the release.


> 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 to this" etc.) so that
> the translation process continues with the really-latest version (after an
> official version is already published) and as hassle/confusion-free for
> l10n teams as possible?
>

There would always be, at a minimum, the ability to generate a delta
between the present and most previous copy of an individual file to see
what exactly changed with the compare documents function using ODF files.


> With the delicate translation process going on in parallel with the
> considered minor content updates I would instead suggest to create odt/pdf
> with errata or corrigenda of a guide (and all its chapters) that gets
> updated regulary and is finally merged with the guide only with its next
> iteration of publication.
>

If publishing were always going to dead trees for a medium I'd say
absolutely the better way to go.

That is need not be the case here however and I would put forward some
opinions:

No document of this type publishes without deficiencies either by error or
omission.

It is valuable to make the most accurate information available to users as
quickly as reasonably possible.

The quicker the team can get feedback from users seeing the changes made to
address these deficiencies an the more readers overall increases the teams
ability to make higher quality documents.

I think publishing complete documents, with changes incorporated, will
generate both better and more feedback than a list of changes in a separate
addendum document.

As I said above this is really the first time I've put what I've taken from
our batting the idea around on a few calls into text and thanks again for
the nudge here.

That then is just a gross view of the thinking and certainly needs more
fleshing out.

Given that it's 1AM here though it is a good spot to end this email.

I'm looking forward to continuing the conversation with you and others here
on the morrow.

Looking forward to hearing your thoughts.

Best wishes,

Drew


>
> To quote wikipedia/*Chicago Manual of Style
> *, "Errata, lists
> of
> errors and their corrections, may take the form 

Re: [libreoffice-documentation] Changes and fixes in Nextcloud for ODFAuthors

[Luca Daghino @ Libero]

Il 13/11/2018 15:24, Olivier Hallot ha scritto:

Hi Luca

Em 12/11/2018 22:48, Luca Daghino @ Libero escreveu:

And... while trying to login to NextCloud right now, I'm forwarded to
this page:

https://nextcloud.documentfoundation.org/apps/user_saml/saml/acs

Can you contact hostmaster at thedocumentfoundation dot org explaining
the issue?

Regards


Sure!

Thank you Olivier! :)

--
Luca Daghino
 - - - - - - - -
Icq/Licq/Gaim #175451007
Debian Powered Linux Registered User #310800 at http://counter.li.org
No retreat baby no surrender
http://www.retenergie.it - coop di produttori e utilizzatori di energia da 
fonti rinnovabili
tad evaarthamaatra-nirbhaasaM svaruupa-shuunyam iva samaadhiH
Sanskrit - Realize it's the common language ;-)


--
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] Changes and fixes in Nextcloud for ODFAuthors

[Luca Daghino @ Libero]

Il 13/11/2018 15:12, Dave Barton ha scritto:

On 13.11.2018 00:48, Luca Daghino @ Libero wrote:

Il 05/11/2018 17:21, Olivier Hallot ha scritto:

Hello fellow Authors

This weekend we worked to fix the NextCloud service for Authors. The
issues were a few and all were fixed.

* The previous ODFAuthor share was a folder under my user ID and thus
was limited in size by the default TDF member storage. We created a
group folder where the limits were increased to a workable condition and
similar to the old Plone size.

* The existing files were moved from my share to the group folder (now I
can breathe !).

* Dave Barton is populating the new share with the relevant files picked
in the old Plone, reproducing the folder structure of the old file
storage.

* As decided in the last doc team meeting, the ODFAuthors share was
renamed "LibreOffice Documentation" .

* Authors interested to join and access LibreOffice Documentation share
are invited to ask in this mailing list. I will assign their login to
the "odfauthors"  group.

* we would like to invite other language communities to join the new
LibreOffice Documentation share in NextCloud, as Brazilians, Germans and
Turks already did.

* Everybody is invited to participate in our documentation team meeting
and every Wednesday at 19:00 (Berlin time)

Kind regards


Hello Olivier,

I created the other day a folder for the Italian community in the new
NextCloud space. Is it possible for you (or infra members) to move
everything in odfauthors/LibreOffice/Italian to this new folder in
nextcloud, maybe using scripts?

Or do we have to move all files manually?

And... while trying to login to NextCloud right now, I'm forwarded to
this page:

https://nextcloud.documentfoundation.org/apps/user_saml/saml/acs

where I see nothing but 3 buttons on the left (one is JSON)

Thank you! :)

Hi Luca,

I don't believe it is possible to automate the copying over of content
from ODFAuthors to Nextcloud in the way that you would like.

I copied over all the required English content by downloading the files
locally to one of my computers, then uploading them to Nextcloud.
Getting the files from ODFAuthors has to be done one file at a time :( ,
but Nextcloud does allow for (very careful) drag and drop batch
uploading :) .


Hello Dave,
Ok, I'll do that asap.



There appears to be a problem with the redirection of your Nextcloud
login that needs fixing.
Guilhem: Any chance you could help Luca with this?

Regards
Dave




Thanks! :)

--
Luca Daghino
 - - - - - - - -
Icq/Licq/Gaim #175451007
Debian Powered Linux Registered User #310800 at http://counter.li.org
No retreat baby no surrender
http://www.retenergie.it - coop di produttori e utilizzatori di energia da 
fonti rinnovabili
tad evaarthamaatra-nirbhaasaM svaruupa-shuunyam iva samaadhiH
Sanskrit - Realize it's the common language ;-)


--
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-documentation] Ask bot language based usage levels

[Drew Jensen]

Howdy,

In today's meeting at one point the idea of mining information, with
regards to what users are struggling with, from the ask bot service.

I tend to browse a lot of sites on the web in languages other than English
(Google is my friend there and it doesn't insult me in the slightest to
read not quite perfect English from the service).

Knowing that ask bot is supporting multiple languages I thought to take a
quick peek at them all.

Here is what I found, this is just a count of questions in each of the
supported languages:
English..29,943
Portuguese (BR).2,004
German...1,633
Spanish1,178
Italian..858
Dutch..249
Japanese198
Turkish128
Korean...51
Chinese (TW)44
Romanian..22
Arabic.11
Czech...8
Croation7
Basque.1

Not sure what if anything that means, but I found it interesting.

Drew

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] Doc Team Meeting Minutes

[Martin Srebotnjak]

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 to this" etc.) so that
the translation process continues with the really-latest version (after an
official version is already published) and as hassle/confusion-free for
l10n teams as possible?

With the delicate translation process going on in parallel with the
considered minor content updates I would instead suggest to create odt/pdf
with errata or corrigenda of a guide (and all its chapters) that gets
updated regulary and is finally merged with the guide only with its next
iteration of publication.

To quote wikipedia/*Chicago Manual of Style
*, "Errata, lists of
errors and their corrections, may take the form of loose, inserted sheets
or bound-in pages. An errata sheet is definitely not a usual part of a
book. It should never be supplied to correct simple typographical errors
 (which may be rectified
in a later printing) or to insert additions to, or revisions of, the
printed text (which should wait for the next edition of the book). It is a
device to be used only in extreme cases where errors severe enough to cause
misunderstanding are detected too late to correct in the normal way but
before the finished book is distributed. Then the errors may be listed with
their locations and their corrections on a sheet that is tipped in
, either before or after the
book is bound, or laid in loose, usually inside the front cover of the
book. (Tipping and inserting must be done by hand, thus adding considerably
to the cost of the book.)"[2]


Thanks,
Martin

V V sre., 14. nov. 2018 ob 20:31 je oseba Olivier Hallot <
olivier.hal...@libreoffice.org> napisala:

> Wednesday November 14th2018, at 19:30 Berlin Time
>
> Presents: Drew, Cathy, Heiko, Olivier
>
> Fall back chat:
> https://irc.documentfoundation.org/?settings=#libreoffice-doc
>
> TDF Jitsi room
> https://jitsi.documentfoundation.org/tdfdocteam
>
> Completed Action Items:
> +
>
> Pending:
> + Update template for Calc Guide (Drew/Dave)
> + Proposal for the future LibreOffice documentation development
> workflow (Dave)
>
> Agenda+ Discussion:
> + Supporting minor updates to published guides (pdf file)
>
> + How to handle the UI changes with Tabbed Notebook as a standard
> feature with 6.2
>  +my suggestin is another appendix which maps the change in
> toolbutton location and menu location between the standard toolbars and
> the notebook bar tabs.(Drew)
>  + Perhaps images or graphs (Drew)
>  + Guides and Help share contents (olivier)
>
> + Calc Guide appendix for LireOffice online
> +   some open questions about the stand alone LOOL and the changes
> to menu structures when it is part of a CMS such as NextCloud
>
> + Appendix for Calculation engine support for threading(Drew)
>  +Really strugglig with this (more a fyi really)
> AI: Emails developers to get more clarifications (Drew)
>
>  + Enter images in document (Cathy)
> AI: Clarify the image anchoring (olivier)
>
>  + Long editing session turns LO slow and unusable (Cathy)
>  + Some crashes.
> AI: Send offending file to olivier for inspection  (Cathy)
>
>  + What is the real user we are targeting with Calc Guide (Cathy)
>   + Upper top of users, knowledgeable Excel user (olivier)
> AI:  + Raise the issue in the mailing list (Cathy)
>
> Next meeting WednesdayNovember21st2018, at 19:30 Berlin Time
>
>
>
>
>
>
> --
> 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: documentation+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/documentation/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-documentation] Doc Team Meeting Minutes

[Olivier Hallot]

Wednesday November 14th2018, at 19:30 Berlin Time

Presents: Drew, Cathy, Heiko, Olivier

Fall back chat:
https://irc.documentfoundation.org/?settings=#libreoffice-doc

TDF Jitsi room
https://jitsi.documentfoundation.org/tdfdocteam

Completed Action Items:
    + 

Pending:
    + Update template for Calc Guide (Drew/Dave)
    + Proposal for the future LibreOffice documentation development
workflow (Dave)

Agenda+ Discussion: 
    + Supporting minor updates to published guides (pdf file)

    + How to handle the UI changes with Tabbed Notebook as a standard
feature with 6.2
 +my suggestin is another appendix which maps the change in
toolbutton location and menu location between the standard toolbars and
the notebook bar tabs.(Drew)
 + Perhaps images or graphs (Drew)
 + Guides and Help share contents (olivier)

    + Calc Guide appendix for LireOffice online
    +   some open questions about the stand alone LOOL and the changes
to menu structures when it is part of a CMS such as NextCloud

    + Appendix for Calculation engine support for threading(Drew)
 +Really strugglig with this (more a fyi really)
AI: Emails developers to get more clarifications (Drew)

 + Enter images in document (Cathy)
AI: Clarify the image anchoring (olivier)
 
 + Long editing session turns LO slow and unusable (Cathy)
 + Some crashes. 
AI: Send offending file to olivier for inspection  (Cathy)

 + What is the real user we are targeting with Calc Guide (Cathy)
  + Upper top of users, knowledgeable Excel user (olivier)
AI:  + Raise the issue in the mailing list (Cathy)
 
Next meeting WednesdayNovember21st2018, at 19:30 Berlin Time






-- 
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: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-documentation] Added a few items to the discussion section on group pad.

[Drew Jensen]

Howdy,

Added a few items to the discussion section on the pad for
Work flow for minor changes to published guides (pdf)
Question on that LOOL appendix for Calc guide
An FYI about were I am or more am not on the appendix on the calculation
engine changes.

Drew

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] Indexing Clarification Needed

[Cathy Crumbley]

HI Milos,

Thank you for taking the time to explain this. It is quite helpful.

From what you describe, this is what I gather about how it works.

 * When a word is selected for an index entry, that word/phrase is
   automatically inserted in the Entry field in the Insert Index Entry
   dialog. It is also given a tag. Index entries for words/phrases with
   that tag cannot be different from what is in the text so the
   translators can’t change them.
 * When the cursor does not highlight a word but rather is next to a
   word, the word it is next to is automatically inserted into the
   Entry field.
 * When the selection and the index entry differ, however slightly, the
   selection is tagged differently. This tag breaks the link between
   the word in the text and the index entry. Thus, the translators are
   able to change the index entries independently of what is in the text.

If my understanding is correct, this means that we could select a 
word/phrase as long as we modify it in the Entry field. This would make 
our task slightly simpler (and more understandable, at least to me) and 
the Contributor Guide could be modified accordingly.


Thanks again,

Cathy


On 11/14/2018 8:27 AM, Milos Sramek wrote:

Dear Cathy and Drew,
as the terminology is unclear, I've prepared a document with explanation
and screenshots: http://sospreskoly.org/~milos/indexentry.odt
I hope it helps

Drew: It is not "indexing a character space". it is placing index entry
to a certain position in the document without relation to any specific
document text. LO distinguishes in fact two types of index entries, but
provides the same interface for both .
Milos


On 11/13/18 4:06 AM, Drew Jensen wrote:

Hi,

Reading along and having Writer open trying to do what you seem to be
asking and to be honest I am totally confused.

Here is what I think you are looking for.

You want me index a space character and give that a tag, which I suppose is
us typing in the word that we didn't just select before we opened the
dialog box.

Assuming that this word is in multiple places in the document, which I
didn't select for the index, i then forego the ability to auto select all
the instances and instead find them by hand, then select another space
character and do it all over again and again.

Is that it?

On Mon, Nov 12, 2018 at 8:07 PM Cathy Crumbley  wrote:


HI Milos,

Thank you for taking the time to explain.  For editing Writer
documentation, I needed to learn about Hunspell, so understand the issue
you are facing.

To help me understand this better, I have some questions:

Is it correct that you want only the singular nominative form of nouns
in the index?

What do you mean by "embedded" index entries?

It sounds like surrounding a word or phrase to save it creates a
different result than inserting the cursor before or after the word or
phrase. But what is the difference in what is saved?

The few times I have made an index entry by inserting the cursor before
or after a word (with no space between) only that word appears in the
index. Since we need to write the exact index entry in the index dialog,
it is puzzling that Writer would still grab neighboring words. This
seems like a bug. Do you know if it has been reported as a bug? Do we
know for sure that it is still a problem?

I think it would be helpful to understand more about what is involved in
translation. My understanding is that some language translators write
their own documentation while others start with the English version. I
don't have a clear sense of how that works. I tend to make a lot of
changes, including sharpening text and rearranging content. However, I
don't have a good sense of what this means for translators. To what
extent does it matter if there are many as opposed to few changes for you?

Thank you for whatever clarification and information you can provide.

Cathy

On 11/9/2018 11:10 AM, Milos Sramek wrote:

Dear Cathy,

I am the author of the request to not to "create index entries that
surround words or phrases".

The rationale is this: In English nouns have just two forms, one for
singular and one for plural. In languages with inflection it is
different, in Slovak we have up to 10 forms of a single word.

In the case of "index entries that surround words or phrases" the
"surrounded word or phrase" goes directly in the index. As we need to
use in translation an appropriate inflected form of the word, in that
case the inflected one will create an index entry, and not the basic
(singular nominative) one.

Example: There is an index entry "document" with three instances. I need
to translate them as "dokument", "dokumentom" "dokumenty". These will
create three independent entrees in the translated index, which is
unacceptable. Therefore, we need those "embedded" index entries.

LO somehow automates insertion of index term - when opening the Index
entry dialog it highlights the nearest word and fills with it the Entry
field. In order to avoid these "surrounded 

[libreoffice-documentation] Re: Request to update Chapter 14 of GS guide regarding extensions

[Drew Jensen]

Actually I went ahead and grabbed the Chapter 14 file from the current GS
guide and updated the text for this, just now.

So, I can put this up the NC server.

Should I create a new directory for a new guide number or just put it into
the feedback folder for the 6.0 guide?

The subject of changing workflow to support minor changes and republishing
the pdf has been talked about but it hasn't been settled how that would
work.

Drew

On Wed, Nov 14, 2018 at 11:36 AM Drew Jensen 
wrote:

> Howdy,
>
> Using this as a place holder for this. (is there a better way already in
> place)
>
> Chapter 14, Customizing LO, should be updated to show that an extension
> can be added by dragging and dropping the oxt file onto the start center
> window. Doing show opens the Extension Manager and triggers the Add
> extension function.
>
> Best wishes,
>
> Drew
>

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-documentation] Request to update Chapter 14 of GS guide regarding extensions

[Drew Jensen]

Howdy,

Using this as a place holder for this. (is there a better way already in
place)

Chapter 14, Customizing LO, should be updated to show that an extension can
be added by dragging and dropping the oxt file onto the start center
window. Doing show opens the Extension Manager and triggers the Add
extension function.

Best wishes,

Drew

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] REMIND: Documentation team call is today at --> 19:30 <-- Berlin Time

[Drew Jensen]

I'll be on the call but have a 14:30 (local time) appointment (scheduled a
couple weeks back) which I can not be late for so may need to leave early
depending on how long it goes.

This is a one time event so the 19:30 is fine with me going forward.

Talk to you soon,

Drew

On Wed, Nov 14, 2018, 10:19 AM Dave Barton  wrote:

> Sorry, I cannot make today's meeting.
>
> Dave
>
>  Original Message  
> From: Olivier Hallot 
> To: LibreOffice Documentation ,
> LibreOffice-l10n 
> Date: Wed, 14 Nov 2018 08:16:40 -0200
>
>
> > Hi Documentation Team (Guides, Help contents) !
> >
> > Our documentation team meeting will take place today at 19:30 CET
> > (Berlin time).
> >
> > We will use the following jitsi  meeting room
> >
> > https://jitsi.documentfoundation.org/tdfdocteam
> >
> > The meeting room is supposed to work will all browsers without the need
> > of a specific plugin.
> >
> > The documentation pad for the meeting minute is
> > https://pad.documentfoundation.org/p/documentation
> >
> > Main topics
> > (Please add  your agenda items to the pad)
> >
> > See you later!
> >
>
> --
> To unsubscribe e-mail to: documentation+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/documentation/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] REMIND: Documentation team call is today at --> 19:30 <-- Berlin Time

[Dave Barton]

Sorry, I cannot make today's meeting.

Dave

 Original Message  
From: Olivier Hallot 
To: LibreOffice Documentation ,
LibreOffice-l10n 
Date: Wed, 14 Nov 2018 08:16:40 -0200


> Hi Documentation Team (Guides, Help contents) !
> 
> Our documentation team meeting will take place today at 19:30 CET
> (Berlin time).
> 
> We will use the following jitsi  meeting room
> 
> https://jitsi.documentfoundation.org/tdfdocteam
> 
> The meeting room is supposed to work will all browsers without the need
> of a specific plugin.
> 
> The documentation pad for the meeting minute is
> https://pad.documentfoundation.org/p/documentation
> 
> Main topics
> (Please add  your agenda items to the pad)
> 
> See you later!
> 

-- 
To unsubscribe e-mail to: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-documentation] Indexing Clarification Needed

[Drew Jensen]

Howdy Milos,

Ďakujem!

Všetko najlepšie.

Drew

On Wed, Nov 14, 2018 at 8:28 AM Milos Sramek  wrote:

> Dear Cathy and Drew,
> as the terminology is unclear, I've prepared a document with explanation
> and screenshots: http://sospreskoly.org/~milos/indexentry.odt
> I hope it helps
>
> Drew: It is not "indexing a character space". it is placing index entry
> to a certain position in the document without relation to any specific
> document text. LO distinguishes in fact two types of index entries, but
> provides the same interface for both .
> Milos
>
>
> On 11/13/18 4:06 AM, Drew Jensen wrote:
> > Hi,
> >
> > Reading along and having Writer open trying to do what you seem to be
> > asking and to be honest I am totally confused.
> >
> > Here is what I think you are looking for.
> >
> > You want me index a space character and give that a tag, which I suppose
> is
> > us typing in the word that we didn't just select before we opened the
> > dialog box.
> >
> > Assuming that this word is in multiple places in the document, which I
> > didn't select for the index, i then forego the ability to auto select all
> > the instances and instead find them by hand, then select another space
> > character and do it all over again and again.
> >
> > Is that it?
> >
> > On Mon, Nov 12, 2018 at 8:07 PM Cathy Crumbley 
> wrote:
> >
> >> HI Milos,
> >>
> >> Thank you for taking the time to explain.  For editing Writer
> >> documentation, I needed to learn about Hunspell, so understand the issue
> >> you are facing.
> >>
> >> To help me understand this better, I have some questions:
> >>
> >> Is it correct that you want only the singular nominative form of nouns
> >> in the index?
> >>
> >> What do you mean by "embedded" index entries?
> >>
> >> It sounds like surrounding a word or phrase to save it creates a
> >> different result than inserting the cursor before or after the word or
> >> phrase. But what is the difference in what is saved?
> >>
> >> The few times I have made an index entry by inserting the cursor before
> >> or after a word (with no space between) only that word appears in the
> >> index. Since we need to write the exact index entry in the index dialog,
> >> it is puzzling that Writer would still grab neighboring words. This
> >> seems like a bug. Do you know if it has been reported as a bug? Do we
> >> know for sure that it is still a problem?
> >>
> >> I think it would be helpful to understand more about what is involved in
> >> translation. My understanding is that some language translators write
> >> their own documentation while others start with the English version. I
> >> don't have a clear sense of how that works. I tend to make a lot of
> >> changes, including sharpening text and rearranging content. However, I
> >> don't have a good sense of what this means for translators. To what
> >> extent does it matter if there are many as opposed to few changes for
> you?
> >>
> >> Thank you for whatever clarification and information you can provide.
> >>
> >> Cathy
> >>
> >> On 11/9/2018 11:10 AM, Milos Sramek wrote:
> >>> Dear Cathy,
> >>>
> >>> I am the author of the request to not to "create index entries that
> >>> surround words or phrases".
> >>>
> >>> The rationale is this: In English nouns have just two forms, one for
> >>> singular and one for plural. In languages with inflection it is
> >>> different, in Slovak we have up to 10 forms of a single word.
> >>>
> >>> In the case of "index entries that surround words or phrases" the
> >>> "surrounded word or phrase" goes directly in the index. As we need to
> >>> use in translation an appropriate inflected form of the word, in that
> >>> case the inflected one will create an index entry, and not the basic
> >>> (singular nominative) one.
> >>>
> >>> Example: There is an index entry "document" with three instances. I
> need
> >>> to translate them as "dokument", "dokumentom" "dokumenty". These will
> >>> create three independent entrees in the translated index, which is
> >>> unacceptable. Therefore, we need those "embedded" index entries.
> >>>
> >>> LO somehow automates insertion of index term - when opening the Index
> >>> entry dialog it highlights the nearest word and fills with it the Entry
> >>> field. In order to avoid these "surrounded words", one needs to enter
> >>> something else (maybe the suggested space after) or to place the entry
> >>> to a neighboring word.
> >>>
> >>> Milos
> >>>
> >>>
> >>> On 11/8/18 6:18 AM, Cathy Crumbley wrote:
>  Hi All,
> 
>  The Contributor Guide is extremely helpful and I deeply appreciate
>  that someone --presumably Jean--invested the time and energy to create
>  it. I would just like a little bit of clarification.
> 
>  Chapter 2 provides guidelines for indexing. On page 11, the guidelines
>  say: "The translators have requested that we do NOT create index
>  entries that surround words or phrases in the text. Instead, we need
>  to create entries that are embedded 

[libreoffice-documentation] REMIND: Documentation team call is today at --> 19:30 <-- Berlin Time

[Olivier Hallot]

Hi Documentation Team (Guides, Help contents) !

Our documentation team meeting will take place today at 19:30 CET
(Berlin time).

We will use the following jitsi  meeting room

https://jitsi.documentfoundation.org/tdfdocteam

The meeting room is supposed to work will all browsers without the need
of a specific plugin.

The documentation pad for the meeting minute is
https://pad.documentfoundation.org/p/documentation

Main topics
(Please add  your agenda items to the pad)

See you later!
-- 
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: documentation+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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy