Compare commits

..

70 commits

Author SHA1 Message Date
Justin Mayer
b7408cbfe9
Merge pull request #3491 from clockback/enable-flake8-unused-arguments 2025-07-22 19:18:09 +02:00
Justin Mayer
87e3b60da7 Update tests for dark mode & GitHub link changes 2025-07-22 17:41:50 +02:00
Jacki
f95466c8fe Implement dark mode for template
Signed-off-by: Jacki <jacki@thejackimonster.de>
2025-07-22 17:41:50 +02:00
Jacki
4cac1ab5f1 Drop loading external image from Github
Signed-off-by: Jacki <jacki@thejackimonster.de>
2025-07-22 17:41:50 +02:00
Ilya Simpson
6df3cfc6e3 Enable flake8-unused-arguments Ruff rule. 2025-07-22 15:39:30 +12:00
Justin Mayer
162d2b8318
Merge pull request #3477 from clockback/document-feed-domain-default 2025-07-21 20:25:08 +02:00
Ilya Simpson
595713b91a Fix default FEED_DOMAIN: None -> SITEURL.
This is similar to how `AUTHOR_REGEX_SUBSTITUTIONS` is described, for
instance.
2025-07-21 20:22:27 +02:00
Justin Mayer
7ef5eae639 Update feed functional tests for FeedGenerator 2.2 2025-07-21 20:14:15 +02:00
Justin Mayer
eb0d4deb01
Merge pull request #3488 from GeorgeHu6/chinese-translation 2025-07-13 13:06:21 +02:00
GeorgeHu6
f92b2a27ab Doc: update Chinese translation 2025-07-13 16:40:13 +08:00
Justin Mayer
95965459f2 docs: Fix linter errors with invoke lint --fix 2025-07-09 09:15:40 +02:00
Justin Mayer
3efb0817e3 Ignore Ruff 0.12 rule compliance in git blame 2025-07-08 08:13:44 +02:00
Justin Mayer
f4ee3b7946
Merge pull request #3483 from boxydog/ruff_0_12_2 2025-07-08 08:10:18 +02:00
Justin Mayer
939434b4ab
Merge pull request #3482 from getpelican/limit-dependabot 2025-07-07 08:25:47 +02:00
boxydog
4dedf17958 Move ruff to 0.12.2 and fix new complaints 2025-07-05 10:09:08 -05:00
Justin Mayer
a29857ac19
Merge pull request #3467 from nkr0/bump-pygments-version 2025-07-05 08:39:01 +02:00
Justin Mayer
bfd1068b82
Merge pull request #3474 from clockback/use-lists-not-tuples 2025-07-05 07:48:57 +02:00
Justin Mayer
0e358c611c
Merge pull request #3479 from clockback/fix-default-slug-regex-substitutions 2025-07-05 07:45:13 +02:00
Ilya Simpson
fca2fde2ed Change lists, not tuples, in config settings
In the documentation, both `SOCIAL` and `LINKS` are described as a list
of tuples, but all examples show them as tuples of tuples. It makes the
most sense for them to be lists, so the examples should match the docs
going forward.

Similarly, `LOCALE` is described as a list, but the examples show it as
a tuple. Likewise, the examples should be lists, in line with the
description.
2025-07-04 20:06:44 +12:00
Justin Mayer
ff4460c3d7 Limit Dependabot scope to GitHub Actions only
Sometimes we intentionally pin specific package versions -- such as for
Pygments, Jinja2, and Markdown -- and thus automated Dependabot PRs for
those packages are spurious and unwanted.
2025-07-01 09:31:01 +02:00
Ilya Simpson
b2ac0e93aa Fixing default SLUG_REGEX_SUBSTITUTIONS in docs.
Backslashes should not have been doubled, given the defaults are raw
strings.
2025-06-07 22:12:46 +12:00
Justin Mayer
9e3e1325c0
Merge pull request #3475 from clockback/enable-flake8-builtins 2025-06-02 15:11:00 +02:00
Ilya Simpson
f44ec52427 Enable flake8-builtins Ruff rule. 2025-06-02 17:22:50 +12:00
Justin Mayer
9f6cc9f0d7
Merge pull request #3473 from clockback/main 2025-05-30 09:42:26 +02:00
Ilya Simpson
ffe22e3c59 Fixing documented default for ARTICLE_SAVE_AS. 2025-05-29 22:29:33 +12:00
Justin Mayer
487486138f
Merge pull request #3470 from emmanuel-ferdman/main
fix: Resolve `datetime` warnings
2025-05-14 09:48:34 +02:00
Emmanuel Ferdman
07f32c1a09
fix: resolve datetime warnings
Signed-off-by: Emmanuel Ferdman <emmanuelferdman@gmail.com>
2025-05-13 06:40:14 -07:00
n
ca32b1b77c bump pygments version to <2.20.0 2025-05-10 12:41:57 +02:00
Justin Mayer
f9711fa10a
Merge pull request #3462 from Kristinita/KiraValidPathMetadataValue
docs: Use raw string for the `PATH_METADATA` setting
2025-04-19 12:28:16 +02:00
Kristinita
7fd66d8a95
docs: Use raw string for the PATH_METADATA setting 2025-04-19 11:00:42 +03:00
Al Sweigart
9c7749a298
docs: Move default values to fix settings anchor links (#3458)
* Fix anchor links for settings by moving default value text down.
* Fix typos in default values.

---------

Co-authored-by: Justin Mayer <entroP@gmail.com>
2025-04-12 12:38:30 +02:00
Justin Mayer
88a6f57940 Upgrade Beautiful Soup & adjust tests to conform 2025-04-11 21:13:41 +02:00
Justin Mayer
5338f4fac2
Merge pull request #3447 from ceyusa/update-docs
docs: Update install from sources using setuptools
2025-03-25 09:51:00 -07:00
Víctor Manuel Jáquez Leal
b71159a11e docs: Update install from sources using setuptools 2025-01-27 06:18:55 +01:00
botpub
69e24fa82f Release Pelican 4.11.0 2025-01-15 17:01:09 +00:00
Justin Mayer
ec95a2c855 Prepare release 2025-01-15 17:53:09 +01:00
Yashas Lokesh
543424aa41
fix: Fix auto-reload with globs in IGNORE_FILES (#3441)
The default `IGNORE_FILES` value of `'.*'` was being compiled to a regular expression and then passed into `watchfiles.DefaultFilter` to filter out files when auto-reload is enabled.

This commit compares the patterns from `IGNORE_FILES` directly with the filename to match the usage of `fnmatch` elsewhere in the codebase. The new filtering class will continue working as expected for custom `IGNORE_FILES` settings.
2025-01-15 17:40:27 +01:00
Vincent Cheng
5be013d9d2
Make build reproducible by reading envvar SOURCE_DATE_EPOCH if set (#3430)
Co-authored-by: Justin Mayer <entroP@gmail.com>
2025-01-15 17:36:52 +01:00
Justin Mayer
64be147463
Merge pull request #3405 from frederik-elwert/improve-simple-theme
Add more blocks to Simple theme's base template
2025-01-15 12:32:12 +01:00
Frederik Elwert
4fcc24ddfe Add test for simple theme and inheritance 2025-01-15 12:00:16 +01:00
Frederik Elwert
af3c2ed0cf Add block name in endblock 2025-01-15 11:58:05 +01:00
Frederik Elwert
d813c5148e Add more blocks to simple base template
This change makes it easier to create new themes by inheriting from the
simple theme. It allows customization of the whole body (while still
making use of the theme’s head), or individual parts of the body like
header, menu, or footer.
2025-01-15 11:58:05 +01:00
Alvin Mites
4878fc82a7
chore: Update link to re-directed example settings file (#3445) 2025-01-15 11:43:52 +01:00
Justin Mayer
8a1c55ed07 docs: Clarify namespace plugin loading order 2025-01-14 12:49:34 +01:00
David Lesieur
9207e1ff62
feat: Add setting to omit selected Typogrify filters. Fixes #3436 (#3439) 2025-01-14 12:48:39 +01:00
Justin Mayer
fa0af6d221
Merge pull request #3438 from davidlesieur/typogrify-test-ignore-tags
test:  Fix `test_typogrify_ignore_tags` due to Typogrify 2.1 changes
2025-01-14 12:41:17 +01:00
Justin Mayer
b3ef32bcf1 test: Require Typogrify 2.1+ to pass updated test 2025-01-14 12:35:17 +01:00
David Lesieur
b4fcb7f4e3 Remove obsolete comment regarding widont. 2025-01-14 12:30:06 +01:00
David Lesieur
7a4c89f64a Adjust test following changes in Typogrify.
Typogrify's 'widont' filter used to ignore the list of 'ignore_tags', but this got fixed in Typogrify.
2025-01-14 12:30:06 +01:00
Justin Mayer
74d76ca0da Pin Pygments due to indentation changes in 2.19 2025-01-14 12:26:35 +01:00
Justin Mayer
a17521b6f7
Merge pull request #3435 from hugovk/add-3.13 2024-12-22 11:45:12 +01:00
Hugo van Kemenade
5bb39c4f6f Replace deprecated logger.warn with logger.warning 2024-12-21 15:53:56 +02:00
Hugo van Kemenade
714a3d53a1 Drop support for EOL Python 3.8 2024-12-21 15:53:13 +02:00
Hugo van Kemenade
7d4adfce3f Add support for Python 3.13 2024-12-21 15:45:35 +02:00
botpub
07c7eacab9 Release Pelican 4.10.2
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
2024-11-27 19:53:23 +00:00
Scott Colby
d9652ef109
fix: SUMMARY_MAX_PARAGRAPHS not respected in some combinations with SUMMARY_MAX_LENGTH (#3427) 2024-11-27 20:51:03 +01:00
Justin Mayer
7096b0a168
Merge pull request #3424 from projectgus/settings/ignore_files 2024-11-27 20:37:49 +01:00
Justin Mayer
ac28ddb9bf
Merge pull request #3425 from mart-e/replacement-indicator-log-full 2024-11-27 20:30:00 +01:00
Martin
31538d1578 [IMP] add information in error message
Not always clear what was the issue with only the keyword
2024-11-11 14:54:48 +01:00
Angus Gratton
1edca55253 settings: Change the default IGNORE_FILES to all "hidden" files.
This is to avoid subtle behaviour that contributed to root cause of
https://github.com/pelican-plugins/sitemap/issues/36

Specifically: if installing Pelican into a local virtualenv with the pdm or uv
default name ".venv", then subdirectories of .venv will contain all of the test
.rst and .md files.

If you then run Pelican in that same root directory using the default PATH
value (".") then it will add those content files to the site.
2024-11-10 12:05:02 +11:00
Justin Mayer
882cd16e11
Merge pull request #3423 from GeorgeHu6/chinese-translation
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
Docs: Update Chinese translation
2024-11-08 10:57:37 +01:00
GeorgeHu6
60261b8c99 Doc: update Chinese translation 2024-11-07 16:31:32 +08:00
Justin Mayer
4ca1454293
Merge pull request #3421 from boxydog/precommit_update_202411
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
2024-11-03 20:57:55 +01:00
boxydog
075542721c pre-commit autoupdate and fix new issues pointed out by ruff 2024-11-03 13:32:32 -06:00
Noel Miller
0da2530d9b
De-couple build workflow from GitHub Pages publication (#3404)
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
2024-10-22 09:59:19 -07:00
Justin Mayer
31264498e1
Add FAQ entry about theme overrides (#3406)
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
2024-10-17 09:13:39 -07:00
Frederik Elwert
92050d90bc Add FAQ regarding theme overrides
Currently, the documentation refers to creating new themes a lot.
It is much less apparent how one can customize an existing theme by
overriding individual templates or adding new ones. This commit adds
an FAQ for this, and also mentions the mechanism in the FAQ on custom
templates.
2024-10-10 14:35:07 +02:00
Justin Mayer
b02abf0220 Improve GitHub issue templates
Some checks failed
build / Test - 3.10 - macos (push) Has been cancelled
build / Test - 3.11 - macos (push) Has been cancelled
build / Test - 3.12 - macos (push) Has been cancelled
build / Test - 3.10 - ubuntu (push) Has been cancelled
build / Test - 3.11 - ubuntu (push) Has been cancelled
build / Test - 3.12 - ubuntu (push) Has been cancelled
build / Test - 3.8 - ubuntu (push) Has been cancelled
build / Test - 3.9 - ubuntu (push) Has been cancelled
build / Test - 3.10 - windows (push) Has been cancelled
build / Test - 3.11 - windows (push) Has been cancelled
build / Test - 3.12 - windows (push) Has been cancelled
build / Lint (push) Has been cancelled
build / Test build (push) Has been cancelled
build / Build docs (push) Has been cancelled
build / Deploy (push) Has been cancelled
2024-10-04 15:06:11 +02:00
Justin Mayer
f5dc4d4b96 Disable blank GitHub issues
Existing issue template categories should cover most any case.
2024-10-04 15:04:13 +02:00
Justin Mayer
478012e0d0 Clarify _include_path() parameter docstring 2024-10-02 19:08:26 +02:00
175 changed files with 4383 additions and 2688 deletions

View file

@ -17,3 +17,5 @@ db241feaa445375dc05e189e69287000ffe5fa8e
4af40e80772a58eac8969360e5caeb99e3e26e78
# Ruff UP031: Use F-string format specifiers instead of percent format
30bde3823f50b9ba8ac5996c1c46bb72031aa6b8
# Upgrade Ruff to 0.12.x & comply with new rules
4dedf1795831db99d18941c707923ba48cc28ce7

View file

@ -17,11 +17,15 @@ assignees: ''
<!-- Checked checkbox should look like this: [x] -->
- [ ] I have read the [Filing Issues](https://docs.getpelican.com/en/latest/contribute.html#filing-issues) and subsequent “How to Get Help” sections of the documentation.
- [ ] I can reproduce this problem with stock/default settings file, theme, and sample content (as described in above “How to Get Help” sections of the documentation).
- [ ] I have searched the [issues](https://github.com/getpelican/pelican/issues?q=is%3Aissue) (including closed ones) and believe that this is not a duplicate.
<!--
Once the above boxes are checked, if you are able to fill in the following list
with your information, it would be very helpful for maintainers.
If you cannot reproduce the problem with stock/default settings file, theme, and sample content,
please close this tab and ask your question in the Discussions area instead:
<https://github.com/getpelican/pelican/discussions>
Otherwise, once the above boxes are checked, please fill out the following list
of information, which would be very helpful for maintainers.
-->
- **OS version and name**: <!-- Replace with version + name -->

View file

@ -8,7 +8,11 @@ assignees: ''
---
<!--
Describe your question/issue here. This space is meant to be used for general questions
Instead of a new issue, please consider submitting your question to:
<https://github.com/getpelican/pelican/discussions>
If for some reason you believe that your question warrants a new issue
instead of a discussion thread, describe your question/issue here.
This space is meant to be used for general questions
that are not bugs, feature requests, or documentation issues.
Before you submit this, lets make sure of a few things.
Please make sure the following boxes are ticked if they are correct.
@ -18,6 +22,7 @@ assignees: ''
<!-- Checked checkbox should look like this: [x] -->
- [ ] I have searched the [issues](https://github.com/getpelican/pelican/issues?q=is%3Aissue) (including closed ones) and believe that this is not a duplicate.
- [ ] I have searched the [documentation](https://docs.getpelican.com/) and believe that my question is not covered.
- [ ] I have carefully read the [How to Get Help](https://docs.getpelican.com/en/latest/contribute.html#how-to-get-help) section of the documentation.
## Issue
<!-- Now feel free to write your issue, but please be descriptive! Thanks again 🙌 ❤️ -->

View file

@ -1,6 +1,6 @@
---
# Ref: https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
blank_issues_enabled: true
blank_issues_enabled: false
contact_links:
- name: '💬 Pelican IRC Channel'
url: https://web.libera.chat/?#pelican

View file

@ -1,13 +1,8 @@
# See https://docs.github.com/en/free-pro-team@latest/
# github/administering-a-repository/enabling-and-disabling-version-updates
---
version: 2
updates:
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "monthly"
open-pull-requests-limit: 10
- package-ecosystem: "github-actions"
directory: "/"
schedule:

View file

@ -1,4 +1,4 @@
# Workflow for publishing to GitHub Pages.
# Workflow for building the site and (optionally) publishing it to GitHub Pages.
name: Deploy to GitHub Pages
on:
workflow_call:
@ -37,13 +37,15 @@ on:
default: ""
description: "The domain to be prepended to feed URLs (Pelican's FEED_DOMAIN setting). If not passed this will default to the URL of your GitHub Pages site, which is correct in most cases."
type: string
deploy:
required: false
default: true
description: "Whether to deploy the site. If true then build the site and deploy it. If false then just test that the site builds successfully but don't deploy anything."
type: boolean
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
@ -88,6 +90,10 @@ jobs:
with:
path: ${{ inputs.output-path }}
deploy:
concurrency:
group: "pages"
cancel-in-progress: false
if: ${{ inputs.deploy }}
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}

View file

@ -15,10 +15,8 @@ jobs:
strategy:
matrix:
os: [ubuntu, macos, windows]
python: ["3.10", "3.11", "3.12"]
python: ["3.10", "3.11", "3.12", "3.13"]
include:
- os: ubuntu
python: "3.8"
- os: ubuntu
python: "3.9"

View file

@ -2,7 +2,7 @@
# See https://pre-commit.com/hooks.html for info on hooks
repos:
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v4.6.0
rev: v5.0.0
hooks:
- id: check-added-large-files
- id: check-ast
@ -16,14 +16,14 @@ repos:
- repo: https://github.com/astral-sh/ruff-pre-commit
# ruff version should match the one in pyproject.toml
rev: v0.4.10
rev: v0.12.2
hooks:
- id: ruff
- id: ruff-check
args: [--fix, --exit-non-zero-on-fix]
- id: ruff-format
- repo: https://github.com/rtts/djhtml
rev: '3.0.6'
rev: '3.0.8'
hooks:
- id: djhtml
- id: djcss

View file

@ -1,6 +1,22 @@
Release history
###############
4.11.0 - 2025-01-15
===================
- Add setting to selectively omit Typogrify filters `(#3439) <https://github.com/getpelican/pelican/pull/3439>`_
- Add more blocks to the Simple themes base template, making it easier to create new themes by inheriting from the Simple theme `(#3405) <https://github.com/getpelican/pelican/pull/3405>`_
- Fix auto-reload behavior upon changes to the theme, content or settings. Make default ``IGNORE_FILES`` recursively ignore all hidden files as well as the `default filters <https://watchfiles.helpmanual.io/api/filters/#watchfiles.DefaultFilter.ignore_dirs>`_ from ``watchfiles.DefaultFilter``. `(#3441) <https://github.com/getpelican/pelican/pull/3441>`_
- Get current year from the ``SOURCE_DATE_EPOCH`` environment variable, if available `(#3430) <https://github.com/getpelican/pelican/pull/3430>`_
- Add Python 3.13 to test matrix and remove Python 3.8 `(#3435) <https://github.com/getpelican/pelican/pull/3435>`_
- Require Typogrify 2.1+ and Pygments <2.19
4.10.2 - 2024-11-27
===================
- Change ``IGNORE_FILES`` setting default to ignore all hidden files
- Fix ``SUMMARY_MAX_PARAGRAPHS`` not being respected in some combinations with ``SUMMARY_MAX_LENGTH``
4.10.1 - 2024-09-28
===================

View file

@ -1,6 +1,7 @@
import datetime
import os
import sys
import time
if sys.version_info >= (3, 11):
import tomllib
@ -30,15 +31,17 @@ extensions = [
source_suffix = ".rst"
master_doc = "index"
project = project_data.get("name").upper()
year = datetime.datetime.now().date().year
copyright = f"2010{year}" # noqa: RUF001
year = datetime.datetime.fromtimestamp(
int(os.environ.get("SOURCE_DATE_EPOCH", time.time())), datetime.timezone.utc
).year
project_copyright = f"2010{year}" # noqa: RUF001
exclude_patterns = ["_build"]
release = project_data.get("version")
version = ".".join(release.split(".")[:1])
last_stable = project_data.get("version")
rst_prolog = f"""
.. |last_stable| replace:: :pelican-doc:`{last_stable}`
.. |min_python| replace:: {project_data.get('requires-python').split(",")[0]}
.. |min_python| replace:: {project_data.get("requires-python").split(",")[0]}
"""
extlinks = {"pelican-doc": ("https://docs.getpelican.com/en/latest/%s.html", "%s")}

View file

@ -103,9 +103,14 @@ lines you changed conform to code style guidelines. You can check that via::
invoke lint
If style violations are found, many of them can be addressed automatically via::
invoke lint --fix
invoke format
If code style violations are found in lines you changed, correct those lines
and re-run the above lint command until they have all been fixed. You do not
need to address style violations, if any, for code lines you did not touch.
and re-run the ``invoke lint`` command until they have all been fixed. You do
not need to address style violations, if any, for code lines you did not touch.
After making your changes and running the tests, you may see a test failure
mentioning that "some generated files differ from the expected functional tests
@ -194,6 +199,7 @@ check for code style compliance via::
If style violations are found, many of them can be addressed automatically via::
invoke lint --fix
invoke format
If style violations are found even after running the above auto-formatters,

View file

@ -64,6 +64,19 @@ How do I create my own theme?
Please refer to :ref:`theming-pelican`.
Can I override individual templates without forking the whole theme?
====================================================================
Yes, you can override existing templates of the theme that you are using, or
add new templates, via the ``THEME_TEMPLATES_OVERRIDES`` variable. For example,
to override the page template, you can define the location for your templates
like this::
THEME_TEMPLATES_OVERRIDES = ["templates"]
You can then define a custom template in ``templates/page.html``.
See :ref:`settings/themes` for details.
I want to use Markdown, but I got an error.
===========================================
@ -105,7 +118,7 @@ How do I make my output folder structure identical to my content hierarchy?
Try these settings::
USE_FOLDER_AS_CATEGORY = False
PATH_METADATA = "(?P<path_no_ext>.*)\..*"
PATH_METADATA = r"(?P<path_no_ext>.*)\..*"
ARTICLE_URL = ARTICLE_SAVE_AS = PAGE_URL = PAGE_SAVE_AS = "{path_no_ext}.html"
How do I assign custom templates on a per-page basis?
@ -122,7 +135,8 @@ For content in Markdown format::
Template: template_name
Then just make sure your theme contains the relevant template file (e.g.
``template_name.html``).
``template_name.html``). If you just want to add a new custom template to an
existing theme, you can also provide it in a directory specified by ``THEME_TEMPLATES_OVERRIDES`` (see :ref:`settings/themes`).
How can I override the generated URL of a specific page or article?
===================================================================

View file

@ -25,10 +25,10 @@ session and create a new virtual environment for Pelican::
Once the virtual environment has been created and activated, Pelican can be
installed via ``python -m pip install pelican`` as noted above. Alternatively, if you
have the project source, you can install Pelican using the distutils method::
have the project source, you can install Pelican using the setuptools method::
cd path-to-Pelican-source
python setup.py install
python -m pip install .
If you have Git installed and prefer to install the latest bleeding-edge
version of Pelican rather than a stable release, use the following command::

File diff suppressed because it is too large Load diff

View file

@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PELICAN 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-25 20:36+0800\n"
"POT-Creation-Date: 2025-07-13 11:46+0800\n"
"PO-Revision-Date: 2024-06-27 19:00+0800\n"
"Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
"Language: zh_CN\n"
@ -16,93 +16,91 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.15.0\n"
"Generated-By: Babel 2.17.0\n"
#: ../../contribute.rst:2 e8f9694c47aa44e7944dae800ee528f3
#: ../../contribute.rst:2 848b6c0ec944440791d56b25e314a8ab
msgid "Contributing and feedback guidelines"
msgstr "项目贡献与意见反馈"
#: ../../contribute.rst:4 784f37182e78474b960306a5a794ae16
#: ../../contribute.rst:4 e8b8762778fd461db0934f07e4fc1fc5
msgid ""
"There are many ways to contribute to Pelican. You can improve the "
"documentation, add missing features, and fix bugs (or just report them). "
"You can also help out by reviewing and commenting on `existing issues "
"<https://github.com/getpelican/pelican/issues>`_."
msgstr ""
"有很多渠道可以参与到贡献项目中来例如帮助改进文档、添加缺失的特性、修复与报告bug。"
"可以从查看 `已有 issues <https://github.com/getpelican/pelican/issues>`_ 开始。"
"有很多渠道可以参与到贡献项目中来例如帮助改进文档、添加缺失的特性、修复与报告bug。可以从查看 `已有 issues "
"<https://github.com/getpelican/pelican/issues>`_ 开始。"
#: ../../contribute.rst:9 e17c3ff0fa71469cbe22cb4ad2640ad8
#: ../../contribute.rst:9 103b2f2862c4469695e4c6aff2321a8d
msgid ""
"Don't hesitate to fork Pelican and submit an issue or pull request on "
"GitHub. When doing so, please consider the following guidelines."
msgstr ""
"随时随地都可以fork Pelican或是在GitHub上提交issue或PR。"
msgstr "随时随地都可以fork Pelican或是在GitHub上提交issue或PR。"
#: ../../../CONTRIBUTING.rst:2 f8bc69070fab4dd7be34e1cc6a42cc02
#: ../../../CONTRIBUTING.rst:2 5ad44a6fdf0b45eaaa800023139694f8
msgid "Filing issues"
msgstr "提出issue"
#: ../../../CONTRIBUTING.rst:4 fe98a059b9c24fcc92358f2c4505174d
#: ../../../CONTRIBUTING.rst:4 c7e2bb966f49419aba7ed7027a977043
msgid "Before you submit a new issue, try `asking for help`_ first."
msgstr "在你提交一个新的issue之前可以先尝试 `请求他人帮助`_ 。"
#: ../../../CONTRIBUTING.rst:5 e9fff7c354614ae28db994c0fcc121c0
#: ../../../CONTRIBUTING.rst:5 a287bb06699b4db79d6dd7491bbe031b
msgid ""
"If determined to create a new issue, first search `Pelican Discussions`_ "
"and `existing issues`_ (open and closed) to see if your question has "
"already been answered previously."
msgstr ""
"当你决定要提出新的issue时先在 `Pelican的讨论版`_ 和 `已有issues`_ 中搜索一下,"
"开放关闭的issue都搜一下来看看你的问题是不是有人之前已经提出过。"
"当你决定要提出新的issue时先在 `Pelican的讨论版`_ 和 `已有issues`_ "
"中搜索一下,开放关闭的issue都搜一下来看看你的问题是不是有人之前已经提出过。"
#: ../../../CONTRIBUTING.rst:14 84cb74beed564f31810674cacf5c1f97
#: ../../../CONTRIBUTING.rst:14 d4a600f2338b458e822aba90e54d4cfd
msgid "How to get help"
msgstr "如何获取帮助"
#: ../../../CONTRIBUTING.rst:16 0557a84947c14606be4fd0565247d85d
#: ../../../CONTRIBUTING.rst:16 db3264afde384c2891d9be7205578556
msgid "Before you ask for help, please make sure you do the following:"
msgstr "在寻求帮助之前,请先尝试如下步骤:"
#: ../../../CONTRIBUTING.rst:18 6d59a3356e734dd196ec8a0739556b4c
#: ../../../CONTRIBUTING.rst:18 3581147764244a548cd2898faaa7799a
msgid ""
"Read the documentation_ thoroughly. If in a hurry, at least use the "
"search field that is provided at top-left on the documentation_ pages. "
"Make sure you read the docs for the Pelican version you are using."
msgstr ""
"完整阅读 documentation_ 。如果你很急,至少先在 documentation_ 左上角的搜索栏"
"中尝试搜索。确保你阅读的文档和使用的Pelican版本相匹配。"
"完整阅读 documentation_ 。如果你很急,至少先在 documentation_ "
"左上角的搜索栏中尝试搜索。确保你阅读的文档和使用的Pelican版本相匹配。"
#: ../../../CONTRIBUTING.rst:21 4b33299936404cf98a66b672fad0e38f
#: ../../../CONTRIBUTING.rst:21 d8e467909ec64ba7900da93b3765bfa6
msgid ""
"Use a search engine (e.g., DuckDuckGo, Google) to search for a solution "
"to your problem. Someone may have already found a solution, perhaps in "
"the form of a ':pelican-doc:`plugins` or a specific combination of "
"settings."
msgstr ""
"使用搜索引擎(例如 DuckDuckGo、Google搜索遇到问题的解决方案。互联网上可能"
"已经有人遇到过相同的问题,解决方法可能包括使用某些 :pelican-doc:`plugins` 或配置"
"一系列的设置选项。"
"使用搜索引擎(例如 DuckDuckGo、Google搜索遇到问题的解决方案。互联网上可能已经有人遇到过相同的问题解决方法可能包括使用某些 "
":pelican-doc:`plugins` 或配置一系列的设置选项。"
#: ../../../CONTRIBUTING.rst:25 b48195d9ef674566b89aabc38139c301
#: ../../../CONTRIBUTING.rst:25 2011839b36504c41b307cc9f817c4a46
msgid "Try reproducing the issue in a clean environment, ensuring you are using:"
msgstr "尝试在一个尽可能简单的环境中重现问题,并确保以下几点:"
#: ../../../CONTRIBUTING.rst:27 685d2888d2c94ea9a752ec433f8b9f1f
#: ../../../CONTRIBUTING.rst:27 2d64217ea3e54dc58a371fc11a6ece8e
msgid ""
"latest Pelican release (or an up-to-date Git clone of Pelican ``main`` "
"branch)"
msgstr "使用最新版本的Pelican或是用Git克隆Pelican的main分支"
#: ../../../CONTRIBUTING.rst:28 910a372d95d8448492eafc66eccd1ccf
#: ../../../CONTRIBUTING.rst:28 721ca09c5a9a495b9fbb6aa86df8be28
msgid "latest releases of libraries used by Pelican"
msgstr "将Pelican使用的库升级到最新版本"
#: ../../../CONTRIBUTING.rst:29 c44f4dc6b05d4be29eccc889f042702c
#: ../../../CONTRIBUTING.rst:29 bbe722bd2be748219d38c134f29569dd
msgid "no plugins or only those related to the issue"
msgstr "此环境中没有使用插件或是只使用和问题相关的插件"
#: ../../../CONTRIBUTING.rst:31 3abdf6131cf4412a8205b634a6651b01
#: ../../../CONTRIBUTING.rst:31 e9f337f01ca546be93bd1d18884a1685
msgid ""
"**NOTE:** The most common sources of problems are anomalies in (1) "
"themes, (2) plugins, (3) settings files, and (4) ``make``/``invoke`` "
@ -111,93 +109,84 @@ msgid ""
"certainly with one of the above-listed elements (and not Pelican "
"itself)::"
msgstr ""
"**注意:** 最常见的问题基本上都产生于主题、插件、设置文件和自动化工具 "
"``make``/``invoke`` 中。如果按照下述步骤生成站点后无法复现之前的问题,那么"
"几乎可以肯定问题出在这四个地方而不在Pelican本身"
"**注意:** 最常见的问题基本上都产生于主题、插件、设置文件和自动化工具 ``make``/``invoke`` "
"中。如果按照下述步骤生成站点后无法复现之前的问题那么几乎可以肯定问题出在这四个地方而不在Pelican本身"
#: ../../../CONTRIBUTING.rst:41 f2331ea165ac4a3c8e70bf98c995f0e8
#: ../../../CONTRIBUTING.rst:41 1420bb3dd096480289b3da1534d7bf64
msgid ""
"If you can generate your site without problems using the steps above, "
"then your problem is unlikely to be caused by Pelican itself, and "
"therefore please consider reaching out to the maintainers of the "
"plugins/theme you are using instead of raising the topic with the Pelican"
" core community."
msgstr ""
"如果按照上述步骤能够正常生成站点那么你的问题不太可能是由Pelican本身导致的"
"请考虑联系对应插件/主题的维护者而不是在Pelican内核的社区中提出问题。"
msgstr "如果按照上述步骤能够正常生成站点那么你的问题不太可能是由Pelican本身导致的请考虑联系对应插件/主题的维护者而不是在Pelican内核的社区中提出问题。"
#: ../../../CONTRIBUTING.rst:46 d83b0036d4894f3ebc73e657a203d11a
#: ../../../CONTRIBUTING.rst:46 bdb7575fa4c74c0891fd686794cc84fd
msgid ""
"If despite the above efforts you still cannot resolve your problem, be "
"sure to include in your inquiry the following information, preferably in "
"the form of links to content uploaded to a `paste service`_, GitHub "
"repository, or other publicly-accessible location:"
msgstr ""
"经过上面这些努力,若您仍无法解决问题,确保你的提问中包括如下信息,可以以 "
"`paste service`_ 链接、GitHub仓库或者其他可公开获取的形式提供"
"经过上面这些努力,若您仍无法解决问题,确保你的提问中包括如下信息,可以以 `paste service`_ "
"链接、GitHub仓库或者其他可公开获取的形式提供"
#: ../../../CONTRIBUTING.rst:51 4281f931e9064336b267bd67a35134e9
#: ../../../CONTRIBUTING.rst:51 b559dc6ca72649baa754cb14d1ac77ca
msgid ""
"Describe what version of Pelican you are running (output of ``pelican "
"--version`` or the HEAD commit hash if you cloned the repo) and how "
"exactly you installed it (the full command you used, e.g. ``python -m pip"
" install pelican``)."
msgstr ""
"描述正在运行的Pelican版本信息可以通过 ``pelican --version`` 命令得到,如果"
"clone的源仓库则可以查看HEAD commit的哈希值以及你是如何安装Pelican的"
"(要包括使用到的命令,例如 ``python -m pip install pelican``"
"描述正在运行的Pelican版本信息可以通过 ``pelican --version`` 命令得到,如果clone的源仓库则可以查看HEAD "
"commit的哈希值以及你是如何安装Pelican的(要包括使用到的命令,例如 ``python -m pip install "
"pelican``"
#: ../../../CONTRIBUTING.rst:54 b1303c98bca840efb895aceb16789eb9
#: ../../../CONTRIBUTING.rst:54 d09a0393a4c1462b878c1adf31a7537d
msgid ""
"If you are looking for a way to get some end result, prepare a detailed "
"description of what the end result should look like (preferably in the "
"form of an image or a mock-up page) and explain in detail what you have "
"done so far to achieve it."
msgstr ""
"如果你希望产生某种特定的最终结果,请详细描述此最终结果是什么样的(最好以图片或者"
"伪页面的形式),,并且细致讲述你做了哪些尝试。"
msgstr "如果你希望产生某种特定的最终结果,请详细描述此最终结果是什么样的(最好以图片或者伪页面的形式),,并且细致讲述你做了哪些尝试。"
#: ../../../CONTRIBUTING.rst:58 8fe972c4685140d5bd1c37f4635f6f09
#: ../../../CONTRIBUTING.rst:58 720ee9dbccc74dccbabb994a2d36638d
msgid ""
"If you are trying to solve some issue, prepare a detailed description of "
"how to reproduce the problem. If the issue cannot be easily reproduced, "
"it cannot be debugged by developers or volunteers. Describe only the "
"**minimum steps** necessary to reproduce it (no extra plugins, etc.)."
msgstr ""
"如果你在尝试解决某些问题,请详细描述如何复现此问题。如果问题很难被复现,其他开发者和志愿者就很难进行调试。"
"尽量只写出复现该问题的 **最少步骤** (无额外插件)。"
"如果你在尝试解决某些问题,请详细描述如何复现此问题。如果问题很难被复现,其他开发者和志愿者就很难进行调试。尽量只写出复现该问题的 **最少步骤**"
" (无额外插件)。"
#: ../../../CONTRIBUTING.rst:62 1f3874f308e64281b910dc716180ebcf
#: ../../../CONTRIBUTING.rst:62 34bdc49c617643d8ae7adb6a433a88fe
msgid ""
"Upload your settings file or any other custom code that would enable "
"people to reproduce the problem or to see what you have already tried to "
"achieve the desired end result."
msgstr ""
"上传你的配置文件以及所有自定义过的代码,这可以使得大家能够重现问题或者看到你已经"
"做出的尝试。"
msgstr "上传你的配置文件以及所有自定义过的代码,这可以使得大家能够重现问题或者看到你已经做出的尝试。"
#: ../../../CONTRIBUTING.rst:65 1fdc6c63f1b141c7a35233607ec0d922
#: ../../../CONTRIBUTING.rst:65 03c88e23c7b54117aa69e003c8bbef6e
msgid ""
"Upload detailed and **complete** output logs and backtraces (remember to "
"add the ``--debug`` flag: ``pelican --debug content [...]``)"
msgstr ""
"上传详细 **完整** 的输出日志以及backtraces信息记得在执行pelican命令时加上 "
"``--debug`` 标记: ``pelican --debug content [...]`` "
"上传详细 **完整** 的输出日志以及backtraces信息记得在执行pelican命令时加上 ``--debug`` 标记: "
"``pelican --debug content [...]`` "
#: ../../../CONTRIBUTING.rst:71 8741dba5da1a4990ae9c30531d05dc19
#: ../../../CONTRIBUTING.rst:71 953240a12cd64be7b9375a4571193314
msgid ""
"Once the above preparation is ready, you can post your query as a new "
"thread in `Pelican Discussions`_. Remember to include all the information"
" you prepared."
msgstr ""
"一旦做好了上述准备,就可以在 `Pelican Discussions`_ 中发起你的问题了。记得在请求"
"中附上收集好的信息。"
msgstr "一旦做好了上述准备,就可以在 `Pelican Discussions`_ 中发起你的问题了。记得在请求中附上收集好的信息。"
#: ../../../CONTRIBUTING.rst:75 b34a3031f5d1427e92a9d1969d7b5274
#: ../../../CONTRIBUTING.rst:75 e9f48bdfc6c744f282c70da3ac581052
msgid "Contributing code"
msgstr "贡献代码"
#: ../../../CONTRIBUTING.rst:77 e29672c736554ebbbd6efd441af19df7
#: ../../../CONTRIBUTING.rst:77 888be6bde2de42a49705f29443a519c1
msgid ""
"Before you submit a contribution, please ask whether it is desired so "
"that you don't spend a lot of time working on something that would be "
@ -205,32 +194,28 @@ msgid ""
" be better suited as a ':pelican-doc:`plugins` — you can `ask for help`_"
" to make that determination."
msgstr ""
"在提交代码修改前,请先询问是否需要此修改,以免你做的工作因为已知原因而被拒绝。"
"想想要添加的新特性是否更适合以 :pelican-doc:`插件` 形式完成。可以通过 "
"`如何获取帮助`_ 来帮助你作出决定。"
"在提交代码修改前,请先询问是否需要此修改,以免你做的工作因为已知原因而被拒绝。想想要添加的新特性是否更适合以 :pelican-doc:`插件` "
"形式完成。可以通过 `如何获取帮助`_ 来帮助你作出决定。"
#: ../../../CONTRIBUTING.rst:82 e263c09fb6e5471eb0c2c3e97994322d
#: ../../../CONTRIBUTING.rst:82 6e1329bbd8354c30b8ffa07f18894d3f
msgid ""
"Also, if you intend to submit a pull request to address something for "
"which there is no existing issue, there is no need to create a new issue "
"and then immediately submit a pull request that closes it. You can submit"
" the pull request by itself."
msgstr ""
"另外如果你的PR是为了解决一个目前没有在issue中出现过的问题那么就没有必要先创建"
"一个新的issue而是可以直接提起PR。"
msgstr "另外如果你的PR是为了解决一个目前没有在issue中出现过的问题那么就没有必要先创建一个新的issue而是可以直接提起PR。"
#: ../../../CONTRIBUTING.rst:87 9b08ef3e5fe4474e9306e4bfe9662fff
#: ../../../CONTRIBUTING.rst:87 bca476812a33487c98d6aa840820671b
msgid "Using Git and GitHub"
msgstr "使用Git与GitHub"
#: ../../../CONTRIBUTING.rst:89 7ad95f82b7d04c0ca97bb958d2425e27
#: ../../../CONTRIBUTING.rst:89 51f8df6063a544baabf35ef3bae28e83
msgid ""
"`Create a new branch`_ specific to your change (as opposed to making your"
" commits in the ``main`` branch)."
msgstr ""
"`创建一个新的分支`_ 来标记你做的修改(而不是直接在主分支中提交)。"
msgstr "`创建一个新的分支`_ 来标记你做的修改(而不是直接在主分支中提交)。"
#: ../../../CONTRIBUTING.rst:91 8a31c5d7ae4045cdbf2aa67e79be3f9c
#: ../../../CONTRIBUTING.rst:91 6c419972402444d5976574902311e2d7
msgid ""
"**Don't put multiple unrelated fixes/features in the same branch / pull "
"request.** For example, if you're working on a new feature and find a "
@ -239,27 +224,25 @@ msgid ""
" to code style formatting should be in a completely separate pull "
"request."
msgstr ""
"**不要把多个无关联的修复/特性修改放在同一个分支/拉去请求中。** 如果当你在做新特性的时候"
"发现了一个bug可以修复但修复这个bug *不需要用到* 这个新特性, **那么请另外创建"
"一个分支并拉取请求。** 类似的,任何对代码风格的格式化都应该在单独的请求中拉取。"
"**不要把多个无关联的修复/特性修改放在同一个分支/拉去请求中。** 如果当你在做新特性的时候发现了一个bug可以修复但修复这个bug "
"*不需要用到* 这个新特性, **那么请另外创建一个分支并拉取请求。** 类似的,任何对代码风格的格式化都应该在单独的请求中拉取。"
#: ../../../CONTRIBUTING.rst:96 ef2e10f7ec5e4fbbb0f977dd09b7be49
#: ../../../CONTRIBUTING.rst:96 ced35621749d426a8e39fdeb9b0f7c90
msgid ""
"Add a ``RELEASE.md`` file in the root of the project that contains the "
"release type (major, minor, patch) and a summary of the changes that will"
" be used as the release changelog entry. For example::"
msgstr ""
"在项目根目录下添加 ``RELEASE.md`` 文件在其中包含release的类型主要、次要、补丁"
"以及对项目改变的概述这些内容会作为该release发布日志的一部分。下面是一个例子"
"在项目根目录下添加 ``RELEASE.md`` "
"文件在其中包含release的类型主要、次要、补丁以及对项目改变的概述这些内容会作为该release发布日志的一部分。下面是一个例子"
#: ../../../CONTRIBUTING.rst:104 24a4d63624f44f63a0ce809901455c02
#: ../../../CONTRIBUTING.rst:104 ca6b2bf54f5248cbb7d90edb678478fc
msgid ""
"Check for unnecessary whitespace via ``git diff --check`` before "
"committing."
msgstr ""
"在提交前使用 ``git diff --check`` 来检查是否有无意义的空白字符。"
msgstr "在提交前使用 ``git diff --check`` 来检查是否有无意义的空白字符。"
#: ../../../CONTRIBUTING.rst:105 11c5b82604fe4638bf9ee6e9ef0a401b
#: ../../../CONTRIBUTING.rst:105 48776b48e4924398b7632b8f05141e78
msgid ""
"First line of your commit message should start with present-tense verb, "
"be 50 characters or less, and include the relevant issue number(s) if "
@ -268,82 +251,73 @@ msgid ""
"``Fixes #585`` or ``Fix #585`` syntax (so the relevant issue is "
"automatically closed upon PR merge)."
msgstr ""
"commit信息的第一行应该以现在时动词开头并且第一行尽量保持在50字以下并且包含相关联"
"issue的编号如果有的话。 例如: ``Ensure proper PLUGIN_PATH behavior. "
"Refs #428.`` 如果此项提交 *完全修复* 了某项已报告的bug请使用例如 ``Fixes #585`` "
"或 ``Fix #585`` 的语法这样的话相关的issue会在PR合并后自动关闭。"
"commit信息的第一行应该以现在时动词开头并且第一行尽量保持在50字以下并且包含相关联issue的编号如果有的话。 例如: "
"``Ensure proper PLUGIN_PATH behavior. Refs #428.`` 如果此项提交 *完全修复* "
"了某项已报告的bug请使用例如 ``Fixes #585`` 或 ``Fix #585`` "
"的语法这样的话相关的issue会在PR合并后自动关闭。"
#: ../../../CONTRIBUTING.rst:110 0c1ff9d0738440e1bce853fc830278af
#: ../../../CONTRIBUTING.rst:110 75acb68d9eaa4230ae230f016bf77b6c
msgid ""
"After the first line of the commit message, add a blank line and then a "
"more detailed explanation (when relevant)."
msgstr ""
"在第一行commit信息后添加一行空白行再进行更多相关的细节描述。"
msgstr "在第一行commit信息后添加一行空白行再进行更多相关的细节描述。"
#: ../../../CONTRIBUTING.rst:112 d817ad5d9e35488eb45d88828ee9f053
#: ../../../CONTRIBUTING.rst:112 51e3a16f76364d91a9abf219c731ff80
msgid ""
"`Squash your commits`_ to eliminate merge commits and ensure a clean and "
"readable commit history."
msgstr ""
"`压缩commit`_ 来消除合并commits确保你的commit历史记录是干净可读的。"
msgstr "`压缩commit`_ 来消除合并commits确保你的commit历史记录是干净可读的。"
#: ../../../CONTRIBUTING.rst:114 b7064f44923a499da3c3ce078470e269
#: ../../../CONTRIBUTING.rst:114 01ddd9df01024d38a8de79122a91cc07
msgid ""
"After you have issued a pull request, the continuous integration (CI) "
"system will run the test suite on all supported Python versions and check"
" for code style compliance. If any of these checks fail, you should fix "
"them. (If tests fail on the CI system but seem to pass locally, ensure "
"that local test runs aren't skipping any tests.)"
msgstr ""
"在你发出PR后持续集成CI系统会在所有支持的Python版本上运行测试套件并且"
"检查代码风格的合规性。如果出现了错误你应该将其修复。如果没有通过CI系统上的"
"测试但是本地测试通过了请再检查一下确保在本地进行了所有CI系统中的检查"
msgstr "在你发出PR后持续集成CI系统会在所有支持的Python版本上运行测试套件并且检查代码风格的合规性。如果出现了错误你应该将其修复。如果没有通过CI系统上的测试但是本地测试通过了请再检查一下确保在本地进行了所有CI系统中的检查"
#: ../../../CONTRIBUTING.rst:121 342f2e6c14b9441caaf3f9b6d2eb764b
#: ../../../CONTRIBUTING.rst:121 bc27587df397410a9bb272f0851756a3
msgid "Contribution quality standards"
msgstr "贡献的质量标准"
#: ../../../CONTRIBUTING.rst:123 842514f115634a5d821d48490d4aed7b
#: ../../../CONTRIBUTING.rst:123 2cf100b3e98b43e5b841493887a1d8be
msgid ""
"Adhere to the project's code style standards. See: `Development "
"Environment`_"
msgstr ""
"遵循项目的代码风格标准。详见 `开发环境`_"
msgstr "遵循项目的代码风格标准。详见 `开发环境`_"
#: ../../../CONTRIBUTING.rst:124 4719590d89be4a5e94817902cc424be5
#: ../../../CONTRIBUTING.rst:124 fffad000d6ca490291bd09cb18fcc75a
msgid ""
"Ensure your code is compatible with the `officially-supported Python "
"releases`_."
msgstr ""
"确保你的代码可以兼容 `python的官方发布版本`_"
msgstr "确保你的代码可以兼容 `python的官方发布版本`_"
#: ../../../CONTRIBUTING.rst:125 fa0ad5dd93e149fa8a12dd339bef9056
#: ../../../CONTRIBUTING.rst:125 907e4426cbc643fb9075e32be169ba42
msgid ""
"Add docs and tests for your changes. Undocumented and untested features "
"will not be accepted."
msgstr ""
"请为你修改的内容添加文档与测试。未注有文档或没有对应测试的特性会被拒绝。"
msgstr "请为你修改的内容添加文档与测试。未注有文档或没有对应测试的特性会被拒绝。"
#: ../../../CONTRIBUTING.rst:127 dc4db53c2ce34e5490a0c57ea800a4da
#: ../../../CONTRIBUTING.rst:127 d2bcbeeb9c0541c2a5ac5ec589a16ca4
msgid ""
":pelican-doc:`Run all the tests <contribute>` **on all versions of Python"
" supported by Pelican** to ensure nothing was accidentally broken."
msgstr ""
"**在Pelican支持的所有Python版本上** :pelican-doc:`执行所有测试 <contribute>` "
"以确保没有意料之外的问题。"
"**在Pelican支持的所有Python版本上** :pelican-doc:`执行所有测试 <contribute>` "
"以确保没有意料之外的问题。"
#: ../../../CONTRIBUTING.rst:130 3a88c2e8326a4acd896d0ac75d4c9ccb
#: ../../../CONTRIBUTING.rst:130 26daa76aea674039be278882a95422f5
msgid ""
"Check out our `Git Tips`_ page or `ask for help`_ if you need assistance "
"or have any questions about these guidelines."
msgstr ""
"若需要帮助或对以上指南有任何疑惑,还可以查看我们的 `Git提示`_ 页面和 `请求帮助`_ 部分。"
msgstr "若需要帮助或对以上指南有任何疑惑,还可以查看我们的 `Git提示`_ 页面和 `请求帮助`_ 部分。"
#: ../../contribute.rst:15 daead9e8fb804eb6acd152b85d837182
#: ../../contribute.rst:15 b4a94275e9c14d8795fa54473ee2f05b
msgid "Setting up the development environment"
msgstr "配置开发环境"
#: ../../contribute.rst:17 1ab6df98bcb141f49e278d153cc96e22
#: ../../contribute.rst:17 a0eb6948883742d2a00665a576ef6aba
msgid ""
"While there are many ways to set up one's development environment, the "
"following instructions will utilize Pip_ and PDM_. These tools facilitate"
@ -351,71 +325,67 @@ msgid ""
"isolated from one another, so you can use different packages (and package"
" versions) for each."
msgstr ""
"在配置开发环境时往往有很多种方式,但下面的指南会使用 Pip_ 和 PDM_ 完成配置。这两个工具"
"都可以用于管理虚拟环境使得不同的Python项目相互隔离这样就可以很方便的在不同的项目中"
"使用不同的库(以及不同的库版本)。"
"在配置开发环境时往往有很多种方式,但下面的指南会使用 Pip_ 和 PDM_ "
"完成配置。这两个工具都可以用于管理虚拟环境使得不同的Python项目相互隔离这样就可以很方便的在不同的项目中使用不同的库以及不同的库版本。"
#: ../../contribute.rst:22 6a9c8f6ddb1d495f8a9bd1b8a131cabd
#: ../../contribute.rst:22 4c5c4d91e6964d709d01102e32310642
msgid "Please note that Python |min_python| is required for Pelican development."
msgstr "请注意要进行Pelican的开发至少需要Python |min_python|"
#: ../../contribute.rst:24 3d994e2a522141d7ada0a8fe13eb4c64
#: ../../contribute.rst:24 5419157e28984a618fc1f0df81deb620
msgid ""
"*(Optional)* If you prefer to `install PDM "
"<https://pdm.fming.dev/latest/#installation>`_ once for use with multiple"
" projects, you can install it via::"
msgstr ""
"*(可选)* 若您想要 `安装PDM <https://pdm.fming.dev/latest/#installation>`_ "
"可以使用下面这条命令:"
"*(可选)* 若您想要 `安装PDM <https://pdm.fming.dev/latest/#installation>`_ "
"可以使用下面这条命令:"
#: ../../contribute.rst:29 dbaa532c292048cb87926dd8b6e3141a
#: ../../contribute.rst:29 a9d08dc294cb4857a58d2c63eae98a15
msgid ""
"Point your web browser to the `Pelican repository`_ and tap the **Fork** "
"button at top-right. Then clone the source for your fork and add the "
"upstream project as a Git remote::"
msgstr ""
"在Web浏览器中进入 `Pelican的代码仓库`_ ,点击右上角的 **Fork** 按钮。然后克隆"
"你自己的这份fork最后添加项目的原仓库为远程仓库upstream"
"在Web浏览器中进入 `Pelican的代码仓库`_ ,点击右上角的 **Fork** "
"按钮。然后克隆你自己的这份fork最后添加项目的原仓库为远程仓库upstream"
#: ../../contribute.rst:38 adbe5d876f114645a3e1b489b2a34bd9
#: ../../contribute.rst:38 4c8ebbf9839441ca9364eeb1d25b180f
msgid ""
"While PDM can dynamically create and manage virtual environments, we're "
"going to manually create and activate a virtual environment::"
msgstr ""
"通过下面的命令可以手动创建并激活一个虚拟环境:"
msgstr "通过下面的命令可以手动创建并激活一个虚拟环境:"
#: ../../contribute.rst:45 ../../contribute.rst:181
#: 6ede38ac05174bc19df4198e735342e0 f6d42cdd70384eaebbe115aefd0d01ec
#: ../../contribute.rst:45 ../../contribute.rst:186
#: 2afe046c20814fe5b3de9a65606505f1 6ec60e6a37b642edb68af7ed1bc82c0b
msgid "Install the needed dependencies and set up the project::"
msgstr "安装必需的依赖并配置项目:"
#: ../../contribute.rst:50 d863bf4dc76e4b18b933f2635a6a3af3
#: ../../contribute.rst:50 59d5dabaab1d409c8873187e5664fe67
msgid "Your local environment should now be ready to go!"
msgstr "现在,你的本地开发环境就配置完成了!"
#: ../../contribute.rst:57 dc19edf71c914f48a953b379efa076c0
#: ../../contribute.rst:57 6fdce76f8ec64275b24366ff03cc6340
msgid "Development"
msgstr "开发"
#: ../../contribute.rst:59 6082eb5afbf14f86a031ed4f53d2943c
#: ../../contribute.rst:59 1d1a814a5dba40bcb84ce824d6312805
msgid ""
"Once Pelican has been set up for local development, create a topic branch"
" for your bug fix or feature::"
msgstr ""
"在配置好Pelican的本地开发环境后请先为你的bug修复或特性增加创建一个分支"
msgstr "在配置好Pelican的本地开发环境后请先为你的bug修复或特性增加创建一个分支"
#: ../../contribute.rst:64 1cafbaea6ec04597b62e871c0f0793b2
#: ../../contribute.rst:64 773cdd3a48894e11a62cb24b25ef4829
msgid ""
"Now you can make changes to Pelican, its documentation, and/or other "
"aspects of the project."
msgstr ""
"在切换到新建的分支后就可以开始对Pelican的文档或其他内容做更改了。"
msgstr "在切换到新建的分支后就可以开始对Pelican的文档或其他内容做更改了。"
#: ../../contribute.rst:68 e0f5da1e216f499d86427e21c23557d4
#: ../../contribute.rst:68 bb120553218b4d0699998fbaf00d32c0
msgid "Setting up ``git blame`` (optional)"
msgstr "配置 ``git blame`` (可选)"
#: ../../contribute.rst:70 2906e116c2dc4a2c8db78fa64820af56
#: ../../contribute.rst:70 644fae63e5ea4e66a24e35a7ada3524c
msgid ""
"``git blame`` annotates lines in a file with information about the pull "
"request that last modified it. Sweeping shallow changes (like formatting)"
@ -424,61 +394,59 @@ msgid ""
"repository, adding ``--global`` if you want this setting to apply to all "
"repositories::"
msgstr ""
"``git blame`` 会在文件中的行上标注有关最后一次修改该行的PR信息。对浅层变化如格式化"
"进行批量更改可能会使这些信息变得不那么有用,因此我们维护一个包含此类更改的列表,"
"以便忽略它们。运行以下命令在您的存储库中设置此配置,如果希望此设置适用于所有存储库,"
"请添加 ``--global`` "
"``git blame`` "
"会在文件中的行上标注有关最后一次修改该行的PR信息。对浅层变化如格式化进行批量更改可能会使这些信息变得不那么有用因此我们维护一个包含此类更改的列表以便忽略它们。运行以下命令在您的存储库中设置此配置如果希望此设置适用于所有存储库请添加"
" ``--global`` "
#: ../../contribute.rst:78 36f257406a294713835841cf549e0f67
#: ../../contribute.rst:78 68b7031047e94e03b0e1b0ea39d0355e
msgid ""
"As noted in a `useful article`_ about ``git blame``, there are other "
"related settings you may find to be beneficial::"
msgstr ""
"就像在 `这篇文章`_ 中提到的,还可以进行一些可能有用的额外设置:"
msgstr "就像在 `这篇文章`_ 中提到的,还可以进行一些可能有用的额外设置:"
#: ../../contribute.rst:89 37a3a813eeb84f408546bf6a83fdafd6
#: ../../contribute.rst:89 c33fd6178fb044dda7073f1fc2cce979
msgid "Running the test suite"
msgstr "运行测试套件"
#: ../../contribute.rst:91 44276ab045104e5c9ab3d2425172d7ac
#: ../../contribute.rst:91 5b51e49bc1ca42c6916c4dceed476057
msgid ""
"Each time you make changes to Pelican, there are two things to do "
"regarding tests: check that the existing tests pass, and add tests for "
"any new features or bug fixes. The tests are located in "
"``pelican/tests``, and you can run them via::"
msgstr ""
"每次对Pelican做出修改后在测试方面需要做两个工作检查是否能通过已有的测试、"
"为新增特性或bug修复创建测试。请将自动化测试文件放在 ``pelican/tests`` 中,"
"接着执行以下命令:"
"每次对Pelican做出修改后在测试方面需要做两个工作检查是否能通过已有的测试、为新增特性或bug修复创建测试。请将自动化测试文件放在 "
"``pelican/tests`` 中,接着执行以下命令:"
#: ../../contribute.rst:98 9557eb87ac4945ccbaf8775aa7768f6e
#: ../../contribute.rst:98 0e03b29d89cc408e9374cb51f7147611
msgid ""
"(For more on Invoke, see ``invoke -l`` to list tasks, or "
"https://pyinvoke.org for documentation.)"
msgstr ""
"(执行 ``invoke -l`` 会列出可以调用的测试任务,关于此的更多文档请参阅 "
"https://pyinvoke.org "
msgstr "(执行 ``invoke -l`` 会列出可以调用的测试任务,关于此的更多文档请参阅 https://pyinvoke.org "
#: ../../contribute.rst:101 d1cebbdf4fcf4be5b918613c5050d638
#: ../../contribute.rst:101 70aad8c721c64d2b8d32488dd9da851e
msgid ""
"In addition to running the test suite, it is important to also ensure "
"that any lines you changed conform to code style guidelines. You can "
"check that via::"
msgstr ""
"除了运行测试套件外,还要确保修改了的部分遵循代码风格指南。可以通过下面的命令"
"检查代码风格:"
msgstr "除了运行测试套件外,还要确保修改了的部分遵循代码风格指南。可以通过下面的命令检查代码风格:"
#: ../../contribute.rst:106 7a0b9ebf408f472aa786f6c3ac639240
#: ../../contribute.rst:106 ../../contribute.rst:200
#: b0ff008dde5e4e0b892e0fc2fa959b6a
msgid ""
"If style violations are found, many of them can be addressed "
"automatically via::"
msgstr "若存在不合规范风格的代码,大多数情况下可以通过下述命令自动纠正:"
#: ../../contribute.rst:111 ebad1e2cb63a45d999d2d3e510711972
msgid ""
"If code style violations are found in lines you changed, correct those "
"lines and re-run the above lint command until they have all been fixed. "
"You do not need to address style violations, if any, for code lines you "
"did not touch."
msgstr ""
"如果在修改过的代码中有地方违反了代码风格规范,请纠正并再次运行上述命令,直到全部纠正。"
"但是若是发现违反代码风格的地方并不是你修改的,请忽略之,不要进行纠正。"
"lines and re-run the ``invoke lint`` command until they have all been "
"fixed. You do not need to address style violations, if any, for code "
"lines you did not touch."
msgstr "如果在修改过的代码中有地方违反了代码风格规范,请纠正并再次运行上述命令,直到全部纠正。但是若是发现违反代码风格的地方并不是你修改的,请忽略之,不要进行纠正。"
#: ../../contribute.rst:110 74ec20f2daf74ad18cc083ad48b89dfe
#: ../../contribute.rst:115 e208ada16ab8425e9fbbcd5f135f6574
msgid ""
"After making your changes and running the tests, you may see a test "
"failure mentioning that \"some generated files differ from the expected "
@ -489,94 +457,83 @@ msgid ""
" have both** ``en_EN.utf8`` **and** ``fr_FR.utf8`` **locales installed**,"
" and then run the following command::"
msgstr ""
"在修改完代码运行测试的过程中你可能会看到测试失败中有提到“some generated files "
"differ from the expected functional tests output” 。这可能是由于你对代码的修改"
"影响到了Pelican的HTML输出若输出的结果确实是你想要的请更新功能测试所用的输出用例。"
"请确保你安装了 ``en_EN.utf8`` 和 ``fr_FR.utf8`` ,然后执行下述命令:"
"在修改完代码运行测试的过程中你可能会看到测试失败中有提到“some generated files differ from the "
"expected functional tests output” "
"。这可能是由于你对代码的修改影响到了Pelican的HTML输出若输出的结果确实是你想要的请更新功能测试所用的输出用例。请确保你安装了 "
"``en_EN.utf8`` 和 ``fr_FR.utf8`` ,然后执行下述命令:"
#: ../../contribute.rst:120 4299259dadd748238f9465eefb84727c
#: ../../contribute.rst:125 a4a3e16c3e0345c99cb2d8b674627afa
msgid ""
"You may also find that some tests are skipped because some dependency "
"(e.g., Pandoc) is not installed. This does not automatically mean that "
"these tests have passed; you should at least verify that any skipped "
"tests are not affected by your changes."
msgstr ""
"你还可能会发现有一些测试由于缺少依赖(例如 Pandoc而被跳过。这并不意味着通过"
"了这些测试,请至少确保对代码的修改不会影响到这些被跳过的测试。"
msgstr "你还可能会发现有一些测试由于缺少依赖(例如 Pandoc而被跳过。这并不意味着通过了这些测试请至少确保对代码的修改不会影响到这些被跳过的测试。"
#: ../../contribute.rst:125 a8835ccddf624fc1994c618ded8cc5ba
#: ../../contribute.rst:130 dd6db784c2534b0ea0842cb736dca7c3
msgid ""
"You should run the test suite under each of the supported versions of "
"Python. This is best done by creating a separate Python environment for "
"each version. Tox_ is a useful tool to automate running tests inside "
"``virtualenv`` environments."
msgstr ""
"你应该在Pelican支持的所有Python版本下运行测试套件。一般会通过为每一个Python版本"
"创建一个虚拟环境来实现这一点。Tox_ 是一个用于在 ``virtualenv`` 环境中自动运行"
"测试的工具。"
"你应该在Pelican支持的所有Python版本下运行测试套件。一般会通过为每一个Python版本创建一个虚拟环境来实现这一点。Tox_ "
"是一个用于在 ``virtualenv`` 环境中自动运行测试的工具。"
#: ../../contribute.rst:133 b8b8c16b0d0743b98de5d759f79d07ba
#: ../../contribute.rst:138 58fd644b4b7248ebb9c8ff899a2f90b1
msgid "Running a code coverage report"
msgstr "运行代码测试覆盖报告"
#: ../../contribute.rst:135 674a92a42d924931801c9f9c02463cd5
#: ../../contribute.rst:140 abe50ab68fef48dea42aa269743fc172
msgid ""
"Code is more likely to stay robust if it is tested. Coverage_ is a "
"library that measures how much of the code is tested. To run it::"
msgstr ""
"经过测试的代码往往具有更好的健壮性。 Coverage_ 是一个用于衡量代码测试覆盖率的库"
"执行下面的命令以调取之:"
msgstr "经过测试的代码往往具有更好的健壮性。 Coverage_ 是一个用于衡量代码测试覆盖率的库执行下面的命令以调取之:"
#: ../../contribute.rst:140 ecb5e7f9e83c4243ba04b58764e573b6
#: ../../contribute.rst:145 9d5ba28c240f464c92db9869c01e3917
msgid ""
"This will show overall coverage, coverage per file, and even line-by-line"
" coverage. There is also an HTML report available::"
msgstr ""
"该命令会展示总体覆盖率以及在每个文件上的覆盖率,甚至还会展示每一行的覆盖情况。"
"同样也会有一份HTML格式的报告供您查看"
msgstr "该命令会展示总体覆盖率以及在每个文件上的覆盖率甚至还会展示每一行的覆盖情况。同样也会有一份HTML格式的报告供您查看"
#: ../../contribute.rst:148 bad31d4cb0b644ac8ecb7885b22072a7
#: ../../contribute.rst:153 45e095f0c0fd4a5b9f75027d12dd891f
msgid "Building the docs"
msgstr "构建文档"
#: ../../contribute.rst:150 47e1f1caa594462d9b3b4403645abf3b
#: ../../contribute.rst:155 e1e8bb56a9c8449a8da8e10fcf45da2a
msgid ""
"If you make changes to the documentation, you should build and inspect "
"your changes before committing them::"
msgstr ""
"若你对文档进行过修改请在commit前完成构建和检查"
msgstr "若你对文档进行过修改请在commit前完成构建和检查"
#: ../../contribute.rst:155 a4961ae22c2c4de9bbc8bb98d3a3ec81
#: ../../contribute.rst:160 9482dc5bee484f0c9f05af197b49ed70
msgid ""
"Open http://localhost:8000 in your browser to review the documentation. "
"While the above task is running, any changes you make and save to the "
"documentation should automatically appear in the browser, as it live-"
"reloads when it detects changes to the documentation source files."
msgstr ""
"执行上述命令后请在Web浏览器中打开 http://localhost:8000 来查看文档。"
"在上述命令执行时,对文档做的任何修改应该会自动反映在浏览器中。"
"执行上述命令后请在Web浏览器中打开 http://localhost:8000 "
"来查看文档。在上述命令执行时,对文档做的任何修改应该会自动反映在浏览器中。"
#: ../../contribute.rst:161 7740ec477ad747ebaa2dde2b2aef45d5
#: ../../contribute.rst:166 82343c9684bb440eb260110d98bb0e59
msgid "Plugin development"
msgstr "插件开发"
#: ../../contribute.rst:163 9505da5fcac24d718f59c797061d2b0f
#: ../../contribute.rst:168 8697f547344e4973ad34f9c619ddf22e
msgid ""
"To create a *new* Pelican plugin, please refer to the `plugin template`_ "
"repository for detailed instructions."
msgstr ""
"要创建一个 *新的* Pelican插件请参阅 `插件模板`_ 仓库以获得更为详细的指导。"
msgstr "要创建一个 *新的* Pelican插件请参阅 `插件模板`_ 仓库以获得更为详细的指导。"
#: ../../contribute.rst:166 5fdae4611a6949b9a4c3bc82c52d3bc6
#: ../../contribute.rst:171 3c505e3035c143c89efd3e648fe00e8e
msgid ""
"If you want to contribute to an *existing* Pelican plugin, follow the "
"steps above to set up Pelican for local development, and then create a "
"directory to store cloned plugin repositories::"
msgstr ""
"若你想在 *已有* Pelican插件中做贡献请先按前文所述步骤配置Pelican的本地开发环境"
"然后创建一个文件夹来存放克隆下来的插件仓库:"
msgstr "若你想在 *已有* Pelican插件中做贡献请先按前文所述步骤配置Pelican的本地开发环境然后创建一个文件夹来存放克隆下来的插件仓库"
#: ../../contribute.rst:172 0f50b12aaf3b4049999130a92fa6b670
#: ../../contribute.rst:177 5523421ea2664b1ab0859216a1c8a463
msgid ""
"Assuming you wanted to contribute to the Simple Footnotes plugin, you "
"would first browse to the `Simple Footnotes`_ repository on GitHub and "
@ -586,129 +543,111 @@ msgstr ""
"假设想要为Simple Footnotes插件做贡献你应该先查看并fork `Simple Footnotes`_ "
"的Github仓库然后克隆你自己fork的那一份再添加原仓库作为Git远程仓库upstream"
#: ../../contribute.rst:185 2efe992372f149c3b63ca22016f8501b
#: ../../contribute.rst:190 e5178eb4654a44919c743d37f00ff4c3
msgid "Create a topic branch for your plugin bug fix or feature::"
msgstr "同样地为你想要进行的bug修复或特性添加创建一个分支"
#: ../../contribute.rst:189 40f3c07d12cc4630bc75355c3449196d
#: ../../contribute.rst:194 af04dad9f528473caa4c4c0f4c33042a
msgid ""
"After writing new tests for your plugin changes, run the plugin test "
"suite and check for code style compliance via::"
msgstr ""
"完成修改并添加测试后,运行测试套件,并检查代码风格:"
msgstr "完成修改并添加测试后,运行测试套件,并检查代码风格:"
#: ../../contribute.rst:195 ba97ce962daa437cbcf2d09897394aed
msgid ""
"If style violations are found, many of them can be addressed "
"automatically via::"
msgstr ""
"若存在不合规范风格的代码,大多数情况下可以通过下述命令自动纠正:"
#: ../../contribute.rst:199 a0ee1e11aaea4f5c8ba4c4704678bbaf
#: ../../contribute.rst:205 06d00f61d5c344d587baa85116b3c1e0
msgid ""
"If style violations are found even after running the above auto-"
"formatters, you will need to make additional manual changes until "
"``invoke lint`` no longer reports any code style violations."
msgstr ""
"如果在自动格式化后仍存在代码风格上的问题,请手动修正这些问题,直到执行 "
"``invoke lint`` 时不再报告问题。"
msgstr "如果在自动格式化后仍存在代码风格上的问题,请手动修正这些问题,直到执行 ``invoke lint`` 时不再报告问题。"
#: ../../contribute.rst:207 e9d1e344bb0d4b2fb9d08c2d71d9a342
#: ../../contribute.rst:213 9a0831b06abd494fad469b7df71c489f
msgid "Submitting your changes"
msgstr "提交更改"
#: ../../contribute.rst:209 716c9f94166d42299d9ee58eed4f9b53
#: ../../contribute.rst:215 23b5d147059b4cea99a213f50d63097a
msgid ""
"Assuming linting validation and tests pass, add a ``RELEASE.md`` file in "
"the root of the project that contains the release type (major, minor, "
"patch) and a summary of the changes that will be used as the release "
"changelog entry. For example::"
msgstr ""
"通过了风格检查和所有测试后,请在项目的根目录下添加一个 ``RELEASE.md`` 文件,"
"其中应包含发布的类型major、minor、patch以及代码变更的摘要这份摘要会被用作"
"更新日志的条目。下面是一个例子:"
"通过了风格检查和所有测试后,请在项目的根目录下添加一个 ``RELEASE.md`` "
"文件其中应包含发布的类型major、minor、patch以及代码变更的摘要这份摘要会被用作更新日志的条目。下面是一个例子"
#: ../../contribute.rst:218 656309283e5642b99981c84da9b04c86
#: ../../contribute.rst:224 6794c41ebe2c4937ba4f3f8e16e7a9d9
msgid "Commit your changes and push your topic branch::"
msgstr "commit你的更改并push对应分支"
#: ../../contribute.rst:224 16617b687db94783b5488884e4c9be1b
#: ../../contribute.rst:230 daa69b097fc14739be924714f8070cf6
msgid ""
"Finally, browse to your repository fork on GitHub and submit a pull "
"request."
msgstr ""
"最后前往Github从你fork的仓库向原仓库提出PR。"
msgstr "最后前往Github从你fork的仓库向原仓库提出PR。"
#: ../../contribute.rst:228 629ae326bd4e4718a8865d3925c02c3e
#: ../../contribute.rst:234 b71524be74c84517a12fcdecb51bc55e
msgid "Logging tips"
msgstr "日志技巧"
#: ../../contribute.rst:230 486bb6ae6c484431923a96b7a7aff0c5
#: ../../contribute.rst:236 a0b70f864ce144eabe0f89d78844c395
msgid "Try to use logging with appropriate levels."
msgstr "请仔细斟酌合适的日志等级。"
#: ../../contribute.rst:232 fbe2aed8f0f5412081461fce5d36e51e
#: ../../contribute.rst:238 3b44fa3ec9b3493e97c310207e5dce91
msgid "For logging messages that are not repeated, use the usual Python way::"
msgstr "对于不重复的日志消息,使用一般的方式即可:"
#: ../../contribute.rst:241 bab220240a0744f5b1170783098b5eac
#: ../../contribute.rst:247 49d4e407310348838660e8c74c6e3fb6
#, python-format
msgid ""
"Do not format log messages yourself. Use ``%s`` formatting in messages "
"and pass arguments to logger. This is important, because the Pelican "
"logger will preprocess some arguments, such as exceptions."
msgstr ""
"请不要自己格式化日志消息,而是使用在日志消息中使用 ``%s`` 并向logger传入参数。请务必"
"遵循这一规则因为Pelican的logger会自动预处理一些特殊的参数例如exception。"
"请不要自己格式化日志消息,而是使用在日志消息中使用 ``%s`` "
"并向logger传入参数。请务必遵循这一规则因为Pelican的logger会自动预处理一些特殊的参数例如exception。"
#: ../../contribute.rst:246 a760419565b8440ebc8b4dc8898520db
#: ../../contribute.rst:252 4ac501dff8bc4554998d3f03486cce0e
msgid "Limiting extraneous log messages"
msgstr "限制低关联日志消息"
#: ../../contribute.rst:248 dcf900d9f7d0424fabff4a9c5a7e5dc8
#: ../../contribute.rst:254 c4dfb487945341cda6c0858954a2ed40
msgid ""
"If the log message can occur several times, you may want to limit the log"
" to prevent flooding. In order to do that, use the ``extra`` keyword "
"argument for the logging message in the following format::"
msgstr ""
"如果同一日志消息会重复多次,你会希望限制这些多余的内容。使用 ``extra`` "
"命名参数来实现这一点:"
msgstr "如果同一日志消息会重复多次,你会希望限制这些多余的内容。使用 ``extra`` 命名参数来实现这一点:"
#: ../../contribute.rst:255 1ca7d769fc9348f8a5f9eef7b614522b
#: ../../contribute.rst:261 4090a3bc71e3441e8a7efd639d36ec1e
msgid ""
"Optionally, you can also set ``'limit_args'`` as a tuple of arguments in "
"``extra`` dict if your generic message needs formatting."
msgstr ""
"可选的,如果通用日志消息需要格式化,可以添加 ``'limit_args'`` 参数并将其对应值"
"设为一个元组。"
msgstr "可选的,如果通用日志消息需要格式化,可以添加 ``'limit_args'`` 参数并将其对应值设为一个元组。"
#: ../../contribute.rst:258 85328a267c464f9aaacb1b0ef289d624
#: ../../contribute.rst:264 dd6530ceb29d4a91902046a3d4e63af6
msgid ""
"Limit is set to ``5``, i.e, first four logs with the same ``'limit_msg'``"
" are outputted normally but the fifth one will be logged using "
"``'limit_msg'`` (and ``'limit_args'`` if present). After the fifth, "
"corresponding log messages will be ignored."
msgstr ""
"限制数默认设为了 ``5`` ,即前四个有相同 ``'limit_msg'`` 参数的日志消息会正常输出,"
"但第五条这样的日志消息会呈现为 ``'limit_msg'`` 参数值本身( ``'limit_args'`` 同理)。"
"第六条及之后的日志消息会被直接忽略。"
"限制数默认设为了 ``5`` ,即前四个有相同 ``'limit_msg'`` 参数的日志消息会正常输出,但第五条这样的日志消息会呈现为 "
"``'limit_msg'`` 参数值本身( ``'limit_args'`` 同理)。第六条及之后的日志消息会被直接忽略。"
#: ../../contribute.rst:263 7a51dbb9559d4a579654b2ab0938d09b
#: ../../contribute.rst:269 50bdb3405a964740aeb91a7d559ba9b5
msgid ""
"For example, if you want to log missing resources, use the following "
"code::"
msgstr ""
"例如,如果你想要用日志记录资源缺失的信息,可以使用下面的代码:"
msgstr "例如,如果你想要用日志记录资源缺失的信息,可以使用下面的代码:"
#: ../../contribute.rst:271 8db05f7332f3475b940fb79d24e74ce7
#: ../../contribute.rst:277 0303387eccd842f9aa57eb3192252dba
msgid "The log messages will be displayed as follows::"
msgstr "最终的日志消息看起来会像这样:"
#: ../../contribute.rst:281 93d618c58e6e4688bebb999ddf591eaa
#: ../../contribute.rst:287 281637c4520d4755993e8bfa46b0326b
msgid "Outputting traceback in the logs"
msgstr "在日志中输出traceback信息"
#: ../../contribute.rst:283 3d56bb4bc804499a8d3c8f14dc614916
#: ../../contribute.rst:289 8bd9319a7a6c4f77bd651057d1cc7c75
msgid ""
"If you're logging inside an ``except`` block, you may want to provide the"
" traceback information as well. You can do that by setting ``exc_info`` "
@ -716,9 +655,8 @@ msgid ""
" can be undesired because tracebacks are long and can be confusing to "
"regular users. Try to limit them to ``--debug`` mode like the following::"
msgstr ""
"当在 ``except`` 块中进行日志记录时你可能会希望同时输出traceback信息。可以"
"简单地将 ``exc_info`` 参数设为 ``True`` 来实现这一功能。但是通过此方法输出的"
"traceback信息会非常长不便于理解。可以像下述代码一样将这些信息限制在 "
"当在 ``except`` 块中进行日志记录时你可能会希望同时输出traceback信息。可以简单地将 ``exc_info`` 参数设为 "
"``True`` 来实现这一功能。但是通过此方法输出的traceback信息会非常长不便于理解。可以像下述代码一样将这些信息限制在 "
"``--debug`` 模式中:"
#~ msgid "latest Pelican release (or an up-to-date Git clone of Pelican master)"

View file

@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PELICAN 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-07-31 22:54+0800\n"
"POT-Creation-Date: 2024-11-07 16:25+0800\n"
"PO-Revision-Date: 2024-06-27 19:00+0800\n"
"Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
"Language: zh_CN\n"
@ -16,29 +16,29 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.15.0\n"
"Generated-By: Babel 2.16.0\n"
#: ../../faq.rst:2 87acb7c16d974b4eb060949b8ce40914
#: ../../faq.rst:2 84467b3ab4b8411589855b3130e14406
msgid "Frequently Asked Questions (FAQ)"
msgstr "常见问题解答"
#: ../../faq.rst:4 76aee892f7f14d0590db2d76c7cc0123
#: ../../faq.rst:4 54c28b1640fd4939b5f196fa377292eb
msgid "Here are some frequently asked questions about Pelican."
msgstr "以下是一些Pelican的常见问题解答。"
#: ../../faq.rst:7 c98549fdd5814984bfa3a6eaf4631d37
#: ../../faq.rst:7 a95f8f3dcb6741949ba9d4761199dd0a
msgid "What's the best way to communicate a problem, question, or suggestion?"
msgstr "交流问题、疑问或提建议的最佳方式是什么?"
#: ../../faq.rst:9 dbecb306adeb482ba3b9bd68483bc372
#: ../../faq.rst:9 d93f8424407d42b2b3ce37b39baecd8a
msgid "Please read our :doc:`feedback guidelines <contribute>`."
msgstr "请参阅文档 :doc:`项目贡献与意见反馈 <contribute>` 。"
#: ../../faq.rst:12 8fe91d51140946f1b2cb131d786c1814
#: ../../faq.rst:12 9fea72b4670c4fe6a3d67e1ddb158f47
msgid "How can I help?"
msgstr "我可以帮上什么忙?"
#: ../../faq.rst:14 d8477da414c446b3936e73931eb4f63a
#: ../../faq.rst:14 3f4b88cf5b814e678a552c821ae4b450
msgid ""
"There are several ways to help out. First, you can communicate any "
"Pelican suggestions or problems you might have via `Pelican Discussions "
@ -50,7 +50,7 @@ msgstr ""
"<https://github.com/getpelican/pelican/discussions>`_ "
"中提出任何关于Pelican的建议或是问题。在提问或建议之前请先查看已关闭或开放的issues中是否已有相关内容以避免内容上的重复。"
#: ../../faq.rst:20 95a29a97e08a452f89aa4eaad191b698
#: ../../faq.rst:20 ca9e66682caf43a481ca91ecace43ed0
msgid ""
"If you want to contribute, please fork `the Git repository "
"<https://github.com/getpelican/pelican/>`_, create a new feature branch, "
@ -62,17 +62,17 @@ msgstr ""
"创建一个新的功能分支并在其中进行修改在修改完成后提出一个PR。项目组会尽快审核你的PR。关于此的更多内容请参见 "
":doc:`项目贡献与意见反馈 <contribute>` 一节。"
#: ../../faq.rst:26 bf7a6828eec74dc588c18e185bdd7090
#: ../../faq.rst:26 f05e9b722b084a439cd6d99b3155910d
msgid ""
"You can also contribute by creating themes and improving the "
"documentation."
msgstr "你可以发起的贡献当然也包括创建主题和改进文档。"
#: ../../faq.rst:29 2ce846241ce744fd81981a376d3f5fe2
#: ../../faq.rst:29 d40c58aeafe54bdaa389c3c05a0fd721
msgid "Is the Pelican settings file mandatory?"
msgstr "Pelican配置文件是必要的吗"
#: ../../faq.rst:31 527720062339422095e2c95755af5584
#: ../../faq.rst:31 96ef0c57471d4a669bd7f2a7f493c23b
msgid ""
"Configuration files are optional and are just an easy way to configure "
"Pelican. For basic operations, it's possible to specify options while "
@ -82,11 +82,11 @@ msgstr ""
"配置文件是可选的其本质是使您可以更方便地配置Pelican。对于一些基本的配置操作完全可以在命令行中指定调用 ``pelican "
"--help`` 可以查看pelican命令的更多信息。"
#: ../../faq.rst:36 d0ca19a2e40c4ecaa9ecba6cc677f142
#: ../../faq.rst:36 e3752aec18514ce292ee4ebd0d95db37
msgid "Changes to the settings file take no effect"
msgstr "修改后的配置文件没有生效"
#: ../../faq.rst:38 5b741cbb28854893818826c593f8e323
#: ../../faq.rst:38 3f5c632fd20446cf8dd70a5eb88dbbcf
msgid ""
"When experimenting with different settings (especially the metadata ones)"
" caching may interfere and the changes may not be visible. In such cases,"
@ -96,11 +96,11 @@ msgstr ""
"在尝试不同的配置时(尤其是尝试不同元数据时),缓存很可能会产生干扰,使得修改不可见。此时,确保配置了 ``LOAD_CONTENT_CACHE ="
" False`` 或在命令行中加上 ``--ignore-cache`` 以禁用缓存。"
#: ../../faq.rst:44 439f2221927b42f7a4c219ab1a76f849
#: ../../faq.rst:44 067892211d0d4f4bae85d65a0132eb1d
msgid "I'm creating my own theme. How do I use Pygments for syntax highlighting?"
msgstr "在自己创建主题时如何使用Pygments来调整语法高亮"
#: ../../faq.rst:46 3475c1550e584c84a118ac061461f9f6
#: ../../faq.rst:46 b1e6ed1bea2e4b3cb3798131f30a828c
msgid ""
"Pygments adds some classes to the generated content. These classes are "
"used by themes to style code syntax highlighting via CSS. Specifically, "
@ -114,30 +114,49 @@ msgstr ""
"``.highlight pre`` 类来自定义语法高亮的外观。在 `Pygments 项目的demo网站 "
"<https://pygments.org/demo/>`_ 上可以预览能够渲染的代码类型。"
#: ../../faq.rst:53 ecffb1f9501f46c88f799b79fc0ba343
#: ../../faq.rst:53 5dccc8ae367545b08bdce61e008e0a20
msgid ""
"You can use the following example commands to generate a starting CSS "
"file from a Pygments built-in style (in this case, \"monokai\") and then "
"copy the generated CSS file to your new theme::"
msgstr "你可以使用下面的命令来让Pygments使用内置风格此处为“monokai”生成一个初始CSS文件然后将此文件拷贝到新主题中"
#: ../../faq.rst:60 8fc71763c5c243339c9e737cc55b99da
#: ../../faq.rst:60 027edae1ebdf4d52b59171a26915c1ac
msgid "Don't forget to import your ``pygment.css`` file from your main CSS file."
msgstr "不要忘了在你的CSS主文件中引入 ``pygment.css`` 文件。"
#: ../../faq.rst:63 ad118f1f46db423fab19f570cd789798
#: ../../faq.rst:63 164af3be4dce45879963c5d3ee0cd264
msgid "How do I create my own theme?"
msgstr "如何创建我自己的主题?"
#: ../../faq.rst:65 1674585960e742cbade644b63d3bb32a
#: ../../faq.rst:65 7b1db6528b0a4735894868a229a5969d
msgid "Please refer to :ref:`theming-pelican`."
msgstr "请参阅 :ref:`theming-pelican` 。"
#: ../../faq.rst:68 b06c6a8df1634d20b988515af6536e2c
#: ../../faq.rst:68 b8e21f837e0744c49cfe8f0cb3a1d5ee
msgid "Can I override individual templates without forking the whole theme?"
msgstr "我只需要覆盖主题中单独的几个模板文件可不可以不fork整个主题"
#: ../../faq.rst:70 70fd7b5c55c246a6a25b20304bfdb616
msgid ""
"Yes, you can override existing templates of the theme that you are using,"
" or add new templates, via the ``THEME_TEMPLATES_OVERRIDES`` variable. "
"For example, to override the page template, you can define the location "
"for your templates like this::"
msgstr "当然可以,覆盖部分模板文件或是添加一些模板文件都是可以的,使用 ``THEME_TEMPLATES_OVERRIDES`` 变量即可。"
"例如若需要覆盖page的模板可以向这样定义你自己的模板文件位置"
#: ../../faq.rst:77 a96870f0cad74996bec2469ea0c2e9e1
msgid ""
"You can then define a custom template in ``templates/page.html``. See "
":ref:`settings/themes` for details."
msgstr "自定义的模板可以为 ``templates/page.html`` 。详情请参看 :ref:`settings/themes` 。"
#: ../../faq.rst:81 b832cd952cf44a0097f383825f0f295f
msgid "I want to use Markdown, but I got an error."
msgstr "我想要使用Markdown但是出错了。"
#: ../../faq.rst:70 c0a89314dbdf4368b2e32d781c0ae95b
#: ../../faq.rst:83 32d9dbde7029412d852ab8e710112573
msgid ""
"If you try to generate Markdown content without first installing the "
"Markdown library, you may see a message that says ``No valid files found "
@ -151,77 +170,79 @@ msgstr ""
"。虽然Markdown并不是必需依赖但如果你写的内容中含有Markdown格式就需要安装Markdown库了。输入下面的命令以安装Markdown库如果需要权限请在前面添加"
" ``sudo`` "
#: ../../faq.rst:80 a4c93b71eb914652b3f05357067f87b3
#: ../../faq.rst:93 46728a367ffe47d9afeb7608e9c0db5f
msgid "Can I use arbitrary metadata in my templates?"
msgstr "在模板中可以使用任意元数据吗?"
#: ../../faq.rst:82 6ac1579e5d8842f5bf97b87745848c6a
#: ../../faq.rst:95 9b7fbafc6d29429a88a079bfb74e3af5
msgid ""
"Yes. For example, to include a modified date in a Markdown post, one "
"could include the following at the top of the article::"
msgstr "当然可以。例如可以在Markdown帖子中包含一个“修改日期”加在文章开头即可"
#: ../../faq.rst:87 d1ad8fa8e07c4500ab754962064749a8
#: ../../faq.rst:100 ce62442a4c9d4347bd6ae8a59476fcee
msgid ""
"For reStructuredText, this metadata should of course be prefixed with a "
"colon::"
msgstr "对于reStructuredText此元数据也应当以冒号为前缀"
#: ../../faq.rst:91 e3c9814b5b3849a7957f964565038e45
#: ../../faq.rst:104 bf869a6da43e448a9cc512843aa4a183
msgid ""
"This metadata can then be accessed in templates such as ``article.html`` "
"via::"
msgstr "此元数据可以在模板中获取到,例如在 ``article.html`` 中,可以像这样获取:"
#: ../../faq.rst:97 11d953b5718c4baeb7f7fbbb9538c763
#: ../../faq.rst:110 b9c9a648b30942b996b124af9fd5a84c
msgid ""
"If you want to include metadata in templates outside the article context "
"(e.g., ``base.html``), the ``if`` statement should instead be::"
msgstr "如果您想在其他模板(例如 ``base.html`` )中获取此元数据,则 ``if`` 语句应改为:"
#: ../../faq.rst:103 99ca0aeea6d14c159cf1f1b8d9cf016d
#: ../../faq.rst:116 b78a678a165d40f4823fac2b19bcafc1
msgid ""
"How do I make my output folder structure identical to my content "
"hierarchy?"
msgstr "如何使得输出目录的结构和content目录的结构保持一致"
#: ../../faq.rst:105 e97223e6c7c94c08a1d42f783fd67f7e
#: ../../faq.rst:118 851d1019c070482991667cc024063d29
msgid "Try these settings::"
msgstr "可以尝试如下配置:"
#: ../../faq.rst:112 d35f11a227ba421596458ea8f26ecde0
#: ../../faq.rst:125 5195876e3f364a838d72b16c568263bc
msgid "How do I assign custom templates on a per-page basis?"
msgstr "如何为某个页面指定某个模板?"
#: ../../faq.rst:114 287bac0946dc47feab068bdb76d0bc2e
#: ../../faq.rst:127 2ddd3cf1fbf048b1819bcfc9b3691a12
msgid ""
"It's as simple as adding an extra line of metadata to any page or article"
" that you want to have its own template. For example, this is how it "
"would be handled for content in reST format::"
msgstr "这非常简单在任何页面或者文章中都可以通过多添加一行元数据来指定特定模板。例如在reST中使用"
#: ../../faq.rst:120 b845784299bf47629e616505000724c1
#: ../../faq.rst:133 6f5eb40b4a5e4f83ab9d1cb48fefad57
msgid "For content in Markdown format::"
msgstr "对于Markdown则使用"
#: ../../faq.rst:124 fa734dbb540e4cda8a5be5fb1b2da124
#: ../../faq.rst:137 2e28d1bf074c437eb5017bf6f345bf71
msgid ""
"Then just make sure your theme contains the relevant template file (e.g. "
"``template_name.html``)."
msgstr "确保对应的模板文件在主题中存在即可(例如 ``template_name.html`` )。"
"``template_name.html``). If you just want to add a new custom template to"
" an existing theme, you can also provide it in a directory specified by "
"``THEME_TEMPLATES_OVERRIDES`` (see :ref:`settings/themes`)."
msgstr ""
#: ../../faq.rst:128 bdee9be4397f4839855295ee1a0fdd12
#: ../../faq.rst:142 675e77f99f3c42bb8715c84a97c7a064
msgid "How can I override the generated URL of a specific page or article?"
msgstr "如何重写某一个页面或文章生成的URL"
#: ../../faq.rst:130 ed91b5bdcbe24473a6fed738784311b8
#: ../../faq.rst:144 7e518b99b29d4787addc732d57e94ed1
msgid ""
"Include ``url`` and ``save_as`` metadata in any pages or articles that "
"you want to override the generated URL. Here is an example page in reST "
"format::"
msgstr "在任意页面或文章中都可以添加 ``url`` 和 ``save_as`` 元数据这样就可以重写URL了。下面以reST格式为例"
#: ../../faq.rst:139 5aa733d8d3bd4d86920e7e142715b1f4
#: ../../faq.rst:153 903306ecaed3483591b4ed2dcba3d183
msgid ""
"With this metadata, the page will be written to "
"``override/url/index.html`` and Pelican will use the URL "
@ -230,18 +251,18 @@ msgstr ""
"有了这样的元数据,此页面会保存为 ``override/url/index.html`` Pelican会将 ``override/url/``"
" 作为链接到此页面的URL。"
#: ../../faq.rst:143 04d9890aa34d4c1e86bc7a49cd64938a
#: ../../faq.rst:157 d80d84fcb6844e25a8452e29c4113181
msgid "How can I use a static page as my home page?"
msgstr "如何使用一个静态页面作为主页?"
#: ../../faq.rst:145 d3e8a4e2d453446f9037fa46e6775080
#: ../../faq.rst:159 e17a2e2dd9014109888bab9286ee607c
msgid ""
"The override feature mentioned above can be used to specify a static page"
" as your home page. The following Markdown example could be stored in "
"``content/pages/home.md``::"
msgstr "上一个问题中提到的特性可以用于实现此需求。下面例子中的Markdown文件保存为 ``content/pages/home.md`` "
#: ../../faq.rst:155 739da75e7ce946af99c9f577e8a284ff
#: ../../faq.rst:169 b99ba0ca8656416cbdc38f3fa263b7eb
msgid ""
"If the original blog index is still wanted, it can then be saved in a "
"different location by setting ``INDEX_SAVE_AS = 'blog_index.html'`` for "
@ -250,11 +271,11 @@ msgstr ""
"如果仍需要原来的博客主页(即 ``'index'`` 直接模板),可以通过设置 ``INDEX_SAVE_AS = "
"'blog_index.html'`` 将其存储在其他位置。"
#: ../../faq.rst:160 5224f09821d24e4a8db6870da1266a20
#: ../../faq.rst:174 fca4725a57dd451fb3b0fb9df78f69b5
msgid "What if I want to disable feed generation?"
msgstr "可以禁用订阅源生成吗?"
#: ../../faq.rst:162 8f014ffab3c44b0ebf2b0d9872bfbfa7
#: ../../faq.rst:176 e9c08140e2ed44f189a7a156db027a3e
msgid ""
"To disable feed generation, all feed settings should be set to ``None``. "
"All but three feed settings already default to ``None``, so if you want "
@ -264,19 +285,19 @@ msgstr ""
"要禁用订阅源,所有订阅源相关的配置都应被设为 ``None`` 。其中有三项设置默认为 ``None`` "
",因此如果要彻底不生成订阅源,你只需要指定下面这些设置:"
#: ../../faq.rst:172 9ab29ccca83c4ecfabcb3ad4dd17c751
#: ../../faq.rst:186 7820a481af4c4f44a40fb3ae80768a1d
msgid ""
"The word ``None`` should not be surrounded by quotes. Please note that "
"``None`` and ``''`` are not the same thing."
msgstr "``None`` 两侧不需要加引号。请注意 ``None`` 和 ``''`` 不是同一个东西。"
#: ../../faq.rst:176 fd8cbe4962d145ccadfd480419dbea9e
#: ../../faq.rst:190 4fa2ffbf1c274ec396a0d756762c260d
msgid ""
"I'm getting a warning about feeds generated without SITEURL being set "
"properly"
msgstr "Pelican警告说由于SITEURL设置不正确无法正常生成订阅源"
#: ../../faq.rst:178 e3135e5903ec422f8d7895866ca6f365
#: ../../faq.rst:192 8d52f14f6b03476897dfb15c188a961a
msgid ""
"`RSS and Atom feeds require all URL links to be absolute "
"<https://validator.w3.org/feed/docs/rss2.html#comments>`_. In order to "
@ -287,17 +308,17 @@ msgstr ""
"<https://validator.w3.org/feed/docs/rss2.html#comments>`_ "
"。为了使得Pelican能正确生成链接你需要将站点的 ``SITEURL`` 设置为完整路径。"
#: ../../faq.rst:183 4f2cd929dda7464cbd577d1249969920
#: ../../faq.rst:197 1412ceb735d44a30b58db3241248e7ec
msgid ""
"Feeds are still generated when this warning is displayed, but links "
"within may be malformed and thus the feed may not validate."
msgstr "虽然Pelican提出了警告但是仍会生成订阅源但其中的链接可能是无效的这会导致订阅源不可用。"
#: ../../faq.rst:187 a9f3465fda8c4a0d9395b2d6d9d5478f
#: ../../faq.rst:201 20cadccc527e4ebda08eac9ed34f5055
msgid "Can I force Atom feeds to show only summaries instead of article content?"
msgstr "可以让Atom订阅源只显示摘要不显示文章内容吗"
#: ../../faq.rst:189 baf140533501453aa8caeddfc276d8fb
#: ../../faq.rst:203 9c45ba2ec5c6402e86e89661b943d1ad
msgid ""
"Instead of having to open a separate browser window to read articles, the"
" overwhelming majority of folks who use feed readers prefer to read "
@ -314,11 +335,11 @@ msgstr ""
" ``content`` "
"字段因此Pelican在发布RSS时默认只包含摘要当然也可以设置为包含文章内容。Pelican在订阅源生成上的如此行为就可以让用户自行选择订阅类型包含了完整内容的Atom或是只包含摘要的RSS。"
#: ../../faq.rst:200 850ac093f2764547a7df74d5d055cbd4
#: ../../faq.rst:214 bf0d4ca837f74d9ab6618db6306c6a70
msgid "Is Pelican only suitable for blogs?"
msgstr "Pelican只适合用于博客吗"
#: ../../faq.rst:202 1fb5d92096b242d09da5e0e490b34685
#: ../../faq.rst:216 49697f375cfc49b08f5d0c2297d15028
msgid ""
"No. Pelican can be easily configured to create and maintain any type of "
"static site. This may require a little customization of your theme and "
@ -328,13 +349,13 @@ msgid ""
"tag-related pages via::"
msgstr "不是的。Pelican可以方便地用于创建维护任何静态站点为此你需要对主题和配置做一些定制。例如如果要为你的产品构建一个宣传网站即不需要使用标签特性从主题中移除与标签相关的HTML代码即可。另外还可以通过下面的设置来禁用标签相关页面的生成"
#: ../../faq.rst:212 5452959b3b694cbc89bb8e91bfbef840
#: ../../faq.rst:226 0a59dd7209554237912579b362d07788
msgid ""
"Why does Pelican always write all HTML files even with content caching "
"enabled?"
msgstr "启用内容缓存后为什么Pelican仍会每次都写入所有HTML文件"
#: ../../faq.rst:214 b27b4b7256f749f1bc5970b95fa742ab
#: ../../faq.rst:228 6291b82d02fc4450a79d1200b5d04f62
msgid ""
"In order to reliably determine whether the HTML output is different "
"before writing it, a large part of the generation environment including "
@ -347,7 +368,7 @@ msgid ""
"reliable."
msgstr "为了确定HTML输出确实和之前的不同模板上下文、插件等很多生成环境都需要保存并比较某种哈希值对于不可哈希的内容类型还需要进行一些额外处理。另外由于插件、分页等内容的存在输出的HTML很可能会与之前不同。因此考虑到处理时间和存储空间每次都重新写入全部HTML会更快更可靠。"
#: ../../faq.rst:223 dcb5b1cf0e1b413bb7c04f6deb4ad5d7
#: ../../faq.rst:237 5cc5e1361f914c92b0670030f0c83f5d
msgid ""
"However, this means that the modification time of the files changes every"
" time, so a ``rsync`` based upload will transfer them even if their "
@ -359,11 +380,11 @@ msgstr ""
"上传时会把没有变化的内容也进行上传。一个简便的解决方法就是给 ``rsync`` 加上 ``--checksum`` "
"选项这会比Pelican在生成时进行校验更快。"
#: ../../faq.rst:230 628a1180f3fd4c0b8301b33e0728d2c2
#: ../../faq.rst:244 b24c40be89b94f3b980cbbda38d46115
msgid "How to process only a subset of all articles?"
msgstr "如何只处理一部分文章?"
#: ../../faq.rst:232 c2bfe768775342bb8386255ea1bbbe4e
#: ../../faq.rst:246 fa34a90481f44ace83ee16401543ce09
msgid ""
"It is often useful to process only e.g. 10 articles for debugging "
"purposes. This can be achieved by explicitly specifying only the "
@ -374,11 +395,11 @@ msgstr ""
"简便起见,在调试时可能只需要处理几篇文章。可以直接在配置项 ``ARTICLE_PATHS`` 中添加需要处理文章的文件名。可以通过像 ``cd "
"content; find -name '*.md' | head -n 10`` 这样的命令获取文章文件名的列表。"
#: ../../faq.rst:238 72d30cb7a6e348c483cba0c6b6de8d3a
#: ../../faq.rst:252 0fa566e3aa084cb9b04e0cee32684222
msgid "My tag cloud is missing/broken since I upgraded Pelican"
msgstr "在升级Pelican后标签云消失或不可用了"
#: ../../faq.rst:240 7d07dcddab5d42d1aab6a8dbd27ce36c
#: ../../faq.rst:254 0bd1304a12c24f048b227c68391b148c
msgid ""
"In an ongoing effort to streamline Pelican, tag cloud generation has been"
" moved out of Pelican core and into a separate `plugin "
@ -389,11 +410,11 @@ msgstr ""
"<https://github.com/pelican-plugins/tag-cloud>`_ 中。查看 :ref:`plugins` "
"文档获取更多关于Pelican插件系统的信息。"
#: ../../faq.rst:246 51c727bc21f946b8915f958312369e0f
#: ../../faq.rst:260 1833dfba94c74f4bb9e9f0a112ed3e0f
msgid "Since I upgraded Pelican my pages are no longer rendered"
msgstr "升级Pelican后一些页面没有被渲染"
#: ../../faq.rst:248 4a0d962bc2d844cbab3d0b3e7f6f7bba
#: ../../faq.rst:262 576e5c2338ba4c43a51bb562301ad0c2
msgid ""
"Pages were available to themes as lowercase ``pages`` and uppercase "
"``PAGES``. To bring this inline with the :ref:`templates-variables` "
@ -405,15 +426,15 @@ msgstr ""
"variables` 一节中的内容保持一致,大写的 ``PAGES`` 被删除了。只要将主题中的 ``PAGES`` 替换为 ``pages`` "
",问题即可解决。例如将原先的:"
#: ../../faq.rst:255 6167ad6b52db43d384247747db1884ca
#: ../../faq.rst:269 355512b9f6b34ece9b6baed128b2ca4d
msgid "with something like::"
msgstr "替换为:"
#: ../../faq.rst:260 a7a04eb9e8e549fa8a2a72db3f35b532
#: ../../faq.rst:274 99ef769943fe41c4a37ca951e905b2ba
msgid "How can I stop Pelican from trying to parse my static files as content?"
msgstr "如何避免让Pelican将我的静态文件解析为内容文件译者注例如要将一个HTML文件作为静态文件"
#: ../../faq.rst:262 6baaf265738d4acaa26f7829c64a0ac5
#: ../../faq.rst:276 4efb20c5b82d41afb07151599fa189dd
msgid ""
"Pelican's article and page generators run before it's static generator. "
"That means if you use a setup similar to the default configuration, where"
@ -426,7 +447,7 @@ msgstr ""
"配置项中,所有以有效内容文件后缀结尾的文件( ``.html`` 、 ``.rst`` 、 ``.md`` "
"等)都会被视为文章或者页面,而不是静态文件。"
#: ../../faq.rst:268 e4591dd94ddd4199900b9a451d12929e
#: ../../faq.rst:282 d959eb6a67fe440caa70105e1692bf93
msgid ""
"To circumvent this issue either use the appropriate ``*_EXCLUDES`` "
"setting or disable the offending reader via ``READERS`` if you don't need"
@ -435,11 +456,11 @@ msgstr ""
"为了避免这个问题,使用合适的 ``*_EXCLUDES`` 配置,在必要时还可以通过 ``READERS`` "
"配置项来直接禁用产生问题的reader。"
#: ../../faq.rst:272 ca927fe2be10411ab365bcc3e4fa4dbd
#: ../../faq.rst:286 5e64dc4b6fad4e7ea07278f5a2529e89
msgid "Why is [arbitrary Markdown syntax] not supported?"
msgstr "为什么不是所有的Markdown语法都支持"
#: ../../faq.rst:274 5c9cc929a6bf4f1db9d4eed5f37fc0af
#: ../../faq.rst:288 6872a70ec1434c41a78d465271761c69
msgid ""
"Pelican does not directly handle Markdown processing and instead "
"delegates that task to the Python-Markdown_ project, the core of which "
@ -455,3 +476,9 @@ msgstr ""
"项目此项目的核心有意只遵循原始的Markdown语法规则而不服从之后传播开的大量Markdown风格。另外 Python-Markdown_"
" 是相当模块化的,你想要使用的语法可能已经有现成的 `Markdown扩展`_ "
"进行了实现。或者也有人创建了支持Markdown变体的Pelican插件如果你想要用某种Markdown变体可以在这些地方寻找支持。"
#~ msgid ""
#~ "Then just make sure your theme "
#~ "contains the relevant template file "
#~ "(e.g. ``template_name.html``)."
#~ msgstr "确保对应的模板文件在主题中存在即可(例如 ``template_name.html`` )。"

View file

@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PELICAN 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 19:06+0800\n"
"POT-Creation-Date: 2025-07-13 11:46+0800\n"
"PO-Revision-Date: 2024-06-25 19:00+0800\n"
"Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
"Language: zh_CN\n"
@ -16,38 +16,35 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.15.0\n"
"Generated-By: Babel 2.17.0\n"
#: ../../install.rst:2 32d9c99d9171418c89daafbe7260daa9
#: ../../install.rst:2 e735e1393d63466092c9fc0a5ee4117d
msgid "Installing Pelican"
msgstr "安装Pelican"
#: ../../install.rst:4 73ec02b650044be6bb17951f4a915075
#: ../../install.rst:4 e34bdf7c1bbb4c75a47f8bd16e626c67
msgid ""
"Pelican currently runs best on |min_python|; earlier versions of Python "
"are not supported."
msgstr ""
"Pelican需要 |min_python| 以上版本的Python不支持更低版本。"
msgstr "Pelican需要 |min_python| 以上版本的Python不支持更低版本。"
#: ../../install.rst:6 9134a5a1bd9a4f54a36a3da163d859d8
#: ../../install.rst:6 ff98ade47da6403e84dd1b2209896d9c
msgid ""
"You can install Pelican via several different methods. The simplest is "
"via Pip_::"
msgstr ""
"有多种方法可以安装Pelican最简单的就是通过 Pip_"
msgstr "有多种方法可以安装Pelican最简单的就是通过 Pip_"
#: ../../install.rst:10 22d5948b07d14a13bc45aa14ef11e856
#: ../../install.rst:10 ae2fcb82534e4a3f81980f69ed94c9ad
msgid "Or, if you plan on using Markdown::"
msgstr "如果您需要使用Markdown请使用下面的命令安装"
#: ../../install.rst:14 b910f7faa2c84e5eb62fbd0fae2544d3
#: ../../install.rst:14 ed597b1eb47949efba0f1781ef7bbd1f
msgid ""
"(Keep in mind that some operating systems will require you to prefix the "
"above command with ``sudo`` in order to install Pelican system-wide.)"
msgstr ""
"(在某些操作系统中,需要在命令前加 ``sudo`` 才能在整个系统上安装Pelican"
msgstr "(在某些操作系统中,需要在命令前加 ``sudo`` 才能在整个系统上安装Pelican"
#: ../../install.rst:17 afb018b5d42e433e8107ca38dfcb545f
#: ../../install.rst:17 04d6784f06dd40e7bff76bf6476aaba1
msgid ""
"While the above is the simplest method, the recommended approach is to "
"create a virtual environment for Pelican via virtualenv_ before "
@ -55,43 +52,40 @@ msgid ""
" open a new terminal session and create a new virtual environment for "
"Pelican::"
msgstr ""
"尽管上面是最简单的安装方法,但我们推荐使用虚拟环境 virtualenv_ 完成"
"Pelican的安装。当您安装好 virtualenv_ 后,打开一个新的命令行并"
"为Pelican创建一个虚拟环境"
"尽管上面是最简单的安装方法,但我们推荐使用虚拟环境 virtualenv_ 完成Pelican的安装。当您安装好 virtualenv_ "
"后打开一个新的命令行并为Pelican创建一个虚拟环境"
#: ../../install.rst:26 7d981233f13e42b6b07fbd5fa58f69fc
#: ../../install.rst:26 08aae819315e48a194a065a3fc3dddad
msgid ""
"Once the virtual environment has been created and activated, Pelican can "
"be installed via ``python -m pip install pelican`` as noted above. "
"Alternatively, if you have the project source, you can install Pelican "
"using the distutils method::"
"using the setuptools method::"
msgstr ""
"当创建并激活虚拟环境后,使用之前提到过的命令 ``python -m pip install pelican`` "
"就可以安装Pelican了。或者如果您想要从源码安装可以使用distutils方式"
"就可以安装Pelican了。或者如果您想要从源码安装可以使用setuptools"
#: ../../install.rst:33 c8109ae3e44541e18e713e39690009ae
#: ../../install.rst:33 368febf14ca740e19fa470b0f832dea1
msgid ""
"If you have Git installed and prefer to install the latest bleeding-edge "
"version of Pelican rather than a stable release, use the following "
"command::"
msgstr ""
"如果安装过Git并且您希望安装Pelican的最最新版本而不是稳定版"
"请使用下面的命令:"
msgstr "如果安装过Git并且您希望安装Pelican的最最新版本而不是稳定版请使用下面的命令"
#: ../../install.rst:38 2ba389e93d084dea8b702336479a0470
#: ../../install.rst:38 2498d09099194317a62e67b907bdd5d3
msgid ""
"Once Pelican is installed, you can run ``pelican --help`` to see basic "
"usage options. For more detail, refer to the :doc:`Publish<publish>` "
"section."
msgstr ""
"当您安装好Pelican可以执行 ``pelican --help`` 命令来查看一些基本用法。"
"在 :doc:`发布站点<publish>` 章节中可以了解更多信息。"
"当您安装好Pelican可以执行 ``pelican --help`` 命令来查看一些基本用法。在 :doc:`发布站点<publish>` "
"章节中可以了解更多信息。"
#: ../../install.rst:42 d1850a31cca24c5281cc7c9fd748b56b
#: ../../install.rst:42 4ef93669753e4bb89252a8c9852e7a71
msgid "Optional packages"
msgstr "可选包"
#: ../../install.rst:44 8428281e15354c71a5aec92e9e0041b9
#: ../../install.rst:44 190eabcd8f3a437cbf895ecee25aff4d
msgid ""
"If you plan on using `Markdown <https://pypi.org/project/Markdown/>`_ as "
"a markup format, you can install Pelican with Markdown support::"
@ -99,7 +93,7 @@ msgstr ""
"如您希望使用 `Markdown <https://pypi.org/project/Markdown/>`_ "
"来写作执行下面的命令来安装Markdown支持"
#: ../../install.rst:49 6dcdacecb0874afd8c88cbf814c522ba
#: ../../install.rst:49 fa8fc8ff397a412f839bc2805696aa45
msgid ""
"Typographical enhancements can be enabled in your settings file, but "
"first the requisite `Typogrify <https://pypi.org/project/typogrify/>`_ "
@ -108,108 +102,94 @@ msgstr ""
"Pelican还支持排版增强若您需要使用请先安装 `Typogrify "
"<https://pypi.org/project/typogrify/>`_ 库,稍后您可以在设置文件中启用它。"
#: ../../install.rst:56 d3ff6383ae9745bc9bfed85654086311
#: ../../install.rst:56 74911273a6934154bad4fadbc0d1f28b
msgid "Dependencies"
msgstr "依赖"
#: ../../install.rst:58 2dc22a3fa6c242bdb5b61005e1910d79
#: ../../install.rst:58 77d44b11ae7e4945b119fd473bb53e67
msgid ""
"When Pelican is installed, the following dependent Python packages should"
" be automatically installed without any action on your part:"
msgstr ""
"当Pelican安装完成后下面的所有Python依赖应该都会自动安装"
"无需另外做任何操作:"
msgstr "当Pelican安装完成后下面的所有Python依赖应该都会自动安装无需另外做任何操作"
#: ../../install.rst:61 4c7a644a29b540869d69acd10e032039
#: ../../install.rst:61 22bdf13ed0a3482fb66f10486518261c
msgid ""
"`feedgenerator <https://pypi.org/project/feedgenerator/>`_, to generate "
"the Atom feeds"
msgstr ""
"`feedgenerator <https://pypi.org/project/feedgenerator/>`_"
"用于生成Atom feeds"
msgstr "`feedgenerator <https://pypi.org/project/feedgenerator/>`_用于生成Atom feeds"
#: ../../install.rst:63 365c8fb0938e4d9fbf78d110b05cb99f
#: ../../install.rst:63 21ddc5ce3bed4f9cab2a454e8319a8c4
msgid "`jinja2 <https://pypi.org/project/Jinja2/>`_, for templating support"
msgstr "`jinja2 <https://pypi.org/project/Jinja2/>`_用于模板系统"
#: ../../install.rst:64 5db63207e60c4997924c3baf8aec8524
#: ../../install.rst:64 9302b2919a4f4de0927060911f69f5ed
msgid "`pygments <https://pypi.org/project/Pygments/>`_, for syntax highlighting"
msgstr "`pygments <https://pypi.org/project/Pygments/>`_用于语法高亮"
#: ../../install.rst:65 72bfb5fc2b514031a42952502746c100
#: ../../install.rst:65 c6e45ac0f3ea4f91953fb2dfc66d29d9
msgid ""
"`docutils <https://pypi.org/project/docutils/>`_, for supporting "
"reStructuredText as an input format"
msgstr ""
"`docutils <https://pypi.org/project/docutils/>`_"
"用于reStructuredText格式"
msgstr "`docutils <https://pypi.org/project/docutils/>`_用于reStructuredText格式"
#: ../../install.rst:67 d00ac0c26d884a2d9d7f02fa89491892
#: ../../install.rst:67 aea17a424f3c4e8eab50172b6653fe16
msgid ""
"`blinker <https://pypi.org/project/blinker/>`_, an object-to-object and "
"broadcast signaling system"
msgstr ""
"`blinker <https://pypi.org/project/blinker/>`_"
"对象-对象的信号广播系统"
msgstr "`blinker <https://pypi.org/project/blinker/>`_对象-对象的信号广播系统"
#: ../../install.rst:69 0d317b007acf49fc879203fa8ffb4048
#: ../../install.rst:69 5da4c8d1fdf349c2afe23ffc9d832816
msgid ""
"`unidecode <https://pypi.org/project/Unidecode/>`_, for ASCII "
"transliterations of Unicode text utilities"
msgstr ""
"`unidecode <https://pypi.org/project/Unidecode/>`_"
"用于将Unicode文本转为ASCII字符的音译"
"`unidecode "
"<https://pypi.org/project/Unidecode/>`_用于将Unicode文本转为ASCII字符的音译"
#: ../../install.rst:72 ded0aae575854f149bcf2ea9efa4ba21
#: ../../install.rst:72 ff81051def5544e1b5d66532453aed25
msgid ""
"`MarkupSafe <https://pypi.org/project/MarkupSafe/>`_, for a markup-safe "
"string implementation"
msgstr ""
"`MarkupSafe <https://pypi.org/project/MarkupSafe/>`_"
"用于转义字符的安全处理"
msgstr "`MarkupSafe <https://pypi.org/project/MarkupSafe/>`_用于转义字符的安全处理"
#: ../../install.rst:74 eae7d8f6f84040339ccfef98e20502d8
#: ../../install.rst:74 0222b4cdfdcb48839f5f6b092071db99
msgid ""
"`python-dateutil <https://pypi.org/project/python-dateutil/>`_, to read "
"the date metadata"
msgstr ""
"`python-dateutil <https://pypi.org/project/python-dateutil/>`_"
"用于读取日期相关的元数据"
"`python-dateutil <https://pypi.org/project/python-"
"dateutil/>`_用于读取日期相关的元数据"
#: ../../install.rst:78 cd33ec4583574c5bb879f08813b9932c
#: ../../install.rst:78 49117127302b49b39bd5b86abae18709
msgid "Upgrading"
msgstr "更新升级"
#: ../../install.rst:80 1513dd1e43564cb29da0a14988e0791d
#: ../../install.rst:80 93962c7d303f4c9fa5ad9d43f86ea50a
msgid ""
"If you installed a stable Pelican release via Pip_ and wish to upgrade to"
" the latest stable release, you can do so by adding ``--upgrade``::"
msgstr ""
"若是通过 Pip_ 安装了稳定版本的Pelican可以通过在安装命令中"
"添加 ``--upgrade`` 来升级到最新版:"
msgstr "若是通过 Pip_ 安装了稳定版本的Pelican可以通过在安装命令中添加 ``--upgrade`` 来升级到最新版:"
#: ../../install.rst:85 fae6900b3acc41d4b7bb34c192fe4c08
#: ../../install.rst:85 1ac1fa009f9e4245ae7f975bda7d5a22
msgid ""
"If you installed Pelican via distutils or the bleeding-edge method, "
"simply perform the same step to install the most recent version."
msgstr ""
"若是通过distutils安装或是通过Git安装了测试版的Pelican"
"重新进行一遍和安装时同样的步骤即可。"
msgstr "若是通过distutils安装或是通过Git安装了测试版的Pelican重新进行一遍和安装时同样的步骤即可。"
#: ../../install.rst:89 89392d36f81f4c7eb75e9a74d1795faa
#: ../../install.rst:89 7845fa285f0b4dcd8e881c9edd61f80c
msgid "Kickstart your site"
msgstr "启动网站"
#: ../../install.rst:91 a8517a0fbbb1420297df214f50d8792d
#: ../../install.rst:91 488ad84175cb45f6a6bb26cec24c1f10
msgid ""
"Once Pelican has been installed, you can create a skeleton project via "
"the ``pelican-quickstart`` command, which begins by asking some questions"
" about your site::"
msgstr ""
"Pelican安装完成后通过 ``pelican-quickstart`` 命令创建项目的整体框架,"
"在运行这个命令时,您需要输入一些与站点相关的信息:"
"Pelican安装完成后通过 ``pelican-quickstart`` "
"命令创建项目的整体框架,在运行这个命令时,您需要输入一些与站点相关的信息:"
#: ../../install.rst:97 50231ba4b02d4e868995bdacbd02b27d
#: ../../install.rst:97 63a773d35b91455b944206337e527a3a
msgid ""
"If run inside an activated virtual environment, ``pelican-quickstart`` "
"will look for an associated project path inside "
@ -219,26 +199,22 @@ msgid ""
"project path on initial invocation, use: ``pelican-quickstart --path "
"/your/desired/directory``"
msgstr ""
"如果是在虚拟环境中执行 ``pelican-quickstart`` ,系统会自动在 "
"``$VIRTUAL_ENV/.project`` 目录中查找这个命令。若这个这个命令存在"
"并且路径是正确的一个新的Pelican项目就会在目标位置创建。否则"
"会默认在当前的工作目录下创建这个项目。若要在初始化时指定项目路径,请使用 "
"``pelican-quickstart --path /your/desired/directory``。"
"如果是在虚拟环境中执行 ``pelican-quickstart`` ,系统会自动在 ``$VIRTUAL_ENV/.project`` "
"目录中查找这个命令。若这个这个命令存在并且路径是正确的一个新的Pelican项目就会在目标位置创建。否则会默认在当前的工作目录下创建这个项目。若要在初始化时指定项目路径请使用"
" ``pelican-quickstart --path /your/desired/directory``。"
#: ../../install.rst:104 ea893addf15c47f182384509b1a3a2f7
#: ../../install.rst:104 b7cdf15328074880bb4fc69dcb7bd26f
msgid ""
"Once you finish answering all the questions, your project will consist of"
" the following hierarchy (except for *pages* — shown in parentheses below"
" — which you can optionally add yourself if you plan to create non-"
"chronological content)::"
msgstr ""
"当您回答完所有问题后,项目就会成功创建。项目中会包含下述的一些层级结构"
"(除了用括号括起来的 *pages*)。如果有一些内容不需要按时间排序,"
"您可以将它们放在pages所在的位置"
"当您回答完所有问题后,项目就会成功创建。项目中会包含下述的一些层级结构(除了用括号括起来的 "
"*pages*。如果有一些内容不需要按时间排序您可以将它们放在pages所在的位置"
#: ../../install.rst:118 7d13a0cc5ebd44159fddc8de68993fc7
#: ../../install.rst:118 05e4fe3b0d0a4c998fba451692a68725
msgid ""
"The next step is to begin to adding content to the *content* folder that "
"has been created for you."
msgstr ""
"接下来就可以开始往 *content* 目录中添加自己创作的内容了。"
msgstr "接下来就可以开始往 *content* 目录中添加自己创作的内容了。"

View file

@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PELICAN 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 19:06+0800\n"
"POT-Creation-Date: 2025-07-13 11:46+0800\n"
"PO-Revision-Date: 2024-06-26 19:00+0800\n"
"Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
"Language: zh_CN\n"
@ -16,26 +16,24 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.15.0\n"
"Generated-By: Babel 2.17.0\n"
#: ../../plugins.rst:4 b1b40bca7d3748008eefe26806d5d5ef
#: ../../plugins.rst:4 3df58bcad1a64350a8e763d87d7470e3
msgid "Plugins"
msgstr "插件"
#: ../../plugins.rst:6 42ca486828e4442a9d74216d0d8bb37d
#: ../../plugins.rst:6 5e0f2aa517254778a71d1e742b051645
msgid ""
"Beginning with version 3.0, Pelican supports plugins. Plugins are a way "
"to add features to Pelican without having to directly modify the Pelican "
"core."
msgstr ""
"Pelican从3.0版本开始支持插件。通过插件不必直接修改Pelican的核心代码就可以给"
"Pelican添加新功能。"
msgstr "Pelican从3.0版本开始支持插件。通过插件不必直接修改Pelican的核心代码就可以给Pelican添加新功能。"
#: ../../plugins.rst:10 6bb8ab4cb7eb44ddb1ed4734f47f6781
#: ../../plugins.rst:10 40ad4aad1dc54b929f6059031edae0d9
msgid "How to use plugins"
msgstr "如何使用插件"
#: ../../plugins.rst:12 822e0bd7ce2f4433a7c39b3accde01a1
#: ../../plugins.rst:12 8fc9f8cba76b4bb9930d80b5b985885a
msgid ""
"Starting with version 4.5, Pelican moved to a new plugin structure "
"utilizing namespace packages that can be easily installed via Pip_. "
@ -44,12 +42,11 @@ msgid ""
"Pelican. To see a list of Pip-installed namespace plugins that are active"
" in your environment, run::"
msgstr ""
"Pelican从4.5版本开始使用了一种全新的插件结构,利用了命名空间包,"
"并且可以轻松地通过 Pip_ 进行安装。支持此结构地插件都会被安装在命名空间包 "
"``pelican.plugins`` 下因此Pelican可以自动发现他们。下面的命令可以用于"
"查看环境中用Pip安装的所有插件"
"Pelican从4.5版本开始使用了一种全新的插件结构,利用了命名空间包,并且可以轻松地通过 Pip_ "
"进行安装。支持此结构地插件都会被安装在命名空间包 ``pelican.plugins`` "
"下因此Pelican可以自动发现他们。下面的命令可以用于查看环境中用Pip安装的所有插件"
#: ../../plugins.rst:20 2b59c5d107dc4b118dc76116910e9495
#: ../../plugins.rst:20 de052285e7f645a9ab551433f3c07d46
msgid ""
"If you leave the ``PLUGINS`` setting as default (``None``), Pelican will "
"automatically discover namespace plugins and register them. If, on the "
@ -58,132 +55,122 @@ msgid ""
"specify will be registered, and you must explicitly list any namespace "
"plugins as well."
msgstr ""
"若将 ``PLUGINS`` 配置项设为默认的 ``None`` Pelican会自动发现命名空间中的"
"插件并且将他们全部加载;若你在 ``PLUGINS`` 设置项中指定了一系列的插件,"
"Pelican就不会去自动发现插件也就是说你需要显式地指定所有要使用的插件。"
"若将 ``PLUGINS`` 配置项设为默认的 ``None`` Pelican会自动发现命名空间中的插件并且将他们全部加载若你在 "
"``PLUGINS`` 设置项中指定了一系列的插件Pelican就不会去自动发现插件也就是说你需要显式地指定所有要使用的插件。"
#: ../../plugins.rst:26 52d1968196294569a478931f7022e686
#: ../../plugins.rst:26 a9675be841b84df584e67087cd23ab34
msgid ""
"If you are using the ``PLUGINS`` setting, you can specify plugins in two "
"ways. The first method specifies plugins as a list of strings. Namespace "
"plugins can be specified either by their full names "
"(``pelican.plugins.myplugin``) or by their short names (``myplugin``)::"
msgstr ""
"在配置 ``PLUGINS`` 时,有两种方式。一是用字符串列表指定插件的名称,可以是包含"
"命名空间的完整名称(例如 ``pelican.plugins.myplugin`` ),也可以是简短名称"
" ``myplugin``"
"在配置 ``PLUGINS`` 时,有两种方式。一是用字符串列表指定插件的名称,可以是包含命名空间的完整名称(例如 "
"``pelican.plugins.myplugin`` ),也可以是简短名称( ``myplugin``"
#: ../../plugins.rst:35 b2c75e52e66e4000968e744ffa4b89a9
#: ../../plugins.rst:35 188bf617180b4a7b9bc09f3fb1c201ae
msgid ""
"Alternatively, you can import them in your settings file and pass the "
"modules::"
msgstr ""
"二是在设置文件中先import进来再将import进的模块放在 ``PLUGINS`` 设置项中:"
msgstr "二是在设置文件中先import进来再将import进的模块放在 ``PLUGINS`` 设置项中:"
#: ../../plugins.rst:43 88af9139373f4cd89fa5b958196c9448
#: ../../plugins.rst:43 2d5db874810245a98b59ab080a0df1a5
msgid ""
"When experimenting with different plugins (especially the ones that deal "
"with metadata and content) caching may interfere and the changes may not "
"be visible. In such cases disable caching with ``LOAD_CONTENT_CACHE = "
"False`` or use the ``--ignore-cache`` command-line switch."
msgstr ""
"在尝试不同的插件时(尤其是那些处理元数据和内容的插件),缓存可能会相互干扰,"
"一些更改不会生效。发生这种情况时,就需要通过设置 ``LOAD_CONTENT_CACHE = False`` "
"或使用 ``--ignore-cache`` 命令行选项禁用缓存。"
"在尝试不同的插件时(尤其是那些处理元数据和内容的插件),缓存可能会相互干扰,一些更改不会生效。发生这种情况时,就需要通过设置 "
"``LOAD_CONTENT_CACHE = False`` 或使用 ``--ignore-cache`` 命令行选项禁用缓存。"
#: ../../plugins.rst:48 d0e3cd59052c4a7d995fb5e1e15d9799
#: ../../plugins.rst:48 7421f93c1d714c9c853fc9311681515a
msgid ""
"If your plugins are not in an importable path, you can specify a list of "
"paths via the ``PLUGIN_PATHS`` setting. As shown in the following "
"example, paths in the ``PLUGIN_PATHS`` list can be absolute or relative "
"to the settings file::"
msgstr ""
"如果插件处于无法直接进行import的路径可以在 ``PLUGIN_PATHS`` 配置项中指定这些路径。"
"如下例所示, ``PLUGIN_PATHS`` 中的路径可以是绝对的,也可以是相对于设置文件的:"
"如果插件处于无法直接进行import的路径可以在 ``PLUGIN_PATHS`` 配置项中指定这些路径。如下例所示, "
"``PLUGIN_PATHS`` 中的路径可以是绝对的,也可以是相对于设置文件的:"
#: ../../plugins.rst:56 4c3de952a8514e5caea402392b911f0b
#: ../../plugins.rst:56 b8406038d0284d3fbef9d3de1fa7fd9f
msgid "Where to find plugins"
msgstr "在哪儿下载插件"
#: ../../plugins.rst:57 16173c9dceb0409f89964412dd7e71e9
#: ../../plugins.rst:57 b07653ce77194a998630a55ae9511de5
msgid ""
"Namespace plugins can be found in the `pelican-plugins organization`_ as "
"individual repositories. Legacy plugins are located in the `pelican-"
"plugins repository`_ and will be gradually phased out in favor of the "
"namespace versions."
msgstr ""
"新的命名空间插件可以在GitHub的 `pelican-plugins 组织`_ 中找到,每个插件都是"
"一个独立的仓库。而老的插件则可以在GitHub的 `pelican-plugins 仓库`_ 中找到。"
"这些老的插件会逐步淘汰并转移到新的命名空间版本。"
"新的命名空间插件可以在GitHub的 `pelican-plugins 组织`_ "
"中找到,每个插件都是一个独立的仓库。而老的插件则可以在GitHub的 `pelican-plugins 仓库`_ "
"中找到。这些老的插件会逐步淘汰并转移到新的命名空间版本。"
#: ../../plugins.rst:65 a30a9862112b47128f6e7b28c6836f27
#: ../../plugins.rst:65 5c55fa6f3d664be2a49b8256dc2f6a2e
msgid ""
"Please note that while we do our best to review and maintain these "
"plugins, they are submitted by the Pelican community and thus may have "
"varying levels of support and interoperability."
msgstr ""
"请注意尽管我们尽全力审查和维护这些插件但这些插件是Pelican社区提交的"
"因此支持性和互操作性程度各不相同。"
msgstr "请注意尽管我们尽全力审查和维护这些插件但这些插件是Pelican社区提交的因此支持性和互操作性程度各不相同。"
#: ../../plugins.rst:70 f4e140c61c0f45ed8ac53dca3b05b1f1
#: ../../plugins.rst:70 25339a713a97492c88b0e60024ac34b8
msgid "How to create plugins"
msgstr "如何创建插件"
#: ../../plugins.rst:72 43013c6cf4f34ca09205e8dab0b9fa6d
#: ../../plugins.rst:72 62b6b4a1a5f0486e8b3a39d6a7050f0a
msgid ""
"Plugins are based on the concept of signals. Pelican sends signals, and "
"plugins subscribe to those signals. The list of available signals is "
"documented in a subsequent section."
msgstr ""
"插件是基于信号这一概念的。Pelican会发送信号插件则订阅这些信号。可用的信号"
"在下一节会贴出来。"
msgstr "插件是基于信号这一概念的。Pelican会发送信号插件则订阅这些信号。可用的信号在下一节会贴出来。"
#: ../../plugins.rst:76 5377a966ab114a29acb61f79eadc632b
#: ../../plugins.rst:76 f8f74b0257be46a1878e72e126166bd0
msgid ""
"The only rule to follow for plugins is to define a ``register`` callable,"
" in which you map the signals to your plugin logic. Let's take a simple "
"example::"
msgstr ""
"对于插件来说,唯一需要遵循的规则就是一定要定义一个可调用的 ``register`` "
"在 ``register`` 中需要将信号映射到插件逻辑上。下面是一个简单的例子:"
"对于插件来说,唯一需要遵循的规则就是一定要定义一个可调用的 ``register`` 在 ``register`` "
"中需要将信号映射到插件逻辑上。下面是一个简单的例子:"
#: ../../plugins.rst:93 2217318326524c62804ec94e55a4ca20
#: ../../plugins.rst:93 163eebc74421416da2ad497830c42771
msgid ""
"Signal receivers are weakly-referenced and thus must not be defined "
"within your ``register`` callable or they will be garbage-collected "
"before the signal is emitted."
msgstr ""
"信号接收器在Pelican中是弱引用的因此不能将它定义在可调用的 ``register`` 中,"
"否则接收器在信号发送之前就会被回收。"
msgstr "信号接收器在Pelican中是弱引用的因此不能将它定义在可调用的 ``register`` 中,否则接收器在信号发送之前就会被回收。"
#: ../../plugins.rst:97 6731cc78478a46c5a0cb51a8cd477318
#: ../../plugins.rst:97 bb63bd2d24e341a1a4f7dfa118648d9a
msgid ""
"If multiple plugins connect to the same signal, plugins will be executed "
"in the order they are connected. With ``PLUGINS`` setting, order will be "
"as defined in the setting. If you rely on auto-discovered namespace "
"plugins, no ``PLUGINS`` setting, they will be connected in the same order"
" they are discovered (same order as ``pelican-plugins`` output). If you "
"want to specify the order explicitly, disable auto-discovery by defining "
"If multiple plugins connect to the same signal, plugins will be invoked "
"in the order they are registered. When the ``PLUGINS`` setting is "
"defined, plugin invocation order will be the order in which the plugins "
"are listed in the ``PLUGINS`` setting. If you rely on auto-discovered "
"namespace plugins and have no ``PLUGINS`` setting defined, plugins will "
"be invoked in the same order that they are discovered (the same order as "
"listed in the output of the ``pelican-plugins`` command). If you want to "
"specify the order explicitly, disable auto-discovery by defining "
"``PLUGINS`` in the desired order."
msgstr ""
"如果多个插件关联到同一个信号,插件将按照它们关联的前后顺序执行。但若设置了 "
"``PLUGINS`` 配置项会以此配置项中的顺序为准。如果您使用了无需PLUGINS设置的新版"
"命名空间插件,它们将按照被探测到的顺序进行连接(与 pelican-plugins 输出的顺序相同)。"
"对于关联到同一个信号的多个插件,将按照它们注册的前后顺序执行。但若设置了 ``PLUGINS`` "
"配置项,则会以此配置项中的顺序为准。如果您使用了无需PLUGINS设置的新版命名空间插件,它们将按照被探测到的顺序进行连接(与 pelican-"
"plugins 输出的顺序相同)。若您此时仍想要显式指定顺序,设置 ``PLUGINS`` 配置项即可。"
#: ../../plugins.rst:105 6dad534cc0014b78a3638a91cc4a1120
#: ../../plugins.rst:107 062aa3a3402141cfbd376d4fee1b5b34
msgid "Namespace plugin structure"
msgstr "命名空间插件的结构"
#: ../../plugins.rst:107 aa6f290c3f4d42558b684d0e3487af95
#: ../../plugins.rst:109 e6968290620d4de3b71ff62d5abba91f
msgid ""
"Namespace plugins must adhere to a certain structure in order to function"
" properly. They need to be installable (i.e. contain ``setup.py`` or "
"equivalent) and have a folder structure as follows::"
msgstr ""
"命名空间插件必须遵循特定的结构才能正常工作。这些插件需要是可安装的"
"(即包含 ``setup.py`` 或其他等效文件),并且遵循下述文件夹结构:"
msgstr "命名空间插件必须遵循特定的结构才能正常工作。这些插件需要是可安装的(即包含 ``setup.py`` 或其他等效文件),并且遵循下述文件夹结构:"
#: ../../plugins.rst:120 b8d73cfdb5f042cca1705f97d693263d
#: ../../plugins.rst:122 b9782f71fae14bce9854b8b5056407d8
msgid ""
"It is crucial that ``pelican`` or ``pelican/plugins`` folder **not** "
"contain an ``__init__.py`` file. In fact, it is best to have those "
@ -192,373 +179,357 @@ msgid ""
"``pelican/plugins/myplugin`` folder to avoid any issues."
msgstr ""
"非常关键的一点就是, ``pelican`` 和 ``pelican/plugins`` 文件夹下都 **不能** 包含 "
"``__init__.py`` 文件。事实上,这两个文件夹下最好是只有上面列出的文件夹,"
"并且保证与插件相关的文件都仅包含在 ``pelican/plugins/myplugin`` 文件夹中,"
"以避免奇奇怪怪的问题。"
"``__init__.py`` 文件。事实上,这两个文件夹下最好是只有上面列出的文件夹,并且保证与插件相关的文件都仅包含在 "
"``pelican/plugins/myplugin`` 文件夹中,以避免奇奇怪怪的问题。"
#: ../../plugins.rst:126 c3f08ae8c0d7415098157bbd1c99ce08
#: ../../plugins.rst:128 8440bc91329c498c90fadab556391a84
msgid ""
"To easily set up the proper structure, a `cookiecutter template for "
"plugins`_ is provided. Refer to that project's README for instructions on"
" how to use it."
msgstr ""
"为了让大家更容易就能建立正确的结构,我们为插件提供了一个 `cookiecutter模板`_ "
"使用方法参考此项目README文件中的指示即可。"
msgstr "为了让大家更容易就能建立正确的结构,我们为插件提供了一个 `cookiecutter模板`_ 使用方法参考此项目README文件中的指示即可。"
#: ../../plugins.rst:132 c2321eec3dc84224918172c5040a259f
#: ../../plugins.rst:134 bb029c6c9ea14a2dac684d516fb9a1eb
msgid "List of signals"
msgstr "信号列表"
#: ../../plugins.rst:134 78c4cfefae7e412f8f6287da2e3c8d34
#: ../../plugins.rst:136 968d92d9b3bb4491ad9c0e4a015e73f9
msgid "Here is the list of currently implemented signals:"
msgstr "下面是目前已经实现了的信号:"
#: ../../plugins.rst:137 7a3c3b8b0f114d54b497ab77b09dc558
#: ../../plugins.rst:139 f2db011f146d40bf9f07ec6b09c7c6d0
msgid "Signal"
msgstr "信号"
#: ../../plugins.rst:137 781b5c11f87f43b9ba4b3e75bee696d0
#: ../../plugins.rst:139 32f683cb25c74315ac803c62868bd7b2
msgid "Arguments"
msgstr "参数"
#: ../../plugins.rst:137 df7d14950fed44f4a4b93908aed36060
#: ../../plugins.rst:139 d02ae4c30dec40ae8bd894fda051562d
msgid "Description"
msgstr "描述"
#: ../../plugins.rst:139 598901e7cb5b49ac9acb5f148bf7c0e7
#: ../../plugins.rst:141 d526b9cb6c3c409f9b2d243082dfbdc3
msgid "initialized"
msgstr "initialized"
#: ../../plugins.rst:139 ../../plugins.rst:140 ../../plugins.rst:158
#: ../../plugins.rst:161 4cedbf9ee7fb4c7abe20e15e4ee1c7fb
#: 704ff7e1ddfc4eb3bd7798d25df1e668 bc98001ef73d419b8f811bbb3d3a571a
#: c9104ccaf84c48d98fafca001ec187e2
#: ../../plugins.rst:141 ../../plugins.rst:142 ../../plugins.rst:160
#: ../../plugins.rst:163 0ab3e30cf009477980c4c619e0a7dc5e
#: 8cf4a2d70a234250a4d9f63e4e8cb49f a600f769faef42d99333442745c7b498
#: a69e7ba2df7a47658b2f0e4ade60d455
msgid "pelican object"
msgstr "pelican object"
#: ../../plugins.rst:140 6f1a09178e2c44c9bda76ed0c0025bef
#: ../../plugins.rst:142 3aff44965eec41269a45fd0b84b8b5d7
msgid "finalized"
msgstr "finalized"
#: ../../plugins.rst:140 175a1d1ab8374325812a00cfd581e54e
#: ../../plugins.rst:142 6a3bd6c773b245af9151ff5669ef7f84
msgid ""
"invoked after all the generators are executed and just before pelican "
"exits useful for custom post processing actions, such as: - minifying "
"js/css assets. - notify/ping search engines with an updated sitemap."
msgstr ""
"所有generator执行完成后调用即pelican退出之前。这对于自定义后处理操作是"
"非常有用的例如可以简化js/css资源、向搜索引擎告知更新后的sitemap。"
msgstr "所有generator执行完成后调用即pelican退出之前。这对于自定义后处理操作是非常有用的例如可以简化js/css资源、向搜索引擎告知更新后的sitemap。"
#: ../../plugins.rst:144 8d390b6db281423d92a4d7bd4921b4b4
#: ../../plugins.rst:146 eecb5a5dc1b84f94a830db617122f365
msgid "generator_init"
msgstr "generator_init"
#: ../../plugins.rst:144 fef4d6e70a4c4365be408a5f1579135c
#: ../../plugins.rst:146 b01311f8da704b55b38e23149c60bc22
msgid "generator"
msgstr "generator"
#: ../../plugins.rst:144 dbe5ff1590dc4df38cb8fd234708c7bd
#: ../../plugins.rst:146 a3c477e7a8d04e94af4ee7a82c873ef2
msgid "invoked in the Generator.__init__"
msgstr "在Generator.__init__中调用"
#: ../../plugins.rst:145 0324812d14d9452fbf28c286c2a10834
#: ../../plugins.rst:147 246a49eb99d34589ac409e5613f27069
msgid "all_generators_finalized"
msgstr "all_generators_finalized"
#: ../../plugins.rst:145 f6170ebf34b247868d149f0efca462b3
#: ../../plugins.rst:147 0dafe1a8f7224b1bbe1af3ebeeac0b31
msgid "generators"
msgstr "generators"
#: ../../plugins.rst:145 d67dff93c28146498074abbf3aeb5103
#: ../../plugins.rst:147 9d5130f91ac748e58d96cfba7711e8f6
msgid "invoked after all the generators are executed and before writing output"
msgstr "在所有generator执行完后写入输出内容前调用"
#: ../../plugins.rst:146 0e9feed7804b4bbdb23711f9d6ad4f40
#: ../../plugins.rst:148 3a7f543549164bb684f47daa5b1b9bd1
msgid "readers_init"
msgstr "readers_init"
#: ../../plugins.rst:146 f0de00423c104ecd8e60fb3450b534b4
#: ../../plugins.rst:148 0946829014734c53a0b1e389df853daf
msgid "readers"
msgstr "readers"
#: ../../plugins.rst:146 b554b35806e34e51bc5ab974fb517541
#: ../../plugins.rst:148 380ba486fff24555b3c312bee4645d23
msgid "invoked in the Readers.__init__"
msgstr "在Readers.__init__中调用"
#: ../../plugins.rst:147 ../../plugins.rst:201 003cdeb23b67433e8cf70c600a42e8e4
#: 7f4a2f6665064a16bcd1b7ea347f5b49
#: ../../plugins.rst:149 ../../plugins.rst:203 04aa2b44a0b84da9b62b952b627a2b5c
#: e725d629327b48e3a7dffad1d07d81d2
msgid "article_generator_context"
msgstr "article_generator_context"
#: ../../plugins.rst:147 8997b3fd1a8d4efb86245916e50c31b9
#: ../../plugins.rst:149 f0c440ead7fc46e2a90685c3fdffb5d4
msgid "article_generator, metadata"
msgstr "article_generator, metadata"
#: ../../plugins.rst:148 ../../plugins.rst:203 4496df152e48410995ae35f73e3ce0e9
#: f46672e3f919441ba2486f9641752913
#: ../../plugins.rst:150 ../../plugins.rst:205 2ed41de1aaed481195aeacbc841459be
#: e9e159b6d49d4cd29ebbe6eb6e0bb3b1
msgid "article_generator_preread"
msgstr "article_generator_preread"
#: ../../plugins.rst:148 ../../plugins.rst:150 ../../plugins.rst:151
#: ../../plugins.rst:154 3408ba823f14463196f2296480e25c7d
#: 43b073d3f3ad4a2ba3d0c18447cb7cf6 c776a7323f0a41babb44daf3abfd6b85
#: f47ca0a3f9654ed4b7653fd946b2d9b6
#: ../../plugins.rst:150 ../../plugins.rst:152 ../../plugins.rst:153
#: ../../plugins.rst:156 37277bd83e254f47b6df91ba6790f79e
#: 9d3b745b96114ff7931cbcc372901c3e b89f87d254984ec59e25045227c708bf
#: d38f0e2931b84b82adcc5aca5a4c2233
msgid "article_generator"
msgstr "article_generator"
#: ../../plugins.rst:148 94e2a57c5b074d068f051d5de850060c
#: ../../plugins.rst:150 7a45243569e84c1e9d5d49b5c1a7b86a
msgid ""
"invoked before a article is read in ArticlesGenerator.generate_context; "
"use if code needs to do something before every article is parsed"
msgstr ""
"在ArticlesGenerator.generate_context读取文章之前调用若代码需要在解析每篇文章前"
"执行某些操作,就可以使用此信号。"
msgstr "在ArticlesGenerator.generate_context读取文章之前调用若代码需要在解析每篇文章前执行某些操作就可以使用此信号。"
#: ../../plugins.rst:150 c58f32123f234e6cafa42aa4ede5bf73
#: ../../plugins.rst:152 87c8e4ad4a104cb889172025f1b0229b
msgid "article_generator_init"
msgstr "article_generator_init"
#: ../../plugins.rst:150 10d3585dc8f94d978643a9c2dc9219a9
#: ../../plugins.rst:152 46c1e5fbb90a4668afda3d66e4520689
msgid "invoked in the ArticlesGenerator.__init__"
msgstr "在ArticlesGenerator.__init__中调用"
#: ../../plugins.rst:151 93ec423e266b4ba9b941a5826e290fec
#: ../../plugins.rst:153 de4b631d41e946c485ebb813e3dd6b62
msgid "article_generator_pretaxonomy"
msgstr "article_generator_pretaxonomy"
#: ../../plugins.rst:151 27290d55819e4bfabe1624059956258f
#: ../../plugins.rst:153 697a45a251fe4188b1f32cec631427b9
msgid ""
"invoked before categories and tags lists are created useful when e.g. "
"modifying the list of articles to be generated so that removed articles "
"are not leaked in categories or tags"
msgstr ""
"在创建类别和标签列表之前调用。例如,当需要变更要生成的文章列表时可以使用,"
"如此可以避免一些已移除文章在分类或标签列表中泄露。"
msgstr "在创建类别和标签列表之前调用。例如,当需要变更要生成的文章列表时可以使用,如此可以避免一些已移除文章在分类或标签列表中泄露。"
#: ../../plugins.rst:154 ../../plugins.rst:202 12c99acda2ac45debe4fc574a246fc63
#: f3bfb220e59d473bb27601c16f5a1625
#: ../../plugins.rst:156 ../../plugins.rst:204 051dcac75cbf4f5ea3a665e6da642324
#: 2360e283fdd142ab8d65792581522e72
msgid "article_generator_finalized"
msgstr "article_generator_finalized"
#: ../../plugins.rst:154 4cb8ed5b4701426b8e1707c6c6b0d48f
#: ../../plugins.rst:156 0c3c808d5b7044018f8566ccc6dd3010
msgid "invoked at the end of ArticlesGenerator.generate_context"
msgstr "在ArticlesGenerator.generate_context的最后调用"
#: ../../plugins.rst:155 c19a632018d44ad2b72d5cf6b7cc9c14
#: ../../plugins.rst:157 60d78048da4843a7a0307218c078d151
msgid "article_generator_write_article"
msgstr "article_generator_write_article"
#: ../../plugins.rst:155 9da20e77d40b45e292ae994fb0fbe97c
#: ../../plugins.rst:157 2ac0d0e7306a4d5086bb2e8b7b17ffb1
msgid "article_generator, content"
msgstr "article_generator, content"
#: ../../plugins.rst:155 a2d5bc3f72b64e47bcaccff3bf27dec2
#: ../../plugins.rst:157 565551e010964925b10a3b5734913119
msgid "invoked before writing each article, the article is passed as content"
msgstr "在写入每篇文章前调用,文章以内容的形式作为参数传入。"
#: ../../plugins.rst:156 0db965f5b99f49e48fc1db531c139f13
#: ../../plugins.rst:158 fd7918c3200f4714b028c8d0a200df98
msgid "article_writer_finalized"
msgstr "article_writer_finalized"
#: ../../plugins.rst:156 c6af98478be14eb283bb95e7b6a3118c
#: ../../plugins.rst:158 e54633543dbf4e5fb2dd4c1bfc09b1c1
msgid "article_generator, writer"
msgstr "article_generator, writer"
#: ../../plugins.rst:156 c48e1152864c4249886f3c7ed4ece85b
#: ../../plugins.rst:158 965e61a0fd6347faa2d7224a50a98b76
msgid ""
"invoked after all articles and related pages have been written, but "
"before the article generator is closed."
msgstr ""
"在所有文章及相关联页面写入完成后在文章generator关闭前调用。"
msgstr "在所有文章及相关联页面写入完成后在文章generator关闭前调用。"
#: ../../plugins.rst:158 f6af27fc844d43779d581cb4383b97ed
#: ../../plugins.rst:160 30df01c5c11a4ed58b006d78b007c68d
msgid "get_generators"
msgstr "get_generators"
#: ../../plugins.rst:158 b41e27f19c47478a8ece4f43a685f6be
#: ../../plugins.rst:160 758447f5e55a4738a14486b0e962034d
msgid ""
"invoked in Pelican.get_generator_classes, can return a Generator, or "
"several generators in a tuple or in a list."
msgstr ""
"在Pelican.get_generator_classes中调用可以返回一个Generator也可以以一个"
"元组或列表的形式返回多个generator。"
msgstr "在Pelican.get_generator_classes中调用可以返回一个Generator也可以以一个元组或列表的形式返回多个generator。"
#: ../../plugins.rst:161 f23075094c4f46958de609a44850eb6d
#: ../../plugins.rst:163 730e948388a24435be216830e0af5be6
msgid "get_writer"
msgstr "get_writer"
#: ../../plugins.rst:161 365671a73e17434f90973ee8e632fa32
#: ../../plugins.rst:163 df9f9fef24984c4bad07b8834e79352f
msgid "invoked in Pelican.get_writer, can return a custom Writer."
msgstr "在Pelican.get_writer前调用可以返回一个自定义Writer。"
#: ../../plugins.rst:163 ../../plugins.rst:204 299eef53e530489a9e7366042919059f
#: 917cc78965d84285bc832cecf181ce55
#: ../../plugins.rst:165 ../../plugins.rst:206 1c172b26e92543d2be488a88cceaf576
#: 252231854c504621b28243dfba9d88ab
msgid "page_generator_context"
msgstr "page_generator_context"
#: ../../plugins.rst:163 26f64e1dbe854ca287aa0f59b269477c
#: ../../plugins.rst:165 a830e240c6564552ba4952bc657120a9
msgid "page_generator, metadata"
msgstr "page_generator, metadata"
#: ../../plugins.rst:164 ../../plugins.rst:205 c2ec4e60dda142569cdcfe5a311b21a5
#: fcd417f63054406ea7869a2a945dc819
#: ../../plugins.rst:166 ../../plugins.rst:207 09add2ea39344ad8936296a07cfd8e82
#: 0fc3cf365d9d418b8225e8f1f5da76d0
msgid "page_generator_preread"
msgstr "page_generator_preread"
#: ../../plugins.rst:164 ../../plugins.rst:166 ../../plugins.rst:167
#: 89c2d7a279604926a290c2665fe8082a 98ab9a5bc2804442a217233f4ab8a003
#: fca779509f1742e99e3d10a6602561c9
#: ../../plugins.rst:166 ../../plugins.rst:168 ../../plugins.rst:169
#: 3c31cfe2f4744cd987f1638a4b82e5de a80ec8c388cb477abbcfc4f558d34df7
#: d485c4f9c2c443748234827727cc887e
msgid "page_generator"
msgstr "page_generator"
#: ../../plugins.rst:164 295fe11e61ba4f80a145ce06a1ffc777
#: ../../plugins.rst:166 4d8b96aa6ebf47d885cd978c336679ff
msgid ""
"invoked before a page is read in PageGenerator.generate_context; use if "
"code needs to do something before every page is parsed."
msgstr ""
"在PageGenerator.generate_context读取页面前调用若代码需要在解析每个页面前"
"执行某些操作,就可以使用此信号。"
msgstr "在PageGenerator.generate_context读取页面前调用若代码需要在解析每个页面前执行某些操作就可以使用此信号。"
#: ../../plugins.rst:166 ../../plugins.rst:207 4f2b1db9b6054af2b0fd0545082bcafd
#: db8ee3e356d84758b427d9f29d034000
#: ../../plugins.rst:168 ../../plugins.rst:209 06adf06d2b204100b9f80850b84bdff0
#: c0988434a401410e8cf6b4528e6d2870
msgid "page_generator_init"
msgstr "page_generator_init"
#: ../../plugins.rst:166 1d4e2e940e0f4dd5a151519aea710454
#: ../../plugins.rst:168 d359da10912949fa999dc3ad5215be66
msgid "invoked in the PagesGenerator.__init__"
msgstr "在PagesGenerator.__init__中调用"
#: ../../plugins.rst:167 ../../plugins.rst:206 319e921c48474a43bbdac4bf43a688f2
#: 5e9b33a48c51417fb5211824b0ad008d
#: ../../plugins.rst:169 ../../plugins.rst:208 0994b38b87704caea04ef0671a7b1c67
#: a97cf5f236a64959aa09838dbe03dfdc
msgid "page_generator_finalized"
msgstr "page_generator_finalized"
#: ../../plugins.rst:167 019fa3fddf2e4725b978326f221c80bd
#: ../../plugins.rst:169 4cfdfe952daf4e3ea5ea1c8b2cf7a664
msgid "invoked at the end of PagesGenerator.generate_context"
msgstr "在PagesGenerator.generate_context的最后调用"
#: ../../plugins.rst:168 0f77c3c609594768a0aaed6529260b97
#: ../../plugins.rst:170 7e2504584a1b4fa4ae88c5002bcbb26f
msgid "page_generator_write_page"
msgstr "page_generator_write_page"
#: ../../plugins.rst:168 0ca5fb200a254cff8529cb5d95e8e26e
#: ../../plugins.rst:170 ea204a5fe703472ea5afea283135b94d
msgid "page_generator, content"
msgstr "page_generator, content"
#: ../../plugins.rst:168 164d45dac5ab4df8abd898c1466e186d
#: ../../plugins.rst:170 22dd198fe6dc498f944e2c0e2c595c6c
msgid "invoked before writing each page, the page is passed as content"
msgstr "在写入每个页面前调用,页面以内容形式作为参数传入"
#: ../../plugins.rst:169 4780473ba6ae47998f891232f122b34a
#: ../../plugins.rst:171 84d5def2c4fc4a2489d2b4fc1fa445df
msgid "page_writer_finalized"
msgstr "page_writer_finalized"
#: ../../plugins.rst:169 6c516a5ae777406ca9ed7bf27b7124c7
#: ../../plugins.rst:171 c55d65276a4e49c58c34d12cc062c90d
msgid "page_generator, writer"
msgstr "page_generator, writer"
#: ../../plugins.rst:169 e8978d0fb878427cbf686608c593aa67
#: ../../plugins.rst:171 b2a3d1c7c2864a08829833bc16b3223e
msgid ""
"invoked after all pages have been written, but before the page generator "
"is closed."
msgstr "调用于所有页面写入完成后在页面generator关闭前。"
#: ../../plugins.rst:171 ../../plugins.rst:208 47bf9969c38b4fef9e15e9d7ea67630e
#: d9a3d5d939d4499b9320ea15dbd3f26e
#: ../../plugins.rst:173 ../../plugins.rst:210 097c5b3dc1d34a5eb7c1b4ae67179b3e
#: a420152f887e4977bdd26a5fa7230915
msgid "static_generator_context"
msgstr "static_generator_context"
#: ../../plugins.rst:171 47064012c4e447f5a1f087a7af420f8f
#: ../../plugins.rst:173 1bbacfe960644e4a902b9c866e3fffce
msgid "static_generator, metadata"
msgstr "static_generator, metadata"
#: ../../plugins.rst:172 ../../plugins.rst:209 7050e1889934465a8837ba65fa249118
#: f45c31c591fd450badd89a7f87c6f991
#: ../../plugins.rst:174 ../../plugins.rst:211 c1242bcf76fc40568f67a2ce4e70c0bb
#: f407aa94870645c891bb349edc3ae9a4
msgid "static_generator_preread"
msgstr "static_generator_preread"
#: ../../plugins.rst:172 ../../plugins.rst:175 ../../plugins.rst:176
#: 1e99fc14855a4a2e8d1f4758e12792d9 45cdf5c2a8d049889b4315d1ea78f462
#: b7ae37b94f2f44feb24ac32b0cdfa447
#: ../../plugins.rst:174 ../../plugins.rst:177 ../../plugins.rst:178
#: 36f5be5c982b42d097c0465f542e490f cf0ebefd743246dd9db1b37a8c6a43a8
#: d5cd54887d904bcca02b0df4f22580e9
msgid "static_generator"
msgstr "static_generator"
#: ../../plugins.rst:172 431017db31bf439f8d3fb5e16b020376
#: ../../plugins.rst:174 1b2fbadf156644429e66ad2e64d26658
msgid ""
"invoked before a static file is read in StaticGenerator.generate_context;"
" use if code needs to do something before every static file is added to "
"the staticfiles list."
msgstr ""
"在StaticGenerator.generate_context读取静态文件前调用若代码需要在每个静态文件"
"加入静态文件列表前进行一些修改,就可以使用此信号。"
msgstr "在StaticGenerator.generate_context读取静态文件前调用若代码需要在每个静态文件加入静态文件列表前进行一些修改就可以使用此信号。"
#: ../../plugins.rst:175 2a380c26f2984e659ec36248a543a4c3
#: ../../plugins.rst:177 654377fe53434f77b3ba294b5689d1d4
msgid "static_generator_init"
msgstr "static_generator_init"
#: ../../plugins.rst:175 832447303775460c83743d831aa58290
#: ../../plugins.rst:177 e9b3cbbde7a6443a81d025d1a4fe6145
msgid "invoked in the StaticGenerator.__init__"
msgstr "在StaticGenerator.__init__中调用"
#: ../../plugins.rst:176 b01307445d54485a9036fb0f9619ff78
#: ../../plugins.rst:178 202be739e43444f48f122d3e5f657a45
msgid "static_generator_finalized"
msgstr "static_generator_finalized"
#: ../../plugins.rst:176 2f7e7e25668b44fc824bb39270c3de96
#: ../../plugins.rst:178 06080672fd614d39a79aa6d3a783087f
msgid "invoked at the end of StaticGenerator.generate_context"
msgstr "在StaticGenerator.generate_context的最后调用"
#: ../../plugins.rst:177 2a34785767ee416dbe41a6aa1f7e4ab1
#: ../../plugins.rst:179 ce174fb4533143518c13b16ab6dbe4c8
msgid "content_object_init"
msgstr "content_object_init"
#: ../../plugins.rst:177 c41d8a8653a94d648b573b5c13db3954
#: ../../plugins.rst:179 5089a38bad1447cab62f350df8e76f31
msgid "content_object"
msgstr "content_object"
#: ../../plugins.rst:177 379b6d76d2f14d05bf1502d2c55b125f
#: ../../plugins.rst:179 d105f652be424f5cad8bfaf7be69ec4b
msgid "invoked at the end of Content.__init__"
msgstr "在Content.__init__的最后调用"
#: ../../plugins.rst:178 10761aa6a1d54ee0a28e562bdacffebf
#: ../../plugins.rst:180 dbda8a11bca744a4ba5fc51d044f1d6e
msgid "content_written"
msgstr "content_written"
#: ../../plugins.rst:178 001ad90e09ab4b21a702b2ed9771a156
#: ../../plugins.rst:180 c8ba95ebcc2e4c79ae79717a730fe504
msgid "path, context"
msgstr "path, context"
#: ../../plugins.rst:178 69b05b02e1564fe4b48dbd2926fdaec3
#: ../../plugins.rst:180 6d9caed8fa24400a86f8ede1c3ecb260
msgid "invoked each time a content file is written."
msgstr "每一次内容文件写入后调用。"
#: ../../plugins.rst:179 30938518f54f46028c8fd03808471be7
#: ../../plugins.rst:181 73a4265b050c4b32be186bb2cec59f30
msgid "feed_generated"
msgstr "feed_generated"
#: ../../plugins.rst:179 e29bf37e7114454099baa21955b7fce0
#: ../../plugins.rst:181 78fa3603986f417286f2e7440f5aff57
msgid "context, feed"
msgstr "context, feed"
#: ../../plugins.rst:179 366ba164593242309dab922c36667dc3
#: ../../plugins.rst:181 13dcd9e5fb2f408db72b87b88877596b
msgid ""
"invoked each time a feed gets generated. Can be used to modify a feed "
"object before it gets written."
msgstr "每个feed生成前调用。可以用于在feed写入前修改之。"
#: ../../plugins.rst:181 0b6d7fc85d374b9c82c60d4a0df69fcd
#: ../../plugins.rst:183 3a959768d5704e459940cbfcf8e1459c
msgid "feed_written"
msgstr "feed_written"
#: ../../plugins.rst:181 d3fdc3a669e9418b9f6e738c549fa151
#: ../../plugins.rst:183 86844bee049a445e87db283bdf325338
msgid "path, context, feed"
msgstr "path, context, feed"
#: ../../plugins.rst:181 3da952e464034f8c8491caa94f0aec2d
#: ../../plugins.rst:183 e79185da7cb54bf5aa59a46846222391
msgid "invoked each time a feed file is written."
msgstr "每一个feed文件写入后调用。"
#: ../../plugins.rst:186 24bf768827184a8a9c2ad9d23d3549e4
#: ../../plugins.rst:188 0fe0539bad1c4fcbbebbdaa98d328ee9
msgid ""
"Avoid ``content_object_init`` signal if you intend to read ``summary`` or"
" ``content`` properties of the content object. That combination can "
@ -567,145 +538,132 @@ msgid ""
"properties instead, or, alternatively, run your plugin at a later stage "
"(e.g. ``all_generators_finalized``)."
msgstr ""
"请避免使用 ``content_object_init`` 信号读取content对象的 ``summary`` 或 "
"``content`` 属性,这可能导致在 :ref:`ref-linking-to-internal-content` 时无法"
"解析链接(请参阅 `pelican-plugins bug #314`_ )。请改用 ``_summary`` 和 "
"``_content`` 属性,或者就在后续阶段再运行插件(例如 ``all_generators_finalized`` 时)。"
"请避免使用 ``content_object_init`` 信号读取content对象的 ``summary`` 或 ``content`` "
"属性,这可能导致在 :ref:`ref-linking-to-internal-content` 时无法解析链接(请参阅 `pelican-"
"plugins bug #314`_ )。请改用 ``_summary`` 和 ``_content`` 属性,或者就在后续阶段再运行插件(例如 "
"``all_generators_finalized`` 时)。"
#: ../../plugins.rst:195 9222300d10c74a9eb27fc229488e63a4
#: ../../plugins.rst:197 77ca681d0d7a4a9ea42f7eebf683f024
msgid ""
"After Pelican 3.2, signal names were standardized. Older plugins may "
"need to be updated to use the new names:"
msgstr ""
"Pelican3.2之后,信号名都进行了标准化,较老的插件可能需要进行更新:"
msgstr "Pelican3.2之后,信号名都进行了标准化,较老的插件可能需要进行更新:"
#: ../../plugins.rst:199 2ba779a696064672965e17c70f70d927
#: ../../plugins.rst:201 c83f9215c5964ba49cb5ed849c777495
msgid "Old name"
msgstr "旧名称"
#: ../../plugins.rst:199 d21e933be9064983aa2cfaeca4f00cb9
#: ../../plugins.rst:201 167435de345b443fa51c27b355121e14
msgid "New name"
msgstr "新名称"
#: ../../plugins.rst:201 805ac7c62fc94113a3481890793f5417
#: ../../plugins.rst:203 bcdf136cbb2c4dedbd90f6e56f584c6b
msgid "article_generate_context"
msgstr "article_generate_context"
#: ../../plugins.rst:202 d6f1a03ae49349b091045c8079b80d44
#: ../../plugins.rst:204 60fe5b91f4a54f0997f93d927b0d81c4
msgid "article_generate_finalized"
msgstr "article_generate_finalized"
#: ../../plugins.rst:203 c967c8322a744c2c970beb6b98b90743
#: ../../plugins.rst:205 31252537627f4042b7f7b4e0a4a33aeb
msgid "article_generate_preread"
msgstr "article_generate_preread"
#: ../../plugins.rst:204 71adeb83fba74317ad0fac5784612a3d
#: ../../plugins.rst:206 719da4844a0a4b6fbb2cf2d9b7e51deb
msgid "pages_generate_context"
msgstr "pages_generate_context"
#: ../../plugins.rst:205 d2297a5ec351411e8a66a74d8168caa0
#: ../../plugins.rst:207 f7c865fd6824473aad024fc606235b48
msgid "pages_generate_preread"
msgstr "pages_generate_preread"
#: ../../plugins.rst:206 fb572935b7f445d298ff2c9c89c59c4e
#: ../../plugins.rst:208 74c47460bacf4fd68f2536580efb1480
msgid "pages_generator_finalized"
msgstr "pages_generator_finalized"
#: ../../plugins.rst:207 0bb615d8a6f643a3a1a9abac2ec4f712
#: ../../plugins.rst:209 b403e7f978c24d989d99587579f31d3c
msgid "pages_generator_init"
msgstr "pages_generator_init"
#: ../../plugins.rst:208 beddb5f81a62458b87c0703355a7b5a4
#: ../../plugins.rst:210 94e5184530c94cc48d00fd819fffd649
msgid "static_generate_context"
msgstr "static_generate_context"
#: ../../plugins.rst:209 8fe8895dcb464e11bb01657e975f1352
#: ../../plugins.rst:211 00ca2c730ad840f584d3f9dd30daf0cd
msgid "static_generate_preread"
msgstr "static_generate_preread"
#: ../../plugins.rst:213 44b14caddfd245c18cacd755fd0023e9
#: ../../plugins.rst:215 f8044e028ccd4d64954e24375a739cd2
msgid "Recipes"
msgstr "具体使用方法举例"
#: ../../plugins.rst:215 c24473f41cc84d028c99fa56af636037
#: ../../plugins.rst:217 0c441d12047240199025f2d3ac954167
msgid ""
"We eventually realised some of the recipes to create plugins would be "
"best shared in the documentation somewhere, so here they are!"
msgstr ""
"下面分享了一些创建插件的具体方法,请享用!"
msgstr "下面分享了一些创建插件的具体方法,请享用!"
#: ../../plugins.rst:219 96de26e8150e4339b3461d2dcc478cf3
#: ../../plugins.rst:221 bb96f2da7b3340cb9ed56ee1ad59796b
msgid "How to create a new reader"
msgstr "如何创建一个新的reader"
#: ../../plugins.rst:221 3f26c1183b814401b333bbd8528675d9
#: ../../plugins.rst:223 49dbbbd2c5ca4798a1b9d67b48630d36
msgid ""
"One thing you might want is to add support for your very own input "
"format. While it might make sense to add this feature in Pelican core, we"
" wisely chose to avoid this situation and instead have the different "
"readers defined via plugins."
msgstr ""
"你可能需要添加对输入文件格式的特殊支持。这似乎可以作为Pelican核心的一个功能"
"但我们选择避免将此功能放在核心中而是通过插件实现不同的reader。"
msgstr "你可能需要添加对输入文件格式的特殊支持。这似乎可以作为Pelican核心的一个功能但我们选择避免将此功能放在核心中而是通过插件实现不同的reader。"
#: ../../plugins.rst:226 8167dcbaa6864da3b2262a2a99e08a15
#: ../../plugins.rst:228 af8936c711204a0aa7c85835124065c5
msgid ""
"The rationale behind this choice is mainly that plugins are really easy "
"to write and don't slow down Pelican itself when they're not active."
msgstr ""
"做出这个决定主要是因为实现这样的格式支持插件非常容易,而且这样在不需要此功能时"
"也不会影响Pelican自身的速度。"
msgstr "做出这个决定主要是因为实现这样的格式支持插件非常容易而且这样在不需要此功能时也不会影响Pelican自身的速度。"
#: ../../plugins.rst:229 26c8185062964b52921860cfa2ce508c
#: ../../plugins.rst:231 11dac8bd71994c18a289086ec95a0273
msgid "No more talking — here is an example::"
msgstr "多说无益,下面是一个具体例子:"
#: ../../plugins.rst:265 ea51efb1925f45e79c87d6e5488cbbcd
#: ../../plugins.rst:267 f6bf903ae8de4ac183ecea699de568dc
msgid "Adding a new generator"
msgstr "添加新的generator"
#: ../../plugins.rst:267 9e04f17a5fa1488d82d3629edf8cdf3f
#: ../../plugins.rst:269 50d39b45550446a493a6d5d6eb971103
msgid ""
"Adding a new generator is also really easy. You might want to have a look"
" at :doc:`internals` for more information on how to create your own "
"generator."
msgstr ""
"添加一个generator也非常简单你可能会想要看一看 :doc:`internals` ,其中有关于"
"如何创建generator的内容。"
msgstr "添加一个generator也非常简单你可能会想要看一看 :doc:`internals` 其中有关于如何创建generator的内容。"
#: ../../plugins.rst:281 f4c92958e88a41a7a0deee697b48fc58
#: ../../plugins.rst:283 1b4bc8c2b02645dd81b06ffdbd759c36
msgid "Adding a new writer"
msgstr "添加新的writer"
#: ../../plugins.rst:283 188bf0e8a68446458ae525c67cfe098c
#: ../../plugins.rst:285 ac526121b895429d8412605bca594684
msgid ""
"Adding a writer will allow you to output additional file formats to disk,"
" or change how the existing formats are written to disk. Note that only "
"one writer will be active at a time, so be sure to either subclass the "
"built-in Writer, or completely re-implement it."
msgstr ""
"添加writer可以让你将其他文件格式输出到磁盘或者可以改变现有格式写入磁盘的方式。"
"请注意一次只能启用一个writer因此请确保继承了内置的Writer并且完全重新实现之。"
msgstr "添加writer可以让你将其他文件格式输出到磁盘或者可以改变现有格式写入磁盘的方式。请注意一次只能启用一个writer因此请确保继承了内置的Writer并且完全重新实现之。"
#: ../../plugins.rst:288 edb5d1fa15bc48859c2912ba7c344286
#: ../../plugins.rst:290 4335016710cd417ca9b8068cb7a45d51
msgid "Here is a basic example of how to set up your own writer::"
msgstr "下面是启用你的自定义writer的一个基本例子"
#: ../../plugins.rst:308 0df8f3318357472cbd72e17e1b5085b2
#: ../../plugins.rst:310 c65b371d4bf740c49dfe190407c9af69
msgid "Using Plugins to Inject Content"
msgstr "使用插件添加内容"
#: ../../plugins.rst:310 d0161dbe86c44111a6295259ec8cab54
#: ../../plugins.rst:312 9f180f86d09f43d7aff4607bb7deb6f1
msgid ""
"You can programmatically inject articles or pages using plugins. This can"
" be useful if you plan to fetch articles from an API, for example."
msgstr ""
"可以通过插件以可编程的方式添加文章或页面。如果你打算从某些API获取文章这就会很有用。"
msgstr "可以通过插件以可编程的方式添加文章或页面。如果你打算从某些API获取文章这就会很有用。"
#: ../../plugins.rst:313 5d5c41dbeb7243d4b497752771bc7858
#: ../../plugins.rst:315 a65dd6bb4d0e48438dcf6d545bfaa053
msgid ""
"Following is a simple example of how one can build a plugin that injects "
"a custom article, using the ``article_generator_pretaxonomy`` signal::"
msgstr ""
"下面是一个简单的示例,说明了如何使用 ``article_generator_pretaxonomy`` "
"信号构建一个添加自定义文章的插件:"
msgstr "下面是一个简单的示例,说明了如何使用 ``article_generator_pretaxonomy`` 信号构建一个添加自定义文章的插件:"

File diff suppressed because it is too large Load diff

View file

@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PELICAN 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-25 20:36+0800\n"
"POT-Creation-Date: 2024-11-07 16:25+0800\n"
"PO-Revision-Date: 2024-06-27 19:00+0800\n"
"Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
"Language: zh_CN\n"
@ -16,22 +16,22 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.15.0\n"
"Generated-By: Babel 2.16.0\n"
#: ../../tips.rst:2 415f61a654104cf4826423e3aa1d3807
#: ../../tips.rst:2 9c4618aaecd44b0d93537cb760e227fa
msgid "Tips"
msgstr "小技巧"
#: ../../tips.rst:4 1bc50144d85845f3a7f21f9ef87bba44
#: ../../tips.rst:4 f49ab5e1ef034ca29140bac3832e8e1c
msgid "Here are some tips about Pelican that you might find useful."
msgstr "以下是一些实用的小技巧。"
#: ../../tips.rst:7 ../../tips.rst:264 d9115f4b162d46e6aa89d56309c1ec41
#: e693dc009e5c466d99655b705223f300
#: ../../tips.rst:7 ../../tips.rst:309 95bea35d0347495bb551fe9486bcd29d
#: b64b7ed713b64f588ea7488c6d0b0441
msgid "Custom 404 Pages"
msgstr "自定义404页面"
#: ../../tips.rst:9 5c7cd70793f44d3c9fcf63779755d62b
#: ../../tips.rst:9 d59dc30de5954aa1abc7c46fbac596c6
msgid ""
"When a browser requests a resource that the web server cannot find, the "
"web server usually displays a generic \"File not found\" (404) error page"
@ -40,36 +40,34 @@ msgid ""
"article), such as this Markdown-formatted example stored in "
"``content/pages/404.md``::"
msgstr ""
"当浏览器请求的资源无法在服务器中找到时web服务器常常会显示一个通用的“File not "
"found 404”的错误页面这可能会不太美观。为了能使用一个与站点主题相匹配的404页面"
"(注意是页面而 **不是** 文章例如下面这个Markdown格式的例子将此文件存为了 "
"``content/pages/404.md`` "
"当浏览器请求的资源无法在服务器中找到时web服务器常常会显示一个通用的“File not found "
"404”的错误页面这可能会不太美观。为了能使用一个与站点主题相匹配的404页面注意是页面而 **不是** "
"文章例如下面这个Markdown格式的例子将此文件存为了 ``content/pages/404.md`` "
#: ../../tips.rst:22 cab28bb6b2a548a09f8cc6e4778f1a78
#: ../../tips.rst:22 416f9b3eeaac4af8bdc9f32b7cdcba39
msgid ""
"The next step is to configure your web server to display this custom page"
" instead of its default 404 page. For Nginx, add the following to your "
"configuration file's ``location`` block::"
msgstr ""
"接下来就是要配置web服务器使其显示此自定义页面而不是默认的404页面。例如对于Nginx"
"在配置文件的 ``location`` 块中添加下面的命令:"
"接下来就是要配置web服务器使其显示此自定义页面而不是默认的404页面。例如对于Nginx在配置文件的 ``location`` "
"块中添加下面的命令:"
#: ../../tips.rst:28 f8acbc4d00de4cfb8dfd9358a8168c14
#: ../../tips.rst:28 5d52fbcc9d9d4603b3f9d97360face10
msgid "For Apache::"
msgstr "对于Apache"
#: ../../tips.rst:32 3701d02f6dba4936a86a9fbb226261e8
#: ../../tips.rst:32 5413c6bcff6a41688ffcede94b9955e4
msgid ""
"For Amazon S3, first navigate to the ``Static Site Hosting`` menu in the "
"bucket settings on your AWS console. From there::"
msgstr ""
"对于Amazon S3实例先在控制台的设置中找到 ``Static Site Hosting`` ,并添加:"
msgstr "对于Amazon S3实例先在控制台的设置中找到 ``Static Site Hosting`` ,并添加:"
#: ../../tips.rst:38 4d111f7cca2e49828e343ff889847358
#: ../../tips.rst:38 9b02aa39367a4c33918bddef02d1788d
msgid "Publishing to GitHub Pages"
msgstr "发布到GitHub Pages"
#: ../../tips.rst:40 f7fa83b00f6d4dd58d6f119725474538
#: ../../tips.rst:40 ca3f1deb69a04d40a89576f580d63781
msgid ""
"If you use `GitHub <https://github.com/>`_ for your Pelican site you can "
"publish your site to `GitHub Pages <https://pages.github.com/>`_ for "
@ -80,14 +78,14 @@ msgid ""
"<https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-"
"github-pages-site>`_."
msgstr ""
"如果将Pelican站点放在了 `GitHub <https://github.com/>`_ 上,那么你就可以将站点"
"免费发布在 `GitHub Pages <https://pages.github.com/>`_ 上。如果是用户或组织的"
"站点,发布的地址为 ``https://<username>.github.io`` ;如果是某个项目的站点,"
"发布的地址则为 ``https://<username>.github.io/<repository>`` 。当然也可以 "
"`在GitHub Pages上使用自定义域名 <https://docs.github.com/en/pages/configuring-a-custom-"
"如果将Pelican站点放在了 `GitHub <https://github.com/>`_ 上,那么你就可以将站点免费发布在 `GitHub "
"Pages <https://pages.github.com/>`_ 上。如果是用户或组织的站点,发布的地址为 "
"``https://<username>.github.io`` ;如果是某个项目的站点,发布的地址则为 "
"``https://<username>.github.io/<repository>`` 。当然也可以 `在GitHub "
"Pages上使用自定义域名 <https://docs.github.com/en/pages/configuring-a-custom-"
"domain-for-your-github-pages-site>`_ 。"
#: ../../tips.rst:46 a3167f2a605d44288b83d66f052e8cdd
#: ../../tips.rst:46 5962c3cb4a0b41289d6b08b9edd2fdee
msgid ""
"There are `two ways to publish a site to GitHub Pages "
"<https://docs.github.com/en/pages/getting-started-with-github-"
@ -97,16 +95,16 @@ msgstr ""
"/getting-started-with-github-pages/configuring-a-publishing-source-for-"
"your-github-pages-site>`_ "
#: ../../tips.rst:48 b2f270c5a15d4e3e92331c3c37db25dd
#: ../../tips.rst:48 ad6f071b3cdc4529a41776f799347da0
msgid ""
"**Publishing from a branch:** run ``pelican`` locally and push the output"
" directory to a special branch of your GitHub repo. GitHub will then "
"publish the contents of this branch to your GitHub Pages site."
msgstr ""
"**从某一分支发布:** 在本地运行 ``pelican`` 后将输出文件夹push到GitHub仓库的"
"某一分支。GitHub就会将该分支的内容发布到GitHub Pages上。"
"**从某一分支发布:** 在本地运行 ``pelican`` "
"后将输出文件夹push到GitHub仓库的某一分支。GitHub就会将该分支的内容发布到GitHub Pages上。"
#: ../../tips.rst:51 4ffdb550d8bf468dbfe4d32dfcda21cd
#: ../../tips.rst:51 6237e147cf4142d9b172588964ec00d2
msgid ""
"**Publishing with a custom GitHub Actions workflow:** just push the "
"source files of your Pelican site to your GitHub repo's default branch "
@ -116,25 +114,24 @@ msgid ""
"your site's source files using GitHub's web interface and any changes "
"that you commit will be published."
msgstr ""
"**从自定义GitHub Actions工作流发布** 将内容源文件推送到GitHub仓库的默认分支"
"然后在GitHub Actions工作流中执行 ``pelican`` 以生成输出文件夹,最后将其发布到你"
"的GitHub Pages站点。此种方法下就无需在本地执行 ``pelican`` 命令了。甚至可以直接"
"在GitHub的网页中在线修改站点内容源文件。"
"**从自定义GitHub Actions工作流发布** 将内容源文件推送到GitHub仓库的默认分支然后在GitHub "
"Actions工作流中执行 ``pelican`` 以生成输出文件夹最后将其发布到你的GitHub Pages站点。此种方法下就无需在本地执行 "
"``pelican`` 命令了。甚至可以直接在GitHub的网页中在线修改站点内容源文件。"
#: ../../tips.rst:60 0e9c34ce1a5948098a5d0812eb8ac1b4
#: ../../tips.rst:60 f2655b8ab23147e58fd68e2385a7624a
msgid "Publishing a Project Site to GitHub Pages from a Branch"
msgstr "从某一分支发布项目站点到GitHub Pages"
#: ../../tips.rst:62 5190ebea8d8b4542ac9ecb98c297594e
#: ../../tips.rst:62 1a156c5a8019400d86a33ce306b521ac
msgid ""
"To publish a Pelican site as a Project Page you need to *push* the "
"content of the ``output`` dir generated by Pelican to a repository's "
"``gh-pages`` branch on GitHub."
msgstr ""
"要将Pelican站点发布为项目页面你需要将Pelican生成的 ``output`` 目录 "
"**push** 到GitHub仓库的 ``gh-pages`` 分支。"
"要将Pelican站点发布为项目页面你需要将Pelican生成的 ``output`` 目录 **push** 到GitHub仓库的 ``gh-"
"pages`` 分支。"
#: ../../tips.rst:66 e12298010e9745b59d60d31ae909fd4c
#: ../../tips.rst:66 22caeeba90b24dbe9f0305370de074fc
msgid ""
"The excellent `ghp-import <https://github.com/davisp/ghp-import>`_, which"
" can be installed with ``pip``, makes this process really easy."
@ -142,15 +139,14 @@ msgstr ""
"可通过 ``pip`` 安装的 `ghp-import <https://github.com/davisp/ghp-import>`_ "
"使这一步变得非常简单。"
#: ../../tips.rst:69 cd5a5847355846dd81a0ad37858358f2
#: ../../tips.rst:69 6ea08af050644b58ae5255dafb4f4d8b
msgid ""
"For example, if the source of your Pelican site is contained in a GitHub "
"repository, and if you want to publish that Pelican site in the form of "
"Project Pages to this repository, you can then use the following::"
msgstr ""
"例如当Pelican站点的源文件已经包含在GitHub仓库中时可以将其作为此仓库的项目页面"
msgstr "例如当Pelican站点的源文件已经包含在GitHub仓库中时可以将其作为此仓库的项目页面"
#: ../../tips.rst:77 18d3e7316a5a48acb337c3c67e94084c
#: ../../tips.rst:77 355b81e8a2194cf9b91bee0f4ee6dca9
msgid ""
"The ``ghp-import output`` command updates the local ``gh-pages`` branch "
"with the content of the ``output`` directory (creating the branch if it "
@ -158,37 +154,36 @@ msgid ""
"the remote ``gh-pages`` branch, effectively publishing the Pelican site."
msgstr ""
"``ghp-import output`` 命令会用 ``output`` 目录下的内容更新本地的 ``gh-pages`` "
"分支(如果此分支不存在则会先创建)。接着再用 ``git push origin gh-pages`` "
"命令更新远程分支 ``gh-pages`` 如此就能够发布Pelican站点了。"
"分支(如果此分支不存在则会先创建)。接着再用 ``git push origin gh-pages`` 命令更新远程分支 ``gh-"
"pages`` 如此就能够发布Pelican站点了。"
#: ../../tips.rst:84 cc8b9d96da674850b39373728000f722
#: ../../tips.rst:84 8a3fd725eba44fa99541376722601cce
msgid ""
"The ``github`` target of the Makefile (and the ``gh_pages`` task of "
"``tasks.py``) created by the ``pelican-quickstart`` command publishes the"
" Pelican site as Project Pages, as described above."
msgstr ""
"``pelican-quickstart`` 在Makefile文件中所生成的 ``github`` 目标(以及为 "
"``gh_pages`` 任务生成的 ``tasks.py`` 使得Pelican站点能像上面描述的那样被发布"
"为项目页面。"
"``pelican-quickstart`` 在Makefile文件中所生成的 ``github`` 目标(以及为 ``gh_pages`` "
"任务生成的 ``tasks.py`` 使得Pelican站点能像上面描述的那样被发布为项目页面。"
#: ../../tips.rst:89 41c7b129fd334796848c4d75404dbe81
#: ../../tips.rst:89 e8ebf23099ed45e7a65d23b9a7e4ccbd
msgid "Publishing a User Site to GitHub Pages from a Branch"
msgstr "从某一分支发布用户站点到GitHub Pages"
#: ../../tips.rst:91 b379f950927d484ba91fbe649a248cfe
#: ../../tips.rst:91 7dc8ae1992b7411d9d6db7cc4a0127cb
msgid ""
"To publish a Pelican site in the form of User Pages, you need to *push* "
"the content of the ``output`` dir generated by Pelican to the ``main`` "
"branch of your ``<username>.github.io`` repository on GitHub."
msgstr ""
"要以用户页面形式发布Pelican站点你需要将Pelican生成的 ``output`` 目录内容 "
"**push** 到 ``<username>.github.io`` 仓库的 ``master`` 分支上。"
"要以用户页面形式发布Pelican站点你需要将Pelican生成的 ``output`` 目录内容 **push** 到 "
"``<username>.github.io`` 仓库的 ``master`` 分支上。"
#: ../../tips.rst:95 6d1bd6c0ff25494e997c4efbdcd1d861
#: ../../tips.rst:95 da706340ef5f4d18bfb183596a4196c9
msgid "Again, you can take advantage of ``ghp-import``::"
msgstr "同样的,此处也可以使用 ``ghp-import`` "
#: ../../tips.rst:101 45fb7ba534af4f7d828e1630e591c02a
#: ../../tips.rst:101 61aa6f0d9fdf407682d3f781ae5475c6
msgid ""
"The ``git push`` command pushes the local ``gh-pages`` branch (freshly "
"updated by the ``ghp-import`` command) to the ``elemoine.github.io`` "
@ -197,21 +192,19 @@ msgstr ""
"``git push`` 命令将本地的 ``gh-pages`` 分支(此分支在刚刚通过 ``ghp-import`` "
"命令进行了更新push到了GitHub仓库 ``elemoine.github.io`` 的 ``master`` 分支。"
#: ../../tips.rst:107 b105e7dd1aef441896c0f59166808113
#: ../../tips.rst:107 f74afbf668a1472d901fe0a16472ab98
msgid ""
"To publish your Pelican site as User Pages, feel free to adjust the "
"``github`` target of the Makefile."
msgstr ""
"要将Pelican站点发布为用户页面可以根据需要修改Makefile中的 ``github`` 目标。"
msgstr "要将Pelican站点发布为用户页面可以根据需要修改Makefile中的 ``github`` 目标。"
#: ../../tips.rst:110 87a89a932eec40e8bfdd5c756f4d54fc
#: ../../tips.rst:110 d69dcdb58a4b4b38aa8b8bf8e4fd733a
msgid ""
"Another option for publishing to User Pages is to generate the output "
"files in the root directory of the project."
msgstr ""
"发布用户页面的另一种方法就是将输出文件生成在项目的根目录下。"
msgstr "发布用户页面的另一种方法就是将输出文件生成在项目的根目录下。"
#: ../../tips.rst:113 dab76a45349c432cb4b763484661ec2c
#: ../../tips.rst:113 4991892f24df40b982faf01ddb292175
msgid ""
"For example, your main project folder is ``<username>.github.io`` and you"
" can create the Pelican project in a subdirectory called ``Pelican``. "
@ -220,22 +213,21 @@ msgstr ""
"例如,项目的主文件夹是 ``<username>.github.io`` ,你可以在子目录 ``Pelican`` "
"中创建一个Pelican项目。然后你可以在这个 ``Pelican`` 文件夹中执行下面的命令:"
#: ../../tips.rst:119 7f13464c92f14cc18f8c00f7dae78f93
#: ../../tips.rst:119 ca5939f8c58b44b69ebfb2f953a4a73b
msgid ""
"Now you can push the whole project ``<username>.github.io`` to the main "
"branch of your GitHub repository::"
msgstr ""
"接着可以将整个项目 ``<username>.github.io`` push到GitHub仓库的master分支中"
msgstr "接着可以将整个项目 ``<username>.github.io`` push到GitHub仓库的master分支中"
#: ../../tips.rst:124 e82ff566e32b4696863aa04216aaf355
#: ../../tips.rst:124 54962439805d47abb121ca9454e7a4cc
msgid "(assuming origin is set to your remote repository)."
msgstr "此处假设远程仓库命名为origin。"
#: ../../tips.rst:127 1958522ba7c34537855505f1e64c7b43
#: ../../tips.rst:127 b3fe320a90904fbda8c7ed8c7bddbd6e
msgid "Publishing to GitHub Pages Using a Custom GitHub Actions Workflow"
msgstr "使用自定义GitHub Actions工作流将站点发布GitHub Pages中"
#: ../../tips.rst:129 19c47b80d248451facd8407bd960b527
#: ../../tips.rst:129 3b368bc0a307473dae560671fd9527be
msgid ""
"Pelican-powered sites can be published to GitHub Pages via a `custom "
"workflow "
@ -246,22 +238,21 @@ msgstr ""
"<https://github.com/getpelican/pelican/blob/main/.github/workflows/github_pages.yml>`_"
" ,你可以直接使用此工作流发布站点:"
#: ../../tips.rst:133 bdc132ef5b974d1eae684d8118e4d914
#: ../../tips.rst:133 a7b1be522b694d9a8beb186b4603a7aa
msgid ""
"Enable GitHub Pages in your repo: go to **Settings → Pages** and choose "
"**GitHub Actions** for the **Source** setting."
msgstr ""
"首先为仓库开启GitHub Pages **Settings → Pages** 中有个 **Source** 设置项,"
"将其选择为 **GitHub Actions** 。"
"首先为仓库开启GitHub Pages **Settings → Pages** 中有个 **Source** 设置项,将其选择为 "
"**GitHub Actions** 。"
#: ../../tips.rst:136 d7d197c176bd4127a75cfaf9dd29212b
#: ../../tips.rst:136 9cc114d8a6b44ff49fa7fecbdbcd012f
msgid ""
"Commit a ``.github/workflows/pelican.yml`` file to your repo with these "
"contents:"
msgstr ""
"往你的仓库中commit一个 ``.github/workflows/pelican.yml`` 文件,文件内容如下:"
msgstr "往你的仓库中commit一个 ``.github/workflows/pelican.yml`` 文件,文件内容如下:"
#: ../../tips.rst:155 656a2b783b6043f2ac26b1e7b342732e
#: ../../tips.rst:155 f7d029425d7047deae43e9506c7f4779
msgid ""
"You may want to replace the ``@main`` with the ID of a specific commit in"
" this repo in order to pin the version of the reusable workflow that "
@ -270,62 +261,63 @@ msgid ""
"you do this you might want to get Dependabot to send you automated pull "
"requests to update that commit ID whenever new versions of this workflow "
"are published, like so:"
msgstr "你可能想要将 ``@main`` 替换为这个仓库中某个特定commit的ID以便将你使用的"
"可重用工作流的版本固定下来,此时,可以使用 ``uses: getpelican/pelican/.github/workflows/"
"github_pages.yml@<COMMIT_ID>`` 。在这种情况下你可能想让Dependabot自动向你发送"
"PR以便在发布新版本的工作流时更新commit ID如下所示:"
msgstr ""
"你可能想要将 ``@main`` 替换为这个仓库中某个特定commit的ID以便将你使用的可重用工作流的版本固定下来此时可以使用 "
"``uses: "
"getpelican/pelican/.github/workflows/github_pages.yml@<COMMIT_ID>`` "
"。在这种情况下你可能想让Dependabot自动向你发送PR以便在发布新版本的工作流时更新commit ID如下所示:"
#: ../../tips.rst:172 0e2e10f42d6142e1b2f9d2251879ffad
#: ../../tips.rst:172 fd060b5d5d824ab8825b384d37872894
msgid ""
"See `GitHub's docs about using Dependabot to keep your actions up to date"
" <https://docs.github.com/en/code-security/dependabot/working-with-"
"dependabot/keeping-your-actions-up-to-date-with-dependabot>`_."
msgstr "请参阅 `GitHub文档 <https://docs.github.com/en/code-security/"
"dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-"
msgstr ""
"请参阅 `GitHub文档 <https://docs.github.com/en/code-security/dependabot"
"/working-with-dependabot/keeping-your-actions-up-to-date-with-"
"dependabot>`_ 了解如何使用Dependabot使您的action保持最新。"
#: ../../tips.rst:174 2475397adfbb48af9a1d16fc0a24d9b9
#: ../../tips.rst:174 1b862876e15c4fcd898c4d9b3ba616c5
msgid ""
"Go to the **Actions** tab in your repo "
"(``https://github.com/<username>/<repository>/actions``) and you should "
"see a **Deploy to GitHub Pages** action running."
msgstr ""
"选中仓库的 **Actions** 标签栏( ``https://github.com/<username>/<repository>"
"/actions`` ),此时你应该会看到已经有一个名为 **Deploy to GitHub Pages** 的"
"action正在运行。"
"选中仓库的 **Actions** 标签栏( "
"``https://github.com/<username>/<repository>/actions`` ),此时你应该会看到已经有一个名为 "
"**Deploy to GitHub Pages** 的action正在运行。"
#: ../../tips.rst:178 df30a15c460b442796f7f2007c283f32
#: ../../tips.rst:178 f8413793636140f9b017abad379b3429
msgid ""
"Once the action completes you should see your Pelican site deployed at "
"your repo's GitHub Pages URL: ``https://<username>.github.io`` for a user"
" or organization site or ``https://<username>.github.io/<repository>>`` "
"for a project site."
msgstr ""
"当此action执行完成就能够通过仓库的GitHub Pages地址 ``https://<username>."
"github.io`` 看到部署好了的用户或组织站点了,对于项目站点,可通过 ``https://"
"<username>.github.io/<repository>`` 访问。"
"当此action执行完成就能够通过仓库的GitHub Pages地址 ``https://<username>.github.io`` "
"看到部署好了的用户或组织站点了,对于项目站点,可通过 ``https://<username>.github.io/<repository>`` "
"访问。"
#: ../../tips.rst:183 f79963fcfd204f2780ff536516e6d407
#: ../../tips.rst:183 d792bb046c474f70aa98b2c16a5b1254
msgid "Notes:"
msgstr "注意事项:"
#: ../../tips.rst:185 3a2dc6a36d38454e85265ef35c5e8010
#: ../../tips.rst:185 89472d2b7231439faf9e51eda07d8323
msgid ""
"You don't need to set ``SITEURL`` or ``FEED_DOMAIN`` in your Pelican "
"settings: the workflow will set them correctly for you"
msgstr ""
"无需在Pelican配置文件中设置 ``SITEURL`` ,工作流会帮你进行设置。"
msgstr "无需在Pelican配置文件中设置 ``SITEURL`` ,工作流会帮你进行设置。"
#: ../../tips.rst:188 ea406746a7db49dfa10de025a3be4a31
#: ../../tips.rst:188 ea2b632160804a6e9bf1b4cecb7de716
msgid ""
"You don't need to commit your ``--output`` / ``OUTPUT_PATH`` directory "
"(``output/``) to git: the workflow will run ``pelican`` to build the "
"output directory for you on GitHub Actions"
msgstr ""
"无需commit ``--output`` 或 ``OUTPUT_PATH`` 所指定的目录( ``output/`` "
"工作流会自己执行 ``pelican`` 命令来构建输出目录。"
"无需commit ``--output`` 或 ``OUTPUT_PATH`` 所指定的目录( ``output/`` 工作流会自己执行 "
"``pelican`` 命令来构建输出目录。"
#: ../../tips.rst:192 a92a4068ac294a22ac80b1db68090634
#: ../../tips.rst:192 fd9fb772fba844f099cac781f2b0642f
msgid ""
"See `GitHub's docs about reusable workflows "
"<https://docs.github.com/en/actions/using-workflows/reusing-workflows>`_ "
@ -334,46 +326,45 @@ msgstr ""
"更多信息请参阅 `GitHub可重用工作流文档 <https://docs.github.com/en/actions/using-"
"workflows/reusing-workflows>`_ 。"
#: ../../tips.rst:195 1264d8a048aa4bd7878845ba2dac0d0d
#: ../../tips.rst:195 f9c527704af24f6da0b4229b7882a25b
msgid ""
"A number of optional inputs can be added to the ``with:`` block when "
"calling the workflow, for example:"
msgstr ""
"有一些可选输入可以添加到工作流的 ``with:`` 块中:"
msgstr "有一些可选输入可以添加到工作流的 ``with:`` 块中:"
#: ../../tips.rst:206 3faf65d7567244e3bc65a15dc84cf247
#: ../../tips.rst:206 956f5bae1fc64096acd2a2540a29004c
msgid "Here's the complete list of workflow inputs:"
msgstr "下面是工作流可用输入参数的完整列表:"
#: ../../tips.rst:209 37919ce86ddb4546bd191440ba1c5b9a
#: ../../tips.rst:209 eb37c894d7bc4278ab1a92e3b82c5603
msgid "Name"
msgstr "名称"
#: ../../tips.rst:209 645ae6a27c7b40ecbc795dbd698b0649
#: ../../tips.rst:209 446faf9e7d544e6aa47d4a1eca506c01
msgid "Required"
msgstr "是否必需"
#: ../../tips.rst:209 18917f8f278440e38882a4f1ca62fc8f
#: ../../tips.rst:209 de96e4f5cd09488296f97f569fe1fb90
msgid "Description"
msgstr "描述"
#: ../../tips.rst:209 99be24eafb6d43578e6eabba25f568fe
#: ../../tips.rst:209 181bbfff09144f5b9c241b2fc79c989d
msgid "Type"
msgstr "值的类型"
#: ../../tips.rst:209 24860d0693b84e6c9297f8733b338824
#: ../../tips.rst:209 c3d44d1e7be6421a83bae2f5dc6e578f
msgid "Default"
msgstr "默认值"
#: ../../tips.rst:211 7e9bb7ea151c4e8c99116dd4decbe3c1
#: ../../tips.rst:211 305d9d73681b4c6c80161cc906d60bbd
msgid "``settings``"
msgstr "``settings``"
#: ../../tips.rst:211 647c4173846f4057920030c8f774d5ea
#: ../../tips.rst:211 dbe6210f19914ae3b11e4caec7a945f0
msgid "Yes"
msgstr "是"
#: ../../tips.rst:211 05c57822d0a249de9718a9a3c56e9e56
#: ../../tips.rst:211 bbd2306b324d4b5eae513cb7a7683286
msgid ""
"The path to your Pelican settings file (``pelican``'s ``--settings`` "
"option), for example: ``\"publishconf.py\"``"
@ -383,26 +374,27 @@ msgstr ""
#: ../../tips.rst:211 ../../tips.rst:216 ../../tips.rst:223 ../../tips.rst:227
#: ../../tips.rst:231 ../../tips.rst:237 ../../tips.rst:243
#: 4e21f78e86f049048a800ddd5c51e230 618fd4eb66ff45b29c98df87b145613c
#: 93083ab6eb974293820f40d16349c100 9684f50652484820b924109f31418cd7
#: 9df48660f1a84fe1af952256c7b58aec cef3fc9239d941969fda711c74994d8c
#: d09fff93593844cfbb0b270b4cd74193
#: 073e18d8ae29406eb05040d4e3a9ae60 7d43e6cfb091410ebec7464da05b61b4
#: 8837cc8935f148fb80f05cc5d3d53629 b2da1f7640f948039230cd835c49accd
#: bfe3d052cdc443bb81fed82e77acf3c1 c93816e00a254ef69c69f05833e8762b
#: ee35302c7e034070af1d234ab919c32a
msgid "string"
msgstr "string"
#: ../../tips.rst:216 f867df810054493f9d6be16271822ddb
#: ../../tips.rst:216 4eab6faa96244f13a09754112a783f2f
msgid "``requirements``"
msgstr "``requirements``"
#: ../../tips.rst:216 ../../tips.rst:223 ../../tips.rst:227 ../../tips.rst:231
#: ../../tips.rst:237 ../../tips.rst:243 019e197dd56b44229549da7a2421ce37
#: 636f76c7f1ca4c61bcea4bbe39a4eb1f 671a0ff87e294e7ab0ac8cdf70fdfe1d
#: 848f43cf99c447a595f4760e2cf25f2b b425d772694640d0a7bae06c236fa1a2
#: d145c924e4f348f5ad24b51286ce61e6
#: ../../tips.rst:237 ../../tips.rst:243 ../../tips.rst:249
#: 197d6ee11fce4a50996a0c458cfdbdad 2086d667b9b1475cb0f002924cdfde12
#: 25e940621f5b48c9af487d898d7f93cf 5664232c9fdd46c7b8278b8ecef8e3b1
#: 6693126a0da74c61b67e14ca8e535ec3 7f8a93a2048140748fa73537bfae2a54
#: 85fd40a29f31490bb23b20f05e574aaa
msgid "No"
msgstr "否"
#: ../../tips.rst:216 0d5ee9c193994b2cac7757e881f01a42
#: ../../tips.rst:216 9d5bdd70e7da4794805180cc758ebe37
msgid ""
"The Python requirements to install, for example to enable markdown and "
"typogrify use: ``\"pelican[markdown] typogrify\"`` or if you have a "
@ -411,138 +403,194 @@ msgstr ""
"需要安装的Python模块例如要开启markdown和typogrify可指定 ``\"pelican[markdown] "
"typogrify\"`` 或者可以指定一个requirements文件 ``\"-r requirements.txt\"`` "
#: ../../tips.rst:216 67298d60de17486dbc1b6841f2c433b9
#: ../../tips.rst:216 03ad0b322a714032bcce9f56ce66318d
msgid "``\"pelican\"``"
msgstr "``\"pelican\"``"
#: ../../tips.rst:223 219a8d185ac440329e8aa7306e55e708
#: ../../tips.rst:223 e568553782b443dbacecaa7ded4c391c
msgid "``output-path``"
msgstr "``output-path``"
#: ../../tips.rst:223 21a3530e340349afa64d7eb69b393c98
#: ../../tips.rst:223 2920ae9de5a64ae1ad82bd2287fa7c1e
msgid "Where to output the generated files (``pelican``'s ``--output`` option)"
msgstr "生成文件的输出位置(会被用于 ``pelican`` 命令的 ``--output`` 选项)"
#: ../../tips.rst:223 dea97da0dfc24941b8850d1d26ea3cd3
#: ../../tips.rst:223 41b90747f0954a5799c8baf4a59d99fd
msgid "``\"output/\"``"
msgstr "``\"output/\"``"
#: ../../tips.rst:227 688ac4687d7841629137bf97ce97deee
#: ../../tips.rst:227 e2cc62185182463abc5140244a808e6d
msgid "``theme``"
msgstr "``theme``"
#: ../../tips.rst:227 2c2e6b6d8a6044c0ba64d00ea1b12d40
#: ../../tips.rst:227 cd3b78d03dcd4554a8ce10a873f5ff9f
msgid ""
"The GitHub repo URL of a custom theme to use, for example: "
"``\"https://github.com/seanh/sidecar.git\"``"
msgstr ""
"要使用的自定义主题的GitHub仓库URL例如 ``\"https://github.com/seanh/"
"sidecar.git\"``"
msgstr "要使用的自定义主题的GitHub仓库URL例如 ``\"https://github.com/seanh/sidecar.git\"``"
#: ../../tips.rst:227 bd63884f7e60412d9a6cccc5da9c47ac
#: ../../tips.rst:227 d94f331173334fb2a84b1caadffb72df
msgid "``\"\"``"
msgstr "``\"\"``"
#: ../../tips.rst:231 9527d9e89d704210baff0bb6e3e23b20
#: ../../tips.rst:231 44ceb2743481486b95c1c739d543f15d
msgid "``python``"
msgstr "``python``"
#: ../../tips.rst:231 1aa44193e62647c0ba275507ea84b42c
#: ../../tips.rst:231 4b5cddab44d24c7c8560e16991b784c7
msgid ""
"The version of Python to use to build the site, for example: ``\"3.12\"``"
" (to use the most recent version of Python 3.12, this is faster) or "
"``\"3.12.1\"`` (to use an exact version, slower)"
msgstr ""
"构建站点时使用的Python版本例如 ``\"3.12\"`` 或 ``\"3.12.1\"``"
msgstr "构建站点时使用的Python版本例如 ``\"3.12\"`` 或 ``\"3.12.1\"``"
#: ../../tips.rst:231 d182ae2dd44c482fb3f2373a7d97087c
#: ../../tips.rst:231 919c0e36e8ff40bcbcc4480081b49ce5
msgid "``\"3.12\"``"
msgstr "``\"3.12\"``"
#: ../../tips.rst:237 dc65b4e578e24d179c38066871c2c572
#: ../../tips.rst:237 842af56c539f4a74a97c7a5b1525eb35
msgid "``siteurl``"
msgstr "``siteurl``"
#: ../../tips.rst:237 5909de5d60224c7b875753f88fd13296
#: ../../tips.rst:237 7fc0777d6e174d6f8d757926a61aa3c8
msgid ""
"The base URL of your web site (Pelican's ``SITEURL`` setting). If not "
"passed this will default to the URL of your GitHub Pages site, which is "
"correct in most cases."
msgstr ""
"站点的基URL会用于配置项 ``SITEURL`` 。若未指定默认值为GitHub Pages站点"
"的URL这适用于大部分情况。"
msgstr "站点的基URL会用于配置项 ``SITEURL`` 。若未指定默认值为GitHub Pages站点的URL这适用于大部分情况。"
#: ../../tips.rst:237 ../../tips.rst:243 0c0b86aa4b984615afb3564b76e379ff
#: c7ddd6347a7f4467b31aaa8f4d4a2309
#: ../../tips.rst:237 ../../tips.rst:243 082f65333e224d71817b82b1e4f515c4
#: 3d786e828a4745db849bdb8f47738db8
msgid "The URL of your GitHub Pages site."
msgstr "GitHub Pages站点的URL"
#: ../../tips.rst:243 af7d2b52c5504ac2b69490a18d14f80f
#: ../../tips.rst:243 e5adb69f985547b7b3cc2bd3f31d4cc3
msgid "``feed_domain``"
msgstr "``feed_domain``"
#: ../../tips.rst:243 2cc126862a8047c286381aa258aad013
#: ../../tips.rst:243 c88f037c9f1f4148bef6347228257f7d
msgid ""
"The domain to be prepended to feed URLs (Pelican's ``FEED_DOMAIN`` "
"setting). If not passed this will default to the URL of your GitHub Pages"
" site, which is correct in most cases."
msgstr ""
"订阅源URL前要附加的域名会用于配置项 ``FEED_DOMAIN`` 。若未指定,默认值为"
"GitHub Pages站点的URL这适用于大部分情况。"
"订阅源URL前要附加的域名会用于配置项 ``FEED_DOMAIN`` 。若未指定,默认值为GitHub "
"Pages站点的URL这适用于大部分情况。"
#: ../../tips.rst:252 b86ab8a1fa24447d99becc592411010e
#: ../../tips.rst:249 358c5aa434cd4ad09beab02df88413d5
msgid "``deploy``"
msgstr "``deploy``"
#: ../../tips.rst:249 b8748aeace5a448d9382e225be98f90c
msgid ""
"This is used to determine whether you will deploy the site or not to "
"GitHub Pages. This is most useful if you want to test a change to your "
"website in a pull request before deploying those change."
msgstr "此项配置用于表示是否要将站点部署至GitHub Pages。当对站点做了更改并且在正式部署前进行测试就可以用到此项。"
#: ../../tips.rst:249 034006b9b71b4cb486f230b8aad873ce
msgid "bool"
msgstr "bool"
#: ../../tips.rst:249 078ac613a8b74703af98c75bb5a007c1
msgid "``true``"
msgstr "``true``"
#: ../../tips.rst:257 e63cf881e3204be8b52ee5d8635ba4cf
msgid "Testing Your Build in a GitHub Pull Request"
msgstr "在Github拉取请求时进行测试"
#: ../../tips.rst:259 a2f6bd3420eb46a08f54efda35a6eaf4
msgid ""
"If you want to test your build in a pull request before deploying to "
"GitHub, your workflow might look something like this:"
msgstr "如果想在正式部署到 GitHub 前在PR中进行测试下面是一个可用的 workflow 示例"
#: ../../tips.rst:288 84393693279741efa82c5ee6b27cbd28
msgid ""
"The ``on`` section of the workflow defines the events that will trigger "
"the workflow. In this example, the workflow will run on pushes to the "
"main branch, pull requests to the main branch, and manual runs of the "
"workflow."
msgstr "工作流的 ``on`` 部分定义了工作流的触发器。在此示例中工作流将在main分支收到push、有PR提起到主分支以及"
"手动运行工作流时执行。"
#: ../../tips.rst:290 cd3c13b2af974a32aa4291d07fc11e9c
msgid ""
"``workflow_dispatch`` defines the deploy boolean to be true by default. "
"This means that if you run the workflow manually, it will deploy the "
"site."
msgstr "``workflow_dispatch`` 将 deploy 的默认值设为 true。也就是说当手动运行工作流时更改的内容就会正式部署。"
#: ../../tips.rst:292 5402cd211d5b4aa8a244c916bb381a5b
msgid ""
"The ``deploy`` input for the job is using a set of standard GitHub "
"workflow variables to control when ``deploy`` will either be true or "
"false (you can customize this to your needs)."
msgstr "job中的 ``deploy`` 使用了一些 GitHub workflow 变量来计算 ``deploy`` 值为 true 还是 false您可以根据需要自定义。"
#: ../../tips.rst:294 d084908e3a0749f0b802b43626cfe2c4
msgid ""
"In this example, the ``deploy`` will be true if the event is a push to "
"the main branch (or merging into main from a PR) or a manual run of the "
"workflow. If the event is a pull request, the ``deploy`` will be false "
"and it will only build an artifact for the site."
msgstr "在此示例中,如果触发事件是推送到主分支(或从 PR 合并到主分支)或手动运行工作流,则 deploy 将为 true"
"如果触发事件只是Pull Request则 ``deploy`` 将为 false并且此时只会为站点构建一个artifact。"
#: ../../tips.rst:297 85e70fc3faa04208979f7bbe92b025ef
msgid "\"Insecure content\" warnings from browsers"
msgstr "浏览器报“不安全的内容Insecure content”警告"
#: ../../tips.rst:254 c81d5f8889c14a069e55fe7472a238f2
#: ../../tips.rst:299 34f7075cf31f416da2aeb529c616d97d
msgid ""
"If your site uses ``https://`` and is broken because the browser is "
"blocking network requests (for example for CSS files) due to \"insecure "
"content\" this may be because GitHub Pages is generating ``http://`` URLs"
" for your site."
msgstr ""
"当站点使用 ``https://`` 时,可能会损坏,无法正常显示,这是由于浏览器阻拦了一些"
"对“不安全内容”的网络请求。可能的原因之一是GitHub Pages给你的站点生成了 ``http://`` "
"URL。"
"当站点使用 ``https://`` "
"时,可能会损坏,无法正常显示,这是由于浏览器阻拦了一些对“不安全内容”的网络请求。可能的原因之一是GitHub Pages给你的站点生成了 "
"``http://`` URL。"
#: ../../tips.rst:258 2a53f882b7e645149d18ce81757b9758
#: ../../tips.rst:303 47271df82577424c8e2c31a9e76a553a
msgid ""
"To fix this go into your site repo's settings and enable the **Enforce "
"HTTPS** setting: go to **Settings → Pages** and check **Enforce HTTPS**. "
"Then re-run the workflow to re-deploy your site. Alternatively, you can "
"use the workflow's ``siteurl`` and ``feed_domain`` settings."
msgstr ""
"要想解决这一问题,需要为站点所在仓库开启 **强制使用HTTPS** :点击 **Settings → Pages** "
"并在其中勾选 **Enforce HTTPS** ,接着再重新执行工作流以重新部署站点。也可以尝试"
"通过配置 ``siteurl`` 与 ``feed_domain`` 解决问题。"
"要想解决这一问题,需要为站点所在仓库开启 **强制使用HTTPS** :点击 **Settings → Pages** 并在其中勾选 "
"**Enforce HTTPS** ,接着再重新执行工作流以重新部署站点。也可以尝试通过配置 ``siteurl`` 与 "
"``feed_domain`` 解决问题。"
#: ../../tips.rst:266 483cbd21e61841d983e2ecc8bc3006bc
#: ../../tips.rst:311 e69189ef4a8440fb8940d8012b4f19d6
msgid ""
"GitHub Pages will display the custom 404 page described above, as noted "
"in the relevant `GitHub docs "
"<https://help.github.com/articles/custom-404-pages/>`_."
msgstr ""
"如果按前述进行配置GitHub Pages是能够正确显示自定义的404页面的相关内容在 "
"`GitHub的文档中 <https://help.github.com/articles/custom-404-pages/>`_ 也有提到。"
"如果按前述进行配置GitHub Pages是能够正确显示自定义的404页面的相关内容在 `GitHub的文档中 "
"<https://help.github.com/articles/custom-404-pages/>`_ 也有提到。"
#: ../../tips.rst:270 6b54e9c354f34e1f9a5a3f50d96b98c3
#: ../../tips.rst:315 1b8c2457f44a4d61a033363830b8bd90
msgid "Update your site on each commit"
msgstr "在每次commit后都更新站点"
#: ../../tips.rst:272 2e83c0c761c94f35ae3056634d8f1552
#: ../../tips.rst:317 476dbdb670924c02a962e78d6a7854c1
msgid ""
"To automatically update your Pelican site on each commit, you can create "
"a post-commit hook. For example, you can add the following to "
"``.git/hooks/post-commit``::"
msgstr ""
"要想在每次commit后自动更新Pelican站点你可以创建一个post-commit钩子。例如"
"可以将下面的内容保存为 ``.git/hooks/post-commit`` "
"要想在每次commit后自动更新Pelican站点你可以创建一个post-commit钩子。例如可以将下面的内容保存为 "
"``.git/hooks/post-commit`` "
#: ../../tips.rst:279 528589366e634f15bb0a702969715286
#: ../../tips.rst:324 36dc5f05eaf84573acada36c59d8d2fc
msgid "Copy static files to the root of your site"
msgstr "将静态文件拷贝到站点根目录"
#: ../../tips.rst:281 dc4267653ef04722a0583915c05b6c88
#: ../../tips.rst:326 4a0722ad68e944ee80e6378259cc1dd6
msgid ""
"To use a `custom domain <https://help.github.com/articles/setting-up-a"
"-custom-domain-with-pages>`_ with GitHub Pages, you need to put the "
@ -557,11 +605,11 @@ msgstr ""
")添加到站点根目录的 ``CNAME`` 文件中。为此,请创建 ``content/extra/`` 目录,并在里面添加一个 ``CNAME`` "
"文件。然后使用Pelican的 ``STATIC_PATHS`` 来告诉Pelican将此文件复制到输出目录"
#: ../../tips.rst:292 5fcdc283f55f4d8ca121cb6438c67a36
#: ../../tips.rst:337 8ad906848762400d9e2462034d151a16
msgid "Note: use forward slashes, ``/``, even on Windows."
msgstr "请注意:务必使用正斜杠 ``/`` 在Windows上也是。"
#: ../../tips.rst:294 326a40a1536c462ea4974ce4b560f54c
#: ../../tips.rst:339 7b109f4944064382babc9158567c8e82
msgid ""
"You can also use the ``EXTRA_PATH_METADATA`` mechanism to place a "
"``favicon.ico`` or ``robots.txt`` at the root of any site."
@ -569,18 +617,17 @@ msgstr ""
"利用 ``EXTRA_PATH_METADATA`` 机制,你可以将 ``favicon.ico`` 或 ``robots.txt`` "
"也拷贝到站点的根目录下。"
#: ../../tips.rst:298 4e589caa6f17438aae1d1a12819c6ef2
#: ../../tips.rst:343 678eea0644b5400496ad9173d05368d5
msgid "How to add YouTube or Vimeo Videos"
msgstr "如何添加YouTube或Vimeo视频"
#: ../../tips.rst:300 5f60f033a7084739af5ef0dce5b91197
#: ../../tips.rst:345 ca57b327dd6b432d82cdc91193bde6bb
msgid ""
"The easiest way is to paste the embed code of the video from these sites "
"directly into your source content."
msgstr ""
"最简单的方法是将这些网站的视频嵌入代码直接粘贴到您的源内容文件中。"
msgstr "最简单的方法是将这些网站的视频嵌入代码直接粘贴到您的源内容文件中。"
#: ../../tips.rst:303 5446d02bebc241e88cc30b484799696c
#: ../../tips.rst:348 0a4f27e2edbe494ab52f73595646986e
msgid ""
"Alternatively, you can also use Pelican plugins like ``liquid_tags``, "
"``pelican_youtube``, or ``pelican_vimeo`` to embed videos in your "
@ -589,45 +636,42 @@ msgstr ""
"或者,您还可以使用例如 ``liquid_tags`` 、``pelican_youtube`` 或 ``pelican_vimeo`` "
"等Pelican插件将视频嵌入。"
#: ../../tips.rst:306 c871fab4a3424b0dba84c1af24f6405f
#: ../../tips.rst:351 e73517b72da347738421784b776b1f1c
msgid ""
"Moreover, markup languages like reST and Markdown have plugins that let "
"you embed videos in the markup. You can use `reST video directive "
"<https://gist.github.com/dbrgn/2922648>`_ for reST or `mdx_video plugin "
"<https://github.com/italomaia/mdx-video>`_ for Markdown."
msgstr ""
"此外像reST和 Markdown这样的标记语言都有对应插件可以让你在其中嵌入视频。"
"可以使用 `reST的视频指令 <https://gist.github.com/dbrgn/2922648>`_ 或者 "
"`Markdown的mdx_video插件 <https://github.com/italomaia/mdx-video>`_ 。"
"此外像reST和 Markdown这样的标记语言都有对应插件可以让你在其中嵌入视频。可以使用 `reST的视频指令 "
"<https://gist.github.com/dbrgn/2922648>`_ 或者 `Markdown的mdx_video插件 "
"<https://github.com/italomaia/mdx-video>`_ 。"
#: ../../tips.rst:313 569b7609cb9d412e942001da7c4a704c
#: ../../tips.rst:358 b9d27cda716048b2ab7c13646d7faf09
msgid "Develop Locally Using SSL"
msgstr "在本地使用SSL进行开发"
#: ../../tips.rst:315 e66f6f1cacc4466682461d251aedb929
#: ../../tips.rst:360 50df9ec072aa47eabbae132fd8f5cb68
msgid "Here's how you can set up your local pelican server to support SSL."
msgstr "以下描述了如何在本地Pelican服务器上配置SSL。"
#: ../../tips.rst:317 138c34c1b6804246b79fda266a1fd937
#: ../../tips.rst:362 9b5045375a874c4d9c29f7109f05c539
msgid ""
"First, create a self-signed certificate and key using ``openssl`` (this "
"creates ``cert.pem`` and ``key.pem``)::"
msgstr ""
"首先,通过 ``openssl`` 创建自签名的证书和密钥,这会生成 ``cert.pem`` 和 "
"``key.pem`` 文件:"
msgstr "首先,通过 ``openssl`` 创建自签名的证书和密钥,这会生成 ``cert.pem`` 和 ``key.pem`` 文件:"
#: ../../tips.rst:321 ac189182bc694bcaa94cd935311f4492
#: ../../tips.rst:366 2f1cfa536fc540f69d671f8a118769d7
msgid ""
"And use this command to launch the server (the server starts within your "
"``output`` directory)::"
msgstr ""
"接着使用下面的命令来开启服务器(此服务器会在 ``output`` 目录下开启):"
msgstr "接着使用下面的命令来开启服务器(此服务器会在 ``output`` 目录下开启):"
#: ../../tips.rst:325 88a33744d69f4f5bbc4a43024c43d3a0
#: ../../tips.rst:370 029ea2b0e4fe4b0f814158ae33e3a8ff
msgid "If you are using ``develop-server.sh``, add this to the top::"
msgstr "如果你使用的是 ``develop-server.sh`` 脚本,在脚本的开头添加:"
#: ../../tips.rst:330 9a783977fe814657b8590185af281b1e
#: ../../tips.rst:375 c2784fdd9fdb433799d57f903d0e49d8
msgid "and modify the ``pelican.server`` line as follows::"
msgstr "然后修改按照下述修改 ``pelican.server`` 一行:"

View file

@ -94,12 +94,14 @@ which you map the signals to your plugin logic. Let's take a simple example::
your ``register`` callable or they will be garbage-collected before the
signal is emitted.
If multiple plugins connect to the same signal, plugins will be executed in the
order they are connected. With ``PLUGINS`` setting, order will be as defined in
the setting. If you rely on auto-discovered namespace plugins, no ``PLUGINS``
setting, they will be connected in the same order they are discovered (same
order as ``pelican-plugins`` output). If you want to specify the order
explicitly, disable auto-discovery by defining ``PLUGINS`` in the desired order.
If multiple plugins connect to the same signal, plugins will be invoked in the
order they are registered. When the ``PLUGINS`` setting is defined, plugin
invocation order will be the order in which the plugins are listed in the
``PLUGINS`` setting. If you rely on auto-discovered namespace plugins and have
no ``PLUGINS`` setting defined, plugins will be invoked in the same order that
they are discovered (the same order as listed in the output of the
``pelican-plugins`` command). If you want to specify the order explicitly,
disable auto-discovery by defining ``PLUGINS`` in the desired order.
Namespace plugin structure
--------------------------

File diff suppressed because it is too large Load diff

View file

@ -246,7 +246,52 @@ Here's the complete list of workflow inputs:
| | | your GitHub Pages site, which is correct | | |
| | | in most cases. | | |
+------------------+----------+--------------------------------------------+--------+---------------+
| ``deploy`` | No | This is used to determine whether you will | bool | ``true`` |
| | | deploy the site or not to GitHub Pages. | | |
| | | This is most useful if you want to test a | | |
| | | change to your website in a pull request | | |
| | | before deploying those change. | | |
+------------------+----------+--------------------------------------------+--------+---------------+
Testing Your Build in a GitHub Pull Request
"""""""""""""""""""""""""""""""""""""""""""
If you want to test your build in a pull request before deploying to GitHub, your workflow might look something like this:
.. code-block:: yaml
name: Build and Deploy Site
on:
push:
branches: ["main"]
pull_request:
branches: ["main"]
workflow_dispatch:
inputs:
deploy:
required: false
default: true
description: "Whether to deploy the site. If checked, then build the site and deploy it. If not checked, then just test that the site builds successfully but don't deploy anything."
type: boolean
jobs:
deploy:
uses: "getpelican/pelican/.github/workflows/github_pages.yml@main"
permissions:
id-token: write
contents: read
pages: write
with:
settings: "publishconf.py"
requirements: "-r requirements.txt"
deploy: ${{ (github.event_name == 'workflow_dispatch' && inputs.deploy == true) || (github.event_name == 'push' && github.ref_type == 'branch' && github.ref_name == github.event.repository.default_branch) }}
The ``on`` section of the workflow defines the events that will trigger the workflow. In this example, the workflow will run on pushes to the main branch, pull requests to the main branch, and manual runs of the workflow.
``workflow_dispatch`` defines the deploy boolean to be true by default. This means that if you run the workflow manually, it will deploy the site.
The ``deploy`` input for the job is using a set of standard GitHub workflow variables to control when ``deploy`` will either be true or false (you can customize this to your needs).
In this example, the ``deploy`` will be true if the event is a push to the main branch (or merging into main from a PR) or a manual run of the workflow. If the event is a pull request, the ``deploy`` will be false and it will only build an artifact for the site.
"Insecure content" warnings from browsers
"""""""""""""""""""""""""""""""""""""""""

View file

@ -252,6 +252,7 @@ class Pelican:
class PrintSettings(argparse.Action):
def __call__(self, parser, namespace, values, option_string):
del option_string # Unused argument
init_logging(name=__name__)
try:
@ -287,6 +288,7 @@ class PrintSettings(argparse.Action):
class ParseOverrides(argparse.Action):
def __call__(self, parser, namespace, values, option_string=None):
del parser, option_string # Unused arguments
overrides = {}
for item in values:
try:
@ -402,8 +404,7 @@ def parse_arguments(argv=None):
"--autoreload",
dest="autoreload",
action="store_true",
help="Relaunch pelican each time a modification occurs"
" on the content files.",
help="Relaunch pelican each time a modification occurs on the content files.",
)
parser.add_argument(
@ -446,8 +447,7 @@ def parse_arguments(argv=None):
choices=("errors", "warnings"),
default="",
help=(
"Exit the program with non-zero status if any "
"errors/warnings encountered."
"Exit the program with non-zero status if any errors/warnings encountered."
),
)

View file

@ -1,3 +1,4 @@
import gzip
import hashlib
import logging
import os
@ -22,8 +23,6 @@ class FileDataCacher:
self._cache_path = os.path.join(self.settings["CACHE_PATH"], cache_name)
self._cache_data_policy = caching_policy
if self.settings["GZIP_CACHE"]:
import gzip
self._cache_open = gzip.open
else:
self._cache_open = open

View file

@ -4,9 +4,8 @@ import locale
import logging
import os
import re
from datetime import timezone
from html import unescape
from typing import Any, Dict, Optional, Set, Tuple
from typing import Any, Optional
from urllib.parse import ParseResult, unquote, urljoin, urlparse, urlunparse
try:
@ -47,7 +46,7 @@ class Content:
"""
default_template: Optional[str] = None
mandatory_properties: Tuple[str, ...] = ()
mandatory_properties: tuple[str, ...] = ()
@deprecated_attribute(old="filename", new="source_path", since=(3, 2, 0))
def filename():
@ -56,10 +55,10 @@ class Content:
def __init__(
self,
content: str,
metadata: Optional[Dict[str, Any]] = None,
metadata: Optional[dict[str, Any]] = None,
settings: Optional[Settings] = None,
source_path: Optional[str] = None,
context: Optional[Dict[Any, Any]] = None,
context: Optional[dict[Any, Any]] = None,
):
if metadata is None:
metadata = {}
@ -226,7 +225,7 @@ class Content:
)
@property
def url_format(self) -> Dict[str, Any]:
def url_format(self) -> dict[str, Any]:
"""Returns the URL, formatted with the proper values"""
metadata = copy.copy(self.metadata)
path = self.metadata.get("path", self.get_relative_source_path())
@ -343,8 +342,7 @@ class Content:
value.geturl(),
extra={
"limit_msg": (
"Other resources were not found "
"and their urls not replaced"
"Other resources were not found and their urls not replaced"
)
},
)
@ -358,8 +356,9 @@ class Content:
origin = joiner(siteurl, Author(path, self.settings).url)
else:
logger.warning(
"Replacement Indicator '%s' not recognized, skipping replacement",
"Replacement Indicator %r not recognized in %r, skipping replacement",
what,
origin,
)
# keep all other parts, such as query, fragment, etc.
@ -396,7 +395,7 @@ class Content:
hrefs = self._get_intrasite_link_regex()
return hrefs.sub(lambda m: self._link_replacer(siteurl, m), content)
def get_static_links(self) -> Set[str]:
def get_static_links(self) -> set[str]:
static_links = set()
hrefs = self._get_intrasite_link_regex()
for m in hrefs.finditer(self._content):
@ -432,7 +431,7 @@ class Content:
return self.get_content(self.get_siteurl())
@memoized
def get_summary(self, siteurl: str) -> str:
def get_summary(self, _siteurl: str) -> str:
"""Returns the summary of an article.
This is based on the summary metadata if set, otherwise truncate the
@ -450,7 +449,7 @@ class Content:
return content
return truncate_html_words(
self.content,
content,
self.settings["SUMMARY_MAX_LENGTH"],
self.settings["SUMMARY_END_SUFFIX"],
)
@ -553,6 +552,7 @@ class SkipStub(Content):
def __init__(
self, content, metadata=None, settings=None, source_path=None, context=None
):
del content, metadata, settings, context # Unused arguments
self.source_path = source_path
def is_valid(self):
@ -592,7 +592,7 @@ class Article(Content):
if self.date.tzinfo is None:
now = datetime.datetime.now()
else:
now = datetime.datetime.utcnow().replace(tzinfo=timezone.utc)
now = datetime.datetime.now(datetime.timezone.utc)
if self.date > now:
self.status = "draft"

View file

@ -7,7 +7,7 @@ from collections import defaultdict
from functools import partial
from itertools import chain, groupby
from operator import attrgetter
from typing import List, Optional, Set
from typing import Optional
from jinja2 import (
BaseLoader,
@ -138,7 +138,7 @@ class Generator:
def _include_path(self, path, extensions=None):
"""Inclusion logic for .get_files(), returns True/False
:param path: the path which might be including
:param path: potential path to include (relative to content root)
:param extensions: the list of allowed extensions, or False if all
extensions are allowed
"""
@ -158,8 +158,8 @@ class Generator:
return False
def get_files(
self, paths, exclude: Optional[List[str]] = None, extensions=None
) -> Set[str]:
self, paths, exclude: Optional[list[str]] = None, extensions=None
) -> set[str]:
"""Return a list of files to use, based on rules
:param paths: the list pf paths to search (relative to self.path)
@ -253,7 +253,7 @@ class Generator:
# return the name of the class for logging purposes
return self.__class__.__name__
def _check_disabled_readers(self, paths, exclude: Optional[List[str]]) -> None:
def _check_disabled_readers(self, paths, exclude: Optional[list[str]]) -> None:
"""Log warnings for files that would have been processed by disabled readers."""
for fil in self.get_files(
paths, exclude=exclude, extensions=self.readers.disabled_extensions
@ -296,6 +296,7 @@ class _FileLoader(BaseLoader):
self.fullpath = os.path.join(basedir, path)
def get_source(self, environment, template):
del environment # Unused argument
if template != self.path or not os.path.exists(self.fullpath):
raise TemplateNotFound(template)
mtime = os.path.getmtime(self.fullpath)
@ -1022,6 +1023,7 @@ class StaticGenerator(Generator):
signals.static_generator_finalized.send(self)
def generate_output(self, writer):
del writer # Unused argument
self._copy_paths(
self.settings["THEME_STATIC_PATHS"],
self.theme,
@ -1131,6 +1133,7 @@ class SourceFileGenerator(Generator):
copy(obj.source_path, dest)
def generate_output(self, writer=None):
del writer # Unused argument
logger.info("Generating source files...")
for obj in chain(self.context["articles"], self.context["pages"]):
self._create_source(obj)

View file

@ -1,4 +1,5 @@
import logging
import warnings
from collections import defaultdict
from rich.console import Console
@ -156,8 +157,6 @@ def init(
def log_warnings():
import warnings
logging.captureWarnings(True)
warnings.simplefilter("default", DeprecationWarning)
init(logging.DEBUG, name="py.warnings")

View file

@ -53,7 +53,7 @@ class Paginator:
"Returns the total number of pages."
if self._num_pages is None:
hits = max(1, self.count - self.orphans)
self._num_pages = int(ceil(hits / (float(self.per_page) or 1)))
self._num_pages = ceil(hits / (float(self.per_page) or 1))
return self._num_pages
num_pages = property(_get_num_pages)

View file

@ -19,7 +19,7 @@ def iter_namespace(ns_pkg):
def get_namespace_plugins(ns_pkg=None):
if ns_pkg is None:
import pelican.plugins as ns_pkg
import pelican.plugins as ns_pkg # noqa: PLC0415
return {
name: importlib.import_module(name)
@ -29,7 +29,7 @@ def get_namespace_plugins(ns_pkg=None):
def list_plugins(ns_pkg=None):
from pelican.log import init as init_logging
from pelican.log import init as init_logging # noqa: PLC0415
init_logging(logging.INFO)
ns_plugins = get_namespace_plugins(ns_pkg)

View file

@ -45,15 +45,15 @@ DUPLICATES_DEFINITIONS_ALLOWED = {
METADATA_PROCESSORS = {
"tags": lambda x, y: ([Tag(tag, y) for tag in ensure_metadata_list(x)] or _DISCARD),
"date": lambda x, y: get_date(x.replace("_", " ")),
"modified": lambda x, y: get_date(x),
"status": lambda x, y: x.strip() or _DISCARD,
"date": lambda x, _y: get_date(x.replace("_", " ")),
"modified": lambda x, _y: get_date(x),
"status": lambda x, _y: x.strip() or _DISCARD,
"category": lambda x, y: _process_if_nonempty(Category, x, y),
"author": lambda x, y: _process_if_nonempty(Author, x, y),
"authors": lambda x, y: (
[Author(author, y) for author in ensure_metadata_list(x)] or _DISCARD
),
"slug": lambda x, y: x.strip() or _DISCARD,
"slug": lambda x, _y: x.strip() or _DISCARD,
}
logger = logging.getLogger(__name__)
@ -121,6 +121,7 @@ class BaseReader:
def read(self, source_path):
"No-op parser"
del source_path # Unused argument
content = None
metadata = {}
return content, metadata
@ -165,6 +166,7 @@ class PelicanHTMLTranslator(HTMLTranslator):
self.body.append(self.starttag(node, "abbr", "", **attrs))
def depart_abbreviation(self, node):
del node # Unused argument
self.body.append("</abbr>")
def visit_image(self, node):
@ -630,8 +632,9 @@ class Readers(FileStampDataCacher):
# eventually filter the content with typogrify if asked so
if self.settings["TYPOGRIFY"]:
import smartypants
from typogrify.filters import typogrify
# typogrify is an optional feature, user may not have it installed
import smartypants # noqa: PLC0415
from typogrify.filters import typogrify # noqa: PLC0415
typogrify_dashes = self.settings["TYPOGRIFY_DASHES"]
if typogrify_dashes == "oldschool":
@ -648,11 +651,22 @@ class Readers(FileStampDataCacher):
smartypants.Attr.default |= smartypants.Attr.w
def typogrify_wrapper(text):
"""Ensures ignore_tags feature is backward compatible"""
"""Ensure compatibility with older versions of Typogrify.
The 'TYPOGRIFY_IGNORE_TAGS' and/or 'TYPOGRIFY_OMIT_FILTERS'
settings will be ignored if the installed version of Typogrify
doesn't have the corresponding features."""
try:
return typogrify(text, self.settings["TYPOGRIFY_IGNORE_TAGS"])
return typogrify(
text,
self.settings["TYPOGRIFY_IGNORE_TAGS"],
**dict.fromkeys(self.settings["TYPOGRIFY_OMIT_FILTERS"], False),
)
except TypeError:
return typogrify(text)
try:
typogrify(text, self.settings["TYPOGRIFY_IGNORE_TAGS"])
except TypeError:
return typogrify(text)
if content:
content = typogrify_wrapper(content)

View file

@ -79,6 +79,7 @@ class abbreviation(nodes.Inline, nodes.TextElement):
def abbr_role(typ, rawtext, text, lineno, inliner, options=None, content=None):
del typ, rawtext, lineno, inliner, options, content # Unused arguments
text = utils.unescape(text)
m = _abbr_re.search(text)
if m is None:

View file

@ -122,8 +122,8 @@ class ComplexHTTPRequestHandler(server.SimpleHTTPRequestHandler):
return mimetype
def log_message(self, format, *args):
logger.info(format, *args)
def log_message(self, msg_format, *args):
logger.info(msg_format, *args)
class RootedHTTPServer(server.HTTPServer):

View file

@ -9,9 +9,10 @@ import sys
from os.path import isabs
from pathlib import Path
from types import ModuleType
from typing import Any, Dict, Optional
from typing import Any, Optional
from pelican.log import LimitFilter
from pelican.paginator import PaginationRule
def load_source(name: str, path: str) -> ModuleType:
@ -24,7 +25,7 @@ def load_source(name: str, path: str) -> ModuleType:
logger = logging.getLogger(__name__)
Settings = Dict[str, Any]
Settings = dict[str, Any]
DEFAULT_THEME = os.path.join(
os.path.dirname(os.path.abspath(__file__)), "themes", "notmyidea"
@ -144,11 +145,12 @@ DEFAULT_CONFIG = {
"DEFAULT_ORPHANS": 0,
"DEFAULT_METADATA": {},
"FILENAME_METADATA": r"(?P<date>\d{4}-\d{2}-\d{2}).*",
"PATH_METADATA": "",
"PATH_METADATA": r"",
"EXTRA_PATH_METADATA": {},
"ARTICLE_PERMALINK_STRUCTURE": "",
"TYPOGRIFY": False,
"TYPOGRIFY_IGNORE_TAGS": [],
"TYPOGRIFY_OMIT_FILTERS": [],
"TYPOGRIFY_DASHES": "default",
"SUMMARY_END_SUFFIX": "",
"SUMMARY_MAX_LENGTH": 50,
@ -157,7 +159,7 @@ DEFAULT_CONFIG = {
"PYGMENTS_RST_OPTIONS": {},
"TEMPLATE_PAGES": {},
"TEMPLATE_EXTENSIONS": [".html"],
"IGNORE_FILES": [".#*"],
"IGNORE_FILES": ["**/.*"],
"SLUG_REGEX_SUBSTITUTIONS": [
(r"[^\w\s-]", ""), # remove non-alphabetical/whitespace/'-' chars
(r"(?u)\A\s*", ""), # strip leading whitespace
@ -319,8 +321,7 @@ def handle_deprecated_settings(settings: Settings) -> Settings:
# EXTRA_TEMPLATES_PATHS -> THEME_TEMPLATES_OVERRIDES
if "EXTRA_TEMPLATES_PATHS" in settings:
logger.warning(
"EXTRA_TEMPLATES_PATHS is deprecated use "
"THEME_TEMPLATES_OVERRIDES instead."
"EXTRA_TEMPLATES_PATHS is deprecated use THEME_TEMPLATES_OVERRIDES instead."
)
if settings.get("THEME_TEMPLATES_OVERRIDES"):
raise Exception(
@ -452,8 +453,7 @@ def handle_deprecated_settings(settings: Settings) -> Settings:
settings[key] = _printf_s_to_format_field(settings[key], "lang")
except ValueError:
logger.warning(
"Failed to convert %%s to {lang} for %s. "
"Falling back to default.",
"Failed to convert %%s to {lang} for %s. Falling back to default.",
key,
)
settings[key] = DEFAULT_CONFIG[key]
@ -475,8 +475,7 @@ def handle_deprecated_settings(settings: Settings) -> Settings:
settings[key] = _printf_s_to_format_field(settings[key], "slug")
except ValueError:
logger.warning(
"Failed to convert %%s to {slug} for %s. "
"Falling back to default.",
"Failed to convert %%s to {slug} for %s. Falling back to default.",
key,
)
settings[key] = DEFAULT_CONFIG[key]
@ -613,7 +612,7 @@ def configure_settings(settings: Settings) -> Settings:
]:
if key in settings and not isinstance(settings[key], types):
value = settings.pop(key)
logger.warn(
logger.warning(
"Detected misconfigured %s (%s), falling back to the default (%s)",
key,
value,
@ -688,8 +687,6 @@ def configure_settings(settings: Settings) -> Settings:
)
# fix up pagination rules
from pelican.paginator import PaginationRule
pagination_rules = [
PaginationRule(*r)
for r in settings.get(

View file

@ -12,20 +12,20 @@ DEFAULT_PAGINATION = 2
FEED_RSS = "feeds/all.rss.xml"
CATEGORY_FEED_RSS = "feeds/{slug}.rss.xml"
LINKS = (
LINKS = [
("Biologeek", "http://biologeek.org"),
("Filyb", "http://filyb.info/"),
("Libert-fr", "http://www.libert-fr.com"),
("N1k0", "http://prendreuncafe.com/blog/"),
("Tarek Ziadé", "http://ziade.org/blog"),
("Zubin Mithra", "http://zubin71.wordpress.com/"),
)
]
SOCIAL = (
SOCIAL = [
("twitter", "http://twitter.com/ametaireau"),
("lastfm", "http://lastfm.com/user/akounet"),
("github", "http://github.com/ametaireau"),
)
]
# global metadata to all the contents
DEFAULT_METADATA = {"yeah": "it is"}

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - Alexis Métaireau</title><link href="/" rel="alternate"></link><link href="/feeds/alexis-metaireau.atom.xml" rel="self"></link><id>/</id><updated>2013-11-17T23:29:00+00:00</updated><entry><title>This is a super article !</title><link href="/this-is-a-super-article.html" rel="alternate"></link><published>2010-12-02T10:14:00+00:00</published><updated>2013-11-17T23:29:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - Alexis Métaireau</title><link href="/" rel="alternate"/><link href="/feeds/alexis-metaireau.atom.xml" rel="self"/><id>/</id><updated>2013-11-17T23:29:00+00:00</updated><entry><title>This is a super article !</title><link href="/this-is-a-super-article.html" rel="alternate"/><published>2010-12-02T10:14:00+00:00</published><updated>2013-11-17T23:29:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</summary><content type="html">&lt;p&gt;Some content here !&lt;/p&gt;
&lt;div class="section" id="this-is-a-simple-title"&gt;
@ -13,10 +13,10 @@ as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
&lt;/pre&gt;
&lt;p&gt;→ And now try with some utf8 hell: ééé&lt;/p&gt;
&lt;/div&gt;
</content><category term="yeah"></category><category term="foo"></category><category term="bar"></category><category term="foobar"></category></entry><entry><title>Oh yeah !</title><link href="/oh-yeah.html" rel="alternate"></link><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
</content><category term="yeah"/><category term="foo"/><category term="bar"/><category term="foobar"/></entry><entry><title>Oh yeah !</title><link href="/oh-yeah.html" rel="alternate"/><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</content><category term="bar"></category><category term="oh"></category><category term="bar"></category><category term="yeah"></category></entry></feed>
</content><category term="bar"/><category term="oh"/><category term="bar"/><category term="yeah"/></entry></feed>

View file

@ -1,10 +1,10 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>A Pelican Blog - Alexis Métaireau</title><link>/</link><description></description><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0000</lastBuildDate><item><title>This is a super article !</title><link>/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A Pelican Blog - Alexis Métaireau</title><link>/</link><description/><atom:link href="/feeds/alexis-metaireau.rss.xml" rel="self"/><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0000</lastBuildDate><item><title>This is a super article !</title><link>/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0000</pubDate><guid isPermaLink="false">tag:None,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0000</pubDate><guid>tag:None,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0000</pubDate><guid isPermaLink="false">tag:None,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item></channel></rss>
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0000</pubDate><guid>tag:None,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item></channel></rss>

File diff suppressed because one or more lines are too long

View file

@ -1,4 +1,4 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog</title><link href="/" rel="alternate"></link><link href="/feeds/all-fr.atom.xml" rel="self"></link><id>/</id><updated>2012-02-29T00:00:00+00:00</updated><entry><title>Deuxième article</title><link href="/second-article-fr.html" rel="alternate"></link><published>2012-02-29T00:00:00+00:00</published><updated>2012-02-29T00:00:00+00:00</updated><author><name></name></author><id>tag:None,2012-02-29:/second-article-fr.html</id><content type="html">&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</content><category term="misc"></category><category term="foo"></category><category term="bar"></category><category term="baz"></category></entry><entry><title>Trop bien !</title><link href="/oh-yeah-fr.html" rel="alternate"></link><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name></name></author><id>tag:None,2010-10-20:/oh-yeah-fr.html</id><content type="html">&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</content><category term="misc"></category></entry></feed>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog</title><link href="/" rel="alternate"/><link href="/feeds/all-fr.atom.xml" rel="self"/><id>/</id><updated>2012-02-29T00:00:00+00:00</updated><entry><title>Deuxième article</title><link href="/second-article-fr.html" rel="alternate"/><published>2012-02-29T00:00:00+00:00</published><updated>2012-02-29T00:00:00+00:00</updated><author><name/></author><id>tag:None,2012-02-29:/second-article-fr.html</id><content type="html">&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</content><category term="misc"/><category term="foo"/><category term="bar"/><category term="baz"/></entry><entry><title>Trop bien !</title><link href="/oh-yeah-fr.html" rel="alternate"/><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name/></author><id>tag:None,2010-10-20:/oh-yeah-fr.html</id><content type="html">&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</content><category term="misc"/></entry></feed>

File diff suppressed because one or more lines are too long

View file

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - bar</title><link href="/" rel="alternate"></link><link href="/feeds/bar.atom.xml" rel="self"></link><id>/</id><updated>2010-10-20T10:14:00+00:00</updated><entry><title>Oh yeah !</title><link href="/oh-yeah.html" rel="alternate"></link><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - bar</title><link href="/" rel="alternate"/><link href="/feeds/bar.atom.xml" rel="self"/><id>/</id><updated>2010-10-20T10:14:00+00:00</updated><entry><title>Oh yeah !</title><link href="/oh-yeah.html" rel="alternate"/><published>2010-10-20T10:14:00+00:00</published><updated>2010-10-20T10:14:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</content><category term="bar"></category><category term="oh"></category><category term="bar"></category><category term="yeah"></category></entry></feed>
</content><category term="bar"/><category term="oh"/><category term="bar"/><category term="yeah"/></entry></feed>

View file

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - cat1</title><link href="/" rel="alternate"></link><link href="/feeds/cat1.atom.xml" rel="self"></link><id>/</id><updated>2011-04-20T00:00:00+00:00</updated><entry><title>A markdown powered article</title><link href="/a-markdown-powered-article.html" rel="alternate"></link><published>2011-04-20T00:00:00+00:00</published><updated>2011-04-20T00:00:00+00:00</updated><author><name></name></author><id>tag:None,2011-04-20:/a-markdown-powered-article.html</id><content type="html">&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - cat1</title><link href="/" rel="alternate"/><link href="/feeds/cat1.atom.xml" rel="self"/><id>/</id><updated>2011-04-20T00:00:00+00:00</updated><entry><title>A markdown powered article</title><link href="/a-markdown-powered-article.html" rel="alternate"/><published>2011-04-20T00:00:00+00:00</published><updated>2011-04-20T00:00:00+00:00</updated><author><name/></author><id>tag:None,2011-04-20:/a-markdown-powered-article.html</id><content type="html">&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
&lt;p&gt;&lt;a href="/unbelievable.html"&gt;a root-relative link to unbelievable&lt;/a&gt;
&lt;a href="/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</content><category term="cat1"></category></entry><entry><title>Article 1</title><link href="/article-1.html" rel="alternate"></link><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name></name></author><id>tag:None,2011-02-17:/article-1.html</id><content type="html">&lt;p&gt;Article 1&lt;/p&gt;
</content><category term="cat1"></category></entry><entry><title>Article 2</title><link href="/article-2.html" rel="alternate"></link><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name></name></author><id>tag:None,2011-02-17:/article-2.html</id><content type="html">&lt;p&gt;Article 2&lt;/p&gt;
</content><category term="cat1"></category></entry><entry><title>Article 3</title><link href="/article-3.html" rel="alternate"></link><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name></name></author><id>tag:None,2011-02-17:/article-3.html</id><content type="html">&lt;p&gt;Article 3&lt;/p&gt;
</content><category term="cat1"></category></entry></feed>
&lt;a href="/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</content><category term="cat1"/></entry><entry><title>Article 1</title><link href="/article-1.html" rel="alternate"/><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name/></author><id>tag:None,2011-02-17:/article-1.html</id><content type="html">&lt;p&gt;Article 1&lt;/p&gt;
</content><category term="cat1"/></entry><entry><title>Article 2</title><link href="/article-2.html" rel="alternate"/><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name/></author><id>tag:None,2011-02-17:/article-2.html</id><content type="html">&lt;p&gt;Article 2&lt;/p&gt;
</content><category term="cat1"/></entry><entry><title>Article 3</title><link href="/article-3.html" rel="alternate"/><published>2011-02-17T00:00:00+00:00</published><updated>2011-02-17T00:00:00+00:00</updated><author><name/></author><id>tag:None,2011-02-17:/article-3.html</id><content type="html">&lt;p&gt;Article 3&lt;/p&gt;
</content><category term="cat1"/></entry></feed>

File diff suppressed because one or more lines are too long

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - yeah</title><link href="/" rel="alternate"></link><link href="/feeds/yeah.atom.xml" rel="self"></link><id>/</id><updated>2013-11-17T23:29:00+00:00</updated><entry><title>This is a super article !</title><link href="/this-is-a-super-article.html" rel="alternate"></link><published>2010-12-02T10:14:00+00:00</published><updated>2013-11-17T23:29:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
<feed xmlns="http://www.w3.org/2005/Atom"><title>A Pelican Blog - yeah</title><link href="/" rel="alternate"/><link href="/feeds/yeah.atom.xml" rel="self"/><id>/</id><updated>2013-11-17T23:29:00+00:00</updated><entry><title>This is a super article !</title><link href="/this-is-a-super-article.html" rel="alternate"/><published>2010-12-02T10:14:00+00:00</published><updated>2013-11-17T23:29:00+00:00</updated><author><name>Alexis Métaireau</name></author><id>tag:None,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</summary><content type="html">&lt;p&gt;Some content here !&lt;/p&gt;
&lt;div class="section" id="this-is-a-simple-title"&gt;
@ -13,4 +13,4 @@ as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
&lt;/pre&gt;
&lt;p&gt;→ And now try with some utf8 hell: ééé&lt;/p&gt;
&lt;/div&gt;
</content><category term="yeah"></category><category term="foo"></category><category term="bar"></category><category term="foobar"></category></entry></feed>
</content><category term="yeah"/><category term="foo"/><category term="bar"/><category term="foobar"/></entry></feed>

View file

@ -27,6 +27,13 @@ body {
text-align: left;
}
@media (prefers-color-scheme: dark) {
body {
background: #070808;
color: #FFFEFE;
}
}
/* Headings */
h1 {font-size: 2em }
h2 {font-size: 1.571em} /* 22px */
@ -106,6 +113,12 @@ dd {margin-left: 1.5em;}
pre{background-color: rgb(238, 238, 238); padding: 10px; margin: 10px; overflow: auto;}
@media (prefers-color-scheme: dark) {
pre {
background: rgb(38, 38, 38);
}
}
/* Quotes */
blockquote {
margin: 20px;
@ -197,6 +210,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
#banner h1 strong {font-size: 0.36em; font-weight: normal;}
@media (prefers-color-scheme: dark) {
#banner h1 a:link, #banner h1 a:visited {
color: #FFFAF8;
}
}
/* Main Nav */
#banner nav {
background: #000305;
@ -213,6 +232,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 5px;
}
@media (prefers-color-scheme: dark) {
#banner nav {
background: #121518;
}
}
#banner nav ul {list-style: none; margin: 0 auto; max-width: 800px;}
#banner nav li {float: left; display: inline; margin: 0;}
@ -255,6 +280,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#featured {
background: #151617;
}
}
#featured figure {
border: 2px solid #eee;
float: right;
@ -284,6 +315,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#content {
background: #111;
}
}
/*
Extras
*****************/
@ -306,6 +343,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
padding: .3em .25em;
}
@media (prefers-color-scheme: dark) {
#extras a:link, #extras a:visited {
color: #888;
}
}
#extras a:hover, #extras a:active {color: #fff;}
/* Blogroll */
@ -339,6 +382,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#about {
background: #222;
}
}
#about .primary {float: left; max-width: 165px;}
#about .primary strong {color: #C64350; display: block; font-size: 1.286em;}
#about .photo {float: left; margin: 5px 20px;}
@ -367,6 +416,12 @@ li:first-child .hentry, #content > .hentry {border: 0; margin: 0;}
.entry-title a:link, .entry-title a:visited {text-decoration: none; color: #333;}
.entry-title a:visited {background-color: #fff;}
@media (prefers-color-scheme: dark) {
.entry-title a:link, .entry-title a:visited {
color: #C74350;
}
}
.hentry .post-info * {font-style: normal;}
/* Content */

File diff suppressed because one or more lines are too long

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

File diff suppressed because one or more lines are too long

View file

@ -1,20 +1,20 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log - Alexis Métaireau</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log - Alexis Métaireau</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/alexis-metaireau.rss.xml" rel="self"/><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a root-relative link to unbelievable&lt;/a&gt;
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
&lt;p&gt;&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a root-relative link to markdown-article&lt;/a&gt;
&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a file-relative link to markdown-article&lt;/a&gt;&lt;/p&gt;
&lt;div class="section" id="testing-sourcecode-directive"&gt;
@ -25,5 +25,5 @@ YEAH !&lt;/p&gt;
&lt;div class="section" id="testing-another-case"&gt;
&lt;h2&gt;Testing another case&lt;/h2&gt;
&lt;p&gt;This will now have a line number in 'custom' since it's the default in
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>

File diff suppressed because one or more lines are too long

View file

@ -1,4 +1,4 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log</title><link href="http://blog.notmyidea.org/" rel="alternate"></link><link href="http://blog.notmyidea.org/feeds/all-fr.atom.xml" rel="self"></link><id>http://blog.notmyidea.org/</id><updated>2012-02-29T00:00:00+01:00</updated><subtitle>A personal blog.</subtitle><entry><title>Deuxième article</title><link href="http://blog.notmyidea.org/second-article-fr.html" rel="alternate"></link><published>2012-02-29T00:00:00+01:00</published><updated>2012-02-29T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2012-02-29:/second-article-fr.html</id><content type="html">&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</content><category term="misc"></category><category term="foo"></category><category term="bar"></category><category term="baz"></category></entry><entry><title>Trop bien !</title><link href="http://blog.notmyidea.org/oh-yeah-fr.html" rel="alternate"></link><published>2010-10-20T10:14:00+02:00</published><updated>2010-10-20T10:14:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-10-20:/oh-yeah-fr.html</id><content type="html">&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</content><category term="misc"></category></entry></feed>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log</title><link href="http://blog.notmyidea.org/" rel="alternate"/><link href="http://blog.notmyidea.org/feeds/all-fr.atom.xml" rel="self"/><id>http://blog.notmyidea.org/</id><updated>2012-02-29T00:00:00+01:00</updated><subtitle>A personal blog.</subtitle><entry><title>Deuxième article</title><link href="http://blog.notmyidea.org/second-article-fr.html" rel="alternate"/><published>2012-02-29T00:00:00+01:00</published><updated>2012-02-29T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2012-02-29:/second-article-fr.html</id><content type="html">&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</content><category term="misc"/><category term="foo"/><category term="bar"/><category term="baz"/></entry><entry><title>Trop bien !</title><link href="http://blog.notmyidea.org/oh-yeah-fr.html" rel="alternate"/><published>2010-10-20T10:14:00+02:00</published><updated>2010-10-20T10:14:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-10-20:/oh-yeah-fr.html</id><content type="html">&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</content><category term="misc"/></entry></feed>

File diff suppressed because one or more lines are too long

View file

@ -1,22 +1,22 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>Deuxième article</title><link>http://blog.notmyidea.org/second-article-fr.html</link><description>&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-02-29:/second-article-fr.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/all.rss.xml" rel="self"/><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>Deuxième article</title><link>http://blog.notmyidea.org/second-article-fr.html</link><description>&lt;p&gt;Ceci est un article, en français.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-02-29:/second-article-fr.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a root-relative link to unbelievable&lt;/a&gt;
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item><item><title>Trop bien !</title><link>http://blog.notmyidea.org/oh-yeah-fr.html</link><description>&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-20:/oh-yeah-fr.html</guid><category>misc</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item><item><title>Trop bien !</title><link>http://blog.notmyidea.org/oh-yeah-fr.html</link><description>&lt;p&gt;Et voila du contenu en français&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-20:/oh-yeah-fr.html</guid><category>misc</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
&lt;p&gt;&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a root-relative link to markdown-article&lt;/a&gt;
&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a file-relative link to markdown-article&lt;/a&gt;&lt;/p&gt;
&lt;div class="section" id="testing-sourcecode-directive"&gt;
@ -27,5 +27,5 @@ YEAH !&lt;/p&gt;
&lt;div class="section" id="testing-another-case"&gt;
&lt;h2&gt;Testing another case&lt;/h2&gt;
&lt;p&gt;This will now have a line number in 'custom' since it's the default in
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>

View file

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - bar</title><link href="http://blog.notmyidea.org/" rel="alternate"></link><link href="http://blog.notmyidea.org/feeds/bar.atom.xml" rel="self"></link><id>http://blog.notmyidea.org/</id><updated>2010-10-20T10:14:00+02:00</updated><subtitle>A personal blog.</subtitle><entry><title>Oh yeah !</title><link href="http://blog.notmyidea.org/oh-yeah.html" rel="alternate"></link><published>2010-10-20T10:14:00+02:00</published><updated>2010-10-20T10:14:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - bar</title><link href="http://blog.notmyidea.org/" rel="alternate"/><link href="http://blog.notmyidea.org/feeds/bar.atom.xml" rel="self"/><id>http://blog.notmyidea.org/</id><updated>2010-10-20T10:14:00+02:00</updated><subtitle>A personal blog.</subtitle><entry><title>Oh yeah !</title><link href="http://blog.notmyidea.org/oh-yeah.html" rel="alternate"/><published>2010-10-20T10:14:00+02:00</published><updated>2010-10-20T10:14:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</id><content type="html">&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</content><category term="bar"></category><category term="oh"></category><category term="bar"></category><category term="yeah"></category></entry></feed>
</content><category term="bar"/><category term="oh"/><category term="bar"/><category term="yeah"/></entry></feed>

View file

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log - bar</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Wed, 20 Oct 2010 10:14:00 +0200</lastBuildDate><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log - bar</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/bar.rss.xml" rel="self"/><lastBuildDate>Wed, 20 Oct 2010 10:14:00 +0200</lastBuildDate><item><title>Oh yeah !</title><link>http://blog.notmyidea.org/oh-yeah.html</link><description>&lt;div class="section" id="why-not"&gt;
&lt;h2&gt;Why not ?&lt;/h2&gt;
&lt;p&gt;After all, why not ? It's pretty simple to do it, and it will allow me to write my blogposts in rst !
YEAH !&lt;/p&gt;
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item></channel></rss>
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Oct 2010 10:14:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-20:/oh-yeah.html</guid><category>bar</category><category>oh</category><category>bar</category><category>yeah</category></item></channel></rss>

View file

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - cat1</title><link href="http://blog.notmyidea.org/" rel="alternate"></link><link href="http://blog.notmyidea.org/feeds/cat1.atom.xml" rel="self"></link><id>http://blog.notmyidea.org/</id><updated>2011-04-20T00:00:00+02:00</updated><subtitle>A personal blog.</subtitle><entry><title>A markdown powered article</title><link href="http://blog.notmyidea.org/a-markdown-powered-article.html" rel="alternate"></link><published>2011-04-20T00:00:00+02:00</published><updated>2011-04-20T00:00:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</id><content type="html">&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - cat1</title><link href="http://blog.notmyidea.org/" rel="alternate"/><link href="http://blog.notmyidea.org/feeds/cat1.atom.xml" rel="self"/><id>http://blog.notmyidea.org/</id><updated>2011-04-20T00:00:00+02:00</updated><subtitle>A personal blog.</subtitle><entry><title>A markdown powered article</title><link href="http://blog.notmyidea.org/a-markdown-powered-article.html" rel="alternate"/><published>2011-04-20T00:00:00+02:00</published><updated>2011-04-20T00:00:00+02:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</id><content type="html">&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a root-relative link to unbelievable&lt;/a&gt;
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</content><category term="cat1"></category></entry><entry><title>Article 1</title><link href="http://blog.notmyidea.org/article-1.html" rel="alternate"></link><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-1.html</id><content type="html">&lt;p&gt;Article 1&lt;/p&gt;
</content><category term="cat1"></category></entry><entry><title>Article 2</title><link href="http://blog.notmyidea.org/article-2.html" rel="alternate"></link><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-2.html</id><content type="html">&lt;p&gt;Article 2&lt;/p&gt;
</content><category term="cat1"></category></entry><entry><title>Article 3</title><link href="http://blog.notmyidea.org/article-3.html" rel="alternate"></link><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-3.html</id><content type="html">&lt;p&gt;Article 3&lt;/p&gt;
</content><category term="cat1"></category></entry></feed>
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</content><category term="cat1"/></entry><entry><title>Article 1</title><link href="http://blog.notmyidea.org/article-1.html" rel="alternate"/><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-1.html</id><content type="html">&lt;p&gt;Article 1&lt;/p&gt;
</content><category term="cat1"/></entry><entry><title>Article 2</title><link href="http://blog.notmyidea.org/article-2.html" rel="alternate"/><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-2.html</id><content type="html">&lt;p&gt;Article 2&lt;/p&gt;
</content><category term="cat1"/></entry><entry><title>Article 3</title><link href="http://blog.notmyidea.org/article-3.html" rel="alternate"/><published>2011-02-17T00:00:00+01:00</published><updated>2011-02-17T00:00:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2011-02-17:/article-3.html</id><content type="html">&lt;p&gt;Article 3&lt;/p&gt;
</content><category term="cat1"/></entry></feed>

View file

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log - cat1</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Wed, 20 Apr 2011 00:00:00 +0200</lastBuildDate><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log - cat1</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/cat1.rss.xml" rel="self"/><lastBuildDate>Wed, 20 Apr 2011 00:00:00 +0200</lastBuildDate><item><title>A markdown powered article</title><link>http://blog.notmyidea.org/a-markdown-powered-article.html</link><description>&lt;p&gt;You're mutually oblivious.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a root-relative link to unbelievable&lt;/a&gt;
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item></channel></rss>
&lt;a href="http://blog.notmyidea.org/unbelievable.html"&gt;a file-relative link to unbelievable&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 20 Apr 2011 00:00:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2011-04-20:/a-markdown-powered-article.html</guid><category>cat1</category></item><item><title>Article 1</title><link>http://blog.notmyidea.org/article-1.html</link><description>&lt;p&gt;Article 1&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-1.html</guid><category>cat1</category></item><item><title>Article 2</title><link>http://blog.notmyidea.org/article-2.html</link><description>&lt;p&gt;Article 2&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-2.html</guid><category>cat1</category></item><item><title>Article 3</title><link>http://blog.notmyidea.org/article-3.html</link><description>&lt;p&gt;Article 3&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 17 Feb 2011 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2011-02-17:/article-3.html</guid><category>cat1</category></item></channel></rss>

File diff suppressed because one or more lines are too long

View file

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log - misc</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Fri, 30 Nov 2012 00:00:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log - misc</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/misc.rss.xml" rel="self"/><lastBuildDate>Fri, 30 Nov 2012 00:00:00 +0100</lastBuildDate><item><title>FILENAME_METADATA example</title><link>http://blog.notmyidea.org/filename_metadata-example.html</link><description>&lt;p&gt;Some cool stuff!&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 30 Nov 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-11-30:/filename_metadata-example.html</guid><category>misc</category></item><item><title>Second article</title><link>http://blog.notmyidea.org/second-article.html</link><description>&lt;p&gt;This is some article, in english&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Wed, 29 Feb 2012 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2012-02-29:/second-article.html</guid><category>misc</category><category>foo</category><category>bar</category><category>baz</category></item><item><title>Unbelievable !</title><link>http://blog.notmyidea.org/unbelievable.html</link><description>&lt;p&gt;Or completely awesome. Depends the needs.&lt;/p&gt;
&lt;p&gt;&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a root-relative link to markdown-article&lt;/a&gt;
&lt;a class="reference external" href="http://blog.notmyidea.org/a-markdown-powered-article.html"&gt;a file-relative link to markdown-article&lt;/a&gt;&lt;/p&gt;
&lt;div class="section" id="testing-sourcecode-directive"&gt;
@ -12,5 +12,5 @@
&lt;div class="section" id="testing-another-case"&gt;
&lt;h2&gt;Testing another case&lt;/h2&gt;
&lt;p&gt;This will now have a line number in 'custom' since it's the default in
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>
pelican.conf, it will …&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Fri, 15 Oct 2010 20:30:00 +0200</pubDate><guid>tag:blog.notmyidea.org,2010-10-15:/unbelievable.html</guid><category>misc</category></item><item><title>The baz tag</title><link>http://blog.notmyidea.org/tag/baz.html</link><description>&lt;p&gt;This article overrides the listening of the articles under the &lt;em&gt;baz&lt;/em&gt; tag.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Sun, 14 Mar 2010 00:00:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-03-14:/tag/baz.html</guid><category>misc</category></item></channel></rss>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - yeah</title><link href="http://blog.notmyidea.org/" rel="alternate"></link><link href="http://blog.notmyidea.org/feeds/yeah.atom.xml" rel="self"></link><id>http://blog.notmyidea.org/</id><updated>2013-11-17T23:29:00+01:00</updated><subtitle>A personal blog.</subtitle><entry><title>This is a super article !</title><link href="http://blog.notmyidea.org/this-is-a-super-article.html" rel="alternate"></link><published>2010-12-02T10:14:00+01:00</published><updated>2013-11-17T23:29:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - yeah</title><link href="http://blog.notmyidea.org/" rel="alternate"/><link href="http://blog.notmyidea.org/feeds/yeah.atom.xml" rel="self"/><id>http://blog.notmyidea.org/</id><updated>2013-11-17T23:29:00+01:00</updated><subtitle>A personal blog.</subtitle><entry><title>This is a super article !</title><link href="http://blog.notmyidea.org/this-is-a-super-article.html" rel="alternate"/><published>2010-12-02T10:14:00+01:00</published><updated>2013-11-17T23:29:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</summary><content type="html">&lt;p&gt;Some content here !&lt;/p&gt;
&lt;div class="section" id="this-is-a-simple-title"&gt;
@ -13,4 +13,4 @@ as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
&lt;/pre&gt;
&lt;p&gt;→ And now try with some utf8 hell: ééé&lt;/p&gt;
&lt;/div&gt;
</content><category term="yeah"></category><category term="foo"></category><category term="bar"></category><category term="foobar"></category></entry></feed>
</content><category term="yeah"/><category term="foo"/><category term="bar"/><category term="foobar"/></entry></feed>

View file

@ -1,4 +1,4 @@
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Alexis' log - yeah</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexis' log - yeah</title><link>http://blog.notmyidea.org/</link><description>A personal blog.</description><atom:link href="http://blog.notmyidea.org/feeds/yeah.rss.xml" rel="self"/><lastBuildDate>Sun, 17 Nov 2013 23:29:00 +0100</lastBuildDate><item><title>This is a super article !</title><link>http://blog.notmyidea.org/this-is-a-super-article.html</link><description>&lt;p class="first last"&gt;Multi-line metadata should be supported
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid isPermaLink="false">tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item></channel></rss>
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexis Métaireau</dc:creator><pubDate>Thu, 02 Dec 2010 10:14:00 +0100</pubDate><guid>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</guid><category>yeah</category><category>foo</category><category>bar</category><category>foobar</category></item></channel></rss>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -14,8 +14,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -14,8 +14,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -14,8 +14,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -14,8 +14,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

View file

@ -27,6 +27,13 @@ body {
text-align: left;
}
@media (prefers-color-scheme: dark) {
body {
background: #070808;
color: #FFFEFE;
}
}
/* Headings */
h1 {font-size: 2em }
h2 {font-size: 1.571em} /* 22px */
@ -106,6 +113,12 @@ dd {margin-left: 1.5em;}
pre{background-color: rgb(238, 238, 238); padding: 10px; margin: 10px; overflow: auto;}
@media (prefers-color-scheme: dark) {
pre {
background: rgb(38, 38, 38);
}
}
/* Quotes */
blockquote {
margin: 20px;
@ -197,6 +210,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
#banner h1 strong {font-size: 0.36em; font-weight: normal;}
@media (prefers-color-scheme: dark) {
#banner h1 a:link, #banner h1 a:visited {
color: #FFFAF8;
}
}
/* Main Nav */
#banner nav {
background: #000305;
@ -213,6 +232,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 5px;
}
@media (prefers-color-scheme: dark) {
#banner nav {
background: #121518;
}
}
#banner nav ul {list-style: none; margin: 0 auto; max-width: 800px;}
#banner nav li {float: left; display: inline; margin: 0;}
@ -255,6 +280,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#featured {
background: #151617;
}
}
#featured figure {
border: 2px solid #eee;
float: right;
@ -284,6 +315,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#content {
background: #111;
}
}
/*
Extras
*****************/
@ -306,6 +343,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
padding: .3em .25em;
}
@media (prefers-color-scheme: dark) {
#extras a:link, #extras a:visited {
color: #888;
}
}
#extras a:hover, #extras a:active {color: #fff;}
/* Blogroll */
@ -339,6 +382,12 @@ div.figure p.caption, figure p.caption { /* margin provided by figure */
-webkit-border-radius: 10px;
}
@media (prefers-color-scheme: dark) {
#about {
background: #222;
}
}
#about .primary {float: left; max-width: 165px;}
#about .primary strong {color: #C64350; display: block; font-size: 1.286em;}
#about .photo {float: left; margin: 5px 20px;}
@ -367,6 +416,12 @@ li:first-child .hentry, #content > .hentry {border: 0; margin: 0;}
.entry-title a:link, .entry-title a:visited {text-decoration: none; color: #333;}
.entry-title a:visited {background-color: #fff;}
@media (prefers-color-scheme: dark) {
.entry-title a:link, .entry-title a:visited {
color: #C74350;
}
}
.hentry .post-info * {font-style: normal;}
/* Content */

View file

@ -12,8 +12,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log <strong>A personal blog.</strong></a></h1>

File diff suppressed because one or more lines are too long

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="./">Alexis' log</a></h1>

View file

@ -11,8 +11,17 @@
</head>
<body id="index" class="home">
<style type="text/css">
div.github_url {
position: absolute;
border: 0;
background: black;
padding: 2px 8px;
width: 120px;
}
</style>
<a href="http://github.com/ametaireau/">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_red_aa0000.png" alt="Fork me on GitHub" />
<div class="github_url" style="top: 0; right: 0; border-radius: 0 0 0 8px;">Fork me on GitHub</div>
</a>
<header id="banner" class="body">
<h1><a href="../">Alexis' log</a></h1>

Some files were not shown because too many files have changed in this diff Show more