Or file an issue so someone else can add it, we're just getting start with this.
## Building from source
To build Grist from source, follow these steps:
@ -242,6 +259,7 @@ GRIST_ADAPT_DOMAIN | set to "true" to support multiple base domains (careful, h
GRIST_ALLOWED_HOSTS | comma-separated list of permitted domains origin for requests (e.g. my.site,another.com)
GRIST_APP_ROOT | directory containing Grist sandbox and assets (specifically the sandbox and static subdirectories).
GRIST_BACKUP_DELAY_SECS | wait this long after a doc change before making a backup
GRIST_BOOT_KEY | if set, offer diagnostics at /boot/GRIST_BOOT_KEY
GRIST_DATA_DIR | directory in which to store document caches.
GRIST_DEFAULT_EMAIL | if set, login as this user if no other credentials presented
GRIST_DEFAULT_PRODUCT | if set, this controls enabled features and limits of new sites. See names of PRODUCTS in Product.ts.
@ -276,7 +294,8 @@ GRIST_FORCE_LOGIN | Much like GRIST_ANON_PLAYGROUND but don't support anonymo
GRIST_SINGLE_ORG | set to an org "domain" to pin client to that org
GRIST_TEMPLATE_ORG | set to an org "domain" to show public docs from that org
GRIST_HELP_CENTER | set the help center link ref
FREE_COACHING_CALL_URL | set the link to the human help (example: email or meeting scheduling tool)
FREE_COACHING_CALL_URL | set the link to the human help (example: email adress or meeting scheduling tool)
GRIST_CONTACT_SUPPORT_URL | set the link to contact support on error pages (example: email adress or online form)
GRIST_SUPPORT_ANON | if set to 'true', show UI for anonymous access (not shown by default)
GRIST_SUPPORT_EMAIL | if set, give a user with the specified email support powers. The main extra power is the ability to share sites, workspaces, and docs with all users in a listed way.
GRIST_TELEMETRY_LEVEL | the telemetry level. Can be set to: `off` (default), `limited`, or `full`.
@ -290,6 +309,7 @@ COOKIE_MAX_AGE | session cookie max age, defaults to 90 days; can be set to
HOME_PORT | port number to listen on for REST API server; if set to "share", add API endpoints to regular grist port.
PORT | port number to listen on for Grist server
REDIS_URL | optional redis server for browser sessions and db query caching
GRIST_SKIP_REDIS_CHECKSUM_MISMATCH | Experimental. If set, only warn if the checksum in Redis differs with the one in your S3 backend storage. You may turn it on if your backend storage implements the [read-after-write consistency](https://aws.amazon.com/fr/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/). Defaults to false.
GRIST_SNAPSHOT_TIME_CAP | optional. Define the caps for tracking buckets. Usage: {"hour": 25, "day": 32, "isoWeek": 12, "month": 96, "year": 1000}
GRIST_SNAPSHOT_KEEP | optional. Number of recent snapshots to retain unconditionally for a document, regardless of when they were made
GRIST_PROMCLIENT_PORT | optional. If set, serve the Prometheus metrics on the specified port number. ⚠️ Be sure to use a port which is not publicly exposed ⚠️.
Garbage-collected languages make you think that you don't need to worry about cleanup for your objects. In reality, there are still often cases when you do. This page gives some examples, and describes a library to simplify it.
## What's the problem
In the examples, we care about a situation when you have a JS object that is responsible for certain UI, i.e. DOM, listening to DOM changes to update state elsewhere, and listening to outside changes to update state to the DOM.
### DOM Elements
So this JS object knows how to create the DOM. Removing the DOM, when the component is to be removed, is usually easy: `parentNode.removeNode(child)`. Since it's a manual operation, you may define some method to do this, named perhaps "destroy" or "dispose" or "cleanup".
If there is logic tied to your DOM either via JQuery events, or KnockoutJS bindings, you'll want to clean up the node specially: for JQuery, use `.remove()` or `.empty()` methods; for KnockoutJS, use `ko.removeNode()` or `ko.cleanNode()`. KnockoutJS's methods automatically call JQuery-related cleanup functions if JQuery is loaded in the page.
### Subscriptions and Computed Observables
But there is more. Consider this knockout code, adapted from their simplest example of a computed observable:
function FullNameWidget(firstName, lastName) {
this.fullName = ko.computed(function() {
return firstName() + " " + lastName();
});
...
}
Here we have a constructor for a component which takes two observables as constructor parameters, and creates a new observable which depends on the two inputs. Whenever `firstName` or `lastName` changes, `this.fullName` get recomputed. This makes it easy to create knockout-based bindings, e.g. to have a DOM element reflect the full name when either first or last name changes.
Now, what happens when this component is destroyed? It removes its associated DOM. Now when `firstName` or `lastName` change, there are no visible changes. But the function to recompute `this.fullName` still gets called, and still retains a reference to `this`, preventing the object from being garbage-collected.
The issue is that `this.fullName` is subscribed to `firstName` and `lastName` observables. It needs to be unsubscribed when the component is destroyed.
KnockoutJS recognizes it, and makes it easy: just call `this.firstName.dispose()`. We just have to remember to do it when we destroy the component.
This situation would exist without knockout too: the issue is that the component is listening to external changes to update the DOM that it is responsible for. When the component is gone, it should stop listening.
### Tying life of subscriptions to DOM
Since the situation above is so common in KnockoutJS, it offers some assistance. Specifically, when a computed observable is created using knockout's own binding syntax (by specifying a JS expression in an HTML attribute), knockout will clean it up automatically when the DOM node is removed using `ko.removeNode()` or `ko.cleanNode()`.
Knockout also allows to tie other cleanup to DOM node removal, documented at [Custom disposal logic](http://knockoutjs.com/documentation/custom-bindings-disposal.html) page.
In the example above, you could use `ko.utils.domNodeDisposal.addDisposeCallback(node, function() { self.fullName.dispose(); })`, and when you destroy the component and remove the `node` via `ko.removeNode()` or `ko.cleanNode()`, the `fullName` observable will be properly disposed.
### Other knockout subscriptions
There are other situations with subscriptions. For example, we may want to subscribe to a `viewId` observable, and when it changes, replace the currently-rendered View component. This might look like so
function GristDoc() {
this.viewId = ko.observable();
this.viewId.subscribe(function(viewId) {
this.loadView(viewId);
}, this);
}
Once GristDoc is destroyed, the subscription to `this.viewId` still exists, so `this.viewId` retains a reference to `this` (for calling the callback). Technically, there is no problem: as long as there are no references to `this.viewId` from outside this object, the whole cycle should be garbage-collected.
But it's very risky: if anything else has a reference to `this.viewId` (e.g. if `this.viewId` is itself subscribed to, say, `window.history` changes), then the entire `GristDoc` is unavailable to garbage-collection, including all the DOM to which it probably retains references even after that DOM is detached from the page.
Beside the memory leak, it means that when `this.viewId` changes, it will continue calling `this.loadView()`, continuing to update DOM that no one will ever see. Over time, that would of course slow down the browser, but would be hard to detect and debug.
Again, KnockoutJS offers a way to unsubscribe: `.subscribe()` returns a `ko.subscription` object, which in turn has a `dispose()` method. We just need to call it, and the callback will be unsubscribed.
### Backbone Events
To be clear, the problem isn't with Knockout, it's with the idea of subscribing to outside events. Backbone allows listening to events, which creates the same problem, and Backbone offers a similar solution.
For example, let's say you have a component that listens to an outside event and does stuff. With a made-up example, you might have a constructor like:
Let's say that a `Game` object is destroyed, and a new one created, but the `basket` persists across Games. As the user continues to score points on the basket, the old (supposedly destroyed) Game object continues to have that inline callback called. It may not be showing anything, but only because the DOM it's updating is no longer attached to the page. It's still taking resources, and may even continue to send stuff to the server.
We need to clean up when we destroy the Game object. In this example, it's pretty annoying. We'd have to save the `basket` object and callback in member variables (like `this.basket`, `this.callback`), so that in the cleanup method, we could call `this.basket.off('points:scored', this.callback)`.
Many people have gotten bitten with that in Backbone (see this [stackoverflow post](http://stackoverflow.com/questions/14041042/backbone-0-9-9-difference-between-listento-and-on)) with a bunch of links to blog posts about it).
Backbone's solution is `listenTo()` method. You'd use it like so:
Then when you destroy the Game object, you only have to call `this.stopListening()`. It keeps track of what you listened to, and unsubscribes. You just have to remember to call it. (Certain objects in Backbone will call `stopListening()` automatically when they are being cleaned up.)
### Internal events
If a component listens to an event on a DOM element it itself owns, and if it's using JQuery, then we don't need to do anything special. If on destruction of the component, we clean up the DOM element using `ko.removeNode()`, the JQuery event bindings should automatically be removed. (This hasn't been rigorously verified, but if correct, is a reason to use JQuery for browser events rather than native `addEventListener`.)
## How to do cleanup uniformly
Since we need to destroy the components' DOM explicitly, the components should provide a method to call for that. By analogy with KnockoutJS, let's call it `dispose()`.
- We know that it needs to remove the DOM that the component is responsible for, probably using `ko.removeNode`.
- If the component used Backbone's `listenTo()`, it should call `stopListening()` to unsubscribe from Backbone events.
- If the component maintains any knockout subscriptions or computed observables, it should call `.dispose()` on them.
- If the component owns other components, then those should be cleaned up recursively, by calling `.dispose()` on those.
The trick is how to make it easy to remember to do all necessary cleanup. I propose keeping track when the object to clean up first enters the picture.
## 'Disposable' class
The idea is to have a class that can be mixed into (or inherited by) any object, and whose purpose is to keep track of things this object "owns", that it should be responsible for cleaning up. To combine the examples above:
Note the `this.autoDispose()` calls. They mark the argument as being owned by `this`. When `this.dispose()` is called, those values get disposed of as well.
The disposal itself is fairly straightforward: if the object has a `dispose` method, we'll call that. If it's a DOM node, we'll call `ko.removeNode` on it. The `dispose()` method of Disposable objects will always call `this.stopListening()` if such a method exists, so that subscriptions using Backbone's `listenTo` are cleaned up automatically.
To do additional cleanup when `dispose()` is called, the derived class can override `dispose()`, do its other cleanup, then call `Disposable.prototype.dispose.call(this)`.
For convenience, Disposable class provides a few other methods:
- `disposeRelease(part)`: releases an owned object, so that it doesn't get auto-disposed.
- `disposeDiscard(part)`: disposes of an owned object early (rather than wait for `this.dispose`).
- `isDisposed()`: returns whether `this.dispose()` has already been called.
### Destroying destroyed objects
There is one more thing that Disposable class's `dispose()` method will do: destroy the object, as in ruin, wreck, wipe out. Specifically, it will go through all properties of `this`, and set each to a junk value. This achieves two goals:
1. In any of the examples above, if you forgot to mark anything with `this.autoDispose()`, and some callback continues to be called after the object has been destroyed, you'll get errors. Not just silent waste of resources that slow down the site and are hard to detect.
2. It removes references, potentially breaking references. Imagine that something wrongly retains a reference to a destroyed object (which logically nothing should, but something might by mistake). If it tries to use the object, it will fail (see point 1). But even if it doesn't access the object, it's preventing the garbage collector from cleaning any of the object. If we break references, then in this situation the GC can still collect all the properties of the destroyed object.
## Conclusion
All JS client-side components that need cleanup (e.g. maintain DOM, observables, listen to events, or subscribe to anything), should inherit from `Disposable`. To destroy them, call their `.dispose()` method. Whenever they take responsibility for any piece that requires cleanup, they should wrap that piece in `this.autoDispose()`.
This should go a long way towards avoiding leaks and slowdowns.
Grist Data Format is used to send and receive data from a Grist document. For example, an implementer of an import module would need to translate data to Grist Data Format. A user of Grist Basket APIs would fetch and upload data in Grist Data Format.
The format is optimized for tabular data. A table consists of rows and columns, containing a single value for each row for each column. Various types are supported for the values.
Each column has a name and a type. The type is not strict: a column may contain values of other types. However, the type is the intended type of the value for that column, and allows those values to be represented more efficiently.
Grist Data Format is readily serialized to JSON. Other serializations are possible, for example, see below for a .proto file that allows to serialize Grist Data Format as a protocol buffer.
## Format Specification
### Document
At the top, Grist Data Format is a Document objectwith a single key “tables” mapping to an array of Tables:
```javascript
{
tables: [Tables…]
}
```
### Table
```javascript
{
name: "TableName",
colinfo: [ColInfo…],
columns: ColData
}
```
The `name` is the name of the table. The `colinfo` array has an item to describe each column, and `columns` is the actual table data in column-oriented layout.
### ColInfo
```javascript
{
name: "ColName",
type: "ColType",
options: <arbitraryoptions>
}
```
The `name` is the name of the column, and `type` is its type. The field `options` optionally specifies type-specific options that affect the column (e.g. the number of decimal places to display for a floating-point number).
### ColData
```javascript
{
<colName1>: ColValues,
<colName2>: ColValues,
...
}
```
The data in the table is represented as an object mapping a column name to an array of values for the column. This column-oriented representation allows for the representation of data to be more concise.
### ColValues
```javascript
[CellValue, CellValue, ...]
```
ColValues is an array of all values for the column. We'll refer to the type of each value as `CellValue`. ColValues has an entry for each row in the table. In particular, each ColValues array in a ColData object has the same number of entries.
### CellValue
CellValue represents the value in one cell. We support various types of values, documented below. When represented as JSON, CellValue is one of the following JSON types:
- string
- number
- bool
- null
- array of the form `[typeCode, args...]`
The interpretation of CellValue is affected by the column’s type, and described in more detail below.
## JSON Schema
The description above can be summarized by this JSON Schema:
Each table should have a column named `id`, whose values should be unique across the table. It is used to identify records in queries and actions. Its details, including its type, are left for now outside the scope of this specification, because the format isn't affected by them.
## Naming
Names for tables and columns must consist of alphanumeric ASCII characters or underscore (i.e. `[0-9a-zA-Z_]`). They may not start with an underscore or a digit. Different tables and different columns within a table must have unique names case-insensitively (i.e. they cannot differ in case only).
Certain names (`id` being one of them) may be reserved, e.g. by Grist, for internal purposes, and would not be usable for user data. Such restrictions are outside the scope of this specification.
Note that this combination of rules allows tables and column names to be valid identifiers in pretty much every programming language (including Python and Javascript), as well as valid names of columns in databases.
## Value Types
The format supports a number of data types. Some types have a short representation (e.g. `Numeric` as a JSON `number`, and `Text` as a JSON `string`), but all types have an explicit representation as well.
The explicit representation of a value is an array `[typeCode, args...]`. The first member of the array is a string code that defines the type of the value. The rest of the elements are arguments used to construct the actual value.
The following table lists currently supported types and their short and explicit representations.
| `Error` | | `['E',string,string?,value?]` | Exception, with first argument exception type, second an optional message, and optionally a third containing additional info. |
An important goal is to represent data efficiently in the common case. When a value matches the column's type, the short representation is used. For example, in a Numeric column, a Numeric value is represented as a `number`, and in a Date column, a Date value is represented as a `number`.
If a value does not match the column's type, then the short representation is used when it's one of the starred types in the table AND the short type is different from the column's short type.
For example:
- In a Numeric column, Numeric is `number`, Text is `string` (being a starred type), but a Date is `['d',number]`.
- In a Date column, Date is `number`, and Numeric value is `['n',number]`, because even though it's starred, it conflicts with Date's own short type.
- In a Text column, Text is `string`, Numeric is `number` (starred), and Date is `['d',number]` (not starred).
Note how for the common case of a value matching the column's type, we can always use the short representation. But the format still allows values to have an explicit type that's different from the specified one.
Note also that columns of any of the starred types use the same interpretation for contained values.
The primary use case is to allow, for example, storing a value like "N/A" or "TBD" or "Ask Bob" in a column of type Numeric or Date. Another important case is to store errors produced by a computation.
Other complex types may be added in the future.
## Column Types
Any of the types listed in the table above may be specified as a column type.
In addition, a column type may specify type `Any`. For the purpose of type interpretations, it works the same as any of the starred types, but it does not convey anything about the expected type of value for the column.
## Other serializations
Grist Data Format is naturally serialized to JSON, which is fast and convenient to use in Javascript code. It is also possible to serialize it in other ways, e.g. as a Google protobuf.
Here is a `.proto` definition file that allows for efficient protobuf representation of data in Grist Data Format.
If you change Grist schema, i.e. the schema of the Grist metadata tables (in `sandbox/grist/schema.py`), you'll have to increment the `SCHEMA_VERSION` (on top of that file) and create a migration. A migration is a set of actions that would get applied to a document at the previous version, to make it satisfy the new schema.
To add a migration, add a function to `sandbox/grist/migrations.py`, of this form (using the new version number):
Some migrations need to actually add or modify the data in a document. You can look at other migrations in that file for examples.
If you are doing anything other than adding a column or a table, you must read this document to the end.
## Philosophy of migrations
Migrations are tricky. Normally, we think about the software we are writing, but migrations work with documents that were created by an older version of the software, which may not have the logic you think our software has, and MAY have logic that the current version knows nothing about.
This is why migrations code uses its own "dumb" implementation for loading and examining data (see `sandbox/grist/table_data_set.py`), because trying to load an older document using our primary code base will usually fail, since the document will not satisfy our current assumptions.
## Restrictions
The rules below should make it at least barely possible to share documents by people who are not all on the same Grist version (even so, it will require more work). It should also make it somewhat safe to upgrade and then open the document with a previous version.
WARNING: Do not remove, modify, or rename metadata tables or columns.
Mark old columns and tables as deprecated using a comment. We may want to add a feature to mark them in code, to prevent their use in new versions. For now, it's enough to add a comment and remove references to the deprecated entities throughout code. An important goal is to prevent adding same-named entities in the future, or reusing the same column with a different meaning. So please add a comment of the form:
```lang=python
# <columnName> is deprecated as of version XX. Do not remove or reuse.
```
To justify keeping old columns around, consider what would happen if A (at version 10) communicates with B (at version 11). If column "foo" exists in v10, and is deleted in v11, then A may send actions that refer to "foo", and B would consider them invalid, since B's code has no idea what "foo" is. The solution is that B needs to still know about "foo", hence we don't remove old columns.
Similar justification applies to renaming columns, or modifying them (e.g. changing a type).
WARNING: If you change the meaning or type of a column, you have to create a new column with a new name.
You'll also need to write a migration to fill it from the old column, and would mark the old column as deprecated.
Leaning towards an id and friendly name. Only id is interpreted by router. Name is checked only to make sure it matches current name of document. If not, we redirect to revised url before proceeding.
Length of ids depends on whether we'll be using them for obscurity to enable anyone-who-has-link-can-view style security.
Organizations get to choose a subdomain, and will access their workspaces and documents at `orgname.getgrist.com`. In addition, personal workspaces need to be uniquely determined by a URL, using `docs-` followed by the numeric id of the "personal organization":
* docs-1234.getgrist.com/
* docs.getgrist.com/o/docs-1234/
Since subdomains need to play along with all the other subdomains we use for getgrist.com, the following is a list of names that may NOT be used by any organization:
* `docs-\d+` to identify personal workspaces
* Anything that starts with underscore (`_`) (this includes special subdomains like `_domainkey`)
* Subdomains used by us for variouspurposes. As of 2018-10-09, these include:
* aws
* gristlogin
* issues
* metrics
* phab
* releases
* test
* vpn
* www
Some more reserved subdomains:
* doc-worker-NN
* v1-* (this could be released eventually, but currently in our code and/or routing "v1-mock", "v1-docs", "v1-static", and any other "v1-*" are special
"Remove column {{- colId }} from {{- tableId }} rules":"Supprimer la colonne {{-colId}} des règles de la table {{-tableId}}",
"Seed rules":"Règles par défaut",
"When adding table rules, automatically add a rule to grant OWNER full access.":"Ajouter automatiquement une règle donnant tous les droits au groupe OWNER.",
"When adding table rules, automatically add a rule to grant OWNER full access.":"Pour chaque ajout de règle pour une table, ajouter automatiquement une règle donnant tous les droits au groupe OWNER.",
"Permission to edit document structure":"Droits d'édition de la structure",
"This default should be changed if editors' access is to be limited. ":"Cette valeur par défaut doit être modifiée si l'on souhaite limiter l'accès des éditeurs. ",
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"Autorise les éditeurs à éditer la structure (modifier/supprimer des tables, colonnes, mises en page...) et à écrire des formules, ce qui donne accès à l'ensemble des données sans prendre en compte d'éventuelles restrictions de droits de lecture.",
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"Autorise les éditeurs à éditer la structure (modifier/supprimer des tables, colonnes, mises en page) et à écrire des formules, ce qui donne accès à l'ensemble des données sans prendre en compte d'éventuelles restrictions de droits de lecture.",
"Add Table-wide Rule":"Ajouter une règle pour l'ensemble du tableau"
},
"AccountPage":{
@ -52,15 +52,15 @@
"Email":"E-mail",
"Name":"Nom",
"Save":"Enregistrer",
"Password & Security":"Mot de passe & Sécurité",
"Password & Security":"Mot de passe et sécurité",
"Login Method":"Mode de connexion",
"Change Password":"Modifier le mot de passe",
"Allow signing in to this account with Google":"Autoriser la connexion à ce compte avec Google",
"Two-factor authentication":"Authentification à deux facteurs",
"Two-factor authentication is an extra layer of security for your Grist account designed to ensure that you're the only person who can access your account, even if someone knows your password.":"L'authentification à double facteur est une couche additionnelle de sécurité pour votre compte Grist qui permet de s'assurer que vous êtes la seule personne qui peut accéder à votre compte, même si quelqu'un d'autre connaît votre mot de passe.",
"Two-factor authentication is an extra layer of security for your Grist account designed to ensure that you're the only person who can access your account, even if someone knows your password.":"L'authentification à double facteur est une couche supplémentaire de sécurité pour votre compte Grist qui permet de s'assurer que vous êtes la seule personne qui peut accéder à votre compte, même si quelqu'un d'autre connaît votre mot de passe.",
"Theme":"Thème",
"API Key":"Clé d’API",
"Names only allow letters, numbers and certain special characters":"Les noms d'utilisateurs ne doivent contenir que des lettres, des chiffres, et certains caractères spéciaux",
"Names only allow letters, numbers and certain special characters":"Les noms d'utilisateurs ne doivent contenir que des lettres, des chiffres et certains caractères spéciaux",
"Language":"Langue"
},
"AccountWidget":{
@ -415,7 +415,7 @@
"Hidden Columns":"Colonnes cachées",
"Lookups":"Champ rapporté",
"No reference columns.":"Pas de colonne de référence.",
"Apply on record changes":"Appliquer lors de modification de la ligne",
"Apply on record changes":"Appliquer lors des modifications de l'enregistrement",
"Duplicate in {{- label}}":"Duplica dans {{-label}}",
"Created By":"Créé(e) par",
"Last Updated At":"Dernière mise à jour le",
@ -544,7 +544,9 @@
"You do not have write access to the selected workspace":"Vous n’avez pas accès en écriture à ce dossier",
"Remove all data but keep the structure to use as a template":"Supprimer toutes les données mais garder la structure comme modèle",
"Remove document history (can significantly reduce file size)":"Supprimer l'historique du document (peut réduire sensiblement la taille du fichier)",
"Download full document and history":"Télécharger le document complet et l'historique"
"Download full document and history":"Télécharger le document complet et l'historique",
"Download":"Télécharger",
"Download document":"Télécharger le document"
},
"NotifyUI":{
"Upgrade Plan":"Améliorer votre abonnement",
@ -629,7 +631,7 @@
"Detach":"Détacher",
"SELECT BY":"SÉLECTIONNER PAR",
"Select Widget":"Choisir la vue",
"SELECTOR FOR":"SÉLECTEUR",
"SELECTOR FOR":"SÉLECTEUR POUR",
"Save":"Enregistrer",
"You do not have edit access to this document":"Vous n’avez pas accès en écriture à ce document",
"Add referenced columns":"Ajouter une colonne référencée",
@ -644,11 +646,11 @@
"Hidden field":"Champ caché",
"Layout":"Mise en page",
"Submission":"Soumission",
"Submit button label":"Libellé du bouton de soumission",
"Submit button label":"Libellé du bouton de validation",
"Success text":"Message de succès",
"Table column name":"Nom de la colonne",
"Enter redirect URL":"Saisir l'URL de redirection",
"Reset form":"Restaurer le formulaire",
"Reset form":"Réinitialiser le formulaire",
"Submit another response":"Soumettre une autre réponse",
"On the call, we'll take the time to understand your needs and tailor the call to you. We can show you the Grist basics, or start working with your data right away to build the dashboards you need.":"Lors de l'appel, nous prendrons le temps de comprendre vos besoins et d'adapter l'appel à vos besoins. Nous pouvons vous montrer les bases de Grist, ou commencer à travailler avec vos données immédiatement pour construire les tableaux de bord dont vous avez besoin.",
"On the call, we'll take the time to understand your needs and tailor the call to you. We can show you the Grist basics, or start working with your data right away to build the dashboards you need.":"Lors de l'appel, nous prendrons le temps de comprendre vos besoins et d'adapter l'appel à ces derniers. Nous pouvons vous montrer les bases de Grist, ou commencer tout de suite à travailler avec vos données pour construire les tableaux de bord dont vous avez besoin.",
"Schedule your {{freeCoachingCall}} with a member of our team.":"Planifiez votre {{freeCoachingCall}} avec un membre de notre équipe."
},
"FormView":{
@ -1340,10 +1342,10 @@
"Header":"Titre"
},
"UnmappedFieldsConfig":{
"Mapped":"Utilisés",
"Mapped":"Utilisé",
"Select All":"Tout sélectionner",
"Unmap fields":"Champs non utilisés",
"Unmapped":"Non utilisés",
"Unmapped":"Non utilisé",
"Clear":"Effacer",
"Map fields":"Champs utilisés"
},
@ -1355,8 +1357,8 @@
"Delete":"Supprimer"
},
"CustomView":{
"Some required columns aren't mapped":"Certaines colonnes obligatoires ne sont pas mappées",
"To use this widget, please map all non-optional columns from the creator panel on the right.":"Pour utiliser cette vue, mappez toutes les colonnes non optionnelles à partir du panneau du créateur sur la droite."
"Some required columns aren't mapped":"Certaines colonnes obligatoires ne sont pas utilisées",
"To use this widget, please map all non-optional columns from the creator panel on the right.":"Pour utiliser cette vue, utilisez toutes les colonnes obligatoires à partir du panneau du créateur sur la droite."
},
"FormContainer":{
"Build your own form":"Créez votre propre formulaire",
"Freeze {{count}} more columns_other":"さらに {{count}} 列固定する",
"Hide {{count}} columns_one":"列非表示",
"Hide {{count}} columns_one":"列を非表示",
"Insert column to the left":"左側に列を挿入",
"Sorted (#{{count}})_other":"ソート (#{{count}})"
"Sorted (#{{count}})_other":"ソート (#{{count}})",
"Attachment":"添付ファイル",
"Add column":"列を追加",
"Adding UUID column":"UUID列を追加",
"Detect Duplicates in...":"重複を検出...",
"UUID":"UUID",
"Add column with type":"型を指定して列を追加",
"Add formula column":"数式列を追加",
"Apply to new records":"新しいレコードに適用",
"Apply on record changes":"レコードの変更に適用",
"Authorship":"作成者名",
"Timestamp":"タイムスタンプ",
"Detect duplicates in...":"重複を検出...",
"Numeric":"数値",
"Text":"テキスト",
"Integer":"整数",
"Toggle":"トグル",
"Date":"日付",
"DateTime":"日時",
"Choice":"選択",
"Choice List":"複数選択",
"Lookups":"Lookups",
"Shortcuts":"ショートカット",
"Show hidden columns":"非表示列を再表示"
},
"DocMenu":{
"This service is not available right now":"このサービスは現在ご利用いただけません",
"Workspace not found":"ワークスペースが見つかりません",
"Discover More Templates":"その他のテンプレート",
"Current workspace":"現在のワークスペース",
"Edited {{at}}":"{{at}}による編集",
"Edited {{at}}":"{{at}}に更新",
"Pin Document":"ドキュメントをピン留めする",
"Remove":"削除",
"By Date Modified":"変更日",
@ -175,7 +198,14 @@
"Add referenced columns":"参照列の追加",
"TRANSFORM":"変換",
"Sort & Filter":"ソート＆フィルター",
"Widget":"ウィジェット"
"Widget":"ウィジェット",
"Submit button label":"送信ボタンのラベル",
"Submit another response":"別の回答を送信",
"Display button":"ボタンを表示",
"Redirect automatically after submission":"送信後に自動的にリダイレクトする",
"Redirection":"リダイレクト",
"Required field":"必須フィールド",
"Enter redirect URL":"リダイレクト先URL"
},
"FloatingPopup":{
"Maximize":"最大化",
@ -374,9 +404,10 @@
"Rules for table ":"テーブルのルール ",
"Checking...":"チェック中…",
"Special Rules":"特別ルール",
"View As":"として表示",
"View As":"役割で表示",
"Seed rules":"シード・ルール",
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"編集者による構造の編集（例：テーブル、列、レイアウトの変更や削除）、および数式の書き込みを許可し、読み取り制限に関係なくすべてのデータにアクセスできるようにする。"
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"編集者による構造の編集（例：テーブル、列、レイアウトの変更や削除）、および数式の書き込みを許可し、読み取り制限に関係なくすべてのデータにアクセスできるようにする。",
"Add Table-wide Rule":"テーブル全体のルールを追加"
},
"FieldEditor":{
"It should be impossible to save a plain data value into a formula column":"単純なデータ値を数式列に保存することは不可能なはずです",
@ -523,7 +554,7 @@
"Code View":"コードビュー",
"Return to viewing as yourself":"自分自身のビューに戻る",
"Raw Data":"生データ",
"Document History":"ドキュメント履歴"
"Document History":"ドキュメントの履歴"
},
"menus":{
"Reference List":"参照リスト",
@ -548,7 +579,7 @@
"You do not have edit access to this document":"このドキュメントの編集権限がありません",
"Add Widget to Page":"ページにウィジェットを追加する",
"Add Page":"ページを追加",
"Document owners can attempt to recover the document. [{{error}}]":"ドキュメントの所有者は、ドキュメントの回復を試みることができます。[{{error}}]",
"Document owners can attempt to recover the document. [{{error}}]":"ドキュメントのオーナーは、ドキュメントの回復を試みることができます。[{{error}}]",
"Reload":"再読み込み",
"Error accessing document":"ドキュメントへのアクセスエラー",
"Enter recovery mode":"回復モードに入る"
@ -722,13 +753,13 @@
"Save Copy":"コピーを保存"
},
"UserManagerModel":{
"View & Edit":"表示と編集",
"View & Edit":"閲覧と編集",
"Owner":"オーナー",
"None":"なし",
"View Only":"閲覧のみ",
"No Default Access":"デフォルトアクセスなし",
"Viewer":"ビューア",
"Editor":"エディター"
"Viewer":"閲覧者",
"Editor":"編集者"
},
"DocumentUsage":{
"Data Size":"データサイズ",
@ -899,7 +930,7 @@
"Close":"閉じる",
"Cancel":"キャンセル",
"Apply on changes to:":"変更を適用する：",
"Apply to new records":"新しいレコードに適用する",
"Apply to new records":"新しいレコードに適用",
"OK":"OK",
"Current field ":"現在のフィールド ",
"Any field":"任意のフィールド",
@ -913,7 +944,13 @@
"Click the Add New button to create new documents or workspaces, or import data.":"「新規追加」ボタンをクリックして、新しいドキュメントまたはワークスペースを作成するか、データをインポートします。",
"Apply conditional formatting to rows based on formulas.":"数式に基づいて条件付き書式を行に適用します。",
"Click on “Open row styles” to apply conditional formatting to rows.":"行に条件付き書式を適用するには、「行書式を開く」をクリックする。",
"Cells in a reference column always identify an {{entire}} record in that table, but you may select which column from that record to show.":"参照列のセルは常にそのテーブル内の {{entire}} レコードを識別しますが、そのレコードからどの列を表示するかを選択することもできます。"
"Cells in a reference column always identify an {{entire}} record in that table, but you may select which column from that record to show.":"参照列のセルは常にそのテーブル内の {{entire}} レコードを識別しますが、そのレコードからどの列を表示するかを選択することもできます。",
"Formulas support many Excel functions, full Python syntax, and include a helpful AI Assistant.":"数式は多くの Excel 関数、完全な Python 構文をサポートし、便利な AI アシスタントが含まれています。",
"A UUID is a randomly-generated string that is useful for unique identifiers and link keys.":"UUIDはランダムに生成される文字列で、一意の識別子やキーとして役立ちます。",
"The total size of all data in this document, excluding attachments.":"添付ファイルを除く、このドキュメント内のすべてのデータの合計サイズ。",
"Lookups return data from related tables.":"Lookupは関連テーブルからデータを返します。",
"Reference columns are the key to {{relational}} data in Grist.":"参照列は、Grist の {{relational}} データへのキーです。",
"These rules are applied after all column rules have been processed, if applicable.":"これらのルールは、列ルールの処理が終わった後に適用されます。"
},
"AppHeader":{
"Personal Site":"個人サイト",
@ -928,7 +965,13 @@
"You do not have edit access to this document":"このドキュメントへのアクセス権がありません",
"Delete {{formattedTableName}} data, and remove it from all pages?":"{{formattedTableName}} データを削除し、すべてのページから削除しますか?",
"Click to copy":"クリックしてコピー",
"Table ID copied to clipboard":"クリップボードにテーブルIDをコピーしました"
"Table ID copied to clipboard":"クリップボードにテーブルIDをコピーしました",
"Edit Record Card":"レコードカードを編集",
"Record Card":"レコードカード",
"Record Card Disabled":"レコードカードを無効化",
"Remove Table":"テーブルを削除",
"Rename Table":"テーブル名を編集",
"{{action}} Record Card":"レコードカードを{{action}}"
},
"NTextBox":{
"false":"false",
@ -1078,5 +1121,17 @@
},
"sendToDrive":{
"Sending file to Google Drive":"Googleドライブにファイルを送信する"
"Permission to edit document structure":"Разрешение на редактирование структуры документа",
"When adding table rules, automatically add a rule to grant OWNER full access.":"При добавлении правил таблицы, автоматически добавить правило для предоставления ВЛАДЕЛЬЦУ полного доступа.",
"This default should be changed if editors' access is to be limited. ":"Это значение по умолчанию следует изменить, если требуется ограничить доступ редакторов. ",
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"Позволяет редакторам редактировать структуру (например, изменять и удалять таблицы, столбцы, макеты) и писать формулы, которые предоставляют доступ ко всем данным независимо от ограничений на чтение."
"Allow editors to edit structure (e.g. modify and delete tables, columns, layouts), and to write formulas, which give access to all data regardless of read restrictions.":"Позволяет редакторам редактировать структуру (например, изменять и удалять таблицы, столбцы, макеты) и писать формулы, которые предоставляют доступ ко всем данным независимо от ограничений на чтение.",
"Enter email address":"Введите адрес электронной почты",
@ -1119,7 +1120,11 @@
"Lookups return data from related tables.":"Lookups возвращают данные из связанных таблиц.",
"Use reference columns to relate data in different tables.":"Используйте ссылочные столбцы для сопоставления данных в разных таблицах.",
"You can choose from widgets available to you in the dropdown, or embed your own by providing its full URL.":"Вы можете выбрать виджеты, доступные вам в раскрывающемся списке, или встроить свой собственный, указав его полный URL-адрес.",
"Formulas support many Excel functions, full Python syntax, and include a helpful AI Assistant.":"Формулы поддерживают множество функций Excel, полный синтаксис Python и включает полезного помощника AI."
"Formulas support many Excel functions, full Python syntax, and include a helpful AI Assistant.":"Формулы поддерживают множество функций Excel, полный синтаксис Python и включает полезного помощника AI.",
"Build simple forms right in Grist and share in a click with our new widget. {{learnMoreButton}}":"Создавайте простые формы прямо в Grist и делитесь ими одним щелчком мыши с помощью нашего нового виджета.. {{learnMoreButton}}",
"Forms are here!":"Формы уже здесь!",
"Learn more":"Узнать больше",
"These rules are applied after all column rules have been processed, if applicable.":"Эти правила применяются после обработки всех правил столбцов, если это применимо."
},
"DescriptionConfig":{
"DESCRIPTION":"ОПИСАНИЕ"
@ -1342,5 +1347,33 @@
},
"Editor":{
"Delete":"Удалить"
},
"FormConfig":{
"Field rules":"Правила полей",
"Required field":"Обязательное поле"
},
"CustomView":{
"Some required columns aren't mapped":"Некоторые обязательные столбцы не сопоставлены",
"To use this widget, please map all non-optional columns from the creator panel on the right.":"Чтобы использовать этот виджет, сопоставьте все необязательные столбцы с панели создателя справа."
},
"FormContainer":{
"Build your own form":"Создайте свою собственную форму",
"Powered by":"Разработано"
},
"FormModel":{
"There was a problem loading the form.":"Возникла проблема с загрузкой формы.",
"You don't have access to this form.":"У вас нет доступа к этой форме.",
"Oops! The form you're looking for doesn't exist.":"Ой! Форма, которую вы ищете, не существует.",
"Oops! This form is no longer published.":"Ой! Эта форма больше не публикуется."
},
"FormErrorPage":{
"Error":"Ошибка"
},
"FormPage":{
"There was an error submitting your form. Please try again.":"При отправке формы произошла ошибка. Пожалуйста, попробуйте еще раз."
},
"FormSuccessPage":{
"Form Submitted":"Форма отправлена",
"Thank you! Your response has been recorded.":"Спасибо! Ваш ответ учтен."
Paul Fitzpatrick
2 months ago