I have used DGW (Domino Global Workbench) 6.5 to create a template consisting of only one language. Therefore I want the database property “Multilingual database” to be disabled since this is a unilingual database.
Source database has database property “Multilingual database” disabled.
Tagged database has database property “Multilingual database” disabled.
Language database has database property “Multilingual database” disabled.
But when I use the newly created Language database (ntf) to “Refresh design” of my production database (nsf) it automatically sets the “Multilingual database” property in the production database. Why?
What am I missing?
Has any one else come across that database properties are enabled even though they shouldn’t?
I had the same problem about 6 mos ago - it is related to the presence of the $Languange and $BabelInfo fields, which tell Notes that it is a multi-lingual db. I removed the field $Language field and all was OK.
BTW, have had nothing but pain over multi-lingual dbs from DGW, not the least of which is poor performance. Best to create separate templates for each language or if db is not to detailed and you are not dealing with more than 3 or 4 Western languages (certainly not using DBCS), include all languages in a single template, i.e.,
I removed field $Language from the icon design note.
Then run Refresh design. But then I got this error message “Design Refresh Failed, Not all specified languages were found in design template”.
Then I also removed the field $BabelInfo from the icon design note. But got the same error message as stated above during Refresh design.
The strange thing about this is that I have four different database templates (four different sources) generated by DGW. All of them has database property “Multilingual database” disabled.
Two of them automatically sets the “Multilingual database” property during Refresh design but the other two works as they’re supposed to and don’t set the database property.
Could it be possible that, although you have disabled the multilanguage option in the database property, one of the design elements in the template has been tagged as multilingual? Therefore, whenever you refresh the production databases, the 'Multilingual database" property is automatically enabled. Just a guess.
The problem, in my case, turned out to be the $Language field in the Icon note of the .nsf-database. It turned out to have TWO values “en” AND “en-US”. Since this $Language field were multivalue of course the database must be Multilingual… and it were automatically set during refresh design.
I removed one “language” from the .ntf. But, during a refresh design the $Langague field isn’t updated. Therefore the problem still existed. You need to do a replace design in order to get the $Language field updated.
How could this happen? Well I found out that we were inconsistent when using DGW. Be aware of altering the checkbox of “Omit langague identifier” when creating new language databases in DGW. I guess this is what happended for us.
Here’s some code that removed the Multilingual property and set the database to only be English (without identifier US).
Sub Initialize
Dim session As New NotesSession
Dim db As NotesDatabase
Dim nc As NotesNoteCollection
Dim icon As NotesDocument
Dim pos As Integer
Dim nid As String
Dim vFlags As Variant
Dim sNewFlags As String
Dim sLanguage As String
Set db = session.CurrentDatabase
Set nc = db.CreateNoteCollection(False)
nc.SelectIcon = True
Call nc.BuildCollection
nid = nc.GetFirstNoteId
Set icon = db.GetDocumentByID(nid)
vFlags = icon.GetItemValue("$Flags")
pos = Instr(vFlags(0), "M") 'flag=M (Multilingual database)
If pos <> 0 Then
'Remove database property Multilingual database
sNewFlags = Left(vFlags(0), pos-1) & Right(vFlags(0), Len(vFlags(0))-pos)
'Set language to English without identifier
sLanguage = "en"
Call icon.ReplaceItemValue("$Flags", sNewFlags)
Call icon.ReplaceItemValue("$DefaultLanguage", sLanguage)
Call icon.ReplaceItemValue("$Language", sLanguage)
Call icon.Save(False, False)
End If
Could you please elaborate on what you mean by “poor performance”? Are you referring to the performance of the language databases or DGW itself? We have to globalize a complex Lotus Notes application at our end. The application consists of a suite of 7 databases. The application is, currently, uni-lingual and has to be translated in to Spanish, Portuguese and French. I have used DGW earlier, but this application is a different ball game altogether.
We have already encountered wierd issues with DGW.
Toggling between the language database and the source database always crashes DGW, not only on my machine but also on my co-developers machine, too. Sometimes, it generates an NSD and crashes the Notes client and Domino Designer, too.
The project database, at times, “refuses” to save the tag settings.
The report created in the Report database is most of the time incomplete.
The functionality of the glossary database is inadequate. For e.g., there is no way to tell, at least I haven’t found one, which glossary term is not being used during the translation process. We have to find those terms manually, or we have a ton of “orphaned” terms in the the glossary database.
Since DGW is not a mainstream application, it is very difficult to get answers to questions you have. The globalization forum is “sparsely populated” and you would be lucky to get answers to any of your postings.
My pain is from the actual dbs created from DGW, not DGW itself. I have no experience with DGW, only its output. My preference is still to maintain separate dbs per language or, as I described earlier, make a single db with all languages.
Much less merde/Scheiße/s**t to deal with (pardon me/pardonnez-moi/entschuldigen Sie mich)
