Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Feature Request: Translation editor

  1. #1

    Question Feature Request: Translation editor

    I think that I have mentioned it before, perhaps in a beta process. But I will do it again. The reason is that I am currently revising a translation of Revelation. BW is a fantastic tool for many reasons. I cannot do without.

    There is, however, one feature that I am still missing. It would be extremely nice and helpful if it was possible to edit the current verse of a given user version. As it is now, I can configure BW to automatically load and display a user note for a verse (or a chapter).

    What I need, would be a window that would automatically load the current verse of a user-defined version. If, for example, I need to check all the renderings of, e.g., polemos, then I would be able to search for polemos, review them and make any changes that I would see necessary.

    If this editor also supports the available tags (inline notes, italics etc etc), then it would be a dream!

    I know that there are excellent translation tools out there, but I really want this function within BibleWorks. As it is now, I am constantly switching between my editor and BW.

    Moreover, I believe it would be useful even to those who are not translators or revisors.

    Am I the only one?
    Dr. Georg S. Adamsen, Denmark
    Specialist in Academic Writing and Biblical Studies
    www.opgavedoktor.dk

  2. #2

    Thumbs up Translator's tool

    I would have loved that when working on the NLT. I kept thinking vaguely of something like that but never formulated it and asked for it. Of course, I also kept wishing the NLT committee would give us the work in progress in a BW-compatible module, so I could check my choices against others, especially throughout the Pentateuch, but also elsewhere in the OT.

    Dale A. Brueggemann

    כִּי עֶזְרָא הֵכִין לְבָבוֹ לִדְרוֹשׁ אֶת־תּוֹרַת יְהוָה וְלַעֲשֹׂת וּלְלַמֵּד בְּיִשְׂרָאֵל חֹק וּמִשְׁפָּט (Ezra 7:10)


  3. #3
    Join Date
    Sep 2007
    Posts
    1,218

    Default

    Dale,

    Are you any relation to Walter? I'm sure you probably get asked that a lot, huh?

  4. #4

    Default Relation?

    Yes, and yes ;o)

    Dale A. Brueggemann

    כִּי עֶזְרָא הֵכִין לְבָבוֹ לִדְרוֹשׁ אֶת־תּוֹרַת יְהוָה וְלַעֲשֹׂת וּלְלַמֵּד בְּיִשְׂרָאֵל חֹק וּמִשְׁפָּט (Ezra 7:10)


  5. #5
    Join Date
    Sep 2007
    Posts
    1,218

    Default

    Wow, interesting. After all these years, I've not yet consulted any of his commentaries, though good friends of mine rave about him. The word is that he deals with the text in a wonderful way. Do you guys interact much about biblical matters and issues, theology, biblical languages, etc.?

  6. #6
    Join Date
    Apr 2004
    Posts
    1,154

    Default

    Quote Originally Posted by Adamsen View Post
    It would be extremely nice and helpful if it was possible to edit the current verse of a given user version. As it is now, I can configure BW to automatically load and display a user note for a verse (or a chapter).

    What I need, would be a window that would automatically load the current verse of a user-defined version. If, for example, I need to check all the renderings of, e.g., polemos, then I would be able to search for polemos, review them and make any changes that I would see necessary.

    If this editor also supports the available tags (inline notes, italics etc etc), then it would be a dream!

    I know that there are excellent translation tools out there, but I really want this function within BibleWorks. As it is now, I am constantly switching between my editor and BW.

    Moreover, I believe it would be useful even to those who are not translators or revisors.

    Am I the only one?
    I think that what you suggest would have unintended consequences. Currently user-compiled versions are treated just like those versions which ship with BibleWorks. Copyright holders would not want others messing with their translations, or if they did, there would be hundreds of different version of the same translation on different computers, as users made changes to the published versions. And if a user made a change, then he would not have available what the official version says. So we do not want to be able to change copyrighted versions. If we were to be able to edit some versions and not others, BibleWorks would have to invent some new system to lock some versions from being editable.
    But what about other user databases? Would those other users want me to change their versions? Would I really want to be able to change their versions, so that I no longer have the original version available? I think not. But how should BibleWorks distinguish between my own user database version and some other user's user database version? I compile both on my computer, so my computer would treat both as belonging to me. That is not right.
    So I, for one, am content with editing my own Bible version outside BibleWorks in WordPad and re-compiling it in BibleWorks from time to time. That way I can search on my version within BibleWorks, and edit it outside of BibleWorks. If I wish, I can sleep on the changes before re-compiling my version (checking my "old" version in BibleWorks with my "new" version in WordPad). If I am happy with the changes, I re-compile my version. If I think I was right the first time, I go and change it back in WordPad. It takes only half a minute to compile, so that should not be a problem.
    If you want to be able to edit someone else's version, you can always export it and make your own user database version of it, with a different name. That way you keep the original as well as your own edition. So I like it the way it is.
    My 2 cents worth,
    Mark Eddy

  7. #7

    Default

    Quote Originally Posted by Mark Eddy View Post
    I think that what you suggest would have unintended consequences. ... Mark Eddy
    Perhaps, perhaps not. I do not suggest that we should be allowed to edit directly in the compiled databases.

    What I suggest is an editor that allows me to edit a text file in a window. I do not suggest that it should be compiled automatically so that copyrighted texts or any other texts are changed.

    It is already possible to export a version as a file that can be edited. Some versions can be edited that way already and recompiled. At least that is the case for a version that I converted and provided for an earlier version of BW.

    I guess that you really don't like the user version compiler at all? It allows us to change copyrighted texts if we should so desire, does it not?
    Dr. Georg S. Adamsen, Denmark
    Specialist in Academic Writing and Biblical Studies
    www.opgavedoktor.dk

  8. #8

    Default

    I agree completely with Georg.

    It would be a very useful feature, not only for translators, but also for transcribers of manuscripts. You could choose one version as your source and edit the text while reading the manuscript.

    Very good suggestion. You have my full support!
    Best wishes
    Wieland
    <><
    ------------------------------------------------
    Wieland Willker, Bremen, Germany
    http://www-user.uni-bremen.de/~wie
    Textcritical commentary:
    http://www-user.uni-bremen.de/~wie/TCG/index.html

  9. #9
    Join Date
    Apr 2004
    Posts
    615

    Default

    I think that this feature would be great. The original purpose of the VDC was to facilitate users working on Bible Translations. I don't think it should be something used to edit current versions, but rather to make new ones from the ground-up.

    At the very least it would be great to have the capability of compiling notes made in the editor into verse notes in a version. If another window was added to the editor in which a person could write their own translation that would be exported into the version, then all the better. Or perhaps instead of a separate window, tags could be used that separate the actual translation text from what would be notes in the new version...
    Jim Darlack - Associate Director of Goddard Library /
    Reference Librarian at Gordon-Conwell Theological Seminary

    Gloucester Assembly of God | Gordon-Conwell Theological Seminary
    The 'Unofficial' BibleWorks Blog | Old in the New | Facebook | LibraryThing

  10. #10
    Join Date
    Apr 2004
    Posts
    1,154

    Default

    Quote Originally Posted by Adamsen View Post
    I guess that you really don't like the user version compiler at all? It allows us to change copyrighted texts if we should so desire, does it not?
    Please forgive me for not being clear. I had no intention of denigrating the version database compiler. I use it all the time. I am working on a couple versions of my own, and I have exported versions produced by others and recompiled them so that I could edit them. I have tried to make sure that I re-name those versions, so that I do not overwrite the original version when I compiled my edited version.
    But I believe that it is good to make it somewhat difficult to overwrite a published version. It should not be able to do so accidentally. It must be the intention of the user to overwrite a version compiled in BibleWorks. And copyrighted versions have to be kept so that they cannot be changed and retain their abbreviation, as protection for the copyright holders.
    When I work on my user databases, I either have the BibleWorks Analysis, Resources, Notes, or Editor tab open. So, if something like you request is desired by many, it would need to be separate from the tabs, so that the information in the tabs can be seen while editing. By editing a user database in something like WordPad outside of BibleWorks, I can have a few lines of the text to be edited open at the bottom of my screen, while devoting most of the space to BibleWorks resources, and see them all at once.
    The tools for exporting and compiling databases work well the way they are. Editing outside of BibleWorks works well for me. If the copyright issues can be dealt with, and enough people want what you suggest, then I leave it to the programmers to decide if it is worth their time to do it. I just want you and them to know that the current functionality works well, and it seems to protect against unwanted changes to databases.
    Mark Eddy

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •