RenJuan/TASKPM
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: Fix problem in PDF generation for user help

Browse source 
Too many levels of headers for the PDF.

FEA: ItEr76S04BugFixing
This commit is contained in:
Manuel Rego Casasnovas 2012-06-14 11:04:14 +02:00
parent c03969199f
commit 69652b89bc
3 changed files with 6 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/src/user/en/16-ldap-authentication.rst
View file

@ -135,8 +135,7 @@ The next example represents a valid LDAP structure to use property strategy.
|- uid=worker2
|- uid=worker3
With attribute
..............
**With attribute**
In this case, each user will have attribute, for example called ``group`` with
the name of the group to which it belongs:
@ -186,8 +185,7 @@ And for example if you want to match some roles:
* All projects edition allowed: ``admins``
* Project creation allowed: ``workers``
By user identifier
..................
**By user identifier**
You can even have a workaround to specify LibrePlan roles directly to users,
without having an attribute in each LDAP user.

6
doc/src/user/es/16-ldap-authentication.rst
View file

@ -139,8 +139,7 @@ estrategia de propiedad.
|- uid=worker2
|- uid=worker3
Con atributo
............
**Con atributo**
En este caso, cada usuario tendrá un atributo, por ejemplo llamado ``group```
con el nombre del grupo al que pertenece:
@ -190,8 +189,7 @@ Y por ejemplo si quiere hacer alguna correspondencia de roles:
* All projects edition allowed: ``admins``
* Project creation allowed: ``workers``
Por identificador de usuario
............................
**Por identificador de usuario**
Incluso puede tener una solución para especificar los roles de LibrePlan
directamente a los usuarios, sin tener un atributo en cada usuario de LDAP.

6
doc/src/user/gl/16-ldap-authentication.rst
View file

@ -139,8 +139,7 @@ estratexia de propiedade.
|- uid=worker2
|- uid=worker3
Con atributo
............
**Con atributo**
Neste caso, cada usuario tenrá un atributo, por exemplo chamado ``group```
co nome do grupo ao que pertence:
@ -190,8 +189,7 @@ E por exemplo se quere facer algunha correspondencia de roles:
* All projects edition allowed: ``admins``
* Project creation allowed: ``workers``
Por identificador de usuario
............................
**Por identificador de usuario**
Incluso pode ter unha solución para especificar os roles de LibrePlan
directamente aos usuarios, sen ter un atributo en cada usuario de LDAP.