search

rubiot / ibiblia

Ferramenta para criação de módulos para o theWord
5 stars 5 forks source link

No module properties when exporting to text and to MySword format #64

Open SalitaNgDiyos opened 5 years ago

SalitaNgDiyos commented 5 years ago

Thanks for everything your doing here, bro! The Lord bless you for your servant's heart. I just notice that this amazing feature strips off the text with all the valuable module properties which are a part of the regular export feature. If it's not a lot to do, is it possible to integrate the module properties as well whenever user exports from the main UI, in the future?

Thanks, Edmund

rubiot commented 5 years ago

Well, that's why I called this "Export to text file" instead of "Export to theWord Bible module"... haha. I just wanted a quick way to edit the text outside iBiblia and import it back. But just out of curiosity, in what way are you using this feature?

Having said that, I could export a complete theWord Bible module for source and destination texts, because I do have their original properties stored in the project. But I don't have them for the reference texts.

SalitaNgDiyos commented 5 years ago

I think what you did was kinda brilliant giving the user lots of flexibility. It also saves me the extra effort to strip off my projects with Strong's Tags using the BibleMergeTool whenever I want to. Instead of having to create 2 project files, one for translation and the other for Strong's association, I can just do one project and come up with both results.

I was just taking extra precaution not to exclude the module properties anytime I export the module if I want just the destination text. It's where I put my translation progress and other important info. MySword allowed me to update my translation regularly thus the module properties.

I think the source and the destination texts are the two most important things for me so what you propose is just perfect. If I need to update the reference texts it would be a very rare situation.

On Wed, Jul 10, 2019, 9:22 PM Rúbio Terra notifications@github.com wrote:

Well, that's why I called this "Export to text file" instead of "Export to theWord Bible module"... haha. I just wanted a quick way to edit the text outside iBiblia and import it back. But just out of curiosity, in what way are you using this feature?

Having said that, I could export a complete theWord Bible module for source and destination texts, because I do have their original properties stored in the project. But I don't have them for the reference texts.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rubiot/ibiblia/issues/64?email_source=notifications&email_token=ALBG4C4XZGTKMVN5XZG7XBDP6XPBZA5CNFSM4H7NIXR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZTOCQY#issuecomment-510058819, or mute the thread https://github.com/notifications/unsubscribe-auth/ALBG4CZUJYQ3CQFOUXIUJRTP6XPBZANCNFSM4H7NIXRQ .

SalitaNgDiyos commented 5 years ago

It would be nice if inclusion of module properties is just an option like a toggle to turn on or off.

rubiot commented 5 years ago

I can infer this from the file type chosen in the save dialog. I'll add types like "Text file | .txt", "theWord Bible module | .ont", for instance.

SalitaNgDiyos commented 5 years ago

Is there also a way to include the verse rules?