README.md | 6 +++---
readlicense_oo/docs/readme.xrm | 24 ++++++++++++------------
2 files changed, 15 insertions(+), 15 deletions(-)
New commits:
commit 51cb2e66897a9dd5676b33d35a5683a8f8e56ef5
Author: Ilmari Lauhakangas <ilmari.lauhakan...@libreoffice.org>
Date: Fri Feb 9 14:19:29 2018 +0200
Updated links in readme files (https etc.)
Change-Id: Id4906290f312dc6d1800d5d17dedf1f07dd3480d
Reviewed-on: https://gerrit.libreoffice.org/49491
Tested-by: Jenkins <c...@libreoffice.org>
Reviewed-by: Adolfo Jayme Barrientos <fit...@ubuntu.com>
diff --git a/README.md b/README.md
index 1a91674665e7..1bbf9b58a481 100644
--- a/README.md
+++ b/README.md
@@ -16,8 +16,8 @@ A quick overview of the LibreOffice code structure.
You can develop for LibreOffice in one of two ways, one
recommended and one much less so. First the somewhat less recommended
way: it is possible to use the SDK to develop an extension,
-for which you can read the API docs [here](http://api.libreoffice.org/)
-and [here](http://wiki.services.openoffice.org/wiki/Documentation/DevGuide).
+for which you can read the API docs [here](https://api.libreoffice.org/)
+and [here](https://wiki.openoffice.org/wiki/Documentation/DevGuide).
This re-uses the (extremely generic) UNO APIs that are also used by
macro scripting in StarBasic.
@@ -68,7 +68,7 @@ Each module should have a `README` file inside it which has
some
degree of documentation for that module; patches are most welcome to
improve those. We have those turned into a web page here:
-http://docs.libreoffice.org/
+https://docs.libreoffice.org/
However, there are two hundred modules, many of them of only
peripheral interest for a specialist audience. So - where is the
diff --git a/readlicense_oo/docs/readme.xrm b/readlicense_oo/docs/readme.xrm
index 86b075aade14..4f4c802581ff 100644
--- a/readlicense_oo/docs/readme.xrm
+++ b/readlicense_oo/docs/readme.xrm
@@ -17,14 +17,14 @@
<body>
<div id="Intro">
<h1 id="Welcome" xml:lang="en-US">${PRODUCTNAME}
${PRODUCTVERSION} ReadMe</h1>
- <p id="LatestUpdates" xml:lang="en-US">For the latest
updates to this readme file, see <a
href="http://www.libreoffice.org/welcome/readme.html";>http://www.libreoffice.org/welcome/readme.html</a></p>
+ <p id="LatestUpdates" xml:lang="en-US">For the latest
updates to this readme file, see <a
href="https://www.libreoffice.org/welcome/readme.html";>https://www.libreoffice.org/welcome/readme.html</a></p>
<p id="A6" xml:lang="en-US">This file contains
important information about the ${PRODUCTNAME} software. You are recommended to
read this information very carefully before starting installation.</p>
- <p id="A7" xml:lang="en-US">The ${PRODUCTNAME}
community is responsible for the development of this product, and invites you
to consider participating as a community member. If you are a new user, you can
visit the ${PRODUCTNAME} site, where you will find lots of information about
the ${PRODUCTNAME} project and the communities that exist around it. Go to <a
href="http://www.libreoffice.org/";>http://www.libreoffice.org/</a>.</p>
+ <p id="A7" xml:lang="en-US">The ${PRODUCTNAME}
community is responsible for the development of this product, and invites you
to consider participating as a community member. If you are a new user, you can
visit the ${PRODUCTNAME} site, where you will find lots of information about
the ${PRODUCTNAME} project and the communities that exist around it. Go to <a
href="https://www.libreoffice.org/";>https://www.libreoffice.org/</a>.</p>
<h3 id="A10" xml:lang="en-US">Is ${PRODUCTNAME} Really
Free for Any User?</h3>
<p id="A11" xml:lang="en-US">${PRODUCTNAME} is free for
use by everybody. You may take this copy of ${PRODUCTNAME} and install it on as
many computers as you like, and use it for any purpose you like (including
commercial, government, public administration and educational use). For further
details see the license text packaged with this ${PRODUCTNAME} download.</p>
<h3 id="A12" xml:lang="en-US">Why is ${PRODUCTNAME}
Free for Any User?</h3>
<p id="A13" xml:lang="en-US">You can use this copy of
${PRODUCTNAME} free of charge because individual contributors and corporate
sponsors have designed, developed, tested, translated, documented, supported,
marketed, and helped in many other ways to make ${PRODUCTNAME} what it is today
- the world's leading Open Source productivity software for home and office.</p>
- <p id="A13b" xml:lang="en-US">If you appreciate their
efforts, and would like to ensure that ${PRODUCTNAME} continues to be available
far into the future, please consider contributing to the project - see <a
href="http://www.documentfoundation.org/contribution/";>http://www.documentfoundation.org/contribution/</a>
for details. Everyone can make a contribution of some kind.</p>
+ <p id="A13b" xml:lang="en-US">If you appreciate their
efforts, and would like to ensure that ${PRODUCTNAME} continues to be available
far into the future, please consider contributing to the project - see <a
href="https://www.documentfoundation.org/contribution/";>https://www.documentfoundation.org/contribution/</a>
for details. Everyone can make a contribution of some kind.</p>
</div>
<div id="Installation">
@@ -104,7 +104,7 @@
<p id="rpminstall7a" xml:lang="en-US">Alternatively,
you can use the 'install' script, located in the toplevel directory of this
archive to perform an installation as a user. The script will set up
${PRODUCTNAME} to have its own profile for this installation, separated from
your normal ${PRODUCTNAME} profile. Note that this will not install the system
integration parts such as desktop menu items and desktop MIME type
registrations.</p>
<h3 id="sdfsdfgf42t2" xml:lang="en-US">Notes Concerning
Desktop Integration for Linux Distributions Not Covered in the Above
Installation Instructions</h3>
<p id="otherinstall1" xml:lang="en-US">It should be
easily possible to install ${PRODUCTNAME} on other Linux distributions not
specifically covered in these installation instructions. The main aspect for
which differences might be encountered is desktop integration.</p>
- <p id="otherinstall2" xml:lang="en-US">The RPMS (or
DEBS, respectively) directory also contains a package named
libreoffice${PRODUCTVERSION}-freedesktop-menus-${PRODUCTVERSION}.0.1-1.noarch.rpm
(or libreoffice${PRODUCTVERSION}-debian-menus_${PRODUCTVERSION}.0.1-1_all.deb,
respectively, or similar). This is a package for all Linux distributions that
support the Freedesktop.org specifications/recommendations (<a
href="http://en.wikipedia.org/wiki/Freedesktop.org";>http://en.wikipedia.org/wiki/Freedesktop.org</a>),
and is provided for installation on other Linux distributions not covered in
the aforementioned instructions.</p>
+ <p id="otherinstall2" xml:lang="en-US">The RPMS (or
DEBS, respectively) directory also contains a package named
libreoffice${PRODUCTVERSION}-freedesktop-menus-${PRODUCTVERSION}.0.1-1.noarch.rpm
(or libreoffice${PRODUCTVERSION}-debian-menus_${PRODUCTVERSION}.0.1-1_all.deb,
respectively, or similar). This is a package for all Linux distributions that
support the Freedesktop.org specifications/recommendations (<a
href="https://en.wikipedia.org/wiki/Freedesktop.org";>https://en.wikipedia.org/wiki/Freedesktop.org</a>),
and is provided for installation on other Linux distributions not covered in
the aforementioned instructions.</p>
<h3 id="sdfsdfgf42t3" xml:lang="en-US">Installing a
Language Pack</h3>
<p id="linuxlangpack1" xml:lang="en-US">Download the
language pack for your desired language and platform. They are available from
the same location as the main installation archive. From the Nautilus file
manager, extract the downloaded archive into a directory (your desktop, for
instance). Ensure that you have exited all ${PRODUCTNAME} applications
(including the QuickStarter, if it is started).</p>
<p id="linuxlangpack2" xml:lang="en-US">Change
directory to the directory in which you extracted your downloaded language
pack.</p>
@@ -161,33 +161,33 @@
<div class="WIN" id="Mapi">
<h2 id="gfh6w1" xml:lang="en-US">Problems When Sending
Documents as E-mails From ${PRODUCTNAME}</h2>
- <p id="pji76w1" xml:lang="en-US">When sending a
document via 'File - Send - Document as E-mail' or 'Document as PDF Attachment'
problems might occur (program crashes or hangs). This is due to the Windows
system file "Mapi" (Messaging Application Programming Interface) which causes
problems in some file versions. Unfortunately, the problem cannot be narrowed
down to a certain version number. For more information visit <a
href="http://www.microsoft.com";>http://www.microsoft.com</a> to search the
Microsoft Knowledge Base for "mapi dll".</p>
+ <p id="pji76w1" xml:lang="en-US">When sending a
document via 'File - Send - Document as E-mail' or 'Document as PDF Attachment'
problems might occur (program crashes or hangs). This is due to the Windows
system file "Mapi" (Messaging Application Programming Interface) which causes
problems in some file versions. Unfortunately, the problem cannot be narrowed
down to a certain version number. For more information visit <a
href="https://www.microsoft.com";>https://www.microsoft.com</a> to search the
Microsoft Knowledge Base for "mapi dll".</p>
</div>
<div id="A11y">
<h2 id="aw22" xml:lang="en-US">Important Accessibility
Notes</h2>
- <p id="access7" xml:lang="en-US">For more information
on the accessibility features in ${PRODUCTNAME}, see <a
href="http://www.libreoffice.org/accessibility/";>http://www.libreoffice.org/accessibility/</a></p>
+ <p id="access7" xml:lang="en-US">For more information
on the accessibility features in ${PRODUCTNAME}, see <a
href="https://www.libreoffice.org/accessibility/";>https://www.libreoffice.org/accessibility/</a></p>
</div>
<div id="UserSupport">
<h2 id="support" xml:lang="en-US">User Support</h2>
- <p id="support1" xml:lang="en-US">The main support page
<a
href="http://www.libreoffice.org/support/";>http://www.libreoffice.org/support/</a>
offers various possibilities for help with ${PRODUCTNAME}. Your question may
have already been answered - check the Community Forum at <a
href="http://www.documentfoundation.org/nabble/";>http://www.documentfoundation.org/nabble/</a>
or search the archives of the 'us...@libreoffice.org' mailing list at <a
href="http://www.libreoffice.org/lists/users/";>http://www.libreoffice.org/lists/users/</a>.
Alternatively, you can send in your questions to <a
href="mailto:us...@libreoffice.org";>us...@libreoffice.org</a>. If you like to
subscribe to the list (to get email responses), send an empty mail to: <a
href="mailto:users+subscr...@libreoffice.org";>users+subscr...@libreoffice.org</a>.</p>
- <p id="faq" url="ahead" xml:lang="en-US">Also check the
FAQ section at <a
href="http://www.libreoffice.org/faq/";>http://www.libreoffice.org/faq/.</a></p>
+ <p id="support1" xml:lang="en-US">The <a
href="https://www.libreoffice.org/get-help/community-support/";>main support
page</a> offers various possibilities for help with ${PRODUCTNAME}. Your
question may have already been answered - check the Community Forum at <a
href="https://www.documentfoundation.org/nabble/";>https://www.documentfoundation.org/nabble/</a>
or search the archives of the 'us...@libreoffice.org' mailing list at <a
href="https://www.libreoffice.org/lists/users/";>https://www.libreoffice.org/lists/users/</a>.
Alternatively, you can send in your questions to <a
href="mailto:us...@libreoffice.org";>us...@libreoffice.org</a>. If you like to
subscribe to the list (to get email responses), send an empty mail to: <a
href="mailto:users+subscr...@libreoffice.org";>users+subscr...@libreoffice.org</a>.</p>
+ <p id="faq" url="ahead" xml:lang="en-US">Also check the
FAQ section at <a
href="https://www.libreoffice.org/get-help/frequently-asked-questions/";>the
LibreOffice website</a>.</p>
</div>
<div id="ReportBugsIssues">
<h2 id="reportbugs" xml:lang="en-US">Reporting Bugs
& Issues</h2>
- <p id="reportbugs1" xml:lang="en-US">Our system for
reporting, tracking and solving bugs is currently BugZilla, kindly hosted at <a
href="https://bugs.libreoffice.org/";>https://bugs.libreoffice.org/</a>. We
encourage all users to feel entitled and welcome to report bugs that may arise
on your particular platform. Energetic reporting of bugs is one of the most
important contributions that the user community can make to the ongoing
development and improvement of ${PRODUCTNAME}.</p>
+ <p id="reportbugs1" xml:lang="en-US">Our system for
reporting, tracking and solving bugs is currently Bugzilla, hosted at <a
href="http://bugs.documentfoundation.org/";>http://bugs.documentfoundation.org/</a>.
We encourage all users to feel entitled and welcome to report bugs that may
arise on your particular platform. Energetic reporting of bugs is one of the
most important contributions that the user community can make to the ongoing
development and improvement of ${PRODUCTNAME}.</p>
</div>
<div id="GettingInvolved">
<h2 id="gettinginvolved1" xml:lang="en-US">Getting
Involved</h2>
<p id="gettinginvolved2" xml:lang="en-US">The
${PRODUCTNAME} Community would very much benefit from your active participation
in the development of this important open source project.</p>
- <p id="gettingimvolved3" xml:lang="en-US">As a user,
you are already a valuable part of the suite's development process and we would
like to encourage you to take an even more active role with a view to being a
long-term contributor to the community. Please join and check out the
contributing page at <a
href="http://www.libreoffice.org/contribution/";>http://www.libreoffice.org/contribution/</a></p>
+ <p id="gettingimvolved3" xml:lang="en-US">As a user,
you are already a valuable part of the suite's development process and we would
like to encourage you to take an even more active role with a view to being a
long-term contributor to the community. Please join and check out the
contributing page at <a
href="https://www.libreoffice.org/community/get-involved/";>the LibreOffice
website</a>.</p>
<h3 id="howtostart" xml:lang="en-US">How to Start</h3>
- <p id="howtostart1" xml:lang="en-US">The best way to
start contributing is to subscribe to one or more of the mailing lists, lurk
for a while, and gradually use the mail archives to familiarize yourself with
many of the topics covered since the ${PRODUCTNAME} source code was released
back in October 2000. When you're comfortable, all you need to do is send an
email self-introduction and jump right in. If you are familiar with Open Source
Projects, check out our To-Dos list and see if there is anything you would like
to help with at <a
href="http://www.libreoffice.org/develop/";>http://www.libreoffice.org/develop/</a>.</p>
+ <p id="howtostart1" xml:lang="en-US">The best way to
start contributing is to subscribe to one or more of the mailing lists, lurk
for a while, and gradually use the mail archives to familiarize yourself with
many of the topics covered since the ${PRODUCTNAME} source code was released
back in October 2000. When you're comfortable, all you need to do is send an
email self-introduction and jump right in. If you are familiar with Open Source
Projects, check out our To-Dos list and see if there is anything you would like
to help with at <a href="https://www.libreoffice.org/community/developers/";>the
LibreOffice website</a>.</p>
<h3 id="subscribe" xml:lang="en-US">Subscribe</h3>
- <p id="subscribe1" xml:lang="en-US">Here are a few of
the mailing lists to which you can subscribe at <a
href="http://www.libreoffice.org/contribution/";>http://www.libreoffice.org/contribution/</a></p>
+ <p id="subscribe1" xml:lang="en-US">Here are a few of
the mailing lists to which you can subscribe at <a
href="https://www.libreoffice.org/get-help/mailing-lists/";>https://www.libreoffice.org/get-help/mailing-lists/</a></p>
<ul>
<li>
<p id="subscribelist1"
xml:lang="en-US">News: annou...@documentfoundation.org *recommended to all
users* (light traffic)</p>
_______________________________________________
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
