First of all, sorry for writing in English, but I was learning German very long time ago (in elementary school) and now I can barely read and write basic sentences in this language. Various translators helps a lot, but they're not perfect, so if you can, please post replies in English.
First possible bug is related to "Biing! Tool Persdata Browser" (WWW button in Dev.-Tools). When opening person in the browser temporary "buffer.persdata" file is created and it is loaded into the program. If this operations fails for some reason, "buffer.persdata" becomes locked (can't be deleted, etc.). Selecting person in library now creates new file "buffer.persdata.part" but data isn't loaded into the program. Both "buffer.persdata" and "buffer.persdata.part" files opens without a hitch in Persdata Editor (.part one after changing its extension). It always happens while opening Jessica Frasen from Devilmarkus Personal section - some others too but that one always locks "buffer.persdata" file. Quick and dirty fix is to close application, delete "buffer.persdata" file and relaunch application.
Related question since we're on personal topic. Is there a way to export/extract only photos from .persdata files? I wanted to change photos of few original employees and some photos from "Biing! Tool Persdata Browser" suited my needs but "bug" mentioned above didn't allow me to load personal data and exporting pictures the usual way. BTW, is it possible to download files from "Biing! Tool Persdata Browser" via normal browser - some are in Uploads section but not all (e.g Devilmarkus' personnel/guests).
On to main issue - Texedit. When testing translations I stumbled upon few text glitches. At first I thought that I did something wrong, but it seems that Texedit was at fault. To reproduce this problem: open Texedit, export data, import data without making any changes (import/export mode doesn't matter), save "BI2TEX" file and voila - it gets bigger by few KB and glitches appears. Easiest one to spot is in "Rangliste" section of "Statistiken" - "Schwierigkeitsgrad: " string is repeated few times. I think I know where problem lies, but not what causes it or how to fix it. Some entries contains more than one actual entries, e.g. entry 72189 looks like this:
ist der Ein_tritt frei! Das char_man_te Bun_ny_girl $ ist der Ein_tritt frei! Der smar_te Gi_go_lo $ ist der Ein_tritt frei! Die net_te Hos_tess $
After importing this entry in that form or even just clicking apply changes button (Ändern) changes this entry to:
ist der Ein_tritt frei! Das char_man_te Bun_ny_girl ist der Ein_tritt frei! Der smar_te Gi_go_lo st der Ein_tritt frei! Die net_te Hos_tess $
All but last "$" are deleted, which is logical, since this char is used as entries delimiter (neat feature BTW).
Hope this will help fix/improve Biing!-Tool, which is already a great tool to mess with the game resources.
Since I'm utterly pissed you get only an utterly useless answer: DON'T MESS WITH THE GAME RESOURCES!;)
Well, messing with game resources is main purpose of this tool, right? Besides, it's the best way to translate the game, which is what I'm trying to do.
Texedit bug update: It seems that bug mentioned earlier is not related to "Schwierigkeitsgrad: " string mentioned as an example - it's another bug. In some cases (hard to tell what triggers it), if entry contains 2 or more consecutive spaces, word directly before those spaces is duplicated few times (probably once for every extra space). For example:
Well, it's kinda weird quoting myself, but it will help keep things clean, at least I think it will . Oh, and sorry for the long post but I couldn't find anything resembling spoiler tags, not to mention line wrapping - I'm really, really sorry.
schrieb ...
First possible bug is related to "Biing! Tool Persdata Browser" (WWW button in Dev.-Tools). When opening person in the browser temporary "buffer.persdata" file is created and it is loaded into the program. If this operations fails for some reason, "buffer.persdata" becomes locked (can't be deleted, etc.). Selecting person in library now creates new file "buffer.persdata.part" but data isn't loaded into the program. Both "buffer.persdata" and "buffer.persdata.part" files opens without a hitch in Persdata Editor (.part one after changing its extension). It always happens while opening Jessica Frasen from Devilmarkus Personal section - some others too but that one always locks "buffer.persdata" file. Quick and dirty fix is to close application, delete "buffer.persdata" file and relaunch application.
I found out, be pure coincidence I might add, solution to this - apply "DGL-Patch für Biing! 2 1.06". You see that "1.06" in the name? That's why I didn't even bother to check what it does since I thought that it's required by 1.06 and it's already included in newer versions... stupid little me . If I can suggest something - the name of this in Downloads could use some suffix like "+", "and above" (in German of course) or something similar - it should be more clearer, especially for people like me who are not too fluent in German. Tool itself could also use somekind of check whether DLG files are "patched" or not - e.g. while trying to add a person using this files for storing own photos.
schrieb ...
Texedit bug update: It seems that bug mentioned earlier is not related to "Schwierigkeitsgrad: " string mentioned as an example - it's another bug. In some cases (hard to tell what triggers it), if entry contains 2 or more consecutive spaces, word directly before those spaces is duplicated few times (probably once for every extra space). For example:
Nothing new on this front I'm affraid - it's well out my reach - only Markus could do something with this.
schrieb ...
On to main issue - Texedit. When testing translations I stumbled upon few text glitches. At first I thought that I did something wrong, but it seems that Texedit was at fault. To reproduce this problem: open Texedit, export data, import data without making any changes (import/export mode doesn't matter), save "BI2TEX" file and voila - it gets bigger by few KB and glitches appears. Easiest one to spot is in "Rangliste" section of "Statistiken" - "Schwierigkeitsgrad: " string is repeated few times. I think I know where problem lies, but not what causes it or how to fix it. Some entries contains more than one actual entries, e.g. entry 72189 looks like this:
ist der Ein_tritt frei! Das char_man_te Bun_ny_girl $ ist der Ein_tritt frei! Der smar_te Gi_go_lo $ ist der Ein_tritt frei! Die net_te Hos_tess $
After importing this entry in that form or even just clicking apply changes button (Ändern) changes this entry to:
ist der Ein_tritt frei! Das char_man_te Bun_ny_girl ist der Ein_tritt frei! Der smar_te Gi_go_lo st der Ein_tritt frei! Die net_te Hos_tess $
All but last "$" are deleted, which is logical, since this char is used as entries delimiter (neat feature BTW).
Good news is that I've found cause and workaround for this bug. Well, of course I can't be 100% sure that my assumptions are correct, since I don't know how Texedit does things internally, but the fact that workaround works confirms my theory. Besides, this findings are based on the way in which game handles strings in memory, so it's most than likely that in-file game data are similar if not identical. My theory is that Marcus assumed that all strings are stored in numerical order and used offsets of consecutive strings as a means to calculate strings length. Unfortunatelly, it's not true for some strings and that is causing this problem. I don't know if I'm clear enough, so I'll just use an example of one of those cases in which some entries are not stored in numerical order:
This is the order in which those entries are stored in game memory (and most likely also in file):
72181: konn_te da_von pro_fi_tie_ren und wird sein Glück so schnell nicht mehr ver_ges_sen.$
72182: konn_te ih_re Brief_ta_sche scho_nen und wird ihr Glück so schnell nicht mehr ver_ges_sen.$
72185:Hur_ra! Frei_er Ein_tritt $
72186:Hur_ra! Frei_er Ein_tritt$
72187:Wir konn_ten es zu_erst gar nicht glau_ben, aber nach_dem $
72188: uns da_von er_zählt hat_te, über_zeug_ten wir uns an Ort und Stel_le selbst. Es ist tat_säch_lich wahr,$
72189: ist der Ein_tritt frei! Das char_man_te Bun_ny_girl $
72183: ist der Ein_tritt frei! Der smar_te Gi_go_lo $
72184: ist der Ein_tritt frei! Die net_te Hos_tess $
72190: lässt wirk_lich al_le Gäs_te um_sonst rein. Wir spra_chen er_feut mit dem net_ten Ma_na_ger, ge_prie_sen und aber_mals ge_prie_sen sei sein Na_me, $
It seems that length of every entry is calculated by substracting its own offset from offset of entry with next id, which gives us:
* offset values taken from memory of partially translated game and are used only as example * lenghts should be exact but it's better to also treat them as example
Entry 72182 doesn't take into consideration that there are another entries between it and entry with next id, so it's calculated length is to big and those extra entries are treated as part of this entry resulting in:
72182: konn_te ih_re Brief_ta_sche scho_nen und wird ihr Glück so schnell nicht mehr ver_ges_sen.$Hur_ra!
Frei_er Ein_tritt $Hur_ra! Frei_er Ein_tritt$Wir konn_ten es zu_erst gar nicht glau_ben, aber nach_dem $ uns
da_von er_zählt hat_te, über_zeug_ten wir uns an Ort und Stel_le selbst. Es ist tat_säch_lich wahr,$ ist der
Ein_tritt frei! Das char_man_te Bun_ny_girl $
Calculated length for entry 72185 is negative since entry with next id has lower offset. And since negative string length is not allowed, it's assumed as 0 and results in empty string Entry 72189 is similar to 72182 - doesn't take into consideration that there are another entries between it and entry with next id, so it's calculated length is to big and those extra entries are treated as part of this entry resulting in:
72189: ist der Ein_tritt frei! Das char_man_te Bun_ny_girl $ ist der Ein_tritt frei! Der smar_te Gi_go_lo $
ist der Ein_tritt frei! Die net_te Hos_tess $
I'm sure, Markus, that you will find an elegant and efficient solution to this problem .
Since I made notes when analising this problem, I might as well post them as a reference - list of all invalid entries with included cause and solution/walkaround:
71638: mit ei_ner an_de_ren$ mit der Hos_tess$ mit dem Zim_mer_mäd_chen$ mit dem Ani_ma_teur$ mit dem Fuz_zy$
mit dem Bun_ny_girl$ mit der Do_mi_na$ mit dem Gi_go_lo$ mit dem Trai_ner$ mit der Trai_ne_rin$ mit dem
Bi_ki_ni_girl$ mit dem Por_tier$ mit dem S&M-Girl$ mit der Kran_ken_schwes_ter$ mit dem Koch$ mit dem Fah_rer$
CAUSE: entries 71657-71671 stored before entry 71638 resulting in excessive length of this entry SOLUTION: delete everything after first $ - everything else is already in their respective entries
71656:$
CAUSE: entries 71657-71671 stored before entry 71638 resulting in negative length of this entry SOLUTION: change this entry to: Wir fra_gen uns nur noch: Wie konn_te er ihr das bloß an_tun?$
71671: mit dem Fah_rer$Schau_platz ei_ner mensch_li_chen Tra_gö_die wur_de heu_te $. Die all_seits be_lieb_te
$ hat_te sich dort mit ih_rem Freund, dem er_folg_rei_chen $ ver_ab_re_det, doch was muß_te sie se_hen, als
sie an_kam? $Der ge_mei_ne Kerl flir_te_te ge_ra_de un_ge_niert mit ei_nem an_de_ren Mann! Und zu al_lem
Über_fluß muß_te es auch noch der win_di_ge $Der ge_mei_ne Kerl flir_te_te ge_ra_de un_ge_niert mit ei_ner
an_de_ren! Und dann auch noch mit der als Schlam_pe wohl_be_kann_ten $ sein, den $, die $ auf den Tod nicht
aus_ste_hen konn_te. Die ar_me $ be_gann hys_te_risch zu schrei_en und zer_riss mit Trä_nen in den Au_gen das
Fo_to von $, das sie im_mer nah bei ih_rem Her_zen ge_tra_gen hat_te. $ wur_de ganz bleich im Ge_sicht und
warf wü_tend die schö_ne Kar_tof_fel auf den Bo_den, die ihr $ bei ih_rer ers_ten Be_geg_nung ge_schenkt
hat_te. $ ver_lor völ_lig die Fas_sung und be_gann wü_tend auf dem Bild des Da_ckels von $
herum_zu_tram_peln, das ihr die_ser ge_schenkt hat_te. $ lief knall_rot an und warf $ wü_tend die Do_se
Büch_sen_pflau_men an den Kopf, die er ihr zum letz_ten Ge_burts_tag ge_schenkt hat_te. $Wir fra_gen uns nur
noch: Wie konn_te er ihr das bloß an_tun?$
CAUSE: entries 71657-71671 stored before entry 71638 resulting in excessive length of this entry SOLUTION: restore entry 71656 (see its notes) and delete everything after first $ - everything else is already in their respective entries
71692:, de_ren Ruf als Schlam_pe weit_hin be_kannt war. $ wälz_te sich ge_ra_de lust_voll stöh_nend$
schä_ker_te ge_ra_de un_ge_niert$ herum, der ja oh_ne_hin schon als schlim_mer Schür_zen_jä_ger be_kannt war.
$ herum, die ja oh_ne_hin schon als un_er_sätt_li_che Nym_pho_ma_nin be_kannt war. $
CAUSE: entries 71704-71707 stored before entry 71693 resulting in excessive length of this entry SOLUTION: delete everything after first $ - everything else is already in their respective entries
71703:$
CAUSE: entries 71704-71707 stored before entry 71693 resulting in negative length of this entry SOLUTION: change this entry to: Welch ei_ne Tra_gö_die. Was hat sie sich bloß da_bei ge_dacht?$
71707: herum, die ja oh_ne_hin schon als un_er_sätt_li_che Nym_pho_ma_nin be_kannt war. $Für $ brach ei_ne
Welt zu_sam_men. $Krei_de_bleich sank er auf die Knie und ver_fluch_te den Tag, an dem er $ zum ers_ten_mal
be_geg_net war. $Mit hoch_ro_tem Kopf zer_tram_pel_te er wü_tend den schö_nen Ti_ro_ler_hut, den ihm $ einst
ge_schenkt hat_te. $Wü_tend warf er die schö_ne Stand_uhr, die er von $ ge_schenkt be_kom_men hat_te und die
er im_mer bei sich trug, auf den Bo_den. $Schrei_end zer_trat er den schö_nen Napf_ku_chen, den ihm $ bei
ih_rer ers_ten Be_geg_nung ge_schenkt hat_te und der ihn im_mer an sie er_in_nern soll_te. $Welch ei_ne
Tra_gö_die. Was hat sie sich bloß da_bei ge_dacht?$
CAUSE: entries 71704-71707 stored before entry 71693 resulting in excessive length of this entry SOLUTION: restore entry 71703 (see its notes) and delete everything after first $ - everything else is already in their respective entries
71720: tur_tel_te ge_ra_de in in_ni_ger Um_ar_mung mit $ schä_ker_te ganz un_ge_niert$ flir_te_te ge_ra_de hef_tig$
CAUSE: entries 71733-71734 stored before entry 71721 resulting in excessive length of this entry SOLUTION: delete everything after first $ - everything else is already in their respective entries
71732:$
CAUSE: entries 71733-71734 stored before entry 71721 resulting in negative length of this entry SOLUTION: change this entry to: Tja, kein Glück währt ewig!$
71734: flir_te_te ge_ra_de hef_tig$ herum und ließ sich wüst von ihm be_fum_meln. $ herum und ließ sich wüst
von ihr be_fum_meln. $Das war zu_viel für $! Mit hoch_ro_tem Kopf warf sie den schö_nen Büs_ten_hal_ter, den
ihr $ ge_schenkt hat_te, auf den Bo_den und rann_te heu_lend da_von. $! Wü_tend warf sie $ die Pa_ckung mit
Di_ät_pil_len, die sie von ihr zu Weih_nach_ten be_kom_men hat_te, an den Kopf. $! Krei_schend zer_fetz_te
sie die Bus_fahr_kar_te, die sie von $ ge_schenkt be_kom_men hat_te und die sie im_mer an sie er_in_nern
soll_te. $! Mit Trä_nen in den Au_gen ließ sie das schö_ne Pa_pier_schiff_chen, das sie ex_tra für $
ge_bas_telt hat_te, fal_len und rann_te schluch_zend da_von. $Tja, kein Glück währt ewig!$
CAUSE: entries 71733-71734 stored before entry 71721 resulting in excessive length of this entry SOLUTION: restore entry 71732 (see its notes) and delete everything after first $ - everything else is already in their respective entries
71746: und schä_ker_te mit ihr rum. $Er flir_te_te ge_ra_de aus_gie_big$ und wur_de noch nicht ein_mal rot da_bei. $
CAUSE: entries 71758-71759 stored before entry 71747 resulting in excessive length of this entry SOLUTION: delete everything after first $ - everything else is already in their respective entries
71757:$
CAUSE: entries 71758-71759 stored before entry 71747 resulting in negative length of this entry SOLUTION: change this entry to: Was soll man da_zu noch sa_gen? Muß_te das jun_ge Glück denn aus_ge_rech_net hier zu_en_de ge_hen?$
71759: und wur_de noch nicht ein_mal rot da_bei. $Den ent_setz_ten $ traf fast der Schlag. Das konn_te doch
ein_fach nicht wahr sein. $Schluch_zend sack_te er in sich zu_sam_men und ver_fluch_te den Tag, an dem er $
zum ers_ten_mal mit sei_ner tol_len Bräu_ne am Strand ge_trof_fen hat_te. $Mit hoch_ro_ten Kopf warf er dem
bö_sen $ ein Wat_te_bäll_chen an den Kopf und rann_te schluch_zend da_von. $Mit Trä_nen in den Au_gen
zer_knüll_te er das schö_ne Bild, das $ für ihn ge_malt hat_te und das er seit dem im_mer bei sich trug.
$Wei_nend ließ er den schö_nen Schal, den er ex_tra für $ ge_strickt hat_te und ihm heu_te schen_ken woll_te,
fal_len und rann_te mit Trä_nen in den Au_gen da_von. $Was soll man da_zu noch sa_gen? Muß_te das jun_ge
Glück denn aus_ge_rech_net hier zu_en_de ge_hen?$
CAUSE: entries 71758-71759 stored before entry 71747 resulting in excessive length of this entry SOLUTION: restore entry 71757 (see its notes) and delete everything after first $ - everything else is already in their respective entries
72182: konn_te ih_re Brief_ta_sche scho_nen und wird ihr Glück so schnell nicht mehr ver_ges_sen.$Hur_ra!
Frei_er Ein_tritt $Hur_ra! Frei_er Ein_tritt$Wir konn_ten es zu_erst gar nicht glau_ben, aber nach_dem $ uns
da_von er_zählt hat_te, über_zeug_ten wir uns an Ort und Stel_le selbst. Es ist tat_säch_lich wahr,$ ist der
Ein_tritt frei! Das char_man_te Bun_ny_girl $
CAUSE: entries 72185-72189 stored before entry 72183 resulting in excessive length of this entry SOLUTION: delete everything after first $ - everything else is already in their respective entries
72184:$
CAUSE: entries 72185-72189 stored before entry 72183 resulting in negative length of this entry SOLUTION: change this entry to: ist der Ein_tritt frei! Die net_te Hos_tess $
72189: ist der Ein_tritt frei! Das char_man_te Bun_ny_girl $ ist der Ein_tritt frei! Der smar_te Gi_go_lo $
ist der Ein_tritt frei! Die net_te Hos_tess $
CAUSE: entries 72185-72189 stored before entry 72183 resulting in excessive length of this entry SOLUTION: restore entry 72184 (see its notes) and delete everything after first $ - everything else is already in their respective entries
Following two entries are not part of the problem, but are containing multiple $ characters hence they were in my notes:
NOTES: - thats how this entry is stored and I have now idea why - maybe it was used as a placeholder at some point - changing or importing this entry will automatically change it to single $ character and it should be ok to do this - didn't encounter any problems
8053: und zeigt ihr grin_send sei_ne star_ken Mus_keln$ und zeigt die_ser grin_send ih_ren run_den Hin_tern$
NOTES: - couldn't get this in game (the same goes for two entries right before this one), so I'm not sure of its use - especially for which gender it's actually used - it's possible that this is remnants from old structure - nearby entries 8024 i 8025 are identical, so probably they are used instead this of one, but I didn't have the time yet to see if it's actually referenced somewhere in game
------------
I've also found few small bugs in game itself, but I'll send them to Markus some other time - need to make sure that they are in fact bugs and not something I've inadvertently broken .
Ah, would have forget - quick question for Markus: Are names/purposes of stats for vacationers (Sportlich, Versoffen, etc.) are official or guessed? Something didn't feel right about them but I can't recall right now what it was since I dropped them when I started dealing with strings.
Besides, it's the best way to translate the game, which is what I'm trying to do.
- I'm really, really sorry.
