Re: [ jEdit-devel ] Plugin localization files

If you are modifying a plugin that is not based on the standard
build-support stuff, you can look the build.xml and see if you can find the
appropriate place to add it.
It's not always a selector in these older build.xml files, but
whatever it is, you should see other file specs in that same place that
look something like this:

            <fileset dir="${src.dir}">
                <include name="actions.xml"/>
                <include name="dockables.xml"/>
                <include name="**/*.props"/>
                <include name="**/*.html"/>
                <include name="**/*.gif"/>
                <include name="**/*.txt"/>
            </fileset>

So this would be the appropriate place to add such a line.

I just did it for imageviewer and infoviewer. Let me know if there are
other plugins that need it too.

If you are unable to test your own builds, then I suppose it is better you
ask someone else to do it.


On Mon, Jan 14, 2013 at 12:54 PM, Robert Schwenn <
Rob...@ka...> wrote:

>  Am 14.01.2013 01:02, schrieb Alan Ezust:
>
> Basically, if the plugin uses build-support/plugin-build.xml it will be
> included automatically. If not, then you need to modify the build.xml
> manually.
>
>
>
> I've had a look now into some build.xml files and maybe I'm able to tell
> a jEdit standard from a special build.xml now. Do You think I should add
> a line like this:
>
> *<filename name="lang_*.properties"/>*
>
> into the "selector" tag with any id, if it appears for me like a standard jEdit build file? Or should we leave this for the plugin maintainer / releaser?
>
>
> p.s.
> You know, I'm not a Java coder, not familiar with Java build process and
> can't test the build. ;-)
>