khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-03 10:20:02 +07:00
Code Issues Packages Projects Releases Wiki Activity

Fix markup

Browse Source 
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This commit is contained in:
Daniel Calviño Sánchez
2017-05-12 22:12:27 +02:00
parent c1143b5a16
commit 02c14a31e5
4 changed files with 24 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
developer_manual/app/users.rst
View File

@@ -1,6 +1,6 @@
==============
===============
User Management
==============
===============
.. sectionauthor:: Bernhard Posselt <dev@bernhard-posselt.com>

14
developer_manual/bugtracker/kanban.rst
View File

@@ -57,12 +57,11 @@ When can I pull?
documented in a comment to the issue before moving it to the "To develop"
step:
* At least one Scenario – written in Gherkin – that tells you and the tester
when the issue is ready to be released.
* A concept describing the planned implementation. This can be as simple as
a “this just needs changes to the login screen CSS” or so complex that you
link to a blog entry somewhere else.
* At least one Scenario – written in Gherkin – that tells you and the tester
when the issue is ready to be released.
* A concept describing the planned implementation. This can be as simple as
a “this just needs changes to the login screen CSS” or so complex that you
link to a blog entry somewhere else.
Who is Assigned?
The maintainer that feels responsible for the issue.
@@ -135,7 +134,8 @@ When can I pull?
can be used as a checklist for what to try. Before you start move the issue to
the “Reviewing” step by assigning the “6 – Reviewing” label.
**Who is Assigned?** No one. Especially not if you are working on something else!
Who is Assigned?
No one. Especially not if you are working on something else!
Reviewing
~~~~~~~~~

1
developer_manual/core/ocs-share-api.rst
View File

@@ -139,6 +139,7 @@ Federated Cloud Shares
Both the sending and the receiving instance need to have federated cloud sharing
enabled and configured. See `Configuring Federated Cloud Sharing <https://docs.nextcloud.org/server/12/admin_manual/configuration_files/federated_cloud_sharing_configuration.html>`_.
.. TODO ON RELEASE: Update version number above on release
Create a new Federated Cloud Share

26
developer_manual/core/translation.rst
View File

@@ -5,7 +5,8 @@ Make text translatable
----------------------
In HTML or PHP wrap it like this ``<?php p($l->t('This is some text'));?>`` or this ``<?php print_unescaped($l->t('This is some text'));?>``.
For the right date format use ``<?php p($l->l('date', time()));?>``. Change the way dates are shown by editing /core/l10n/l10n-[lang].php.
For the right date format use ``<?php p($l->l('date', time()));?>``. Change the way dates are shown by editing :file:`/core/l10n/l10n-{lang}.php`.
To translate text in JavaScript use: ``t('appname','text to translate');``
@@ -54,21 +55,22 @@ Automated synchronization of translations
-----------------------------------------
Multiple nightly jobs have been setup in order to synchronize translations - it's a multi-step process:
``perl l10n.pl read`` will rescan all PHP and JavaScript files and generate the templates.
The templates are pushed to `Transifex`_ (tx push -s).
All translations are pulled from `Transifex`_ (tx pull -a).
``perl l10n.pl write`` will write the PHP files containing the translations.
Finally the changes are pushed to Git.
#. ``perl l10n.pl read`` will rescan all PHP and JavaScript files and generate the templates.
#. The templates are pushed to `Transifex`_ (tx push -s).
#. All translations are pulled from `Transifex`_ (tx pull -a).
#. ``perl l10n.pl write`` will write the PHP files containing the translations.
#. Finally the changes are pushed to Git.
Please follow the steps below to add translation support to your app:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Create a folder ``l10n``.
Create the file ``ignorelist`` which can contain files which shall not be scanned during step 4.
Edit ``l10n/.tx/config`` and copy/paste a config section and adapt it by changing the app/folder name.
Run ``perl l10n.pl read`` within the folder :file:`l10n`.
Add the newly created translation template (l10n/Templates/<appname>.pot) to Git and commit the changes above.
After the next nightly sync job a new resource will appear on Transifex and from now on every night the latest translations will arrive.
#. Create a folder ``l10n``.
#. Create the file ``ignorelist`` which can contain files which shall not be scanned during step 4.
#. Edit ``l10n/.tx/config`` and copy/paste a config section and adapt it by changing the app/folder name.
#. Run ``perl l10n.pl read`` within the folder :file:`l10n`.
#. Add the newly created translation template (*l10n/Templates/<appname>.pot*) to Git and commit the changes above.
#. After the next nightly sync job a new resource will appear on Transifex and from now on every night the latest translations will arrive.
Translation sync jobs:
~~~~~~~~~~~~~~~~~~~~~~