[Reported] Dooble browser -- localization can [NOT] be fixed easily { HP issue #9964 }

[KitsunePrefecture]

Ahoy !

I updated Dooble – hoping localization fixed.

When I launched : the same warning can be found →

Dooble wants to find language files at Linux way settings/config directory →
/boot/home/Translations/Dooble_hu_HU.qm

I investigated
Is it really missing ?
or was just created / put elsewhere ?

1. First I wanted to check in user directory

/boot/home/config/settings/dooble
or
/boot/home/config/settings/Dooble

~> ls -l /boot/home/config/settings/*oobl*
total 546
-rw-r--r-- 1 user root  20480 dec.    9 10:05 dooble_accepted_or_blocked_domains.db
-rw-r--r-- 1 user root      0 dec.    3 08:26 dooble_certificate_exceptions.db
-rw-r--r-- 1 user root      0 dec.    3 08:46 dooble_charts.db
-rw-r--r-- 1 user root  53248 jan.    2 14:19 dooble_cookies.db
-rw-r--r-- 1 user root  12288 dec.    3 08:26 dooble_downloads.db
-rw-r--r-- 1 user root 360448 jan.    2 12:59 dooble_favicons.db
-rw-r--r-- 1 user root  36864 jan.    2 14:19 dooble_history.db
-rw-r--r-- 1 user root  12288 dec.    3 08:26 dooble_search_engines.db
-rw-r--r-- 1 user root  36864 jan.    2 14:19 dooble_settings.db
-rw-r--r-- 1 user root      0 dec.    3 08:26 dooble_style_sheets.db
drwx------ 1 user root   2048 jan.    2 14:19 WebEnginePersistentStorage
~> 
~> ls -ld /boot/home/config/settings/*oobl*
drwxr-xr-x 1 user root 2048 jan.    2 14:19 /boot/home/config/settings/dooble
~> 

Nothing like the given language file : Dooble_hu_HU.qm, not even a Translations directory.

2. So I wanted to check in application directory

/boot/system/apps/dooble
or
/boot/system/apps/Dooble

~> ls -ld /boot/system/apps/*oobl*
dr-xr-xr-x 1 user root 0 jan.    2 13:44 /boot/system/apps/Dooble
~> ls -l /boot/system/apps/Dooble
total 3351
dr-xr-xr-x 1 user root       0 jan.    2 13:44 Data
-r-xr-xr-x 1 user root 3431159 jan.    2 13:44 Dooble
dr-xr-xr-x 1 user root       0 jan.    2 13:44 Images
dr-xr-xr-x 1 user root       0 jan.    2 13:44 lib
dr-xr-xr-x 1 user root       0 jan.    2 13:44 Translations
~> ls -l /boot/system/apps/Dooble/Translations/
total 23629
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_ae.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_ae.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_af.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_af.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_al_sq.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_al_sq.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_al.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_al.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_am.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_am.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_Arab_BH_DZ_EG_IQ_JO_KW_LY_MA_OM_QA_SA_SY_YE.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_Arab_BH_DZ_EG_IQ_JO_KW_LY_MA_OM_QA_SA_SY_YE.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_as.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_as.ts
-r--r--r-- 1 user root     27 jan.    2 13:44 dooble_ast.qm
-r--r--r-- 1 user root 235089 jan.    2 13:44 dooble_ast.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_az.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_az.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_bd_bn.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_bd_bn.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_be.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_be.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_bg.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_bg.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_ca.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ca.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_crh.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_crh.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_cz.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_cz.ts
-r--r--r-- 1 user root  77619 jan.    2 13:44 dooble_de_DE.qm
-r--r--r-- 1 user root 267373 jan.    2 13:44 dooble_de_DE.ts
-r--r--r-- 1 user root  77619 jan.    2 13:44 dooble_de.qm
-r--r--r-- 1 user root 267373 jan.    2 13:44 dooble_de.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_dk.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_dk.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_ee.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ee.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_en.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_en.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_eo.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_eo.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_es.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_es.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_et.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_et.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_eu.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_eu.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_fi.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_fi.ts
-r--r--r-- 1 user root 128507 jan.    2 13:44 dooble_fr_FR.qm
-r--r--r-- 1 user root 256780 jan.    2 13:44 dooble_fr_FR.ts
-r--r--r-- 1 user root 127019 jan.    2 13:44 dooble_fr.qm
-r--r--r-- 1 user root 256548 jan.    2 13:44 dooble_fr.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_French_BE_BJ_BF_BI_FR_KM_CD_CI_DJ_DM_PF_TF_GA_GN_HT_LB_LU_ML_MR_YT_MC_NC_NE_NG_SN_TG_TN.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_French_BE_BJ_BF_BI_FR_KM_CD_CI_DJ_DM_PF_TF_GA_GN_HT_LB_LU_ML_MR_YT_MC_NC_NE_NG_SN_TG_TN.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_galician.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_galician.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_gl.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_gl.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_gr.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_gr.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_hb.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_hb.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_hi.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_hi.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_hr.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_hr.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_hu.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_hu.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_id.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_id.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_ie.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_ie.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_il.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_il.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_it.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_it.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_jp.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_jp.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_kk.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_kk.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_kn.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_kn.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_ko.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ko.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_ku.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ku.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_ky.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ky.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_lk.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_lk.ts
-r--r--r-- 1 user root     43 jan.    2 13:44 dooble_lt.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_lt.ts
-r--r--r-- 1 user root     39 jan.    2 13:44 dooble_lv.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_lv.ts
-r--r--r-- 1 user root     36 jan.    2 13:44 dooble_mk.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_mk.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_ml.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ml.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_mn.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_mn.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_mr.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_mr.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_ms.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ms.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_mt.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_mt.ts
-r--r--r-- 1 user root 109178 jan.    2 13:44 dooble_nl.qm
-r--r--r-- 1 user root 248553 jan.    2 13:44 dooble_nl.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_no.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_no.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_np.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_np.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_pa.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_pa.ts
-r--r--r-- 1 user root  54818 jan.    2 13:44 dooble_pl_PL.qm
-r--r--r-- 1 user root 254910 jan.    2 13:44 dooble_pl_PL.ts
-r--r--r-- 1 user root     41 jan.    2 13:44 dooble_pl.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_pl.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_Portuguese_AO_BR_CV_GW_MO_MZ_ST_TL.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_Portuguese_AO_BR_CV_GW_MO_MZ_ST_TL.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_ps.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ps.ts
-r--r--r-- 1 user root 111801 jan.    2 13:44 dooble_pt_BR.qm
-r--r--r-- 1 user root 249636 jan.    2 13:44 dooble_pt_BR.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_pt.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_pt.ts
-r--r--r-- 1 user root     40 jan.    2 13:44 dooble_ro.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ro.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_ru.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_ru.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_rw.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_rw.ts
-r--r--r-- 1 user root     36 jan.    2 13:44 dooble_se.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_se.ts
-r--r--r-- 1 user root     37 jan.    2 13:44 dooble_sk.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_sk.ts
-r--r--r-- 1 user root     40 jan.    2 13:44 dooble_sl.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_sl.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_sq.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_sq.ts
-r--r--r-- 1 user root     44 jan.    2 13:44 dooble_sr.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_sr.ts
-r--r--r-- 1 user root     33 jan.    2 13:44 dooble_sw.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_sw.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_th.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_th.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_tr.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_tr.ts
-r--r--r-- 1 user root     16 jan.    2 13:44 dooble_vn.qm
-r--r--r-- 1 user root 235071 jan.    2 13:44 dooble_vn.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_zh_CN_simple.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_zh_CN_simple.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_zh_CN_traditional.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_zh_CN_traditional.ts
-r--r--r-- 1 user root     26 jan.    2 13:44 dooble_zh_TW.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 dooble_zh_TW.ts
-r--r--r-- 1 user root 160017 jan.    2 13:44 qtbase_ar.qm
-r--r--r-- 1 user root 165337 jan.    2 13:44 qtbase_bg.qm
-r--r--r-- 1 user root 210159 jan.    2 13:44 qtbase_ca.qm
-r--r--r-- 1 user root 174701 jan.    2 13:44 qtbase_cs.qm
-r--r--r-- 1 user root 181387 jan.    2 13:44 qtbase_da.qm
-r--r--r-- 1 user root 220467 jan.    2 13:44 qtbase_de.qm
-r--r--r-- 1 user root     16 jan.    2 13:44 qtbase_en.qm
-r--r--r-- 1 user root 165170 jan.    2 13:44 qtbase_es.qm
-r--r--r-- 1 user root 148156 jan.    2 13:44 qtbase_fa.qm
-r--r--r-- 1 user root 179941 jan.    2 13:44 qtbase_fi.qm
-r--r--r-- 1 user root 166167 jan.    2 13:44 qtbase_fr.qm
-r--r--r-- 1 user root 189580 jan.    2 13:44 qtbase_gd.qm
-r--r--r-- 1 user root 138690 jan.    2 13:44 qtbase_he.qm
-r--r--r-- 1 user root 149711 jan.    2 13:44 qtbase_hr.qm
-r--r--r-- 1 user root 160494 jan.    2 13:44 qtbase_hu.qm
-r--r--r-- 1 user root 161166 jan.    2 13:44 qtbase_it.qm
-r--r--r-- 1 user root 129911 jan.    2 13:44 qtbase_ja.qm
-r--r--r-- 1 user root 156799 jan.    2 13:44 qtbase_ko.qm
-r--r--r-- 1 user root 153608 jan.    2 13:44 qtbase_lv.qm
-r--r--r-- 1 user root 179956 jan.    2 13:44 qtbase_nl.qm
-r--r--r-- 1 user root 196424 jan.    2 13:44 qtbase_nn.qm
-r--r--r-- 1 user root 162982 jan.    2 13:44 qtbase_pl.qm
-r--r--r-- 1 user root 208516 jan.    2 13:44 qtbase_pt_BR.qm
-r--r--r-- 1 user root 203767 jan.    2 13:44 qtbase_ru.qm
-r--r--r-- 1 user root 125763 jan.    2 13:44 qtbase_sk.qm
-r--r--r-- 1 user root 194487 jan.    2 13:44 qtbase_tr.qm
-r--r--r-- 1 user root 158274 jan.    2 13:44 qtbase_uk.qm
-r--r--r-- 1 user root 133919 jan.    2 13:44 qtbase_zh_CN.qm
-r--r--r-- 1 user root 126185 jan.    2 13:44 qtbase_zh_TW.qm
-r--r--r-- 1 user root    240 jan.    2 13:44 README
~> 

OK, so language file exists - they are in Translations directory

that is under directory

/boot/system/apps/Dooble

I can link it to point that directory, but possibly under compilation that might be changed to this Haiku way directory, and then after installation the language files would be available for Dooble it won’t be failing to find language files and Dooble starts with localization.

[KitsunePrefecture]

MuHaHa …

Even if I created the link,

~> ln -s /boot/system/apps/Dooble/Translations Translations
~> ls -l Translations
lrwxrwxrwx 1 user root 37 jan.    2 16:42 Translations -> /boot/system/apps/Dooble/Translations
~>

---

---

the localization fails,

the same way,

as the expected file names changed already …

~> ls -l /boot/system/apps/Dooble/Translations/*hu_HU*
ls: cannot access '/boot/system/apps/Dooble/Translations/*hu_HU*': No such file or directory
~> ls -l /boot/system/apps/Dooble/Translations/*hu*
-r--r--r-- 1 user root     26 jan.    2 13:44 /boot/system/apps/Dooble/Translations/dooble_hu.qm
-r--r--r-- 1 user root 235088 jan.    2 13:44 /boot/system/apps/Dooble/Translations/dooble_hu.ts
-r--r--r-- 1 user root 160494 jan.    2 13:44 /boot/system/apps/Dooble/Translations/qtbase_hu.qm
~>

---

---

EDIT :

a bit stupid to wire the file names into the app -it used to be only the file type e.g .qm in this case.
Now we have 3 different files instead of one.
Especially stupid if it changes and the code does not follow the changes.

[cocobean]

@KitsunePrefecture

the localization fails

Remove the linkage.

Test this in terminal:

• set DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations
• /boot/system/apps/Dooble/Dooble

Review the proper finding of your translations

[KitsunePrefecture]

Done -

~> ls -l Translations
lrwxrwxrwx 1 user root 37 jan.    2 16:42 Translations -> /boot/system/apps/Dooble/Translations
~> rm Translations
~> ls -l Translations
ls: cannot access 'Translations': No such file or directory
~> set DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations
~> 
~> /boot/system/apps/Dooble/Dooble

---

---

otherwise the result is the same as the Warning tells about different file name … other language than english cannot selectable as the list is empty under ‘English’

[BiPolar]

shouldn’t that be export DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations instead of set?

Dooble indeed seems to use that environment variable, so… I’d try with export @KitsunePrefecture.

[KitsunePrefecture]

Now I have to go to night shift … however I do not understand why dont you catch that
Dooble expect a special name and seems meanwhile it changed … so never find the file
as the name does not match…
I woll prove you in the morning so after next 9 hours here - since now.

[BiPolar]

@KitsunePrefecture

[…] I do not understand why dont you catch […]

I think we DO understand that well enough.

We are trying to both provide you with a possible workaround, and trying to understand where the problem is… either to fix it on HaikuPorts side, or to report the issue to Dooble developers, if needed.

I was counting on Dooble trying to find, say dooble_hu.qm after not fiding dooble_hu_HU.qm (notice that there are both dooble_de.qm and dooble_de_DE.qm files exist, but no dooble_es_ES or dooble_en_UK, only the more generic _es.qm / _en.qm ones.

If the proposed:

> export DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations
> /boot/system/apps/Dooble/Dooble

Does not work for you, that would also point to a problem with what QLocale::system().name() returns, or how Dooble handles it (besides the issue with the wrong Translations path).

Edit:

Regarding that hu vs hu_HU change in the names… maybe you can also try (after the export thing)… setting your “Preferred language” on the Locale preflet as “Magyar” (that should set things to hu), instead of “Magyar (Magyarország)” (that sets the locale to hu_HU).

[KitsunePrefecture]

As I wrote–

Welcome to the Haiku shell.

~> export DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations
~> env|grep -E -i dooble
DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations
~>
~> env|grep -E -i hu
LC_MONETARY=hu.UTF-8
LC_MESSAGES=hu.UTF-8
LC_CTYPE=hu.UTF-8
LC_TIME=hu.UTF-8
LC_COLLATE=hu.UTF-8
LC_NUMERIC=hu.UTF-8
~> env|grep -E -i lc_
LC_MONETARY=hu.UTF-8
LC_TYPE=en_US.UTF-8
LC_MESSAGES=hu.UTF-8
LC_CTYPE=hu.UTF-8
LC_TIME=hu.UTF-8
LC_COLLATE=hu.UTF-8
LC_NUMERIC=hu.UTF-8
~>
~> /boot/system/apps/Dooble/Dooble

I had not found

Magyar

but only
**Magyar-Magxaeország **

let’s sleep some hours before continue.
My eyes are glueing from hard sleepness.

[cocobean]

@KitsunePrefecture

Nothing like the given language file : Dooble_hu_HU.qm, not even a Translations directory.

Whoa… is this an oversight???

• /boot/system/apps/Dooble/Translations (proper directory location)

-r–r–r-- 1 user root 26 jan. 2 13:44 dooble_hu.qm
-r–r–r-- 1 user root 235088 jan. 2 13:44 dooble_hu.ts

No provision of: Dooble_hu_HU.qm
Note: this file is not provided within source code or during app build cycle. Possible coding error. The naming use of ‘hu_HU’ is used for the Dooble Hungarian dictionary files, but not the Dooble Hungarian translation files.

So, report this to the Dooble developer here: Issues · textbrowser/dooble (github.com)

Workaround: You can repackage a test build with renaming/linkage to Dooble_hu_HU.qm …

[KitsunePrefecture]

Dear @cocobean ,

@cocobean

So, report this to the Dooble developer here: Issues · textbrowser/dooble (github.com)

I let this task to report it on github for someone else

who also related,

willing to use github,

and have an account there :j

@cocobean

Workaround: You can repackage a test build with renaming/linkage to Dooble_hu_HU.qm …

Dear Ken,

I’m honoured 8D

Let’s say … on a PC … I’m a power user and a really curious guy.
Me not a developer at all ,
so I won’t botch into development or related stuff - maximum in the shell … as once I was a sysadmin.
But as Haiku is not an AIX or any Linux, I need to learn.

So, for last attempt I would show you
what approach I’ve chosen to try out

a dity resolve …

As a former sysadmin - in a terminal - I started a workaround …
I prepared a directory of Translations
where the LC files are there - and Hungarians would be in the required format

using only FS operations (commands)

Welcome to the Haiku shell.

~> cd /boot/home/config/settings/dooble/
~/config/settings/dooble> cp -r /boot/system/apps/Dooble/Translations /boot/home/config/settings/dooble/
~/config/settings/dooble> ls -ltr
total 568
-rw-r–r-- 1 user root 0 dec. 3 08:26 dooble_certificate_exceptions.db
-rw-r–r-- 1 user root 12288 dec. 3 08:26 dooble_downloads.db
-rw-r–r-- 1 user root 12288 dec. 3 08:26 dooble_search_engines.db
-rw-r–r-- 1 user root 0 dec. 3 08:26 dooble_style_sheets.db
-rw-r–r-- 1 user root 0 dec. 3 08:46 dooble_charts.db
-rw-r–r-- 1 user root 20480 dec. 9 10:05 dooble_accepted_or_blocked_domains.db
-rw-r–r-- 1 user root 372736 jan. 3 20:38 dooble_favicons.db
dr-xr-xr-x 1 user root 10240 jan. 4 07:09 Translations
-rw-r–r-- 1 user root 53248 jan. 4 07:51 dooble_cookies.db
drwx------ 1 user root 2048 jan. 4 07:52 WebEnginePersistentStorage
-rw-r–r-- 1 user root 32768 jan. 4 07:52 dooble_history.db
-rw-r–r-- 1 user root 36864 jan. 4 07:52 dooble_settings.db
~/config/settings/dooble> chmod 755 Translations
~/config/settings/dooble> cd Translations
~/config/settings/dooble/Translations> ls -l hu
-r–r–r-- 1 user root 26 jan. 4 07:04 dooble_hu.qm
-r–r–r-- 1 user root 235088 jan. 4 07:04 dooble_hu.ts
-r–r–r-- 1 user root 160494 jan. 4 07:04 qtbase_hu.qm
~/config/settings/dooble/Translations> cp -r ./dooble_hu.qm ./dooble_hu_HU.qm
~/config/settings/dooble/Translations> cp -r ./dooble_hu.ts ./dooble_hu_HU.ts
~/config/settings/dooble/Translations> cp -r ./dooble_hu.ts ./dooble_hu_HU.ts
~/config/settings/dooble/Translations> ls -l hu
-r–r–r-- 1 user root 26 jan. 4 07:06 dooble_hu_HU.qm
-r–r–r-- 1 user root 235088 jan. 4 07:08 dooble_hu_HU.ts
-r–r–r-- 1 user root 26 jan. 4 07:04 dooble_hu.qm
-r–r–r-- 1 user root 235088 jan. 4 07:04 dooble_hu.ts
-r–r–r-- 1 user root 160494 jan. 4 07:09 qtbase_hu_HU.qm
-r–r–r-- 1 user root 160494 jan. 4 07:04 qtbase_hu.qm
~/config/settings/dooble/Translations>
~/config/settings/dooble/Translations>
~/config/settings/dooble/Translations>
~/config/settings/dooble/Translations> export DOOBLE_TRANSLATIONS_PATH=/boot/home/config/settings/dooble/Translations
~/config/settings/dooble/Translations> /boot/system/apps/Dooble/Dooble

As a RESULT - I got a new - different error/warning message

The file /boot/home/config/settings/dooble/dooble_hu_HU.qm perhaps incomplete.

LOL 8D

The others are the same as before.
Disabled. English only.

After I quit Dooble in Terminal the next error/warning messages appeared

QObject::killTimer: Timers cannot be stopped from another thread
QObject::~QObject: Timers cannot be stopped from another thread
~/config/settings/dooble/Translations>

Anyway.

Conclusion :

Localization for - Hungarian language - surely can be solved by Dooble developers – upstream

[KitsunePrefecture]

For all non-English readers - who installed Dooble and would join an experiment …

I’m intrigued –

can you

reach a localized Dooble –

exporting the Translations directory
and launch Dooble from Terminal ?

Required commands :

export DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations

env|grep -E -i dooble (to check the variable exported or not)

/boot/system/apps/Dooble/Dooble

EDIT :

Seems noone dare to do test of localization …

[BiPolar]

@KitsunePrefecture

Seems noone dare to do test of localization …

Or haven’t had the time, or right mood to do so… until now!

Dooble’s search path for “Translations” is indeed broken. It searches for that Translations path, as a subdir of the CURRENT working directory.

For example… I’ve set my “Prefered language” to Español (Argentina) (that’s es_AR), and called it like this (notice my working dir):

[~/SourceCode/OscarL/KeyCursor (master)]
> /boot/system/apps/Dooble/Dooble

Dooble complains of not being able to find /boot/home/SourceCode/OscarL/KeyCursor/Translations/dooble_es_AR.qm. No sh**!

Good news is… the export DOOBLE_TRANSLATIONS_PATH=/boot/system/apps/Dooble/Translations thing DOES works… as in… after doing that, it complains it can’t find: /boot/system/apps/Dooble/Translations/dooble_es_AR.qm

After that… I’ve set my “Prefered language” to Español (that’s it: plain es NOT es_ES or other variant… locale -l return just: es). That SHOULD work, as the file /boot/system/apps/Dooble/Translations/dooble_es.qm DOES exists after installing Dooble.

Problem is… that Dooble tries to find the dooble_es_ES.qm variant instead. As I’ve already pointed out… that seems like a problem with what QLocale::system().name() is returning: es_ES when it should be just es in this particular case (similar case with hu_HU vs hu for you @KitsunePrefecture).

The path issue I guess we could patch it over HaikuPorts (and report it upstream to Dooble, if deemed necessary).

Not sure where to report that QLocale issue, as I don’t know if is a problem with our Qt port, somewhere on Haiku’s Locale API, or what.

Edit: got the same “Warning! the file […] is perhaps incomplete” after copying the _es files as es_AR. Why include the darn files in the first place if you can’t ever use them!

[KitsunePrefecture]

Dear Oscar,

Well, then you are more accurete in proving and tracking cause than me – I just simply thought it was the name itself wired as intended in the code of Dooble.
That way I thought and written earlier I find it stupid.

Now it has a reason the query of locale is written bogus or works wrong - so possibly not intended just should be fixed.

Thanks for your workaround at Haikuports - as it happens - in the name of other non-English users, at least those who would like to use this browser on their native language.

For reporting the issue … we might assume other dev who would peek here can give some good advice …
… or you can ask for it in Haiku IRC !..

[BiPolar]

For reference, I’ve opened issue #9964 on HaikuPorts.

[KitsunePrefecture]

Quite complete - thanks.
I would change the title again - as [Reported].

[KitsunePrefecture]

upgrade package dooble-2023.12.25-1 to 2023.12.25-2 from repository HaikuPorts

I assumed this update - on Haikuports - would be for
localization fix …
… unfortunately still not. :((…

[korli]

It certainly works. Switch the language to system, click Apply, restart Dooble.

[KitsunePrefecture]

Good joke.

The problem is …

… even Dooble updated :

I have

The System option has been disabled.

yet.

[kim1963]

[korli]

Does it work for your language on Linux? If yes, then it’s a bug for Qt at Haikuports bug tracker, otherwise it’s a bug in Dooble at Dooble bug tracker.