Translation sync failed for PR #1135 (zh-cn)

Offen
#1,137 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python

Rechercherichtung

Start with the reported structural parity failure in lectures/likelihood_ratio_process.md and inspect the edition’s open PR #310, which carries the English version this translation assumes. The issue says to merge #310 before carrying this change, then use translate forward -f likelihood_ratio_process.md or \translate-resync only if the stated source branch condition holds. Done means the translation sync succeeds without the listed directive and anchor mismatches.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

translation-sync-failure
Translation sync failure

Source PR: #1135
Target repo: QuantEcon/lecture-python.zh-cn
Target language: zh-cn

Errors
  • Error processing lectures/likelihood_ratio_process.md: Error: structural parity check failed for lectures/likelihood_ratio_process.md:
    • directive count differs: source has 54, output has 43 — a wholesale mismatch usually means the document was re-fenced or truncated
    • directive #32 name changed: source line 1438 has {code-cell}, output line 1273 has {note}
    • directive #38 name changed: source line 1864 has {code-cell}, output line 1654 has {exercise}
    • directive #39 name changed: source line 1889 has {exercise}, output line 1672 has {solution-start}
    • directive #40 name changed: source line 1907 has {solution-start}, output line 1733 has {solution-end}
    • directive #41 name changed: source line 1967 has {solution-end}, output line 1736 has {exercise}
    • directive #42 name changed: source line 1970 has {exercise}, output line 1747 has {solution-start}
    • directive #43 name changed: source line 1981 has {solution-start}, output line 1779 has {solution-end}
    • target anchors diverge — missing from output: (nature_likeli_f)=, (lrp_model_selection)=, (lrp_chernoff)=
    • Translation behind: lectures/likelihood_ratio_process.md: zh-cn's translation of it is at source 07975d5. This PR's change assumes the English that translation PR QuantEcon/lecture-python.zh-cn#310 carries, and it is still open in the edition. Merge it, then carry this change.
Recovery

Recover a lecture from a checkout of the source's default branch, not by re-running this sync:

  • lectures/likelihood_ratio_process.md: merge QuantEcon/lecture-python.zh-cn#310 in the edition first; it carries the English this PR's change assumes. Then carry this PR's change into the lecture: translate forward -f likelihood_ratio_process.md, or \translate-resync on this PR under the condition below.

Any other lecture named above:

  • one the edition has: translate forward -f <file>;
  • one the edition does not have yet: translate init -f <file>.

<file> is the lecture's path inside the docs folder. translate forward regenerates the whole lecture, so do not run it on a lecture that has been natively reviewed: carry the change into that one by hand. translate init -f overwrites a translation without asking, so use it only for a lecture the edition does not have.

\translate-resync on #1135 re-runs this sync from the PR's merge-time snapshot, for every file the PR changed, not only those named above. Use it only when none of those files has changed on the source's default branch since the PR merged; otherwise it reverts the later changes (QuantEcon/action-translation#276). For each file the PR changed,

git rev-list --count 6071051dfe42e75bbecb0682bfc65daf4dc8f60d..origin/main -- <path>

must print 0. A structural-parity failure repeats exactly on a resync, so fix its cause first.

Vorherrschende Sprache
TeX
Sterne
135
Forks
64
Ø Merge
9 Std. 17 Min.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus QuantEcon/lecture-python.myst

Alle Issues in QuantEcon/lecture-python.myst

Ähnliche Issues

Weitere Issues zu Internationalization

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.