Multi-languages string: Polystring
draft-bouilland-polystring-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Aurélien Bouilland | ||
| Last updated | 2019-08-19 (Latest revision 2019-02-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Managing multi-languages support for a service with autonomous parts can be complex. Having its internal parts be polyglot, and coalece to end-user's language only on display is one solution. This paper discuss a format to store, exchange, and algorithms to consume multi-language strings to this goal.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)