Weblate 3.7.1 Documentationmain.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 468 页 | 5.53 MB | 1 年前3- The Weblate Manual 3.7main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 468 页 | 5.53 MB | 1 年前3
- The Weblate Manual 3.10main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 553 页 | 8.32 MB | 1 年前3
- The Weblate Manual 3.10.1main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 555 页 | 8.28 MB | 1 年前3
- Weblate 3.8 Documentationmain.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 487 页 | 8.18 MB | 1 年前3
- The Weblate Manual 3.10.3main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 560 页 | 8.57 MB | 1 年前3
- The Weblate Manual 3.10.2main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 560 页 | 8.57 MB | 1 年前3
- The Weblate Manual 3.9.1main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 550 页 | 8.97 MB | 1 年前3
- The Weblate Manual 3.9main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 540 页 | 8.92 MB | 1 年前3
- The Weblate Manual 3.4main.c -o po/hello.pot Then you can update individual translation files to match newly created templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs caches parsed templates and avoids the need to do parsing with every single request. You can configure it using the following snippet (the loaders setting is important here): TEMPLATES = [ { template.backends.django.DjangoTemplates', 'DIRS': [ os.path.join(BASE_DIR, 'templates'), ], 'OPTIONS': { 'context_processors': [ 'django.contrib0 码力 | 415 页 | 1.73 MB | 1 年前3
共 298 条
- 1
- 2
- 3
- 4
- 5
- 6
- 30