i18n(ja): update JA Text in sveltkit.mdx - #4015
Conversation
✅ Deploy Preview for tauri-v2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tauri-releases canceled.
|
github-actions
Bot
added
i18n
| **SPA** Single-Page Application： シングルページ・アプリケーション。単一のページで構成された Web アプリケーションで、最初に必要なコードを読み込んでおき、利用者の操作に応じて動的にサーバーと通信して必要な部分の内容のみ更新を行なう方式（ページ全体の再読込が発生しない）。 | ||
| **SSG** Static Site Generation： 静的サイト生成。ビルド時に静的なHTMLファイルを生成し、それを再利用する方式。 | ||
| **SSR** Server-Side Rendering： サーバーサイド・レンダリング。クライアントのリクエスト時にサーバー側でHTMLを生成し、ブラウザに返す方式。 |
There was a problem hiding this comment.
Well, SPA not necessarily has to contact a server, in the old days, the SPA were pages made in adobe flash, nowawdays we can have SPA made in multiple ways that works totally by itself online or not (as within a Tauri app) or just a plain SPA website for demo. The main difference from SSG is that SPA is 'built' at runtime, not sure 'built' is the correct word, while SSG you got the full html/js/css ready for serve. And SPA vs SSR is that the 'build' part happens locally (SPA) or remotely (SSR)
There was a problem hiding this comment.
@vasfvitor Thank you for your comments and explanation. This TranslationNote is aimed to provide JA readers a quick reference for the look-alike acronyms SPA/SSG/SSR which are confusing for us (JA). Probably the technical details are not necessary here, so I will revise the TranslationNote just to show the translation words only.
BTW, it would be nice if Tauri Glossary page is available somewhere in the Tauri-Doc.
Updated Japanese translations for SPA, SSG, and SSR definitions.
2 participants
Description
"i18n(ja): update JA Text in sveltkit.mdx up to EN PR#3387;
kit { };fallback: 'index.html'line is added;