)]}'
{"tools/generatepot.sh":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"a9364a511084a60af57f6e45310251db76db3d0c","unresolved":false,"context_lines":[{"line_number":13,"context_line":"# License for the specific language governing permissions and limitations"},{"line_number":14,"context_line":"# under the License."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"DOCNAME\u003di18n"},{"line_number":17,"context_line":"DIRECTORY\u003ddoc"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"if [ -x \"$(command -v getconf)\" ]; then"}],"source_content_type":"text/x-sh","patch_set":1,"id":"5ff73747_5745b46f","line":16,"range":{"start_line":16,"start_character":8,"end_line":16,"end_character":12},"updated":"2017-04-22 10:10:09.000000000","message":"question: what is the reason of the name? Can\u0027t we have a more meaningful name like i18n-guide or something? We already use \u0027i18n.po(t)\u0027 for glossary and I am not sure it is a good idea to use the same name.","commit_id":"2fa413323ffaa096ae40411b720a4e29c2ed0e8c"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"bf46f486b93e7131b1e5453a0664d43380e031bd","unresolved":false,"context_lines":[{"line_number":13,"context_line":"# License for the specific language governing permissions and limitations"},{"line_number":14,"context_line":"# under the License."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"DOCNAME\u003di18n"},{"line_number":17,"context_line":"DIRECTORY\u003ddoc"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"if [ -x \"$(command -v getconf)\" ]; then"}],"source_content_type":"text/x-sh","patch_set":1,"id":"5ff73747_d758a457","line":16,"range":{"start_line":16,"start_character":8,"end_line":16,"end_character":12},"in_reply_to":"5ff73747_5745b46f","updated":"2017-04-22 10:11:11.000000000","message":"This name is visible in Zanata, so IMHO the name should be a name which translators easily understand.","commit_id":"2fa413323ffaa096ae40411b720a4e29c2ed0e8c"},{"author":{"_account_id":14482,"name":"Ian Y. Choi","email":"ianyrchoi@gmail.com","username":"ianychoi"},"change_message_id":"aa979c9f1ff467d956467ccac31979eb29f3f12c","unresolved":false,"context_lines":[{"line_number":13,"context_line":"# License for the specific language governing permissions and limitations"},{"line_number":14,"context_line":"# under the License."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"DOCNAME\u003di18n"},{"line_number":17,"context_line":"DIRECTORY\u003ddoc"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"if [ -x \"$(command -v getconf)\" ]; then"}],"source_content_type":"text/x-sh","patch_set":1,"id":"5ff73747_07891e74","line":16,"range":{"start_line":16,"start_character":8,"end_line":16,"end_character":12},"in_reply_to":"5ff73747_d758a457","updated":"2017-04-24 15:05:13.000000000","message":"Thanks a lot for your comment. I have not considered glossary i18n.pot filename when I chose the DOCNAME. Done","commit_id":"2fa413323ffaa096ae40411b720a4e29c2ed0e8c"}]}