L20n/Projects/Source File Format: Difference between revisions
Jump to navigation
Jump to search
(Created page with '= Status = = Goals = = Non-Goals = = Timelines/Milestone = These are the bugs of interest: {| border="1" |- ! scope="col" | Bug ! scope="col" | Owner ! scope="col" | Status …') |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= Status = | = Status = | ||
__NOTOC__ | |||
= Active Projects = | |||
{| class="fullwidth-table sortable" style="width: 100%;" | |||
|- | |||
| width="25%" style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" | '''Description''' | |||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" | '''Leader''' | |||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" | '''Goal''' | |||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" | '''ETA''' | |||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" | '''Status''' | |||
|- | |||
|[[L20n/Projects/Source File Format/Defined Error Recovery|Defined Error Recovery]] | |||
| ?? | |||
| Specify what gets parsed if there are type-written errors and then determine how | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Project/Source File Format/Multi locale source format|Multi-locale source format]] | |||
| ?? | |||
| Specify the multi-locale source format | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Projects/Source File Format/Type annotations|Type annotations ]] | |||
| ?? | |||
| The l20n file format should also allow something to declare exactly what is happening with a particular use case. | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Projects/Source File Format/L10n Brief|L10n Brief]] | |||
| ?? | |||
| An l10n brief might explain the general context and usage of entities of a file. Again, this is helpful for developers to explain their work, localizers to see context and usage, and tool authors to build more context into their tools. | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Projects/Source File Format/Internal vs External Properties|Internal vs External Properties]] | |||
| ?? | |||
| L20n will differentiate between internal and external properties. This will removes any problem with name conflicts between the two use cases. Also, this should be useful for localizers who use either plain text editors or tools to have a distinction between the two types. | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Projects/Source File Format/Placeables|Placeables]] | |||
| ?? | |||
| The l20n file format needs to provide a markup to place strings. | |||
| August 15 | |||
| Nothing started | |||
|- | |||
|[[L20n/Projects/Source File Format/Type Definition|Type Definition]] | |||
| ?? | |||
| The l20n file format needs a define the types used within an entity and how they are recognized, and how they are used by localizers. | |||
| August 15 | |||
| Nothing started | |||
|} | |||
<br> | |||
= Goals = | = Goals = | ||
= Non-Goals = | = Non-Goals = | ||
Latest revision as of 19:19, 24 June 2010
Status
Active Projects
| Description | Leader | Goal | ETA | Status |
| Defined Error Recovery | ?? | Specify what gets parsed if there are type-written errors and then determine how | August 15 | Nothing started |
| Multi-locale source format | ?? | Specify the multi-locale source format | August 15 | Nothing started |
| Type annotations | ?? | The l20n file format should also allow something to declare exactly what is happening with a particular use case. | August 15 | Nothing started |
| L10n Brief | ?? | An l10n brief might explain the general context and usage of entities of a file. Again, this is helpful for developers to explain their work, localizers to see context and usage, and tool authors to build more context into their tools. | August 15 | Nothing started |
| Internal vs External Properties | ?? | L20n will differentiate between internal and external properties. This will removes any problem with name conflicts between the two use cases. Also, this should be useful for localizers who use either plain text editors or tools to have a distinction between the two types. | August 15 | Nothing started |
| Placeables | ?? | The l20n file format needs to provide a markup to place strings. | August 15 | Nothing started |
| Type Definition | ?? | The l20n file format needs a define the types used within an entity and how they are recognized, and how they are used by localizers. | August 15 | Nothing started |
Goals
Non-Goals
Timelines/Milestone
These are the bugs of interest:
| Bug | Owner | Status |
|---|