-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve translatable strings. #1903
base: stable
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good approach, but there is still room for improvements. ;-)
@@ -309,8 +309,8 @@ static const TxnTypeVec short_types | |||
// Translators: this is a stock transaction describing cover | |||
// buying stock, and recording capital gain/loss | |||
N_("Buy to cover short"), | |||
N_("Buy back stock to cover short position, and record capital gain/loss. " | |||
"\n\nIf you are unable to calculate capital gains you can enter a placeholder " | |||
N_("Buy back stock to cover short position, and record capital gain/loss.\n\nIf " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better split the message and keep the layout "\n\n" outside of the translation, e.g.:
printf ("%s\n\n%s", _(para1), _(para2))
@@ -394,8 +394,8 @@ static const TxnTypeVec short_types | |||
// split when shorting stock | |||
N_("Stock split"), | |||
N_("Company issues additional units, thereby reducing the stock price by a divisor, " | |||
"while keeping the total monetary value of the overall investment constant. " | |||
"\n\nIf the split results in a cash in lieu for remainder units, please " | |||
"while keeping the total monetary value of the overall investment constant.\n\nIf " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above
@@ -1727,7 +1727,7 @@ | |||
<property name="model">imexporter-list</property> | |||
<property name="visible">True</property> | |||
<property name="can-focus">True</property> | |||
<property name="tooltip-text" translatable="yes">This list contains the file formats that AQBanking knows how to import. The profile list contains specializations and is populated according to which format you select in this list.</property> | |||
<property name="tooltip-text" translatable="yes">This list contains the file formats that AqBanking knows how to import. The profile list contains specializations and is populated according to which format you select in this list.</property> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally we would in a separate "preparing patch for msgmerge" replace all occurrences of "AQBanking" in all .po files using sed. Before grep also the sources.
@@ -191,7 +191,7 @@ gnc_plugin_bi_import_getFilename(GtkWindow *parent) | |||
gtk_file_filter_set_name (filter, "text files (*.txt)"); | |||
gtk_file_filter_add_pattern (filter, "*.txt"); | |||
filters = g_list_append( filters, filter ); | |||
filename = gnc_file_dialog(parent, _("Import Bills or Invoices from csv"), filters, NULL, GNC_FILE_DIALOG_IMPORT); | |||
filename = gnc_file_dialog(parent, _("Import Bills or Invoices from CSV"), filters, NULL, GNC_FILE_DIALOG_IMPORT); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps also a term to grep for.
(set-opt options headingpage2 optname-invoice-number-text (G_ "Invoice #: ")) | ||
(set-opt options headingpage2 optname-ref-text (G_ "Reference: ")) | ||
(set-opt options headingpage2 optname-jobname-text (G_ "Engagement: ")) | ||
(set-opt options headingpage2 optname-invoice-number-text (G_ "Invoice #:")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to insert the space somewhere else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, i've checked the report and it looks ok for me.
@@ -1335,11 +1335,11 @@ gnc_option_db_book_options(GncOptionDB* odb) | |||
N_("Length of time to change the used invoice report. A value of 0 means disabled."), | |||
0.0, 0.0, 20.0, 1.0); | |||
gnc_register_taxtable_option(odb, business_section, | |||
N_("Default Customer TaxTable"), "f1", | |||
N_("Default Customer Tax Table"), "f1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also a grep candidate.
Are there any errors in the content of the changes? If not, please accept the PR, as I can't work through the tasks you suggested. |
To be done after PR #1895 |
51b7f00
to
22adbb7
Compare
Very good, but I see still markups in glade files:
If we can replace the last remaining |
I think this one is easy to fix by splitting the text into separate labels like... As for the other two files, if you want to remove the markup, I do not think splitting the text is worth while or appropriate. The only thing I can suggest is for the dialog-user, remove all the italics and just put |
Seems OK for me, but now someone (I fear I) has to create the preparing patch for the po files. |
I started on that but quickly realized that there are wording changes as well as formatting changes. I can robotically remove the markup and the associated fuzzies but while I can manage to fix the translation of -"the starting balance.\n"
-"\n"
-"<b>Note:</b> all accounts except Equity and placeholder accounts may have an "
-"opening balance."
+"the starting balance." in some European languages there's no way I could do so in the languages using non-latin scripts. What do you do in those cases? |
If you patch the po files before the msgmerge, no new fuzzy flags should be created. That is also the logical error in @cstim's remove-suffix.sh. It would also remove before existing fuzzy flags.
This label was split in 2 or 3. IMHO it is OK to mark them as fuzzy.
I see 2 tasks:
|
@jralls other patches can map
|
Largely manual then. Well, that isn't happening by Sunday so I guess these changes get to sit out another cycle. As for
Uh-huh. We also have Arabic, Bengali, Cyrillic, Devanagari, Hangul, Hebrew, Kannada, Manipuri, Marathi, Tamil, Telugu, Urdu, and Vietnamese. I guess one can look at existing msgids with full stops and see if there's a corresponding character at the end of the line. Maybe by December. |
These strings are labeled as "Source needs review" in Weblate.
as recommended in the GUI-Guidelines for 'Markups in Text' in the wiki. * Replace markup elements such as <b> * Change attribute elements
... from the following content.
use gnc-class-title instead of <span weight="bold" size="larger"> and gnc-class-emphasis instead of <span style="italic">
0e91092
to
beaab58
Compare
These strings are labeled as "Source needs review" in Weblate.