freeipa

0 Fork 0

Files

T

John Dennis 4015667bbe ticket 1650 - compute accurate translation statistics

ticket 1650 (https://fedorahosted.org/freeipa/ticket/1650) has
an extensive discussion of the issues, please refer to that.

This patch does the following:

* does not count fuzzy translations when computing translation
  statistics via the "msg-stats" make target in install/po

* adds a new make target called "pull-po" which pulls updated po files
  from Transifex (configure.ac includes some trailing whitespace fixes)

* turns off the generation of fuzzy translation suggestions during the
  message merge phase.

2011-08-18 14:25:58 +02:00

conf

rename static to ui

2011-01-20 14:12:47 +00:00

html

Fixed browser configuration pages

2011-08-17 17:28:25 +00:00

migration

Fixed broken links in ipa_error.css and ipa_migration.css.

2011-08-11 13:38:36 +00:00

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +02:00

Fixed browser configuration pages

2011-08-17 17:28:25 +00:00

tools

Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place.

2011-08-09 13:12:19 +02:00

Fixed problem selecting value from combobox

2011-08-17 18:03:29 +00:00

updates

Correct sudo runasuser and runasgroup attributes in schema

2011-07-19 08:06:41 -04:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +02:00

Makefile.am

rename static to ui

2011-01-20 14:12:47 +00:00

README.schema

Add some basic rules for adding new schema

2010-08-27 13:40:37 -04:00

README.schema

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.