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


BTW:

With "file for file" I meant the review process.

P.S. Please let the "<defaultinline/>" phrase string out of translation or remove it if you want.

Removal of it by ohallot is already in gerrit.


Am 07.07.2018 um 18:49 schrieb Sophia Schröder:
Sorry for the extra work, but... ;-) :-*

-------- Weitergeleitete Nachricht --------
Betreff:     Re: Minutes of ESC call 2017-07-05
Datum:     Sat, 7 Jul 2018 18:44:56 +0200
Von:     Sophia Schröder <sophia.schroeder@libreoffice.org>
Organisation:     LibreOffice.org
An:     libreoffice@lists.freedesktop.org



* Documentation (Olivier)
     + New help
         + Testing in bug hunting session tomorrow (installs)
         + Small corrections in XSLT filter
         + tweaks in CSS by fitoshido – people start contributing
     + Help contents
         + cosmetic refactor by SophiaS
         + Contents for [NatNum12] by Lazlo Nemetz
         + Contents fixes (ohallot, fitoshido)
* l10n (Sophie)
    + gave feedback to Olivier on reformat patches – cosmetics changes
      not ideal for our l10n volunteers
    + better to also have actual help content changes alongside

I am with you. Please see my minor cosmetical changes as they are intented:
A ground work for further improvements and easier work with the help
files themselves.
And it is planned as a "Long Term Project" to not flood translators with
minor changes at once.

Let me explain it in one phrase as an example:

"Press the Enter key." - In this form, the plain text will be displayed
to our user.

But hey, we have also at least two other forms of this sentence:

"Press the <emph>Enter</emph> key.", which will display the word "Enter"
in bold.

And there is "Press the <item type="keycode">Enter</item> key.", which
behaves like the second case for now.

But in the end, the last one let us play with more possibilities in css
styles, no? (I am not sure, just speculating).
I am thinking about an underlying background of a key, for example.

And yes, I am experimenting a bit here and there to find out best
solutions and practices.

So yes, carefull reviewings and criticisms are very welcome.

And things like "<emph>Print </emph>icon" - l only say kerning and
spacing in the resulting text.

I would like to extend/expand help textes by the way, while also
reducing translation work by using the embedding feature instead of
translating the same sentence several times again, but honestly, I have
no clue how that works.

I also changed my workflow to work file for file, hope that helps, at
least in my case for merge conflicts I cannot solve online, but also for
reviewing.

Regards / Mit freundlichen Grüßen

Sophia Schröder
---
www.LibreOffice.org
German Language Team
Help Files Debugger
IRC: SophiaS

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice



--
Regards / Mit freundlichen Grüßen

Sophia Schröder
---
www.LibreOffice.org
German Language Team
Help Files Debugger
IRC: SophiaS


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