# Non-English packages in the General registry

**URL:** <https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052>\
**Category:** Community\
**Created:** [May 9, 2026, 6:19pm UTC](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052 "2026-05-09T18:19:57Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [May 12, 2026, 11:34am UTC](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052/21 "2026-05-12T11:34:00Z")

</div>

Fair point, let me clarify: “move” in the sense that _future_ versions will live in another registry, and with a nice, user-friendly transition process and upgrade path.

---

<div class="post-metadata">

**Author:** ![putianyi888](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/putianyi888/32/32279_2.png) [@putianyi888](https://discourse.julialang.org/u/putianyi888)\
**Post date:** [May 13, 2026, 9:05am UTC](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052/22 "2026-05-13T09:05:55Z")

</div>

Since Julia already supports URL dependency, a package registering to General is no longer the only way of promoting it. I think General should enforce a much stricter rule.

As for moving packages out of General, it could be achieved without breaking manifests by adding deprecation marks and redirecting.

---

<div class="post-metadata">

**Author:** ![Mason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mason/32/2423_2.png) [@Mason](https://discourse.julialang.org/u/Mason)\
**Post date:** [May 13, 2026, 11:48am UTC](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052/23 "2026-05-13T11:48:06Z")

</div>

> [@putianyi888](#):
>
> Since Julia already supports URL dependency, a package registering to General is no longer the only way of promoting it. I think General should enforce a much stricter rule.

URL dependencies aren’t first class deps though. E.g. they won’t be properly resolved transitively, and won’t do things like version resolution.

---

<div class="post-metadata">

**Author:** ![jlapeyre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jlapeyre/32/4514_2.png) [@jlapeyre](https://discourse.julialang.org/u/jlapeyre)\
**Post date:** [May 13, 2026, 10:19pm UTC](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052/24 "2026-05-13T22:19:42Z")

</div>

Maybe a key “language” in some section of Project.toml

[Previous page](https://discourse.julialang.org/t/non-english-packages-in-the-general-registry/137052.md?page=1)