Issue 19060 - Zip dictionaries package organization
Summary: Zip dictionaries package organization
Status: CLOSED WONT_FIX
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@lingucomponent
QA Contact: issues@lingucomponent
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-04 14:44 UTC by maison.godard
Modified: 2013-02-24 20:34 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Some guidelines on zip file architecture (7.64 KB, application/octet-stream)
2003-09-04 14:46 UTC, maison.godard
no flags Details
French SpellChecker (318.05 KB, application/octet-stream)
2003-09-04 14:49 UTC, maison.godard
no flags Details
uk_UA spellchecker (1.31 MB, application/octet-stream)
2003-09-04 15:11 UTC, maison.godard
no flags Details
sv_SE spellchecker (130.37 KB, application/octet-stream)
2003-09-04 15:15 UTC, maison.godard
no flags Details
sv hyphenation (15.08 KB, application/octet-stream)
2003-09-04 15:16 UTC, maison.godard
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description maison.godard 2003-09-04 14:44:51 UTC
Hi,

First, some CC's will be added when a zip language file will be modified
I ask the concerned readers to check the package and post a reply to tell if it 
is correct or not

I'll try to put a detailled Log on what has been modified for each package

I post a small document concerning DicOOo but sumaryzing the zip file structure

Thanks
Laurent
Comment 1 maison.godard 2003-09-04 14:46:38 UTC
Created attachment 9002 [details]
Some guidelines on zip file architecture
Comment 2 maison.godard 2003-09-04 14:49:51 UTC
Created attachment 9003 [details]
French SpellChecker
Comment 3 maison.godard 2003-09-04 15:03:56 UTC
*fr_FR.zip - sgauti@openoffice.org
merged GPL-fr to README_fr_FR.txt
Comment 4 maison.godard 2003-09-04 15:11:43 UTC
Created attachment 9005 [details]
uk_UA spellchecker
Comment 5 maison.godard 2003-09-04 15:14:03 UTC
*uk_UA.zip - lvm@mystery.lviv.net
merged copyright to readme
Comment 6 maison.godard 2003-09-04 15:15:14 UTC
Created attachment 9006 [details]
sv_SE spellchecker
Comment 7 maison.godard 2003-09-04 15:15:54 UTC
*sv_SE.zip - stekman@sedata.org
merged following files to readme
- contributors
- copying
- copyright
-news

*sv_SE.zip - stekman@sedata.org
Removed hyph_sv_SE.dic from package
Comment 8 maison.godard 2003-09-04 15:16:45 UTC
Created attachment 9007 [details]
sv hyphenation
Comment 9 maison.godard 2003-09-04 15:17:14 UTC
*hyph_sv.zip - stekman@sedata.org
creation
need a README_hyph_sv.txt file
need be to added in list
Comment 10 khendricks 2003-09-04 16:53:05 UTC
Hi, 
 
I think we need to think this through a bit more before racing ahead here. 
 
Since we have to open up every zip and repackage it we should: 
 
1. always make sure the package name has both language and region information 
 
(so hyph_sv.zip should really be hyph_sv_SE.zip) since there may be cases when 
one language is spoken in two differnt regiosn that have different hyphenation rules 
due to different accents and pronounciation of the same word. 
 
This happens with en since US and GB do hyphenate differently. 
 
We should also think about forcing the README_* to be really two files since mixing 
encodings in any one file will create problems for most text editors! 
 
So my idea os simply catting the files together messes up on some of these. 
 
Perhaps we need to think about the correct format for the README file since mixing 
encodings is going to mess things up. 
 
Perhaps if we go with pure UTF-8 we could then have a text file that would be 
readable under ascii/latin1 as is but that could support multiple encodings in the 
same file. 
 
Are there any/many text editors that will properly handle utf-8 chars for all platforms 
(Windows, Linux, Solaris, MacOSX, FreeBSD, Irix, etc). 
 
I think emacs and kate under Linux will proeprly handle utf-8 files. 
 
What do you think? 
 
Should we convert every *.txt file to utf-8 first before concatenating them? 
 
Kevin 
 
Comment 11 maison.godard 2003-09-04 19:11:53 UTC
HI

Kevin I agree with you

Sorry if my question is dummy, but, what about an swx file handling 
(if possible) multiple charset for README ?

Laurent
Comment 12 khendricks 2003-09-04 21:12:31 UTC
Hi, 
 
Would and swx version work for your "preview contets of Readme"? 
 
Perhaps the right way to do this is to leave all of the peices as they are but create a 
new ReadMe_*.swx which contains all of them properly converted into a writer 
document. 
 
Would DicOOo be able to show that file when the box to review the readme is 
selected? 
 
Kevin 
 
Comment 13 khendricks 2003-09-04 21:13:18 UTC
Hi, 
 
Adding myself to CC on this one. 
 
Kevin 
 
Comment 14 maison.godard 2003-09-05 07:12:47 UTC
Hi

DicOOo can handle sxw files as it uses OOo to display the readme files
I just have to now it before

- sxw is a solution (need changing 2 lines of code)

an other
- I can dive in OOO Zip package api in order to retreive all files 
except .aff, .dic ... and display them
In the next coming version, all files (for different dictionaries)  
are merged into one only file when edited - I need to invitagate a 
more deeper though ... This last solution would work but i expect 
some problems on character sets when doing it dynamically and we will 
the not standardize the Zip content

Let me know

Laurent
Comment 15 khendricks 2003-09-05 14:12:21 UTC
Hi, 
 
I think since the installer can only be used inside of OOo and it is only 2 lines of code 
to change we should keep all files in all zips the same as they are now except for the 
**addition** of a README_lang_country.swx file that combines all of the extra 
pieces. 
 
If that sounds like a good idea, let's do that instead of just merging differnt text files 
with differnt encodings into one. 
 
Richard and Laurent are we in agreement? 
 
Kevin 
 
Comment 16 maison.godard 2003-09-05 14:40:48 UTC
it's ok for me

I wait for Richard agreement before beginning to modify my current 
building version (Beta5.5)

Should it be possible to make a call on lingucomponent list to have 
people doing these sxw files (especially for "strange" character sets)

do we expect more than one sxw file/zip archive or all will be merged 
into only one file ? I prefer only one, it should be sufficient

Laurent
Comment 17 richard.holt 2003-09-06 17:53:47 UTC
Downloaded the Architecture notes, and the first 4 dicts. 
I will upload to stardiv this afternoon.

About the README_xx_XX.sxw.  I can handle it but it seems it would be
more accessible as a text file.  I prefer using a text editor for
small files compared to OOo.  Maybe my system doesn't have enough
horsepower. Small files are slow.  

But, on the other hand, if you guys feel it's a good move, I can do
it. Just need to redo my group of files (dicts) to create an sxw. 

Perhaps we should agree on a layout for the sxw? I'll take a look at
the architecture.sxw.  By the way, it makes downloading easier if you
don't include your local path in the filename, leave only the
filename.ext.   

One other note, I'm on a dialup line, flatrate, but I don't stay
online constantly. Therefore, I don't check by issue number for
messges unless I receive an email.  Just in case I seem slow in
answering. :-))

Richard.
Comment 18 caolanm 2010-03-29 21:11:23 UTC
DicOOo is redundant now given super-dooper extensions, right?
Comment 19 caolanm 2010-03-29 21:11:40 UTC
closing