issue_comments
7 rows where "updated_at" is on date 2022-09-01 sorted by user
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions
id | html_url | issue_url | node_id | user ▼ | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1233680261 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233680261 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiHeF | simonw 9599 | 2022-09-01T03:05:57Z | 2022-09-01T03:05:57Z | OWNER | OK, I'm convinced that it's time to start figuring this out. I've done a little bit of this with Django in the past, but Datasette isn't built on Django. It looks to me like the key library for implementing this is Babel: https://babel.pocoo.org/en/latest/ It's been around since 2007 and is very widely used: https://github.com/python-babel/babel/network/dependents?package_id=UGFja2FnZS01MDM0NTU3NQ%3D%3D Also found these hints on getting it to work with Jinja: https://stackoverflow.com/questions/12046998/babel-doesnt-recognize-jinja2-extraction-method-for-language-support |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 | |
1233680769 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233680769 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiHmB | simonw 9599 | 2022-09-01T03:06:44Z | 2022-09-01T03:06:44Z | OWNER | My hope is that Datasette actually has a relatively small i18n footprint - there really aren't that many screens with strings that will need translating. Translating the documentation would be a much bigger task, but that's not a blocker on getting the interface itself internationalized. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 | |
1233682708 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233682708 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiIEU | simonw 9599 | 2022-09-01T03:09:36Z | 2022-09-01T03:09:36Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 | ||
1233697166 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233697166 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiLmO | simonw 9599 | 2022-09-01T03:36:44Z | 2022-09-01T03:36:44Z | OWNER | I don't want to start any efforts around documentation translation until after the Datasette 1.0 release, because I'd like to be confident that we're not translating documentation that may have some big changes before Datasette is fully stable! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 | |
1234925616 | https://github.com/simonw/datasette/issues/1798#issuecomment-1234925616 | https://api.github.com/repos/simonw/datasette/issues/1798 | IC_kwDOBm6k_c5Jm3gw | simonw 9599 | 2022-09-01T23:56:33Z | 2022-09-01T23:56:33Z | OWNER | Oh that's a classic YAML problem, I hadn't realized it would affect Datasette like this! You should be able to fix it by quoting the ```yaml
title: Some title
description_html: |-
This is an experiment. databases: "off": tables: products_from_owners: title: products_from_owners* description_html: |- Description ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Parts of YAML file do not work when db name is "off" 1359557737 | |
1233684765 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233684765 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiIkd | johnfelipe 428820 | 2022-09-01T03:12:50Z | 2022-09-01T03:12:50Z | NONE | I want to begin translation to es and it documentation, if u like i would do PR asap. But user interface, frontend and backend is a good feature be i18n support. When you have may be .pot file I can translate to, or Json file with all strings for internationalized |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 | |
1233702481 | https://github.com/simonw/datasette/issues/1775#issuecomment-1233702481 | https://api.github.com/repos/simonw/datasette/issues/1775 | IC_kwDOBm6k_c5JiM5R | johnfelipe 428820 | 2022-09-01T03:48:27Z | 2022-09-01T03:48:27Z | NONE | I want to do may be 3 or 4 PR for your evaluation, and when you allowed then I want supporting that effort El mié, 31 de ago. de 2022, 10:36 p. m., Simon Willison ***@***.*** escribió:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
i18n support 1323346408 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 2