Force interface language by config file #792
レビューアなし
ラベル
ラベルなし
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
マイルストーンなし
プロジェクトなし
担当者なし
2 人の参加者
通知
期日
期日は未設定です。
依存関係
依存関係が設定されていません。
リファレンス: Plume/Plume#792
読み込み中…
Add table
新しいイシューから参照
説明はありません。
ブランチ "DearRude/force-lang" の削除
ブランチの削除は恒久的です。 実際に削除されるまでの短い期間、ブランチが存在したままになることもありますが、たいていは元に戻すことはできません。 続行しますか?
As explained in #785, trying to force the language interface which specified in
.env
file.I tried the commented code below and re-compiled the front, but nothing happened. Since I didn't find any other piece which gets browser language, I assume my method of recompilation is flawed. (Only do
cargo web deploy -p plume-front --release
)So I made this WIP PR as @igalic suggested. 😁
Codecov Report
The issue with the front-end is that it runs in the browser: it can't access the environment variables of the server.
I think the solution would be to:
lang
property to every<html>
tag we render, containing the language code that we chose to render the pagelang
attribute to detect the language instead of relying onnavigator.language
as we currently do.I hope this isn't too much. I can try to guide you more if need detailed steps, I know it can be hard to get started on a codebase you know nothing about. Feel free to ask me here or on Matrix if you have any questions.
The feature is missing, so it's not the issue at hand, but doing just that was actually not sufficient. You must also rebuild Plume, as it's build script (build.rs) is the one copying files from
target/
to where static files should beプルリクエストはクローズされました