Typst 2025 社区通话

Laur

Question is asked the same question, really. There are a bunch of other things which I consider as important, which are not quite as large, but also complex. For example, better font handling across the board, like there's bunch of open issues with regards to font selection, font fallback, warnings, loading fonts from files, bundling fonts with packages or templates. So there's a lot of design space to be explored there, but it is quite important. Okay, what is the vision of the Typst Universe package approval process? Long term, especially as the amount of packages and updates would increase over time?

实际上，这个问题和之前问的差不多。还有一些我认为很重要，但规模没那么大，但也比较复杂的事情。比如，全面提升字体处理能力，像字体选择、字体回退、警告、从文件加载字体、将字体与包或模板捆绑等方面，都存在很多未解决的问题。这方面有很多设计空间可以探索，而且非常重要。好的，Typst Universe 包的审批流程的愿景是什么？特别是长期来看，随着包的数量和更新的增加？

Reknih

Yes, that's definitely something we've discussed. And in the team, the question is to like, to what extent, for example, do you can involve AI? We think that ultimately human review will be required to meet the requirements such as Typst Universe, especially the naming requirements. But we want to automate more of the process and we want to move into a model where some authors with like a good track record have a certain level of trust and can, for example, publish updates rapidly without blocking on human review.

是的，这绝对是我们讨论过的事情。团队内部的问题是，比如，在多大程度上可以引入 AI？我们认为，最终仍然需要人工审核来满足 Typst Universe 的要求，特别是命名要求。但我们希望更多地自动化这个过程，并希望转向一种模式，即一些拥有良好记录的作者可以获得一定程度的信任，例如，可以快速发布更新，而无需等待人工审核。

Laur

Especially for updates. Yeah, I think we could make that faster for initial. I think in general, the naming rule has been a success. People might have different opinions on that, but I personally consider it a success. I would say it's a larger success for packages than for templates, especially for templates, lots of templates are just the descriptive name with the prefix modern.

特别是对于更新来说。是的，我认为我们可以让初始设置更快。总的来说，我认为命名规则是成功的。人们可能对此有不同的看法，但我个人认为它是成功的。我想说它在包方面比在模板方面更成功，尤其是对于模板来说，很多模板只是带有前缀“modern”的描述性名称。

Reknih

Yeah, that's a bit of a disaster. But yes.

嗯，那确实有点糟糕。不过是的。

Laur

it's a bit defeating the purpose of the thing. Not really since but there still isn't one canonical package versus which is the point of the rule. But yeah, it's not great, but. Yeah, overall. Well, I could, I could imagine. I mean, and I also some thoughts on this, but right now it's already pretty automated. And we also want to have a custom basically website to submit packages in the future, gotta moving away from GitHub. And then aside from the name, there really isn't that much that needs to be checked manually. So I think the process can be scaled without basically not being true to its core anymore.

这有点违背了初衷。倒也不是说完全违背，因为仍然没有一个规范的软件包，而这正是规则的意义所在。但总的来说，情况不太好。嗯，我可以想象。我的意思是，我对此也有一些想法，但现在它已经相当自动化了。而且我们将来也想拥有一个定制的网站来提交软件包，从而摆脱 GitHub。然后，除了名称之外，实际上没有太多需要手动检查的东西。所以我认为这个过程是可以扩展的，而不会背离其核心。

Reknih

Yeah, and one thing that will make us migrate away from the repository eventually is not only that the number of package submissions is growing, but also the size of that repository is growing. And at some point, it becomes untenable to keep it in Git.

最终促使我们放弃这个仓库的原因，不仅是提交的软件包数量在增长，而且仓库的规模也在增长。在某个时候，用 Git 维护它变得难以为继。

Laur

Yeah, greetings to next packages.

祝贺下一个软件包。

Laur

Okay?

好吗？

Laur

Yeah, maybe. Imagine you can take this one with a journalist.

也许吧。想象一下，你可以和记者一起讨论这件事。

Reknih

Yeah, so right now we're working, started working together with a publisher and larger publisher in Scandinavia was not only publishing scientifically, but sort of across the board to work on a Typst enabled process. And that will be an interesting case study. What we think is that the typst adoption in the sciences basically needs to come bottom up. We think that Typst it is and should be adopted first for teaching, for theses, for tech reports, and for submissions where users publish camera ready documents and that only then there is leverage and demand in the community that allows us to approach publishers. So that's like from the social engineering side and also from the technical side and being a compelling proposition to the publishers.

好的，所以现在我们正在和一家出版商合作，是斯堪的纳维亚半岛一家比较大的出版商，他们不仅出版科学类书籍，也出版其他类型的书籍，一起合作开发一个支持 Typst 的流程。这将会是一个有趣的案例研究。我们认为 Typst 在科学领域的应用基本上需要自下而上地进行。我们认为 Typst 应该首先被用于教学、论文、技术报告以及用户提交相机就绪文档的场景，只有这样，社区中才会有足够的推动力和需求，从而使我们能够与出版商进行合作。所以这是从社会工程的角度来看，同时也是从技术的角度来看，使其成为对出版商有吸引力的提议。

Reknih

As businesses, we think that we want to flesh out HTML's support and bring it out of the experimental stage so that doing submissions and is really compelling with regards to multi-channel channel, independent publishing, and getting a web version of a paper right away. And that could bring the publisher a tangible benefit. And at that time, it's a survival for us to approach them to do deals. I don't think that currently work manpower is best invested in approaching publishers because I think those projects have quite long lease cycles.

作为企业，我们认为我们应该完善对 HTML 的支持，并使其脱离实验阶段，以便在多渠道、独立发布和立即获得论文的 Web 版本方面，提交内容真正具有吸引力。这可以为出版商带来切实的利益。到那时，为了生存，我们需要与他们达成协议。我认为目前投入人力去接触出版商并不是最佳选择，因为我认为这些项目的周期相当长。

Laur

Whereas one quick interruption. I think we learned from the previous multi calls is that not just we, but also you want a bit more interactivity? It's quite a frontal right now. So if you want to speak at any point in time, you can just request to speak and then you can also just tell us your question or tell us your opinion so that we can have a bit of more of a discussion here. Only if you don't do that, we will just continue to read the Q&A.

刚才有个小小的打断。我想我们从之前的多次会议中了解到，不仅仅是我们，你们也希望有更多的互动性？现在这种形式有点像单方面的演讲。所以如果你想在任何时候发言，你可以请求发言，然后你也可以直接告诉我们你的问题或你的意见，这样我们就可以进行更多的讨论。如果你们不这样做，我们就只能继续读问答环节的内容了。

Reknih

so for example Adrik has raised their hand. Hey, Adrik?

比如，Adrik 举手了。嘿，Adrik，你好吗？

Laur

Yes, let's mute.

让我们静音。

Reknih

Request him to unmute. If I can do that on Discord, I don't think so. Yes.

请求他取消静音。如果我能在 Discord 上做到，我想应该也可以在这里做到。是的。

Adrik Ivanov

yes, okay. So I have also posted it on Slido, but, you said that there is warichū or whatever in the roadmap. So as far as I know, what is like Japanese and CJK annotation for text, kind of like the footnotes and also Ruby and then some, no, something relating to Japanese typesetting. How far along in the development process is it going to take to get a point, the CJK typesetting things, CJKV?

好的。我也在 Slido 上发布了，但是，你说路线图里有割注之类的东西。据我所知，那是指日语和 CJK 文本的注释，有点像脚注和 Ruby，还有一些与日语排版相关的东西。

Laur

So, what we, what I can say is that we have this is maybe also an announcement.

要到什么程度的开发过程才能实现 CJK 排版，CJKV？我们可以说——这也许也是一个公告……

Laur

We will hire a new Rust developer, full time Rust developer soon. Thanks to external funding from a company that we will also disclose soon, I think. And CJK will probably not be their first focus, but I think this could be a focus. So right now we're just quite stretched for resources. But once that person is more, basically. Involved in the project then, I could imagine, for example, making CJK a priority there. So I really can't give a time frame, but I would say in the medium term, it is definitely a priority.

我们很快会聘请一位新的全职 Rust 开发者。感谢一家公司的外部资助，我们也会尽快公布这家公司。CJK 可能不会是他们首要关注的重点，但我认为这可以成为一个重点。所以现在我们的资源非常紧张。但是一旦那个人更多地参与到项目中，我就可以想象，例如，将 CJK 作为优先事项。所以我真的无法给出时间表，但我想说，在中期，这绝对是一个优先事项。

Reknih

Yeah, and what I also want to say in terms of CJK is that we are really dependent on the community for the moment since we do not have any native speakers of any CJK language or even a second language speakers of a CJK language on our team. So we don't really know firsthand what the conventions are. And I think we've got a few amazing contributors in the community. For example, around Tinymist, where a lot of the community members contributing there are from China. And then also in the main compiler repo, and that we are dependent on the input and export. And I would say that if you're a resident of either France or Germany, then you should keep your eyes peeled if you want to join us as a full time developer for Rust in our team and, um, we will post a job posting here on our Discord and it will be visible on GitHub and on our web page as well.

是的，关于 CJK（中日韩统一表意文字），我想说的是，目前我们非常依赖社区，因为我们的团队中没有任何以 CJK 语言为母语的人，甚至没有以 CJK 语言为第二语言的人。所以我们并不真正了解第一手的惯例。我认为我们在社区里有一些很棒的贡献者。例如，在 Tinymist 方面，很多贡献者都来自中国。然后在主编译器仓库中，我们也依赖于大家的输入和输出。我想说，如果你是法国或德国的居民，如果你想加入我们的团队，成为 Rust 的全职开发者，请密切关注，我们将在 Discord 上发布招聘信息，GitHub 和我们的网页上也会显示。

Laur

I mean this is a small ad ad segment. This is will be the dream open source job because we are contractually obliged because this wrote a sponsors that the person only works on open source stuff.

这是一个小小的广告环节。这将是梦想中的开源工作，因为我们有合同义务，因为我们的赞助商规定这个人只能从事开源工作。

Reknih

Exactly and in the chat with regards to only hiring in Benelux, only hiring in Germany and France or and not in Benelux, they say speakers, we have our payroll setups for Germany and France and really for each European country. You need your own payrolls accountant and we are not in the business of collecting payroll accountants now and hiring outside of the European Union is even more complicated. And ultimately, that's money we want to pay as a salary and not to some third party accountant.

没错，在聊天中，关于只在比荷卢经济联盟、德国和法国招聘，或者不在比荷卢经济联盟招聘的问题，他们说，我们的工资系统是为德国和法国设置的，实际上每个欧洲国家都需要自己的工资单会计，而我们现在不做收集工资单会计的事情，而且在欧盟以外招聘就更复杂了。最终，我们希望把钱作为工资支付，而不是给第三方会计。

Laur

If another person that had requested to speak. Shockjaw? I'll invite you to the stage.

如果还有其他人想发言——Shockjaw？我会邀请你上台。

Shockjaw

Thanks, I appreciate you dragging me up here.

谢谢，感谢你把我拉上来。

Shockjaw

One thing I am kind of curious about, is the potential roadmap for tagged PDFs for like accessibility requirements and other fun stuff like. What that roadmap may look like?

我有点好奇的一件事是，带标签的 PDF 的潜在路线图，比如可访问性要求和其他有趣的东西。这个路线图可能是什么样的？

Laur

Yeah, so the first thing that will need to happen, but to make this journey start is that the outstanding pull request and to migrate Typst to killer needs to be completed and merged. So this is something that Laur also Laurenz, like me, is working on. He's also in the call. That is also sort of a bit blocked on me, but this is definitely something we want to get done for v0.14. And then hopefully we'll also start with tagging. v0.14 will most likely not have and full support that we can really confidently say tagged true, but we will start and then hopefully continue over the next release or releases. But it is alongside HTML the top priority on the compiler side. I'm curious. I'm curious whether you have had requirements for tech PDF or whether you're just an accessibility enthusiast.

好的，要开始这个过程，首先需要完成并合并待处理的 pull request，将 Typst 迁移到 killer。Laur，也就是 Laurenz，和我都在做这件事，他也在这次会议中。这件事也稍微卡在我这里了，但我们肯定想在 v0.14 版本中完成。然后希望我们也能开始使用 tagging。v0.14 版本很可能不会有完整的支持，让我们能自信地说 tagging 为 true，但我们会开始，然后希望在接下来的一个或多个版本中继续。但在编译器方面，它与 HTML 一起是最优先事项。我很好奇_我想知道你是否有对 tagged PDF 的需求，或者你只是一个无障碍爱好者。

Shockjaw

As a part of my government work, yes. PDF 2/A requirements are part of it.

作为我政府工作的一部分，是的，PDF 2/A 是其中一部分要求。

Laur

An arduous requirement nonetheless.

尽管如此，这仍然是一个艰巨的要求。

Reknih

Yeah, sounds like a lot of things are coming off the back of HTML support, which I'm quite stoked about. Exactly, and we also have a contributor contributing, as Laurence said, new PDF stag. So there should be a lot of work on tech PDF coming from that as well.

是的，听起来很多东西都是基于 HTML 支持而来的，我对此感到非常兴奋。没错，正如劳伦斯所说，我们还有一位贡献者在贡献新的 PDF 功能。因此，在 tagged PDF 方面应该会有很多工作。

Laur

Yeah, it should take credit, but purchase Duo. I think this is the larger thing that enables this now than the HTML work. All right?

是的，……。我认为这比 HTML ……

Reknih

Exactly, and okay, exactly. You can just request to speak and otherwise we'll keep the storytel in the slider and we'll send an email to the speaker who has with their session and if they come online of they should request to speak. That's the ERP talk. And if not, we'll continue with the call as we are right now.

没错，好的，没错。你可以直接申请发言，否则我们会保持故事在幻灯片中，我们会给会议的发言人发送邮件，如果他们上线，他们应该申请发言。这是 ERP 的讨论。如果没有，我们将像现在这样继续通话。

Reknih

All right, do we dive into the next top right question? Or do we have .

好的，我们直接开始下一个右上角的问题吗？还是说…

Laur

the third one done? Because the one, so I don't think we have current numbers, but if you want to have a rough idea where we add, then you can go to YouTube and watch the video of Martin's keynotes he gave at the Typst's Berlin meet where some of these numbers are.

第三个做完了吗？因为那个，所以我不认为我们有最新的数据，但如果你想大致了解我们在哪里增加，你可以去 YouTube 观看 Martin 在 Typst 柏林聚会上发表的主题演讲视频，里面有一些数据。

Reknih

I can just that we have about 10K weekly active users in the web app and that the growth trajectory has recovered from Christmas. And that growth, especially around Typst 0.13 as well, is quite dynamic at the moment.

我可以说我们在 Web 应用中大约有 1 万名周活跃用户，并且增长轨迹已经从圣诞节恢复。而且，尤其是在 Typst 0.13 版本发布前后，增长势头目前非常强劲。

Laur

All right, would CeTZ has to be a package level? Typst have some high level capabilities like that directly?

好的，CeTZ 必须是包级别的吗？Typst 是否有一些类似的高级功能可以直接使用？

Reknih

Um, I think I think question marks betray a French speaker.

嗯，我想问号暴露了法语使用者的身份。

Laur

Yes, definitely, you can always see a French speaker online, But so, so I, what I want to in the medium term is not replacing CeTZ, I think.

是的，当然，你总能在网上看到说法语的人。但所以，我中期想做的不是替换 CeTZ。

Laur

That is not the right direction to go in, but rather to have more useful primitives that packages like CeTZ can use. Right now, they really have to do a lot of basically working around the compiler or shipping complex things. At least that's my understanding of it. So for example, the for the path function, the old one, which is not duplicated, didn't allow for multiscale point path, which is a pain.

那不是正确的方向，而是应该有更多有用的原语，像 CeTZ 这样的包可以使用。现在，他们真的必须做很多基本上是绕过编译器或者发布复杂的东西。至少我理解的是这样。所以例如，对于路径函数，旧的那个，没有被复制的那个，不允许使用多尺度点路径，这很麻烦。

Laur

And I could also imagine having things like polygon intersections or binary shape operations natively in typst and better alignment primitives. But it would be more the drawing side and maybe even a bit more low level than CeTZ. Then we do not plan to have plotting built into Typst anymore. Like we had that on our website for a while, but we have removed that. I think that's best left to packages and it's cool that packages can do so many things without having to build everything in.

我还可以想象在 Typst 中原生支持多边形相交或二元形状运算，以及更好的对齐原语。但这更多的是绘图方面，甚至可能比 CeTZ 更底层一点。我们不打算在 Typst 中内置绘图功能了。就像我们之前在网站上放了一段时间，但我们已经删除了。我认为最好留给包来做，而且包可以在不必构建所有东西的情况下做这么多事情，这很酷。

Reknih

And I also think that, especially with Typst upcoming, if you have seen, for example, make sense's talk about Lilac at the meetup and he's working on that. Yeah, definitely a definitely watch that because it's a great talk. And second of all, I think that with plotting libraries in the community, there can be some competition about API design and stuff. And it's a more dynamic space in which it's easier to like iterate on these giant API surfaces.

而且我也认为，特别是随着 Typst 的发展，如果你看过，比如说，make sense 在 meetup 上关于 Lilac 的演讲，他正在做那个。是的，绝对值得一看，因为那是个很棒的演讲。其次，我认为社区中的绘图库在 API 设计等方面可能会存在一些竞争。这是一个更具活力的领域，更容易在这些巨大的 API 表面上进行迭代。

Laur

You see that even just with our official templates, which sadly, less well maintained than many community or let's say the good community templates, our packages, I think spreading things out of the community is good because it just gives just a larger space to the mass stuff, people working on stuff and coming up with stuff.

你可以看到，即使是我们的官方模板，很遗憾，它们的维护不如许多社区模板，或者说好的社区模板、我们的包。我认为将事情分散到社区中是件好事，因为它只是给大众提供了更大的空间，让人们可以做事情、想出东西。

Reknih

All right? Then I think we have a speaker request, and I'll invite whomever had that request to stage or no, they've withdrawn their request. This is your opportunity to read request to go to stage. Otherwise, I think we'll move on with the questions.

好的吗？然后我认为我们有一个演讲者请求，我会邀请提出请求的人上台，或者不，他们已经撤回了请求。这是你提出上台请求的机会。否则，我想我们将继续提问。

Reknih

Right?

是吗？

Laur

I guess.

我猜是的。

Reknih

questions. I guess our balance columns are short term goal. If you ask me, they are. I have, yes, yes, and unfortunately, Laurenz is a compiler tech lead, so unless I have been told that in principle they are easy, but there are few annoying edge cases which I don't want to think about right now, not ever.

问题。我猜我们的平衡列是短期目标。如果你问我，它们是。我有，是的，是的，但不幸的是，Laurenz 是一个编译器技术负责人，所以除非有人告诉我原则上它们很容易，但有一些烦人的边缘情况，我现在不想考虑，甚至永远不想考虑。

Reknih

Yeah, the last part maybe wasn't entirely truthful.

嗯，最后一部分可能不完全是实话。

Laur

I think the right time for balance comes might have been 0.12 because it's fits with all these relay out things we did then. So that would have deleted even further. In principle? It is not super complex, I think, but it is definitely tricky because it involves relayer to balance things out. And I don't want to really want to drag the focus away from HTML and PDF right now. Yeah.

我觉得平衡的最佳时机可能是 0.12 版本，因为它与我们当时做的所有这些重排版的东西相吻合。所以这可能会进一步删除。原则上来说，它不是超级复杂，我认为，但它绝对很棘手，因为它涉及到重排版来平衡。而且我现在真的不想把注意力从 HTML 和 PDF 上移开。是的。

Reknih

and I'd say that tax point 12 was like a giant a cycle thriller because the release cycle was so fucking long. We wanted to ship and like two months before the release, we thought we could ship, We could cut the release in 10 days.

我觉得 Typst 12 就像一部巨大的周期惊悚片，因为发布周期太他妈长了。我们想发布，在发布前两个月，我们认为可以发布，我们可以在 10 天内完成发布。

Laur

Try refactoring footnotes and making them work in a new layout engine. Another the constant block of release.

尝试重构脚注，使其在新布局引擎中工作。另一个是持续不断的发布障碍。

Reknih

like. Like for example, like my family is like, what's what's happening at Typst? So we are working on footnotes, but we're working on footnotes. Four months ago, I was like, yes.

比如，比如，我的家人会问，Typst 进展如何？所以我们正在研究脚注，但我们已经在研究脚注了。四个月前，我就觉得快完成了。

Laur

Anyway, so balanced columns, I would say are a medium priority. Probably not 0.14, maybe 0.15. It's...

总之，我认为平衡列是一个中等优先级的功能。可能不会在 0.14 版本中发布，也许会在 0.15 版本中。

Reknih

Yeah, it can excuse for me personally, after this call.

好的，对我个人来说，这次通话结束后可以请假。

Laur

And if someone wants to step up, I think that is possible, but tricky. So I'm definitely open to it. But to step up for this, you would basically need to get your mind into this whole relay out thing, maybe read the layout blog post I wrote, and maybe start a discussion in the layout forge. And then it can be done as a community contribution. Otherwise it we'll need to wait for one more one or two releases.

如果有人想主动承担，我认为这是可能的，但很棘手。所以我对此持开放态度。但要主动承担这件事，你基本上需要全身心投入到整个布局相关的事情中，也许可以读一下我写的布局博客文章，也许可以在布局的 forge 中发起讨论。这样就可以作为社区贡献来完成。否则，我们需要再等一到两个版本。

Reknih

Yeah, and I hear that Tinger has a water situation on his hands in the chat, so I would like to extend my excuses for being too entertaining on this call. I see that that wasn't expected.

好的，我听说 Tinger 在聊天中遇到了问题，所以我想为我在这次通话中过于活跃而道歉。我看到这是意料之外的。

Laur

The whole point.

重点就在于此。

Reknih

I think, I think that was the whole point. Entertaining sexy people and preparing 5 minutes before. Yes, em, but you can see that since our speakers aren't here, by the way, if you are the speaker for Typst in an ERP session, again, if you're join now, no problem, please request this week. Let's move on to the next operated question. Directory Walking would be awesome for the next version. I have a few use cases for dynamically passing files in my project dictionary directory. Laurenz, Does directory walking violate the guarantees that Typst give to its users or is it okay since in the project dictionary directory.

我觉得，我觉得这就是重点。让性感的人娱乐，并在 5 分钟前准备。是的，嗯，但你可以看到，因为我们的演讲者不在这里，顺便说一句，如果你是 Typst 在 ERP 会议上的演讲者，再说一遍，如果你现在加入，没问题，请在本周提出请求。让我们继续下一个操作问题。目录遍历对于下一个版本来说会很棒。我有一些用例，可以在我的项目目录中动态传递文件。Laurenz，目录遍历是否违反了 Typst 给用户的保证，或者在项目目录中是否可以？

Laur

it doesn't violate anything? It needs to have a good interface and in the compiler, basically, and it needs to have a good interface in the language, which is basically two design problems. And if I remember correctly, there is a bunch of discussion around that already on GitHub, and we decided that it is blocked on a path type because if you basically just have a walk or whatever function, then you can't really distinguish well between files and directories. And with a path type, that would be a bit nicer. The path type is something that I definitely also want to ship soon.

它没有违反任何东西，是吗？它需要在编译器中有一个好的接口，基本上，并且需要在语言中有一个好的接口，这基本上是两个设计问题。如果我没记错的话，GitHub 上已经有很多关于这方面的讨论了，我们认为它被路径类型阻塞了，因为如果你只是有一个 `walk` 或者其他什么函数，你就不能很好地区分文件和目录。有了路径类型，会更好一些。路径类型也是我肯定想尽快发布的东西。

Reknih

I'm not sure the next one after. Basically, the whole path situation also plugs into yielding, for example, multiple files out of one Typst document when doing HTML export. So you have like multiple HTML document I can link to each other that you can navigate between. That's one of the things we want to do, for example, to switch our internal documentation systems payload to Typst, either standalone or integrated into our web framework. And path type is maybe a part of the puzzle there, or at least a related topic.

我不确定下一个是什么。基本上，整个路径的情况也与 yielding 有关，例如，在进行 HTML 导出时，从一个 Typst 文档中导出多个文件。所以你有多个 HTML 文档，它们可以相互链接，你可以在它们之间导航。这是我们想做的事情之一，例如，将我们的内部文档系统 payload 切换到 Typst，无论是独立的还是集成到我们的 Web 框架中。路径类型可能是其中的一部分，或者至少是一个相关的话题。

Laur

Yeah. And the path type...

是的。而且路径类型...

Reknih

...

Laur

...thought of prepared a bit?

...想好了准备一下吗？

Reknih

The last with...

Laur

The deprecation of the path function, because I didn't just want to swap it out.

路径函数的弃用，因为我不想直接替换它。

Reknih

And I just wanted to answer the second post. I voted questions since it's so similar to what we've answered before, which is what will be the focus of the next release? And we've all already talked about it a lot. So the focus will be improvements through HTML export like asked and PDF accessibility, as well as like some standards, in particular PDF/UA-1 and PDF/H too, eh.

我只是想回答第二个帖子。我投了重复问题，因为它和我们之前回答过的问题非常相似，也就是下一个版本的重点是什么？我们都已经讨论过很多次了。所以重点将是通过 HTML 导出的改进，比如提问和 PDF 可访问性，以及一些标准，特别是 PDF/UA-1 和 PDF/H too。

Laur

Once again, the reminder... This is exactly what I'm talking about. The reminder that if you request to speak, you get protein treatment in response to the questions because we prefer to not speak into the void.

再次提醒...这正是我要说的。提醒一下，如果你请求发言，你会得到针对问题的优先处理，因为我们不喜欢对着空气说话。

Reknih

Yes? Welcome back.

是吗？欢迎回来。

Reknih

Yeah. Thanks for round 2. So I guess mine's a little bit more specific. I've noticed that quarto is kind of taking a liking to Typst for PDF exports. Are there more conversations with Posit as a whole for and...

好的，感谢第二轮。我觉得我的问题可能更具体一些。我注意到 Quarto 似乎越来越喜欢用 Typst 来导出 PDF 了。那么，和 Posit 整体之间，是否有更多关于……的讨论？

Pachi

maybe hopefully funding. Who knows?

也许能拿到资金，谁知道呢？

Laur

This is the time to mention that Posit is the company that will sponsors of the full of time road.

现在是时候提一下，Posit 公司将会赞助全职的 Road 项目。

Reknih

Haha, I figured.

我猜到了。

Reknih

Yeah.

Reknih

And so first of all, thank to them for their support. And second of all, I feel like with their contribution Quatro's needs will have like a direct connection with them and going forward we will have regular syngaps with posets team Carlos from Caro in particular. So if there's something they need, certainly input they are entitled to give.

首先，感谢他们的支持。其次，我觉得有了他们的贡献，Quatro 的需求会和他们直接联系起来，未来我们会和 Posets 团队定期进行同步，特别是和 Caro 的 Carlos。所以如果他们有什么需要，当然有权提出意见。

Laur

Then, since somebody else requested to speak, we can continue in the slido. Revoke route update. Yeah, so I think that fits into a general like to the styling topic. There are a bunch of things I don't really like about the styling system. For example, how default `show`, `set` rules work, basically that if you write show heading and then replace it with something entirely else, it's still bold. This was sort of a side effect of the way we changed.

既然有人要求发言，我们可以继续处理 Slido。撤销路由更新。是的，我认为这属于一个更广泛的样式主题。我对样式系统有很多不喜欢的地方。例如，默认的`show`、`set`规则的工作方式，基本上如果你写了 show heading，然后用完全不同的东西替换它，它仍然是粗体。这是我们改变方式的副作用。

Laur

It will definitely become a topic again. But not for 0.14. It also ties in with custom elements because for custom elements of the hacks that we have in the compiler, we will need decide whether we expose them or not. For example, we have this locatable annotation on elements in the compiler that basically says, does this work with query? And the reason this exists is because making everything locatable is just not really feasible in the current implementation is too expensive. Our custom, some elements. I don't want to have a locatable annotation, so we'll need to figure something out. And this is also part of the reason why custom elements are for key. Next question is custom elements when we already answered that.

这肯定会再次成为一个话题。但不是在 0.14 版本。它也与自定义元素有关，因为对于编译器中我们所做的自定义元素 hack，我们需要决定是否公开它们。例如，我们在编译器中的元素上有一个可定位的注解，它基本上说明了这个元素是否能与 query 一起使用？之所以存在这个注解，是因为在当前的实现中，让所有东西都可定位实际上是不可行的，成本太高了。我们的自定义元素，我不想有一个可定位的注解，所以我们需要想出一些办法。这也是自定义元素是 key 的原因之一。下一个问题是自定义元素，我们已经回答过了。

Reknih

yeah.

Reknih

And I want to, I just have had a look at the questions that are done there. And I want to pull one up because we already sort of talked about it. Yes UA will be a focus for the next release.

我想，我只是看了一下那里提出的问题。我想挑一个出来，因为我们已经讨论过了。是的，UA 将是下一个版本的重点。

Reknih

And one thing that I want to add to the whole European regulation, I think, yeah, there's upcoming regulation for accessible documents the Americans cited for a while and the Americans with it. AB, this act, otherwise known as Ada. But there's another piece of European regulation that is upcoming, which is that electronic invoicing will be compulsory for B2B transactions. And that means that you PDF file basically contains an attachment XML file that is machine readable and describes your invoice. And largely thanks to contribution PDF, embedding any file as a feature that shipped in 0.1. But we're still missing the last puzzle piece, which is amending the Pdf's metadata stream such that it says, hey I'm an invoice. And that's something that could certainly ship in a PDF focus release.

我想补充一点关于整个欧洲监管的，我认为，是的，即将出台关于无障碍文档的法规，美国人引用了一段时间，还有美国的 AB 法案，也就是 Ada。但还有一项即将出台的欧洲法规，即电子发票将成为 B2B 交易的强制要求。这意味着你的 PDF 文件基本上包含一个附件 XML 文件，该文件是机器可读的，并描述了你的发票。很大程度上要感谢 PDF 的贡献，嵌入任何文件都是 0.1 版本中的一个功能。但我们仍然缺少最后一块拼图，那就是修改 PDF 的元数据流，使其声明，嘿，我是一张发票。这肯定可以在 PDF 重点版本中发布。

Laur

Okay, so on the question of which breaking changes you would like to do, if you had something to change the Typst right now, what would it be so? I have an old message in the Discord server about that, and part of it is still applicable. So let me just link that in the chat, A bunch of it would maybe be a bit different though, but some of these things I still would like to change, but they're just so, so large breaking changes that we sort of have to bundle them to not make it a horrible experience.

好的，关于你想做的重大更改的问题，如果你现在要更改 Typst，你会改什么？我在 Discord 服务器上有一条关于此的旧消息，其中一部分仍然适用。让我把它链接到聊天中，其中很多可能有点不同，但其中一些东西我仍然想改变，但它们是如此巨大的重大更改，以至于我们必须将它们捆绑在一起，才不会造成糟糕的体验。

Laur

Okay, will it be possible to write tabs universe readme of packages in types?

好的，是否可以用 Typst 编写关于包的 tabs universe 自述文件？

Reknih

I would say that it's safe to say that yes, once HTML export is more mature.

我认为可以肯定地说，是的，一旦 HTML 导出更加成熟。

Reknih

And have you considered? Yeah.

你考虑过吗？嗯。

Laur

the list is old. Not all of the things in the list are accurate. I just didn't want to make a new list now because I don't have any.

这个列表有点旧了，里面的东西不完全准确。我只是现在不想重新做一个新的列表，因为我手头没有。

Reknih

What.

Laur

and I don't have a new list, That's what I want to say because that was not English.

我没有新的列表，我想说的是这个，因为刚才说的不是英语。

Reknih

yeah. All right, let's go for the next question. Have you considered a way to give more? Version compatibility, Just compiler version and all other packages. I would like to maybe invite the guy.

好的。我们来看下一个问题。有没有考虑过提供更多的版本兼容性？比如编译器版本和所有其他包的版本。我想邀请一下这位朋友。

Laur

And so many of them became breaking with Evers. And I was wondering if there would be maybe a way to define a maximum version... compatibility version with Typst or something that could be useful.

很多包在最新版 break 掉了。我在想是否有可能定义一个与 Typst 的最大版本兼容性或类似的东西，这可能会有用。

Laur

This has come up a bunch of times, but it's sort of tricky because if you put it in your Typst ???, you basically didn't look into the future, right?

这个问题已经出现过很多次了，但这有点棘手，因为如果你把它放在你的 Typst ???中，你基本上没有考虑到未来，对吧？

Lord

Yeah. That's the issue. And so I was just wondering if you had maybe discussed of a system that could work for this, because I saw there was an issue on GitHub, I think that was closed for the reason you just said.

是的。这就是问题所在。所以我只是想知道你们是否讨论过一个可行的系统，因为我看到GitHub上有一个问题，我认为是因为你刚才说的原因而被关闭的。

Laur

I think the only way I can see doing it is having this metadata externally somehow in Typst Universe. But what I dislike about that, I don't really want the compiler to make choices depending on separate metadata that doesn't come with a package, because the package doesn't necessarily come from type universe. It should come from a directory or somewhere else. I think a better way to go about this is to have. I'm not quite sure whether I would have this in the compiler, but definitely in things like Tinymist and the web app now just to upgrade packages. And we could we have like a warning. Oh, this package is outdated. Perhaps try updating it if there's an error.

我觉得我能想到的唯一方法是在 Typst Universe 中以某种方式外部存储这些元数据。 但我不喜欢这样，我真的不希望编译器根据与包不在一起的单独元数据做出选择，因为包不一定来自 type universe。 它应该来自一个目录或其他地方。 我认为更好的方法是拥有。 我不太确定是否应该在编译器中加入这个，但肯定会在 Tinymist 和 Web 应用程序中加入，以便升级软件包。 我们可以发出一个警告，例如“哦，这个软件包已过期。 如果出现错误，请尝试更新它。”

Reknih

I was in a culture talk with someone who was using the Springer paper templates. So Springer paper template, basically. And she said, oh, it's not compatible with Typst 0.13 because it didn't updated...

我当时在和一个使用 Springer 论文模板的人进行文化交流。就是 Springer 论文模板。她说，哦，它与 Typst 0.13 不兼容，因为它没有更新……

Reknih

Says I could imagine that we introduced a new package submission process. Typst could be aware of the test suit offer package Typst could be aware of, all right there examples. And new readme and we need those to compile. And if they stop compiling, then Typst Universe will start like graying out the package and displaying a warning. This thing is not compatible with the latest Typst version. So basically that would mean a problem each release, rerunning acceptance shapes against the packages and marking the packages that don't pass as not compatible.

我觉得我们可以设想一下，引入一个新的包提交流程。Typst 可以知道测试套件，提供包 Typst 可以知道的例子，都在那里。还有新的 readme，我们需要它们能够编译。如果它们停止编译，那么 Typst Universe 就会开始灰显该包并显示警告，提示此包与最新的 Typst 版本不兼容。所以基本上，这意味着每次发布都会出现问题，需要针对这些包重新运行验收形状测试，并将未通过测试的包标记为不兼容。

Laur

Well, I think there's a bunch of things we can do, but ideally outside of the compiler. Thank you?

嗯，我认为我们可以做很多事情，但理想情况下是在编译器之外。谢谢？

Laur

Because there'd be a place like Typst Universe that store showcase of article projects written in Typst.

因为会有一个像 Typst Universe 这样的地方，存储用 Typst 编写的文章项目的展示。

Reknih

Yeah, which I just wanted to say, this is a place like this on a forum. I think it's less discoverable than Universe, the showcase category on the forum. But in principle, you can go there and post and it's meant for things like this. Exactly, so let me just bring up the link. Or. Yeah exactly. Yeah.

是的，我只是想说，论坛上也有类似的地方。我认为它不如 Universe 那么容易被发现，论坛上的展示类别也是如此。但原则上，你可以去那里发帖，它是为类似的事情准备的。没错，让我把链接发出来。或者，是的，没错。

Laur

something you could do is have Typst Universe be a bit more of a hub to explore other things like showcasing the forum and stuff. That's the way it was intended. That's where it's called the Typst Universe.

你可以做的是让 Typst Universe 成为一个中心，去探索其他东西，比如展示论坛之类的。这才是它原本的意图。这就是它被称为 Typst Universe 的原因。

Reknih

Yeah, and we could definitely do that. And maybe also if the person who has asked the question has some more input on what they've thought about then. They can come up to the stage or maybe put it in the chat so we can have a better idea.

是的，我们肯定可以这样做。也许如果提问者对他们的想法有更多的补充，他们可以上台或者在聊天中提出，这样我们就能更好地了解情况。

Laur

Is this person telling you the farm is down right now from from 10 people clicking on it or no?

这个人告诉你现在服务器宕机是因为有 10 个人点击它造成的吗？还是什么原因？

Reknih

I fucking hate Discourse. I fucking hate her so much. Just let me control the cubes real quick.

我真他妈讨厌 Discourse，我太讨厌它了。让我赶紧控制一下这些立方体。

Laur

Okay, for me it is sort of working. It's just slow.

好吧，对我来说，它算是能用，就是有点慢。

Reknih

Yeah, it...

Laur

seems that it's really, it's really sad, like it's not, not a lot of people.

感觉有点惨，好像没多少人。

Reknih

Yeah, it's said it is wet and weird. Yeah, let's not talk about it.

好的，他们说它又湿又怪。 好的，我们别谈这个了。

Laur

I mean, there are large discourse forums. I don't know whether we're doing something wrong, but .

我的意思是，有很多大型讨论论坛。 我不知道我们是不是做错了什么，但是...

Reknih

I'm don't know how they do it. They must run it on like the fucking...

我不知道他们是怎么做到的。他们肯定是在跑，就像那个...

Laur

Microsoft Mariana 1.

微软的 Mariana 1。

Reknih

Yes, that's a quantum chip for everyone who hasn't seen, and it really does have a name that is almost as ridiculous. But enough renting about this course. Let's, em.

是的，这是一个量子芯片，给那些还没见过的人看的，而且它的名字确实也很离谱。不过关于这个课程的吐槽就到此为止吧。我们，嗯。

Laur

This is a nice question. Who are the current team members and what do they each work on? So I can start? I'm working on the compiler as the core compiler developer. Martin can continue.

这是个好问题。目前的团队成员有哪些，他们各自负责什么工作？我可以先开始吗？我作为核心编译器开发者，正在研究编译器。Martin 可以继续。

Reknih

Yeah I'm working on the web app and the home page and I'm currently go working on the brand a bit too and making the homepage better. So that's exciting.

是的，我正在开发 Web 应用程序和主页，目前也在做一些品牌方面的工作，并改进主页。这很令人兴奋。

PgSuper

Well I'm working on a compiler and I mostly work on layout stuff. Or you might have seen like some features like line numbers simple, which was a very unexpected feature. And I see the lots of work on tables. For me, the tables guy.

我正在研究编译器，主要负责布局方面的工作。或者你可能见过一些功能，比如行号，这算是个非常出乎意料的功能。我还在做很多表格方面的工作。我是表格负责人。

Laur

Well, I guess I can also answer. I'm working on plushies. Yeah I'm basically working on brands and like typst's brand and other aspects of the company. Yeah, thank you.

嗯，我想我也可以回答。我正在做毛绒玩具。是的，我基本上在做品牌，比如 Typst 的品牌和公司的其他方面。好的，谢谢。

Ana

And I'm a developer to, and I used to contribute to the compiler a little, but I mostly work on the web app these days. And I'm also like the chief package officer. So I review all the packages that are submitted, the Typst Universe.

我也是一个开发者，以前也为编译器贡献过一点代码，但现在我主要在 Web 应用程序上工作。我也是首席包管理官，负责审核所有提交的 Typst Universe 包。

Reknih

Exactly, and Ana is currently working on a secret upcoming Typst Pro future.

没错，而且 Ana 目前正在开发一个秘密的 Typst Pro 特性项目。

Laur

Top secret.

绝密。

Reknih

Top secret. I mean, there are upcoming Sub Pro features that are unexpected.

绝密。我是说，即将推出的 Sub Pro 功能会出乎意料。

Laur

Yes, not the one she's working on though, anyway. And is content flowing into designated areas on the roadmap? Yes, I would say yes. Not in the near future, but in the medium to far future.

是的，但不是她正在做的那个。内容是否流入路线图上的指定区域？是的，我觉得是的。不是在近期，而是在中远期。

Reknih

In the Typst lingo that is called box chaining. And I think there's a GitHub issue for that.

在 Typst 的术语里，这叫做盒子链。我觉得 GitHub 上应该有个 issue 讨论过。

Laur

Maybe. There was some discussion about it briefly after 0.12 with some ideas being thrown around. Maybe it was in the layout for it so? Probably doable to find that if you're interested in it. If you don't get I'm just seen it.

可能吧。0.12 版本发布后，曾经有过一些简短的讨论，也提出了一些想法。也许是在布局相关的讨论里？如果你感兴趣，应该可以找到。如果你没找到，我好像见过。

Reknih

Any updates or thoughts on internal introspection re-layouting to circumvent the five layout reiteration limit without increasing it? Asking for frame? We see you. Local introspection is certainly something that is appealing to us, and I think it has not come up since. When worked on the new table of contents four times.

关于内部 introspection 重新布局，有没有什么更新或想法，可以在不增加五次布局迭代限制的情况下绕过它？要 frame？我们加了。局部 introspection 对我们来说肯定是有吸引力的，而且我觉得自从上次我做了新的目录之后，就再也没有人提过了。

Laur

but I at least done at least on my end.

但至少我这边已经完成了。

Reknih

All right, and should I repeat what I said before?

好的，需要我重复我之前说的话吗？

Laur

I think now it's better.

我觉得现在这样好多了。

Reknih

And basically that's by Ana. It's something we worked on. Would have liked to have when we did the new outlines and I think Laurenz may have some more thoughts to share.

基本上，这是 Ana 做的。是我们一起完成的。希望我们在做新的大纲时就能有这个，我想 Laurenz 可能会有更多想法要分享。

Laur

Yeah, so maybe we do sort of have something in the end, re-layouting, em, recompiling, realizing, and resell everything. We have something similar in layout engine already for read outing a page to make footnotes work and to make floating figures work and stuff. So it's natural to it have the middle ground between we read out the whole document, we re-layout the page, and we relayed something that the user specifically asked to be relay outed and stabilized locally. But I have not yet thought about it really, what would be needed to implement that and to expose that. So it's a design discussion we can start, but, yeah, I don't have any updates or thoughts to share right now.

好的，所以也许我们最终可以做一些事情，比如重新排版、重新编译、重新渲染，然后重新显示所有内容。在布局引擎中，我们已经有类似的东西，可以用来重新排版页面，以实现脚注和浮动图形等功能。所以很自然地，可以在重新排版整个文档、重新排版页面以及重新排版用户明确要求重新排版并局部稳定的内容之间找到一个中间地带。但我还没有真正考虑过，实现这一点需要什么，以及如何暴露它。所以这是一个我们可以开始的设计讨论，但是，是的，我现在没有任何更新或想法可以分享。

Laur

There some of the, let me quickly finish on the side of the diagnostics. If it does not converge, the title of the next question, I guess. So we don't have plans to increase the number of introspection loops, at least not in a way where the user can control it. I may accept at one day that it might need to be 6 or 7, but we don't have plans to make it user configurable. There's a bunch of discussion about that on GitHub and thoughts about how we can still improve the situation and make it easier to debug. I think that's best just write up on. I can share the link if I can find it.

关于诊断方面，让我快速说完。如果它不收敛，那就是下一个问题了。所以我们没有计划增加内省循环的次数，至少不会以用户可控的方式增加。我可能会在某一天接受它可能需要 6 或 7 次，但我们没有计划让用户可以配置。GitHub 上有很多关于这方面的讨论，以及关于我们如何改进这种情况并使其更容易调试的想法。我认为最好写下来。如果我能找到，我可以分享链接。

Reknih

And we are also considering, for example, allowing you to, in a debug environment in the web app, for example, view the document at each in iteration of the introspection group or maybe even like limit them down so you can use it to debug and see where things have gone wrong. So that's something we're considering. But this one of those instances where we are negotiating with terrorists and just have to tell the community to write better packages.

我们也在考虑，例如，允许你在 Web 应用程序的调试环境中，查看内省组每次迭代时的文档，或者甚至可以限制它们，这样你就可以用它来调试并查看哪里出了问题。所以这是我们正在考虑的事情。但这属于我们与恐怖分子谈判的情况之一，只能告诉社区编写更好的包。

Laur

Yeah, we will just have the entire ecosystem if we make it configurable. Do you think typst release and tinymist release needs to be somehow synchronized? It's an interesting question. I wonder if it comes from the tinymist folks or not. Probably not, but what? Be more interesting if it would.

如果把它做成可配置的，我们就能拥有整个生态系统。你觉得 Types 和 Tinymist 的发布需要某种同步吗？这是个有趣的问题。我想知道这问题是否来自 Tinymist 的开发者。可能不是，但如果真是那样会更有趣。

Laur

It is interesting because I recently thought again about auto formatting on the web app and we still haven't really decided yet on how we do that, whether we integrate a community formatter or whether we write our own. And the problem even already starts ignoring everything else with the fact that when I make a Typst release, I also published the web app at the same time. So I can't really wait for the Typstyle maintainers to upgrade Typstyle to the new Typst version because I need it right away. And so these are definitely interesting problems. But I think so far it's been working well with having tinymist on its own release schedule and well, then maybe the tinymist developers have thoughts on there, but.

这很有意思，因为我最近又在考虑 Web 应用上的自动格式化问题，我们还没有真正决定如何处理，是集成社区的格式化工具，还是自己编写一个。问题甚至在忽略其他一切之前就已经开始了，因为当我发布 Typst 版本时，我也会同时发布 Web 应用。所以我不能真的等着 Typst 维护者将 Typst 升级到新的 Typst 版本，因为我需要立即使用它。所以这些绝对是有趣的问题。但我认为到目前为止，让 Tinymist 拥有自己的发布时间表运作良好，也许 Tinymist 开发者对此有想法，但是…

Laur

Yeah, the tinymist, I'm very, very impressed by the development there. It's probably them oops. I, another...

是的，tinymist，我对那里的开发印象非常深刻。可能是他们…哎呀。我，另一个…

Reknih

We continue to, we continue to joke that @Myriad-Dreamin is actually 20 people.

我们一直开玩笑说纸夜实际上有 20 个人。

Reknih

All right, let's move on to the next question. Will Typst support the digital signature spec and then linked Adobe spec? And I think the answer in the medium term will be no. Why? Because like, I basically don't want to ship stuff in typst that is better suited for specialized tools. And I think that it is more well suited for software that integrates into Typst.

好的，让我们继续下一个问题。Typst 是否会支持数字签名规范？我认为中期来看答案是否定的。为什么？因为我基本上不想在 Typst 中加入更适合专业工具的东西。我认为它更适合集成到 Typst 中的软件。

Reknih

Furthermore, I think that with digital signatures especially, people's requirements are very different based on where they are. For example, for some people, a digital signature from a document reader might be enough. Some people require additional signature to be exclusively from DocuSign, others yet, for example, we in the European Union have a digital signature standard where the only digital signature that is actually corresponds to a physical signature on paper is when you verify with your government issued ID or have a voice chat with an agent, which is a service that we can not offer. I can see integrating third party signing kit into the typst web app with Typst Pro, but I can not see building it into the Typst compiler.

此外，我认为对于数字签名，不同地区的人们的需求差异很大。例如，对某些人来说，文档阅读器提供的数字签名可能就足够了。有些人则要求必须是 DocuSign 提供的签名。还有一些人，例如欧盟，我们有一个数字签名标准，只有通过政府颁发的身份证验证或与客服进行语音聊天才能实现的数字签名，才真正对应于纸质签名，而我们无法提供这种服务。我可以看到将第三方签名工具包集成到 Typst Web App 中，并作为 Typst Pro 的一部分，但我认为无法将其构建到 Typst 编译器中。

Laur

Do we have plans for another meetup? Do we want to spend another full week preparing things? And then at the day of the meetup, drive with a car, sharing and car to get 20 pizzas from the pizzeria clothes to the authors?

我们有计划再搞一次线下聚会吗？我们想再花整整一周时间准备吗？然后在聚会当天，开车，拼车，从披萨店拿 20 个披萨，分发给作者们？

Reknih

Wait, what? Driving in the car?

等等，什么？在车里开车？

Laur

Any plans for another meetup this year? I missed the first one and would be soaked to go to the next. The pizza is awesome, which is why why it was worth it. We could have gotten pizza from any place and they would have delivered it to us, but the pizza they have, it's better, but they don't deliver it.

今年有计划再举办一次聚会吗？我错过了第一次，很想参加下一次。披萨太棒了，所以才值得去。我们可以从任何地方买披萨，他们都会送货上门，但他们提供的披萨更好吃，只是不送货。

Reknih

Yeah, I would say that's like rank theft Laurenz.

是的，我会说这就像是盗用军衔，Laurenz。

Laur

I did pay it. (Laugh)

我付过了。（笑）

Reknih

Yeah, indeed. And I think there will be a meetup this year, but, and there will be Pizza again, I think. Yeah. And we asked people identify, it was hilarious. And the next time when I arrived, like a sorting algorithm, I will make it be aware of spaces.

是的，没错。而且我觉得今年会有聚会，而且我想会有披萨。是的。我们让大家表明身份，那场面很搞笑。下次我来的时候，就像一个排序算法一样，我会让它能识别空格。

Laur

Sorry for all the insiders, people, you need to come to the Meetup villain if you want to learn more about these.

对不起各位内部人士，如果你想了解更多这些事情，你需要来参加聚会。

Reknih

Yeah, and I think the people who have been there can attest to it's having been a lot of fun, I hope. And we had a speak request for about 5 seconds. But this is a meeting.

是的，而且我想去过的人可以证明那真的很有趣，我希望如此。我们收到了一个大约 5 秒钟的发言请求。但这是个会议。

Laur

I didn't invite them. You can, you can join the stage unless you have retracted it again.

我没有邀请他们。你可以加入发言，除非你又撤回了。

Laur

Okay, maybe not.

好吧，可能不是。

Reknih

Okay, wait, I'll just invite to become a speaker. Okay.

好的，稍等，我邀请你成为发言人。好的。

Laur

right. Okay, well, will it that be possible to actually write some package in Rust instead of having to manage the WASM API? Probably no, because then needs to be compiled in some way. And WASM is the best way.

好的，那么，有没有可能用 Rust 编写一些包，而不是必须管理 WASM API？可能不行，因为那样需要以某种方式进行编译。而 WASM 是最好的方式。

Reknih

Yeah, and then you get like platform dependency, and no, thanks.

是啊，然后你就会遇到平台依赖的问题，不了，谢谢。

Laur

So I guess you mean like like a plugin that is directly loaded as a dynamic library or something, but there is a secret nightmare, so probably no.

所以我想你的意思是，像一个直接作为动态库加载的插件之类的，但是这里面隐藏着隐私问题，所以可能不行。

Reknih

Yeah, I guess this person just wants to implement shell escape. Again, I think what I applied super about raising a number of iterations applies here as well. And I think...

嗯，我想这个人只是想实现 shell escape。再说一遍，我认为我之前说的关于增加迭代次数的建议在这里也适用。而且我觉得…

Reknih

Confirm now that we have talked about it. And there you go here, could the shadow scpr be reintroduced, but ensure that it can not be used for piracy related purposes?

现在确认一下我们已经讨论过了。然后这里，shell escape 能否被重新引入，但要确保它不能用于盗版相关目的？

Reknih

There was a Nintendo thing in the PR.

PR 里有个任天堂的东西。

Laur

Right, wait, we can talk about it .

对，等等，我们可以聊聊这个。

Reknih

On April 1?

在愚人节？

Laur

Yeah, in a few weeks, three and a half weeks, we can talk about it.

嗯，几周后，三周半后，我们可以聊聊。

Reknih

Yeah.

是的。

Laur

Do you want to answer the old question from 5:07?

你想回答 5:07 的老问题吗？

Reknih

I think I will do that. Typst is privately funded as a majority. Typst's multiple revenue streams: Typst Pro, Typst on premises and Typst open source support being our commercial revenue streams. Then of course, as we've said before, this call Posit is generously supporting us, as is our community via GitHub Sponsors, the open source. And we are receiving some government grants, in particular from the European Union through the foundation and NL for HTML Export at the moment and save for the European Union money, All of that is private. So I guess, yes, Typst is majority privately funded.

我想我会那样做。Typst 目前主要由私人资助。Typst 有多种收入来源：Typst Pro、Typst 本地部署和 Typst 开源支持是我们的商业收入来源。当然，正如我们之前所说，Posit 慷慨地支持我们，我们的社区也通过 GitHub Sponsors 和开源项目支持我们。我们还收到了一些政府拨款，特别是来自欧盟通过基金会和 NLfor HTML Export 的拨款。除了欧盟的资金，所有其他的都是私人的。所以我想，是的，Typst 主要由私人资助。

Laur

Okay, have we ever get the speak request.

好的，我们收到发言请求了吗？

Reknih

okay? Did somebody confirm? But yeah, that okay, interesting. And that way keep us on your to.

好的？有人确认了吗？好吧，好的，有意思。这样可以让我们随时了解情况。

Laur

Interactive PDF, so I guess you mean forms?

交互式 PDF，所以你指的是表单吗？

Reknih

I think that we once had a contributor who worked on that, but I think he burnt out from it a bit. And since it's sort of floating in the void.

我觉得我们之前有个贡献者做过这个，但他好像有点累了，然后现在就有点悬在空中。

Laur

it's personally for me, not a priority if someone wants to pick it up.

对我个人而言，这不是优先事项，如果有人想接手，也可以。

Laur

Which is now linked in the chat? We'll. Help basically have things over. And we're also obviously there too discuss things, but it's not a priority.

链接已发在聊天框。我们基本上会提供帮助，当然也会讨论问题，但这不是重点。

Reknih

Yeah, and if you do pick it up and need to draw on on our like PDF, better scars and experience, then we'll also be glad to have a call. But it would be maybe a good idea to familiarize yourself with the issue and.

好的，如果你接手了，需要借鉴我们之前在 PDF 上的经验，我们也很乐意开个会。但最好先熟悉一下问题。

Reknih

PDF 2.0 and PDF A 4 on the long term roadmap.

PDF 2.0 和 PDF A 4 在长期路线图上。

Reknih

Certificate types doesn't really do that. Is deprecated in PDF or 2.0 that it needs to do. It has some compatibility behaviors that we would need to remove for the 2.0 export and some other stuff we're to write. But these are mostly like mechanical changes, but PDF Afr won't be a big change to you unless somebody implements forms. So I guess sort of linked together. And I would be interested to know, what's your use case for PDF 2.0 is versus 1.7, which we are outputting right now?

证书类型实际上并没有做这些。它在 PDF 2.0 中已被弃用。它有一些兼容性行为，我们需要为 2.0 导出删除，还有一些其他的东西需要编写。但这些大多是机械性的改变，除非有人实现了表单，否则 PDF Afr 对你来说不会有很大的改变。所以我想这有点关联。我很想知道，你使用 PDF 2.0 的用例是什么，而不是我们现在输出的 1.7？

Laur

Now has some thoughts. Maybe he wants to join the stage.

现在有一些想法，可能想加入进来。

Laur

Sorry, you don't have to.

没关系，你不必这么做。

Reknih

PDF UA 1 is tied to PDF 1.7, and it's true that in PDF 2.0, tagging is different and more rich. And then generate a PDF 2.0 S, some more accessible format, and the PDF UA two standard A requires it and B gives more indep guidance on how to write an accessible PDF.

PDF UA 1 与 PDF 1.7 相关联，确实在 PDF 2.0 中，标记方式有所不同，也更加丰富。然后生成一个 PDF 2.0 S，一种更易访问的格式，PDF UA 2 标准 A 对此有要求，B 提供了关于如何编写可访问 PDF 的更多独立指导。

Reknih

All right?

Laur

Have you thought about improving Typst as a Rust lib, with better docs and word input helpers for diagnostics etc. I mean, sure, we can do that. I think this is a thing that would be fairly easy to contribute to. There's also, for example, the thing that we might want to extract some stuff from the CLI into Typst kit, for example, the watcher. There will, of course, be a bit of bike-shading involved in the APIs.

你有没有考虑过改进 Typst，把它作为一个 Rust 库，提供更好的文档和单词输入助手，用于诊断等等。我的意思是，当然，我们可以这样做。我认为这件事很容易贡献。例如，我们可能想从 CLI 中提取一些东西到 Typst kit 中，比如 watcher。当然，API 中会涉及到一些不必要的争论。

Laur

One thing I definitely want to do is re-export the crates that Typst depends on like commemo and stuff from Typst so that it's not as big a hassle to specify the dependencies and get everything into shape. Yeah, I think I think the world `impl` is the word `trait`. It's interesting. It is like there were a bunch of different interfaces before that. This is like the fifth iteration or something, and I think it is good because it's very flexible. But it takes some time to wrap your head around it, so the better docs will definitely be good and not too much work total. I'm not sure exactly what helpers for diagnostics means, but better document world input is definitely something we can.

我肯定想做的一件事是重新导出 Typst 依赖的 crates，比如 commemo 之类的，从 Typst 导出，这样指定依赖项并使所有内容成形就不会那么麻烦了。对，我觉得 `impl` 这个词就是 `trait`。挺有意思的。好像之前有很多不同的接口。这像是第五次迭代了，我觉得挺好的，因为它非常灵活。但需要花一些时间才能理解它，所以更好的文档肯定会很好，而且总的来说工作量也不会太大。我不确定诊断的 helpers 具体是什么意思，但更好的文档绝对是我们能做的。

Laur

Person that asked this ones.

问这个问题的人。

Reknih

Be kind to us.

Laur

What meanst? What is the meaning of .

什么意思？是什么的意思？

Reknih

What is the meaning of this? Laurenz, I think it just doomed when you accept it worked. It worked, it worked, it worked.

这是什么意思？Laurenz，我觉得你接受它能用的时候，它就注定完蛋了。它能用，它能用，它能用。

Pachi

Can you hear me?

能听到我说话吗？

Reknih

Yes, welcome.

可以，欢迎。

Pachi

Thank you by diagnostics. Well, this design to build an application using Typst for layouting and generating PDF, and for some energy efficiency certificate related issues.

感谢 diagnostics。这个设计的目的是使用 Typst 进行排版和生成 PDF，以及解决一些能源效率认证相关的问题，来构建一个应用程序。

Pachi

And I have to dig in the code to learn how to use the library. That's normal, but for instance, when I want to print the warnings and errors, I have to go deep into the library because it it's not very clear how to do it. And sometimes to recreate or some of the afford that you have for right into the console to the terminal. And I had to dig into some label, but there is even from a different crate that it's not entirely, but it seems to be related. So I mean, it's all very spread around and sometimes it's very difficult to understand how all the pieces fit together.

我不得不深入研究代码来学习如何使用这个库。这很正常，但例如，当我想打印警告和错误时，我必须深入到库的内部，因为它不是很清楚该怎么做。而且有时候为了重新创建或者实现你在控制台或终端上拥有的功能，我不得不研究一些标签，但这些标签甚至来自不同的 crate，虽然不完全相关，但似乎有关联。所以我的意思是，所有东西都非常分散，有时很难理解所有部分是如何组合在一起的。

Pachi

And also the word implementation is really nice once you understand it and maybe even quite easy it. But you have to first understand well what's a file ID and, eh, how you keep the file IDs and how they match between the names of the files and the IDs or how the Typst find a file for a package or a source etc. And there are lots of little missing pieces of information that it would be have better docs on that. But I think it's so fanta-, the library is so fantastic, so great, that I'm sure many more Rust developers would come to improve the library. And the software, they can use it in different ways from the Typst compiler.

而且，一旦你理解了它的实现方式，就会觉得它非常好，甚至可能很简单。但你首先要很好地理解什么是文件 ID，以及如何保存文件 ID，以及它们如何在文件名和 ID 之间匹配，或者 Typst 如何为包或源文件等找到文件。有很多缺失的信息，如果能有更好的文档就好了。但我认为这个库太棒了，太好了，我相信会有更多的 Rust 开发者来改进这个库。而且这些软件，他们可以用不同于 Typst 编译器的方式来使用它。

Laur

Okay, I think that's very fair. Sounds to me like it's really primarily a docs issue. And for example, like for the diagnostics, like the interface that Typst exposes is it tries to be as abstract? Well, not as abstract as possible, but as abstract as necessary so that you can read, display it in any way you like in the terminal or in the web app or wherever, and which is why it's a bit removed from just printed to the console, which is why various other crates like codespan reporting are involved. I think we can try to move some of that stuff to Typst Kit, but to me it sounds like the main issue is to read the docs and that makes a lot of sense like the things like file IDs.

好的，我觉得这很合理。听起来主要是一个文档问题。例如，对于诊断信息，Typst 暴露的接口试图尽可能抽象？好吧，不是尽可能抽象，而是根据需要进行抽象，这样你就可以在终端、Web 应用或任何地方以你喜欢的方式读取和显示它。这就是为什么它与直接打印到控制台有点脱节的原因，这也是为什么涉及到像 codespan reporting 这样的各种其他 crate。我认为我们可以尝试将其中一些内容移到 Typst Kit，但对我来说，主要问题是阅读文档，这很有意义，比如文件 ID 之类的东西。

Reknih

Yeah, and I can say like even back, way back when the file IDs were source IDs, I'd constantly like every two months or something, I have to interact with the web apps while implementation for some reason or other. And every time I have to ask Laurenz, what does the source IDs do and why can't I construct it and stuff like this?

是的，我可以说，甚至早在文件 ID 还是源 ID 的时候，我经常，大概每两个月左右，就不得不因为某些原因与 Web 应用的实现进行交互。而且每次我都不得不问 Laurenz，源 ID 是做什么的，为什么我不能构造它，以及诸如此类的问题？

Laur

Yeah.

Pachi

Yeah. For instance, I only think that README is not having a some way of having access or or packages or some way to extra how to get information from, for instance, embedded packages, from downloaded packages or from. A kiter directory on some directory because those could be quite modular elements. And there is in type this kit. There is a way to have a front-load helper. There's a font load helper, but there's not some helper to get packages from, from the network. You have to search in Typst, and that's another missing part that that are very spread around. There's seeing a Typst embedded packages trait that is quite interesting but difficult to understand how to use it until you know well.

是的。例如，我认为 README 缺少某种访问或获取包的方式，或者某种从嵌入式包、下载的包或某个目录下的 kiter 目录中提取信息的方式，因为这些可能是非常模块化的元素。在 Typst 的 kit 中，有一种预加载助手的方法，但没有助手可以从网络获取包。你必须在 Typst 中搜索，这是另一个缺失的部分，而且非常分散。有一个 Typst 嵌入式包 trait，非常有趣，但很难理解如何使用，除非你非常了解它。

Laur

I think? Well, I do. I do like refactoring stuff. So just moving around stuff from the CLI Typst is actually would be a day well spent for me.

我想？好吧，我是这么想的。我确实喜欢重构东西。所以仅仅是从 CLI Typst 移动东西对我来说实际上就是有意义的一天。

Reknih

Amazing.

Laur

Matthew, Matthew considers that a day well spent for me, but I think this is something we can improve in the short term.

Matthew 认为这对我来说是有意义的一天，但我认为这是我们可以在短期内改进的事情。

Reknih

All right, and thank you for coming to the stage and sharing your feedback.

好的，感谢您来到台上分享您的反馈。

Laur

I think this is something that should be inspiring to other people to join the stage, to join the conversation.

我觉得这件事应该能激励其他人加入进来，参与讨论。

Reknih

Yes, and be an inspiring leader and affect the change you want to see in typst. And so now we are the first time people on stage it again. But is expert.

是的，成为一个鼓舞人心的领导者，并在 Typst 中推动你想要看到的改变。所以现在我们再次邀请了第一批人上台，但这次是专家。

Laur

you don't yet exist, but you would really like to see developers. It's interesting because this was a question that was also asked last time. And we said something about chemistry. And I just recently saw that there is some sort of community working on chemistry packages.

你现在可能还不存在，但你真的很想看到开发者。有趣的是，上次也有人问过这个问题。我们当时提到了化学。我最近看到好像有个社区在开发化学相关的包。

Reknih

Nice, so you should join those people, especially if you know something about chemistry. I think maybe it's being a stoner comes to those always have surprising breadth of knowledge about chemistry.