extract locales from vue files

[cconard96]

No description provided.

[trasher]

Please fix conflict

[cedric-anne]

It does not seems to work as expected.

For instance, after applying the following patch and run the extrat command, the new string was not added to pot file.

diff --git a/js/src/vue/Debug/Toolbar.vue b/js/src/vue/Debug/Toolbar.vue
index 48acb1c694..d59bb80fda 100644
--- a/js/src/vue/Debug/Toolbar.vue
+++ b/js/src/vue/Debug/Toolbar.vue
@@ -328,6 +328,7 @@
             }
         }).done((data) => {
             ajax_request.profile = data;
+            const a = __('This text should be extracted');
 
             $.each(ajax_request.profile.sql.queries, (i, query) => {
                 ajax_request.profile.sql.queries[i].query = cleanSQLQuery(query.query);

[cedric-anne]

Also, running the command on current main branch result in warnings:

./js/src/vue/Debug/Widget/HTTPRequests.vue:154: warning: unterminated string

[cconard96]

It does not seems to work as expected.

For instance, after applying the following patch and run the extrat command, the new string was not added to pot file.

diff --git a/js/src/vue/Debug/Toolbar.vue b/js/src/vue/Debug/Toolbar.vue
index 48acb1c694..d59bb80fda 100644
--- a/js/src/vue/Debug/Toolbar.vue
+++ b/js/src/vue/Debug/Toolbar.vue
@@ -328,6 +328,7 @@
             }
         }).done((data) => {
             ajax_request.profile = data;
+            const a = __('This text should be extracted');
 
             $.each(ajax_request.profile.sql.queries, (i, query) => {
                 ajax_request.profile.sql.queries[i].query = cleanSQLQuery(query.query);

It seems random when it works. I know for a fact that at least some strings were extracted. All using the same __ function.

Also, running the command on current main branch result in warnings:

Makes absolutely no sense to me. A file with nothing even matching the patterns for localization functions and a line that is completely valid JS same with the other line in the function.

row.css('background-color', '#FFFF7B80');

[cedric-anne]

I think it may be due to some (not so) recent JS language features that are not handled correctly by xgettext.

We have to understand what can cause such issues, to ensure we will not have issues with translation extracting. For instance, here is the kind of issues that may appears when new language features are introduced: https://savannah.gnu.org/bugs/?func=detailitem&item_id=62158