gtranslator issueshttps://gitlab.gnome.org/GNOME/gtranslator/-/issues2023-12-28T10:19:22Zhttps://gitlab.gnome.org/GNOME/gtranslator/-/issues/195Toast can be very long2023-12-28T10:19:22ZMaximilianoToast can be very long![image](/uploads/38727e2b2d8fadcda783ae6db550fd7f/image.png)![image](/uploads/38727e2b2d8fadcda783ae6db550fd7f/image.png)MaximilianoMaximilianohttps://gitlab.gnome.org/GNOME/gtranslator/-/issues/194Using "find" will slow/freeze/crash gtranslator when the po file is big2024-01-09T07:12:55ZlumingzhUsing "find" will slow/freeze/crash gtranslator when the po file is big## STEP:
- open gtranslator
- open a big po file like [gimp.po-ui.master.zh_CN.po](/uploads/17bc1089caab139c0876d874da3e2ca8/gimp.po-ui.master.zh_CN.po)
- use "find" to search some Chinese words like “蒙板” (English words can trigger this ...## STEP:
- open gtranslator
- open a big po file like [gimp.po-ui.master.zh_CN.po](/uploads/17bc1089caab139c0876d874da3e2ca8/gimp.po-ui.master.zh_CN.po)
- use "find" to search some Chinese words like “蒙板” (English words can trigger this bug as well but better than Chinese words)
- click "find next" button repeatedly
- click "find next" button quickly and repeatedly if gtranslator didn't freeze or crash
## RUNTIME:
- OS: Fedora Silverblue 39.20231125.0 (2023-11-25T02:15:38Z)
- DE: GNOME 45.1
- gtranslator: 45.3 from flathub
PS: #144 still exists.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/192undo/redo buttons are never enabled2023-11-27T06:34:58ZMaximilianoundo/redo buttons are never enabledBoth buttons are permanently insensitive, at least when translating from a file.Both buttons are permanently insensitive, at least when translating from a file.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/188Crash when typing special characters2023-10-28T12:38:02ZRafael FontenelleCrash when typing special charactersI'm experiencing crashes as soon as I typo any special character like ã ã à ç etc. Other characters work just fine.
This only happens with GtranslatorDevel flatpak package, not when built locally from master branch.
Output when it cras...I'm experiencing crashes as soon as I typo any special character like ã ã à ç etc. Other characters work just fine.
This only happens with GtranslatorDevel flatpak package, not when built locally from master branch.
Output when it crashes:
```
(gtranslator:2): GLib-CRITICAL **: 22:25:30.278: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed
(gtranslator:2): GLib-CRITICAL **: 22:25:30.278: g_variant_new_variant: assertion 'value != NULL' failed
```
Versions:
- GtranslatorDevel flatpak: 45.1-2-gc34e776a+
- Built locally: 45.2.r5722.1315ed6ahttps://gitlab.gnome.org/GNOME/gtranslator/-/issues/187Crash when searched term doesn't exist2023-10-25T06:51:28Zrene-cotyCrash when searched term doesn't existWhen searching for a string in a .po file, if it doesn't exist the app will crash.
Same happens when the string existed but was then edited and researched again after that.
(Here is a demo, where I was searching for the word 'compatibl...When searching for a string in a .po file, if it doesn't exist the app will crash.
Same happens when the string existed but was then edited and researched again after that.
(Here is a demo, where I was searching for the word 'compatible' which doesn't exist in my file: after I hit 'Enter' the app freezes)
[Capture vidéo du 2023-10-06 15-37-07.webm](/uploads/1165f01ebd3783099a15c1ff55aa73ec/Capture_vid%C3%A9o_du_2023-10-06_15-37-07.webm)https://gitlab.gnome.org/GNOME/gtranslator/-/issues/185Trying to change the sort order of strings freezes the app2023-10-02T17:36:36ZJürgen BenvenutiTrying to change the sort order of strings freezes the appWhen I try to change the sort order of strings in `gtranslator`, the app freezes and I have to close it. Version is Flatpak 45.1.When I try to change the sort order of strings in `gtranslator`, the app freezes and I have to close it. Version is Flatpak 45.1.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/183Search navigation doesn't scroll main panel2023-09-28T06:09:33ZRafael FontenelleSearch navigation doesn't scroll main panel## Description
When using the search feature and clicking the "next" arrow to navigate through the search results, I've noticed an issue. While the lower panel correctly updates to display the next search result's content, the main panel...## Description
When using the search feature and clicking the "next" arrow to navigate through the search results, I've noticed an issue. While the lower panel correctly updates to display the next search result's content, the main panel fails to scroll to the corresponding position of the search result in the list of messages. As a result, the user needs to manually scroll through the list to locate the newly displayed search result, which disrupts the workflow and can lead to confusion.
## Expected Behavior
Upon clicking the "next" arrow in the search dialog, the main panel should automatically scroll to the position of the displayed search result in the list of messages.
## Steps to Reproduce
1. Open a po file in the translation editor.
2. Enter a search query in the search dialog.
3. Click the "next" arrow to navigate through the search results.
4. Observe that the lower panel updates to show the next search result, but the main panel remains stationary.
## Video
![search-in-gtr](/uploads/1358d45d26f40a1456be1f2634364436/search-in-gtr.webm)https://gitlab.gnome.org/GNOME/gtranslator/-/issues/182Unable to PO file from CLI or double-clicking it in a file browser2023-08-28T16:43:31ZRafael FontenelleUnable to PO file from CLI or double-clicking it in a file browserWhen I double click a PO file in the Files app or run `flatpak run org.gnome.GtranslatorDevel any_file.po`, the GUI won't come up and `echo $?` gives me 139 exit code. What works is to launch Gtranslator and use the file selector to open...When I double click a PO file in the Files app or run `flatpak run org.gnome.GtranslatorDevel any_file.po`, the GUI won't come up and `echo $?` gives me 139 exit code. What works is to launch Gtranslator and use the file selector to open a PO file.
version: 45.alpha0-9-g6bdad099+
Logs:
- [strace-log.txt](/uploads/62697716184cf79c5fbe460e89e58b19/strace-log.txt)
- [debug-messages.txt](/uploads/b0c0fa0326da2d689675b77f100f3ad2/debug-messages.txt)https://gitlab.gnome.org/GNOME/gtranslator/-/issues/181[45.alpha] unable to build - error: format not a string literal and no format...2023-08-01T11:02:10ZFabian Bornschein[45.alpha] unable to build - error: format not a string literal and no format argumentsHi. While trying to build the new alpha release I face following error:
```
[36/157] Compiling C object src/libgtranslator.so.p/gtr-language.c.o
[37/157] Compiling C object src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o
FAILE...Hi. While trying to build the new alpha release I face following error:
```
[36/157] Compiling C object src/libgtranslator.so.p/gtr-language.c.o
[37/157] Compiling C object src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o
FAILED: src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o
cc -Isrc/libgtranslator.so.p -Isrc -I../gtranslator/src -I. -I../gtranslator -Isrc/translation-memory -I../gtranslator/src/translation-memory -Isrc/codeview -I../gtranslator/src/codeview -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/graphene-1.0 -I/usr/lib/graphene-1.0/include -I/usr/include/libadwaita-1 -I/usr/include/appstream -I/usr/include/libgda-6.0 -I/usr/include/libgda-6.0/libgda -I/usr/include/libxml2 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gtksourceview-5 -I/usr/include/libsoup-3.0 -I/usr/include/json-glib-1.0 -flto=auto -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/gtranslator/src=/usr/src/debug/gtranslator -flto=auto -fPIC -pthread -mfpmath=sse -msse -msse2 -mfpmath=sse -msse -msse2 -mfpmath=sse -msse -msse2 -MD -MQ src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o -MF src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o.d -o src/libgtranslator.so.p/gtr-close-confirmation-dialog.c.o -c ../gtranslator/src/gtr-close-confirmation-dialog.c
../gtranslator/src/gtr-close-confirmation-dialog.c: In function ‘build_multiple_docs_dialog’:
../gtranslator/src/gtr-close-confirmation-dialog.c:333:3: error: format not a string literal and no format arguments [-Werror=format-security]
333 | adw_message_dialog_format_body (ADW_MESSAGE_DIALOG (dlg), str);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
[38/157] Compiling C object src/libgtranslator.so.p/gtr-application.c.o
[39/157] Compiling C object src/libgtranslator.so.p/gtr-file-dialogs.c.o
[40/157] Compiling C object src/libgtranslator.so.p/gtr-context.c.o
```
Log:
[gtranslator-45alpha0-1-x86_64-build.log](/uploads/79725e8312c930b5740eb666a846f9da/gtranslator-45alpha0-1-x86_64-build.log)
System:
* Archlinux
* GTK4 4.11.3
* libadwaita 1.4alpha
* gtksourceview 5.8.0https://gitlab.gnome.org/GNOME/gtranslator/-/issues/180Introduce spellchecking2023-08-25T07:49:03ZDaniel Garcia MorenoIntroduce spellcheckingThe spell checking functionality was removed during the migration to Gtk4 because the [gspell](https://gitlab.gnome.org/GNOME/gspell/) library it's not available for gtk4.
Recently Christian Hergert has released a simple spell check lib...The spell checking functionality was removed during the migration to Gtk4 because the [gspell](https://gitlab.gnome.org/GNOME/gspell/) library it's not available for gtk4.
Recently Christian Hergert has released a simple spell check library, [libspelling](https://gitlab.gnome.org/chergert/libspelling), that we should use to bring back the spell check in the translation source view.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/177--version output diverges from About dialog2023-07-18T18:23:40ZRafael Fontenelle--version output diverges from About dialogJust updated my GtranslatorDevel from nightly, and looks like it is from the latest commit dddcd3e1 so far. I see a previous commmit bumping the version to 45.alpha, but About dialog doesn't show that version.
```shell
$ flatpak run org...Just updated my GtranslatorDevel from nightly, and looks like it is from the latest commit dddcd3e1 so far. I see a previous commmit bumping the version to 45.alpha, but About dialog doesn't show that version.
```shell
$ flatpak run org.gnome.GtranslatorDevel --version
... omitted some debug info printed ...
gtranslator - 45.alpha0
```
![Screenshot of Gtranslator's About dialog showing version "42.0.279-gdddcd3e1+"](/uploads/8749d0f681ccc4c85d770bd6eed6db40/image.png)https://gitlab.gnome.org/GNOME/gtranslator/-/issues/176Add pot/po translation wit AI2023-06-24T19:45:56ZTAO ZUHONGAdd pot/po translation wit AI## Translate with language file(LINGUAS)
Translate to all languages in the language file(LINGUAS), based on pot file<br/>
param 1: pot file<br/>
param 2: LINGUAS<br/>
## Translate all language file in the po folder
Translate all languag...## Translate with language file(LINGUAS)
Translate to all languages in the language file(LINGUAS), based on pot file<br/>
param 1: pot file<br/>
param 2: LINGUAS<br/>
## Translate all language file in the po folder
Translate all language file in the po folder with native language<br/>
param 1: native language<br/>
param 2: po folder<br/>
## Translate to specific language<br/>
param 1: pot/po file<br/>
param 2: input language<br/>
param 3: target language<br/>https://gitlab.gnome.org/GNOME/gtranslator/-/issues/173GNOME 42 is end-of-life2023-05-30T18:35:25ZJohn Erling BladGNOME 42 is end-of-lifeThe GNOME 42 runtime is no longer supported as of March 21, 2023.The GNOME 42 runtime is no longer supported as of March 21, 2023.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/172Download from DL fails for "Norwegian (Bokmål and Nynorsk)" team2023-07-18T19:33:51ZJohn Erling BladDownload from DL fails for "Norwegian (Bokmål and Nynorsk)" teamTrying to download po-files for translation from Damned Lies for "Secrets" gives an error message "Error loading file info: Not Found". The culprit may be that Norwegian as used in the team identifier is the macro language with code "no"...Trying to download po-files for translation from Damned Lies for "Secrets" gives an error message "Error loading file info: Not Found". The culprit may be that Norwegian as used in the team identifier is the macro language with code "no", while Bokmål is a language with code "nb" and Nynorsk is a language with code "nn".
The team identifier "Norwegian (Bokmål and Nynorsk)" is combined as most Norwegians read and write both forms. The team identifier use "no", but the team page links "nb" and "nn". The team page is at [Oversettelseslag for Norwegian (Bokmål and Nynorsk)](https://l10n.gnome.org/teams/no/).
Ref [gtr-translate.page](https://gitlab.gnome.org/GNOME/gtranslator/-/blob/master/help/C/gtr-translate.page)
```
You will have to register at Damned Lies platform and <link href="http://l10n.gnome.org/teams/">join the team of translators</link> for your target language.
```
Note that there exist separate pages for [Bokmål](https://l10n.gnome.org/teams/nb/) and [Nynorsk](https://l10n.gnome.org/teams/nn/) but there are no teams.
Note also that I'm listed as check-in, but not as a translator on the teams page. Not sure if that is relevant, as I'm clearly a member of the team.
Actual version is "42.0", downloaded from [flathub](https://flathub.org/apps/details/org.gnome.Gtranslator).
![bilde](/uploads/ce178fe7fe58a3ce8fb5ec11765b4408/bilde.png)https://gitlab.gnome.org/GNOME/gtranslator/-/issues/169Create and use Gtranslator emblem2023-01-05T14:48:04ZPhilip Gotophilip.goto@gmail.comCreate and use Gtranslator emblemMany GNOME apps have an emblem that is used for their Matrix room and GitLab page that helps with their branding. It would be nice if Gtranslator also has this. Some examples of how that could look like (generated with [Emblem](https://a...Many GNOME apps have an emblem that is used for their Matrix room and GitLab page that helps with their branding. It would be nice if Gtranslator also has this. Some examples of how that could look like (generated with [Emblem](https://apps.gnome.org/app/org.gnome.design.Emblem/)):
<img src="/uploads/a0af31092a0403aab4afd1414e99f39f/emblem_gtranslator_green_flat_light.png" width=64px>
<img src="/uploads/9f8dec925994005412708771d1815523/emblem_gtranslator_green_flat_dark.png" width=64px>
<br>
<img src="/uploads/f0543a0c6f3b86292a1680f29b6373fe/emblem_gtranslator_green_grad_up.png" width=64px>
<img src="/uploads/9b3b038d3ee0a8716074f16e27bfc145/emblem_gtranslator_green_grad_down.png" width=64px>https://gitlab.gnome.org/GNOME/gtranslator/-/issues/165Remove Quit entry from main menu2023-11-29T22:33:18ZMaximilianoRemove Quit entry from main menuThe headerbar already has a quit option, generally the last option is "About Translator".The headerbar already has a quit option, generally the last option is "About Translator".https://gitlab.gnome.org/GNOME/gtranslator/-/issues/158[Regression] Focus lost when clicking on string in message table2022-05-11T18:37:47ZDaniel Mustieles García[Regression] Focus lost when clicking on string in message tableYesterday I updated GTR to last flatpak's versions (v42) and I've notice that, when I click on a string in the table message focus is not in the translated_string box, so if I start typing, text is shown out of that box.
This was workin...Yesterday I updated GTR to last flatpak's versions (v42) and I've notice that, when I click on a string in the table message focus is not in the translated_string box, so if I start typing, text is shown out of that box.
This was working in previous versions, I think this has been changed due to commits to give focus to search bar when Ctrl-F is pressed.
Can this be fixed without damaging the give_focus_to_search_bar function?
I think this is an important issue (just my opinion).
Thanks!GNOME 42Daniel Garcia MorenoDaniel Garcia Morenohttps://gitlab.gnome.org/GNOME/gtranslator/-/issues/157Port preferences window to HdyPreferencesWindow2023-12-23T10:47:43ZMaximilianoPort preferences window to HdyPreferencesWindowThe current style is incompatible with libadwaita, this dialog will make any attempt to port the app to GTK 4 harder.
It would be interesting to count with designer's help with this preference which would probably be a good fit for a Li...The current style is incompatible with libadwaita, this dialog will make any attempt to port the app to GTK 4 harder.
It would be interesting to count with designer's help with this preference which would probably be a good fit for a ListBox
![image](/uploads/23f15ddd6f39e24109775532cf205a28/image.png)
cc: @bertob , @adayhttps://gitlab.gnome.org/GNOME/gtranslator/-/issues/156Opening the search bar and pressing `esc` hides the searchbar but keeps the b...2022-05-11T19:31:06ZDaniel Garcia MorenoOpening the search bar and pressing `esc` hides the searchbar but keeps the button pressed![image](/uploads/9a929cbcad7f7b6ab4505712ed7cc262/image.png)
Opening the search bar and pressing `esc` hides the searchbar but doesn't change the button state and it's not possible to show it again without pressing in the button.![image](/uploads/9a929cbcad7f7b6ab4505712ed7cc262/image.png)
Opening the search bar and pressing `esc` hides the searchbar but doesn't change the button state and it's not possible to show it again without pressing in the button.https://gitlab.gnome.org/GNOME/gtranslator/-/issues/155Clicking on Edit or Add notes open the codeview2022-04-05T10:44:31ZDaniel Garcia MorenoClicking on Edit or Add notes open the codeviewClicking in the right sidebar menu is triggering the code viewer always, even if you click directly in the "Add note", the code viewer dialog is shown.Clicking in the right sidebar menu is triggering the code viewer always, even if you click directly in the "Add note", the code viewer dialog is shown.