Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
7
Erster Beitrag:
vor 3 Jahren, 6 Monaten
Letzter Beitrag:
vor 3 Jahren, 5 Monaten
Beteiligte Autoren:
Rasta, Ola, Al, Adri, Allard

WD 19 Help editor Native Language problem

Startbeitrag von Rasta am 22.12.2014 16:40

Greetings,

I am trying to create Help for my application only in my native language, but when I go to generate help pages for the project I get only blank books and pages.

Kind Regards,
Rasta

Antworten:

Hi Rasta,

I've had the same problem for as long as I remember, since version 5.5.:(
Please tell the forum, if you find a way to do that...:-)

In the meantime, while waiting for PCSoft to get their multilingual system work correctly, if you want a decent help system during this decade, I recommend dr.Explain:
http://www.drexplain.com/

best regards
Ola

von Ola - am 23.12.2014 07:55
I have no problems at all generating help files in my native language.
Make sure you switch to the correct language before you edit the help file.
Realize you create separate help files for every language you support.

Bes regards,

Adri

von Adri - am 23.12.2014 15:04
Hi,

You can generate the help suposely. I however do it a bit diffirent. After having problems as well.

Ok how I do it. I donnot create help files by generating them from help fillout out in help sections of windows. I create the help manually. Just adding books and pages and add Tekst end Pictures etc.

Then in the application I create a help button for a specific page . If one hits F1 on a specific page it loads the help and opens that specific help page.

How do I do that ?

Every helppage has a umber when you create a new page I refer to that in the code of the button ( button is a hidden button )

for instance:
WHelp("Help_Admin012.chm",3) This relates the the third help page

This works for me very well


Regards

Allard

von Allard - am 23.12.2014 18:07
Hi,

Adri, I don't know how you did it but everytime I generate help in my language I get blank pages :(

Allard, it is a good method, but I have a lot of windows to explain and it is easy to get lost.

Ola, I have tried dr.explain and it is great. I like the visual aids a lot, and will try to create manual with it. But I have a small question about it, as I am unfamiliar with it, will I be able to link the pages with my WD applications with shortcuts like F1 as Allard mentioned above?

Kind Regards,
Rasta

von Rasta - am 26.12.2014 19:18
Hello Rasta

There has been a lot of discussion about DR.Explain in the forum over the years, so a search using "dr explain" as a topic will give you some good background info.

These threads are a good starting point.
http://27130.foren.mysnip.de/read.php?27131,71344,72057#msg-72057
http://27130.foren.mysnip.de/read.php?27131,88697,88702#msg-88702

Regards
Al

von Al - am 26.12.2014 20:44
Hi Rasta

You asked: "will I be able to link the pages with my WD applications with shortcuts like F1 as Allard mentioned above?"

Yes. Here's how I do context-specific (window-level) help with dr.Explain:

I have most of my windows based on templates.
For instance, in my form-type window template initialization I have the help keywords set for different user languages like:

wHelpKeywordFi is string = "Lomakkeet" //Finnish
wHelpKeywordEn is string = "Forms" //English

...etc.

So, if the user interface is set in Finnish, and if there is not yet a specific help page made for a specific form window, F1 will open the help page which has the keyword "Lomakkeet" associated with it. This help page will show the generic instructions applicable to all form-type windows.

Then, when I have made the specific help page to cover a specific form and its peculiarities, I will overwrite the generic help keyword(s) in the window initialization code, like:

sHelpKeywordFi = "Tuotteen ylläpito" //Finnish
sHelpKeywordEn = "Product maintenance" //English

...etc.

And in dr.Explain, in the respective help page's properties, there must be a keyword equal to the window's helpkeyword. It directs the help request to the correct help page, regardless what the help page's title or filename is.

Additionally a help-type button, associated to the F1 shortcut key, is needed for each window. I have it included in all my window templates. It has the following code:

SWITCH Nation() //Kieli
CASE nationFinnish: WHelp( HelpFi, sHelpKeywordFi ) //Nation() = 008 = Finnish, "Työmyyrä.chm"
CASE nationFrench: WHelp( HelpFr, sHelpKeywordFr ) //Nation() = 005 = French
OTHER CASE: WHelp( HelpEn, sHelpKeywordEn ) //Nation() = 003 = English
END

And in the program initialization code the help files' filenames must be defined like:

HelpFi is string = "MyAppNameFi.chm" //Finnish help file
HelpEn is string = "MyAppNameEn.chm" //English help file


...etc.

Respectiverly, in dr.Explain there must exist, as a minimum, a help page which has the keyword "Lomakkeet" in the Finnish help file and keyword "Forms" in the English help file. And the same applies to all the basic generic help pages for all templetes.

Now the F1 key will open the correct specific help page, and if it does not exist, the generic help page for the window type.

Best regards
Ola

von Ola - am 27.12.2014 09:54
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.