I think Max hit the nail on the head. I never liked the solution of
downloading English files *and renaming them* to serve as "catch all" when
the Spanish files are not there. I think that the right solution is to keep
the original filenames so that the user knows that the server.es.properties
is using spotter.en.dict
So names such as spotter.dict, context-index, etc should be abolished in
favor of language-specific naming (spotter.en.dict, context-index.en, etc).
When there isn't something from Spanish that we need to use from English,
we just point server.es.properties to e.g. spotter.en.properties
Makes sense?
Cheers
Pablo
On Dec 5, 2012 12:06 AM, "Max Jakob" <[email protected]> wrote:
> On Tue, Dec 4, 2012 at 5:47 PM, Rafa Haro <[email protected]> wrote:
> > Problem is server.properties file points to default
> > spotter.dict, which is fetched by download.sh script.
> > The generated dictionary (surfaceForms.tsv.spotterDictionary) is
> > never renamed and moved by index.sh script.
>
> The download.sh script gets some standard data for English and puts
> them in a place where the standard properties file can find it. If new
> data is produced, the properties have to be changed to point to the
> user-generated data.
> When the index.sh script would move the file, existing data would be
> overwritten, which is bad if you still need the old data. Having one
> properties file per language (or per use case) is a good solution in
> my view.
>
> Cheers,
> Max
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Dbp-spotlight-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbp-spotlight-users
