Created attachment 11873 [details]
Last version 1.0.4

adding Sophie to CC

adding Kevin to CC

Hi, 
 
Thanks for adding me.  I agree whole-heartedly with adding DicOOo.   
 
If it helps I could easily add it to the lingucomponent project and could deliver it anywhere from 
scp/source/lingu or I could make it part of the dictionaries and deliver the file to share/dict/ooo/ if 
you think anyone would think to look there. 
 
Just let me know if I can help. 
 
Kevin 
 

Hi Martin,

Here is a private discussion with Kevin which may interrest you
let me know

Laurent
------------------------
Hi Kevin

A button pointing to it in tools/options/linguistic couls suit the need to 
find it, even if deeply stored in share/dict/ooo ?

Laurent 
------------------------
Hi Laurent,

I think that would require an UI change that they do not want to make in the 
1.1.1 series (but I am not sure).

it is too bad you can't create some kind of start up macro that could be 
installed alone (not as part of a .swx file) that would someone provide or 
offer the service.  

I am just not usre how to add this without adding a button or something that 
changes the UI (and therefore all of the documentation and training materials 
that go along with it).

Any ideas?

Kevin
-----------------------
Hi kevin

If i know where to find DicOOo, it is possible to provide a macro ( as addon 
or built-in) that launch dicOOo.sxw

It would be rather simple

--> Find /share/dict/ooo/DicOOO.sxw local directory ie: what is OOo directory
--> LoadComponentFromURL from this path

Let me know if it this kind of macro is more suitable than an UI change

Laurent 
------------------------------
Hi,

It can't hurt and the macro would be useful no matter where it end up (you 
just need to change the path it looks at).

I think it might be a good idea.  Please add this information to the issue so 
that Martin sees it and can provide feedback on it if need be.

Kevin

Hi Martin, All,
the summary suggests a target milestone :-)
Martin, do you have one in mind?
Greetings, Stefan

accepted for 1.1.1, kevin do you still volunteer for this issue ?

Hi,

I would be happy to house it in the "dictionaries" module and pack it right into the zip file
so that it will get unpacked right into share/dict/ooo/.  This would be very easy to do and
would require no changes to scp (only to dictionaries).

If that is okay, we really need another "standard" macro written by Laurent (hopefully!)

> From Laurent
> It would be rather simple
> 
> --> Find /share/dict/ooo/DicOOO.sxw local directory ie: what is OOo directory
> --> LoadComponentFromURL from this path
> 
> Let me know if it this kind of macro is more suitable than an UI change
> 
> Laurent 

That macro would need to be stored along with all of the other standard macros.

Which project holds the standard macros?

Once I know that and once I have a macro from Laurent to invoke DicOOo from share/dict/ooo
we are in business.

I will make the commits to dictionaries tonight to add DicOOo and pack it up so that it gets 
delivered to share/dict/ooo/

Then all we will be short is his macro to find DicOOo and launch it.

Hope this helps,

Kevin

Hi,

Just committed to CVS for cws_fix645_ooo111fix2

RCS file: /cvs/external/addons/dictionaries/diclst/Attic/DicOOo.sxw,v
done
Checking in diclst/DicOOo.sxw;
/cvs/external/addons/dictionaries/diclst/Attic/DicOOo.sxw,v  <--  DicOOo.sxw
new revision: 1.1.2.1; previous revision: 1.1
done
Checking in diclst/makefile.mk;
/cvs/external/addons/dictionaries/diclst/makefile.mk,v  <--  makefile.mk
new revision: 1.2.32.1; previous revision: 1.2
done
Checking in util/makefile.mk;
/cvs/external/addons/dictionaries/util/makefile.mk,v  <--  makefile.mk
new revision: 1.2.32.1; previous revision: 1.2
done

So DicOOo.sxw will now be deliver to share/dict/ooo/ along with the other writing aids.

We still need a new "standard" macro" to find and load DicOOo.

Hopefully Laurent can supply one.  Then once I find out where
in CVS this standard macro should go, I will commit it as well.

Then we can close this out.

Laurent, the ball is in your court!

Kevin

Can we cvs remove lingucomponent/www/dicooo/DicOOo.sxw then to avoid confusion?

reassigned due to kevins last comment.

Hi,

I do not think we should remove the one from the website.  People still will want to download it 
separately since most people don't use CVS to checkout the source OOo 1.0.X and OOo 1.1.0 and 
prior users will want to use it as well.

Once OOo 1.1.1 has been out for a while then we can remove the website one but even then, being 
able to get it for older releases without having to do a 

cvs co -r cws_fix645_ooo111fix2 dictionaries

would probably be a good thing.

My 2 cents,

Kevin

I'm not going to prevent people from downloading.
I suggest that we have *one* home location for DicOOo.sxw.
AFAIK this is
http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries/dicooo/DicOOo.sxw
(aka ftp.stardiv.de) at the moment and all download pages link to this version.
I would prefer if we use CVS and I'm fine with the external project.
I would automate the mirroring to ftp.stardiv.de.

Laurent, do you have CVS access to the OOo repository?

Hi all,

thanks for this great news !!

@kevin
i'll write the macro tomorrow morning and post it there as a sxw file ... to 
let you check my bugs :)

@stefan
i've CVS acces to fr native-lang project
But i'm not very familiar with this system so the less i modify things, the 
more i'm "cool" (not stressed)

Thanks all for taking care

Laurent

Hi all,

1)
Here is the 1st version of the launcher macro StartDicOOo()
Please find also some suggestions
- Deliver it in DicOOo library, launcher module ?
- Should be plugged with an addon to let user find it more easally than 
browsing macro libraries ?

2)
I ommit the self update feature in the analysis
So, the launcher is based on a DicOOo.lst text file (instead of an hard coded 
fiename) in share/dict/ooo containing the full path to DicOOo.sxw 
Nevertheless, i need then to change DicOOo itself (a new 1.1 version) to let 
it handle this file and restrict updates to administrative setups (ie, the 
user is allowed to write in share/dict/ooo). A message will occur for normal 
users that a new version is available but they have to switch to 
administrative mode to perform the update
Then, i'll update this DicOOo.lst file
a security for the macro StartDicOOo would then be to hard code the name 
DicOOo.sxw and use it if the file provided in DicOOo.lst is not found

Feel free to comment all this stuff ...

Thanks 

laurent
----------------------------------
Sub StartDicOOo()

Dim ThePath as string
Dim aService as object
Dim MyDicOOo as string
dim TheDoc as object 
dim args(1) as new com.sun.star.beans.PropertyValue

'Find path
aService = CreateUnoService("com.sun.star.util.PathSubstitution")
ThePath =ConvertToURL(aService.substituteVariables("$(prog)", true))
ThePath=ThePath & "/../share/dict/ooo"

'read DicOOo.lst file
Open ThePath & "/DicOOo.lst" for input as #1
	line input #1, MyDicOOo
close #1
MyDicOOo=ConvertToURL(MyDicOOo)

'Opens DicOOo main file
args(0).name="InteractionHandler"
args(0).value=""
args(1).name="MacroExecutionMode"
args(1).value=com.sun.star.document.MacroExecMode.ALWAYS_EXECUTE_NO_WARN '4
TheDoc=StarDesktop.loadComponentFromURL(MyDicOOo,"_blank",0,args())

End Sub

sorry, some updates/correction

"2) I ommit" please read "2) i ommitted"

DicOOo modifications are easy but it may take some time to gather all 
translations of UI if some occurs. I'll try not to add new sentences 
though ... if i can

Thanks 

Laurent

Hi again :)

here we are .... !!

Please find
- DicOOo 1.1 (version to be tested - should work)
- version.txt needed on mirrors
- the final StartDicOOo Macro

let me know

Regards

Laurent
------------------------
Option Explicit

Sub StartDicOOo

Dim ThePath as string
Dim aService as object
Dim MyDicOOo as string
dim TheDoc as object 
dim args(1) as new com.sun.star.beans.PropertyValue

on error resume next

'Find path
aService = CreateUnoService("com.sun.star.util.PathSubstitution")
ThePath =ConvertToURL(aService.substituteVariables("$(prog)", true))
ThePath=ThePath & "/../share/dict/ooo"

if  fileExists(ThePath & "/DicOOo.lst") then
'read DicOOo.lst file
	Open ThePath & "/DicOOo.lst" for input as #1
		line input #1, MyDicOOo
	close #1
else
'create default DicOOo.lst file
	Open ThePath & "/DicOOo.lst" for output as #1
		MyDicOOo=ThePath & "/DicOOo.sxw"
		print #1, MyDicOOo
	close #1
endif

'security
if Not fileExists(MyDicOOo) then
	MyDicOOo= ThePath & "/DicOOo.sxw"
endif
MyDicOOo=ConvertToURL(MyDicOOo)	

'Opens DicOOo main file
args(0).name="InteractionHandler"
args(0).value=""
args(1).name="MacroExecutionMode"
args(1).value=com.sun.star.document.MacroExecMode.ALWAYS_EXECUTE_NO_WARN '4
TheDoc=StarDesktop.loadComponentFromURL(MyDicOOo,"_blank",0,args())

End Sub

Created attachment 12353 [details]
DicOOo 1.1

Created attachment 12355 [details]
needed on mirrors for self-update

I should be done !
reassigned to Kevin

Hi Laurent,

Thanks but I am unsure what to do with all of the pieces.

1. I know to take this DicOOo.sxw and commit it to cvs in dictionaries to replace the one that is 
there

2. what do I do with version.txt and why?

3. The macro you put in the body of this issue?  Should it have a particular name?  Where should it 
go?  What file in the installed OOo should this be found in?  Once I know that I can find what 
module and file in CVS is used to generate that and commit the changes?

4. How would a user actually invoke in this macro?

Sorry for my ignorance but what I know about macros and the like you could put in a thimble with 
lots of room left over.

Thanks,

Kevin

Hi Kevin

>Thanks but I am unsure what to do with all of the pieces.

well neither do I ;)

>1. I know to take this DicOOo.sxw and commit it to cvs in dictionaries to 
>replace the one that is there

Yes if checked on your side
Older versions are safe as they ran for some months
This one is new - Changes are not so big only dealing with self-update
Do you want me to update it on stardiv (with version.txt file) ?

>2. what do I do with version.txt and why?

The version.txt has to go on mirror synchronized with a new DicOOo version
Basically DicOOo checks this file content to compare its internal version to 
the one that is on the mirror to detect if an update has occur
Then it proposes the update

>3. The macro you put in the body of this issue?  Should it have a particular 
>name?

I suggest to put it in a library called DicOOo in a module called Launcher
Put can be put in an existing library

> Where should it go?
among standard macros (as tools)

> What file in the installed OOo should this be found in?  

?????

>Once I know that I can find what module and file in CVS is used to generate 
>that and commit the changes?

Well i don't know enough internal OOo structure to help you 

>4. How would a user actually invoke in this macro?
Well that is the problem
An addon.xcu should do the trick
merged to OOo xcu files, it should let appear an entry
DicOOo in Tools/addons

in fact, there are 2 solutions but can only help and not do all the stuff
1- put this starter macro in an addon and launch this addon (with pkgchk --s) 
on OOo install. Is it possible ? It would be great as Library and menu entries 
would be automatically istalled
2- hard install this macro and modify menu entries by merging some xcu file 
(don't know if so easy though)

Let me know

Laurent 
 

Hi Laurent,

Okay, the best I could do without adding menus or dialogs is as follows.

1. First I converted your inline Basic to an xml utf-8 encoded DicOOo.xba file

2. I copied DicOOo.sxw into share/dict/ooo/

3. I copied DicOOo.xba and a revised script.xlb file into user/basic/Standard/

Now if a user goes to Tools->Macros under the Standard a "DicOOo" appears.

If I click it, then DicOOo.sxw is launched and all works.

I will attached the files to here next.

What do you think about this approach?

It would mean only slight modifications to the wizards/ module.

Kevin

Created attachment 12368 [details]
The DicOOo.xba file

Created attachment 12369 [details]
the file to add the DicOOo to the Standard Macro menu

Hi, 
 
Okay I have tested this and it seems to work.  But if we decide to keep it here as a "Standard" 
Macro as part of the "wizards" module we could in fact remove DicOOo.sxw from dictionaries 
where I put it and move it here in wizards. 
 
If we do that then we could install it  the user's user/basic/Standard/  so it ends up right beide 
DicOOo.xba and so can be written to and updated by a normal user and not require admin mode. 
 
Comments? 
 
Please let me know which solution if best and I will do my best to make the commits. 
 
Thanks, 
 
Kevin 
  

Hi Kevin,
 
> Okay I have tested this and it seems to work.

Ok !

>But if we decide to keep ... remove DicOOo.sxw from dictionaries 

Yes we can, but we will loose features
 
> If we do that then we could install it  the user's user/basic/Standard/  so 
it ends up right beside DicOOo.xba and so can be written to and updated by a 
normal user and not require admin mode. 

How would you then handle self-update mode ?
What about guidelines provided in the sxw file in all the languages ?

I don't have THE solution. It depends on how you consider DicOOo
1- a static package that won't evoluate (new languages, bug corrections, add 
fetaures)
2- a dynamic package as it is now with self update feature ...

I prefer solution 2 as it does not imply modifciations anymore to DicOOo 
structure but it's up to you 

What about the solution of an addon to plug a sub-menu entry in tools/addon 
menu pointing on the launcher macro ? Is it possible to launch pkgchk at the 
end of the install process ?

Laurent

Hi Laurent, 
 
I did not mean to make DicOOo.sxw an pure .xba file.  I just meant we coud put the DicOOo.sxw 
into user/ tree so that users could more easily update it.  The only difference is if we pack it up 
form the dictionaries/ module or from the wizards module.  Frankly, I think the best way to do this 
is to create a Launcher Wizard (since DicOOo is really a Wizard that leads you through 
downloading and installing dictionaries). 
 
Unforutnately, I know knothing about macros at all.  I had to grep all through the OOo cvs to find 
that wizards was the best place and then study the code there to figure out how to add it by 
example. 
 
I can not find any current Addons examples even in the SDK.  What must Addons.xcu look like.  
What do those fields mean? 
 
So I think the best solution for 1.1.1 is either  to: 
 
1.  add it to the OOo CVS tree by adding it to Macros and then eventually moving it to its own 
Wizard with its own Wizard Menu entry. 
 
or 
 
2. build pkgchk packages for Add-Ons but I have no idea how to do that.  Do you know how to 
build a good Addon package and how the .xcu and all of the other things should look? 
 
Thanks, 
 
 
Kevin 
 
 

Hi Kevin,
 
>I did not mean to make DicOOo.sxw an pure .xba file.  I just meant we coud   
> put the DicOOo.sxw into user/ tree so that users could more easily update 
>it.  The only difference is if we pack it up form the dictionaries/ module or 
>from the wizards module. 

Well it could work (i would then have to modify DicOOo again - not a problem) 
but i don't think it is a good idea though
- What about multi-user -net installation : each user will have to download 
DicOOo updates
- I think DicOOo is an administrative tool. Only one version should be on the 
system and all user (and the launcher macro) could be able to find it so 
share/dict/ooo would be a good place for the dicooo.lst file (and of course 
the original one for backup)
- Technically speaking, it is difficult to overwrite DicOOo.sxw file inside 
DicOOo macro itself. That's why the version number is appened to the name of 
the new version allowing user to store it whereever he wants. The only problem 
of rights is for the launcher wizard to store the path. If in share/dict/ooo 
(so all users can find the dicooo.lst file) i must have writting rights (ie 
adminstrative mode). Not doing that, other users won't be able to know that a 
new version is enabled on the system 

> Frankly, I think the best way to do this is to create a Launcher Wizard 
>(since DicOOo is really a Wizard that leads you through 
> downloading and installing dictionaries). 

This launcher wizard is the purpose of the macro i supplied StartDicOOo
No problem to bring it with the wizards macros. But StartDicOOo has to be able 
to find where to find the current DicOOo file (purpose of dicooo.lst file)

Perharps someone knowing better the OOo CVS architecture than me could help to 
decide
 
>I can not find any current Addons examples even in the SDK.  What must 
>Addons.xcu look like.  
>What do those fields mean? 

developpers guide chapter 4.3 provides a detailled explanation on its 
structure and how to build one
 
>1.  add it to the OOo CVS tree by adding it to Macros and then eventually 
>moving it to its own 
>Wizard with its own Wizard Menu entry. 

requires OOo menu modifications
  
>2. build pkgchk packages for Add-Ons but I have no idea how to do that.  Do 
>you know how to 
>build a good Addon package and how the .xcu and all of the other things 
>should look? 

Yes i did some simple addons and this one is very simple (no icon, just an 
entry under tools/addons pointing on the StartDicOOo launcher macro)
BUT we have to be sure that this addon installation with pkgchk can be 
launched during OOo installation 
If yes, i can provide the addon.xcu file

Thanks

Laurent

Hi Laurent, 
 
I think if you provide all of the pieces that pkgchk would need to isntall, I can make scp 
modifications to install them during normal installation by adding things to scp/source/lingu. 
 
Otherwise, given my limited knownledge of things, the best I can do is the Tools->Macro 
which will show  
 
Standard 
     DicOOo 
     Module1 
 
If you then click on DicOOo, the StartDicOOo macro will appear and running that will nicely bring 
up DicOOo.sxw and it does work (I have tested it). 
 
For 1.2 we should be able to make it a full fledged Wizard (I would like to call it Launcher" that 
could be used to run DicOOoStart, and other things we think up later.... 
 
Martin and Stefan,and others would you please add your comments so that we know what you 
would prefer. 
 
Thanks, 
 
Kevin 
 

Ok Kevin,

i build the Addon package asap (probably beginning of this week end)

Laurent

mh->tv: can you please give advice as Kevin requested ?!

Kevin already started to work on this issue -> STARTED

Hi Kevin

As promised please find the addon to install DicOOo launcher

The macro is embedded to it so you don't have to care about wich branch of CVS 
to put it in

To install it :

- shutdown OOo (and quick start)
- copy the AddonDicOOo.zip file into <OOo>/share/uno_packages (dont't unzip it)
- run the command: <ooo>/program/pkgchk -s

be carefull: remove DicOOo Library if you have one already installed before 
otherwise install will fail

To control :

Start OOo
You should see an new menu entry in Tools/addons/DicOOo
Launch it, DicOOo will start (hope so !)

If you look at tools/macro/macro, you will see a new DicOOo library containing 
the launcher

For OOo 1.1.1 distribution :

at the end of OOo install
- copy the AddonDicOOo.zip file into <OOo>/share/uno_packages (dont't unzip 
it)- or include it into the setup tree if possible
- run the command: <ooo>/program/pkgchk -s

DicOOo launcher will then be installed as a shared component visible from all 
users !!!

I will post all of this on the issue --> Done :)

Let me know

Laurent 

Created attachment 12398 [details]
Addon to install DicOOo launcher

Hi,

Okay, I think we are all except for where to put the version.txt file?

It seems version.txt has been removed from the DicOOo directory under lingucomponent.

So where should version.txt be put?

Does anyone know?

All other pieces are in place except for this one last piece!

Ideas anyone?

Kevin

Hi kevin,

Great Job !! Congratulations
 
> So where should version.txt be put?
> 

version.txt is not locally needed
it has to remain on mirrors to let the local DicOOo check if there is a new 
version available (against its internal version number)

i'll update mirrors asap with DicOOo1.1

Laurent 

Hi Laurent,

Then I am resolving this as fixed.
Please verify and close this issue once 1.1.1 has been released.

I am building a new version of 1.1.1 with MacOSX right now and I will
test thigns to make sure it all works.

Thanks,

Kevin

AFAIK we wanted to get away from the pkgchk approach so, before closing this
issue we need to make sure that the menu entry gets generated with the standard
installation.

Hi Tom,

Yes we used the patches we talked about and not pkgchk at all.

With those patches and pieces in place ....

- the build completes fine

- once installed if I go to Tools->Macro->Macro...  I now see a Launcher directory with an entry 
DicOOo.  If I click on it, the macro StartDicOOo is displayed.

- that macro properly launches DicOOo.sxw and it nicely downloaded and installed the new 
German combined orthography dictionary with no problems.

So unless it was supposed to appear someplace else, all is fine.  

Was it supposed to appear under AutoPilots as well?

Thanks,

Kevin

Ah, ok, if that way of starting the macro is sufficient than everything is fine ;)
I thought you would like to see an additional entry in the Tools Menu or in the
AutoPilots menu. But maybe this would be overkill..

Hi,

>Ah, ok, if that way of starting the macro is sufficient than everything is 
>fine ;)

No !!!!!
I definitivelly don't aggree
DicoOo will the be useless and not seen in 95% of cases

That's why i proposed the pkgchk (ok, you don't want it ..) but try to put an 
entry in tools menu around linguistic section ... or autopilot as you want

We must have a menu entry !!! sorry

:)

Laurent

Hi Tom, 
 
I agree with laurent that this will porbably never be found ;-) 
 
Did you expact it to appear in some other place?  Did I mess up somehting in scp or wizards or is 
there some other mdoule I need to modify to get this to work? 
 
Thanks, 
 
Kevin 
 

Hi, 
 
Okay I took a peak at this.  it seems that in scp/source/office/profile.scp you can see the 
information used to create the Wizrds menu entyries. 
 
They all look something like the following: 
 
ConfigurationItem GID_CONFIGURATIONITEM_COMMON_MENUS_WIZARD_M#_XXXXXX 
 
where: 
 
# is a number that distinguishes one menu entry from another and 
 
XXXXXXX is one each of TITEL, YRL, TARGETNAME, and IMAGEIDENTIFIER 
 
The last number in my file seems to be M15 so I think the following entries might be close to what 
we want: 
 
ConfigurationItem GID_CONFIGURATIONITEM_COMMON_MENUS_WIZARD_M16_TITEL 
    #ifdef WEB_PRODUCT 
        ModuleID         = GID_MODULE_PRG_WRT; 
    #else 
        ModuleID         = GID_MODULE_PRG_WRT_BIN; 
    #endif 
        Path             = "org.openoffice.Office.Common/Menus/Wizard/*['m16']/Title"; 
        KEY_ALL_LANG_LETTER; 
        ALL_LANG(Value, STR_DIR_MENU_WIZARD_LAUNCHER); 
        Styles           = (CFG_STRING, CREATE); 
End 
 
ConfigurationItem GID_CONFIGURATIONITEM_COMMON_MENUS_WIZARD_M16_URL 
    #ifdef WEB_PRODUCT 
        ModuleID         = GID_MODULE_PRG_WRT; 
    #else 
        ModuleID         = GID_MODULE_PRG_WRT_BIN; 
    #endif 
        Path             = "org.openoffice.Office.Common/Menus/Wizard/*['m16']"; 
        Key              = "URL"; 
       Value            = "macro:///Launcher.DicOOo.StartDicOOo"; 
        Styles           = (CFG_STRING, CREATE); 
End 
 
ConfigurationItem 
GID_CONFIGURATIONITEM_COMMON_MENUS_WIZARD_M16_TARGETNAME 
    #ifdef WEB_PRODUCT 
        ModuleID         = GID_MODULE_PRG_WRT; 
    #else 
        ModuleID         = GID_MODULE_PRG_WRT_BIN; 
    #endif 
        Path             = "org.openoffice.Office.Common/Menus/Wizard/*['m16']"; 
        Key              = "TargetName"; 
        Value            = "_self"; 
        Styles           = (CFG_STRING, CREATE); 
End 
 
ConfigurationItem 
GID_CONFIGURATIONITEM_COMMON_MENUS_WIZARD_M16_IMAGEIDENTIFIER 
    #ifdef WEB_PRODUCT 
        ModuleID         = GID_MODULE_PRG_WRT; 
    #else 
        ModuleID         = GID_MODULE_PRG_WRT_BIN; 
    #endif 
        Path             = "org.openoffice.Office.Common/Menus/Wizard/*['m16']"; 
        Key              = "ImageIdentifier"; 
        Value            = "private:image/3216"; 
        Styles           = (CFG_STRING, CREATE); 
End 
 
 
But I am not sure. 
 
I think the entry for TITEL has to have more information that translates the term "Launcher" into 
many differnt languages. 
 
But I am not sure where those translations are put. 
 
Is this something close? 
 
Kevin 
 

Hi, 
 
I looked and found scp/source/office/profile.lng  which defines the translations 
 
Here is the one for the formula wizard ... 
 
 
[STR_DIR_MENU_WIZARD_FORMULAR] 
88 = "表å<96>®(~R)..." 
81 = "ã<83><95>ã<82>©ã<83>¼ã<83> (~R)..." 
90 = "Fo~rm..." 
30 = "~Öüñìá..." 
34 = "Formulario..." 
55 = "Fo~rmulário..." 
48 = "Fo~rmularz..." 
03 = "F~ormulário..." 
82 = "ì<96><91>ì<8B><9D>(~R)..." 
33 = "Form~ulaire..." 
96 = "Form..." 
01 = "Fo~rm..." 
07 = "Ôîðìà..." 
86 = "表å<8D><95>(~R)..." 
31 = "F~ormulier..." 
46 = "F~ormulär..." 
45 = "F~ormular..." 
49 = "F~ormular..." 
39 = "~Formulario..." 
35 = "Luo ~lomake..." 
37 = "F~órmula..." 
66 = "Fo~rm..." 
42 = "FormuláÅ<99>..." 
97 = "â<80>®×<98>×<95>פסâ<80>¬" 
91 = "Fo~rm..." 
43 = "Fo~rmulár..." 
36 = "Å°~rlap..." 
50 = "~Obrazec..." 
 
So I think we need to make one of these for  
 
STR_DIR_MENU_WIZARD_LAUNCHER 
 
That says shows all of the translations for something like 
 
"DicOOo Launcher" 
 
or whatever you want here Laurent. 
 
I think with those changes and translations added to scp/source/profile.scp and profile.lng we will 
probably see something in the AutoPilot/Wizards menu. 
 
Can you look at the example and generate a set of tranalations for the string you would like 
there? 
 
I can then use this to test things on my build. 
 
Kevin 
 
 
 

Hi, 
 
Okay, I tried my changes (see patch DicOOo_menu.patch) and now I have a nice Autopilot 
Menu that works. 
 
The problem is the patch is missing all of the translations for the phrase 
"DicOOo Launcher" 
 
I have attached the patch. 
 
Tom if you can look it over and Laurent if you can provide some translations, I will then commit 
this and finally close this thing out for good! 
 
Please see the attached DicOOo_menu.patch 
 
Hope this helps, 
 
Kevin 
 

Created attachment 12468 [details]
patch to applyy to scp to create Menu item for DicOOo

Hi kevin

Thanks a lot

2 solutions for the menu label:
- Simply "DicOOo" which would not require any translation,, or "DicOOo Macro"
- Use some translation given inside
DicOOo.Translation.InitialiseLangue
The closest would be traduction(Langue,9)="Install the selected dictionaries."
But need to be checked for all lanuguages 

Laurent

Great work Kevin! So you found out about the menu entries yourself before I
found time to give you info on this ;)
Please make sure you enclose your latest SCP changes in an #ifdef OSL_PRODUCT so
we make sure the entry only appears in OO.o (not StarOffice).

Hi Laurent,

> 2 solutions for the menu label:
> - Simply "DicOOo" which would not require any translation,, or "DicOOo Macro"

Since "DicOOo" is a proper noun (name for something), then it would not be translated at all right? 
If that is what you want, that is fine with me.  But will everyone know what DicOOo is or does?

If so, then I have no trouble just making it 

"DicOOo ..."

for all languages under AutoPilots and be done with it.
   
It is your call.  Just tell me what you want and provide 
translations (if needed) and I will fix things and commit it. 


Hi Tom,

Please make sure you enclose your latest SCP changes in an #ifdef OSL_PRODUCT so
we make sure the entry only appears in OO.o (not StarOffice).

Okay I will do that.  Is this needed in both profile.lng and profile.scp or only profile.scp?
I assume if the profile.scp parts are ifdef'd out then any translations in profile.lng
are meaningless and can be left it.


Is the patch then okay (with the ifdef added) to commit (after Laurent has decided on a name)?

Thanks,

Kevin

>>Please make sure you enclose your latest SCP changes in an #ifdef OSL_PRODUCT so
>>we make sure the entry only appears in OO.o (not StarOffice).

>Okay I will do that.  Is this needed in both profile.lng and profile.scp or
only profile.scp?
>I assume if the profile.scp parts are ifdef'd out then any translations in
profile.lng
>are meaningless and can be left it.

Yes.

>Is the patch then okay (with the ifdef added) to commit (after Laurent has
decided on a name)?

Seems to be okay :)

Hi, 
 
Okay I have added the translations given to me by Laurent and then used DicOOo (a proper 
name) in all of the remainder. 
 
I am ready to commit this and close this issue.   
 
The problem is I think they have closed the fix2 tree. 
 
May I commit this still to that tree? 
 
Thanks, 
 
Kevin 
 

Hi, 
 
I went ahead and committed it but I am not sure that it will make it. 
 
So with this, I am now closing this issue. 
 
People can reopen if it missed the tree for the next tree. 
 
I have my fingers crossed.....  ;-) 
 
Kevin 
 

I see it in fix3.
Reopen if needed.

Hi all 
 
please find the last DicOOo revision 1.2.3 
Due to a misconfiguration (who said bug ?), i had to update 
Sorry for any inconvenience :( 
 
No impact on translation related to issue IZ 24567 
 
Sorry again 
 
Laurenty 

Created attachment 13375 [details]
DicOOo rev. 1.2.3

hjs: Kevin is on holiday.

Just for information :

With OOo 680 m24 20040204, DicOOo 1.0 and DicOOo 1.2.3 make OOo crashed (Tested 
with English OOo 680 m24 20040204 on French Win2k SP4).

Don't forget a version of DicoOOo for OOo 2.0.

Committed to ooo111regression3.

Verified.

i was on sick leave :-(

as all seems to be done, i close this issue...