Copied from upstream: dair-ai/Prompt-Engineering-Guide#140
Original author: @silopolis
Originally created: 2023-04-18
Hello human intelligences :)
As explained here, I started setting up a Crowdin project to translate the project and stumbled on configuring Nextra's i18n file naming pattern for translated files (see my message here).
If as suggested by @omarsar, translated files could live in their own tree, and we could get rid of the .en in English source file names, that would make this configuration a piece of cake. It would also ease the import of existing translations in Crowdin, in addition to automating the creation of new languages for translators as well as the translation update workflow.
Thus, I'm proposing to use a locales or lang directory at the root of the repository, holding a two letter language code named folders for each translation. In each of these, the hierarchy of the translated files would follow the one of the English sources.
I.e., for French, that'd be lang/fr/[pages|guides]/.
Hope you'll like that proposal
TY
J
Edit: Actually, the real pain point is the .en in English source file names, as configuration would be as easy with a 'merged hierarchy'
Hello human intelligences :)
As explained here, I started setting up a Crowdin project to translate the project and stumbled on configuring Nextra's i18n file naming pattern for translated files (see my message here).
If as suggested by @omarsar, translated files could live in their own tree, and we could get rid of the
.enin English source file names, that would make this configuration a piece of cake. It would also ease the import of existing translations in Crowdin, in addition to automating the creation of new languages for translators as well as the translation update workflow.Thus, I'm proposing to use a
localesorlangdirectory at the root of the repository, holding a two letter language code named folders for each translation. In each of these, the hierarchy of the translated files would follow the one of the English sources.I.e., for French, that'd be
lang/fr/[pages|guides]/.Hope you'll like that proposal
TY
J
Edit: Actually, the real pain point is the
.enin English source file names, as configuration would be as easy with a 'merged hierarchy'