You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Dennis E. Hamilton" <de...@acm.org> on 2014/12/25 00:42:16 UTC
Explaining Java (was RE: Java 32)
I finished checking on the Java-specific messages and the six messages only have a single place where each is produced.
It appears that a single (default en) page could provide the necessary information for reference from any messages in the installed binaries.
Andrea suggests
The page could be included in the set of "standard pages" (the
"xx pages", see http://openoffice.apache.org/website-native.html
and then each translation team can decide whether to use the
English one or their translated one.
A. Is this a potential way to do it?
1. Create an ooo-site/trunk/content/xx/java/ directory.
2. Create leftnav.mdtext and index.mdtext files there.
3. The content/xx/java/index.mdtext would become the English Language version that
We adopt for the target.
If further "breakout" is required, it can be handled in that directory at a later time.
B. Having done that, and having the message be agreeable, internationalization can commence.
C. At an appropriate time, the content/java/ directory is created and it is arranged that this and content/xx/java/ are synchronized. (I have no idea what order this has to be in and which is the master.)
D. The current content/download/common/java.html can be redirected to content/java/
Or
E. The adjusted default messages that link to the site will link to http://openoffice.org/java and be in the build in time to test (4.1.2?) developer builds with the new messages and the new site pages.
How am I doing?
-----Original Message-----
From: Andrea Pescetti [mailto:pescetti@apache.org]
Sent: Monday, December 22, 2014 00:12
To: dev@openoffice.apache.org
Subject: Re: Java 32
On 22/12/2014 Dennis E. Hamilton wrote:
> I am assuming that we can do the job with a single text. So I
> see no problem with where it is kept.
> One consideration might be the maintenance of the different-language
> versions and how browsers are routed to the correct one.
The page could be included in the set of "standard pages" (the "xx
pages", see http://openoffice.apache.org/website-native.html and then
each translation team can decide whether to use the English one or their
translated one.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Andrea Pescetti <pe...@apache.org>.
On 27/12/2014 Dennis E. Hamilton wrote:
> How about this? Create an ooo-site/trunk/content/java/ *folder*
> where the index.htm will be the new version of the target file.
> This can be done in advance because and, after the text is
> considered OK, internationalization could proceed without pressure
> in anticipation of 4.2.0.
> there is no link to it from anywhere yet.
This would be OK. then java/index.html becomes, for translations,
xx/product/java.html ; we already do this for other files.
> I missed the message about timing and 4.1.2 versus 4.2.0 somehow.
> So, we can we discuss changes to the messages and maybe make
> bugzilla issues but changes should not be made to the trunk until
> 4.1.2 is out the door?
Code and translations follow separate paths. The current trunk can be
freely modified and it will lead to, say, 4.2.0 (exact numbering still
undecided). For a bugfix release (like 4.1.2) we will have a separate
line based on "AOO410", the one that was used for 4.1.0 and 4.1.1. So
code is OK.
Translations, instead, currently have only one version available: in our
example, it can be set to trunk or to the 4.1.2 branch. And it is
currently aligned with trunk. So if we created (for code) a 4.1.2 branch
and you pushed the new English string to it, translators wouldn't find
it in Pootle and wouldn't be able to localize it.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Explaining Java (was RE: Java 32)
Posted by "Dennis E. Hamilton" <de...@acm.org>.
-- replying to this below --
From: Andrea Pescetti [mailto:pescetti@apache.org]
Sent: Friday, December 26, 2014 15:44
To: dev@openoffice.apache.org
Subject: Re: Explaining Java (was RE: Java 32)
On 25/12/2014 Dennis E. Hamilton wrote:
> A. Is this a potential way to do it?
> 1. Create an ooo-site/trunk/content/xx/java/ directory.
> 2. Create leftnav.mdtext and index.mdtext files there.
> 3. The content/xx/java/index.mdtext would become the English Language version that
> We adopt for the target.
> If further "breakout" is required, it can be handled in that directory at a later time.
In "xx" we try to avoid too many subdirectories. The Java file could
find a place in the "product" directory, and be referenced from the
leftnav in that directory (extended a few hours ago).
> B. Having done that, and having the message be agreeable,
> internationalization can commence.
> C. At an appropriate time, the
> content/java/ directory is created and it is arranged that this and
> content/xx/java/ are synchronized. (I have no idea what order this
> has to be in and which is the master.)
"xx" is generated from the English content, so steps are: write English
page; copy to xx (structure, i.e., filenames and directories, may
change); translators add it.
<orcmid>
How about this? Create an ooo-site/trunk/content/java/ *folder*
where the index.htm will be the new version of the target file.
This can be done in advance because and, after the text is
considered OK, internationalization could proceed without pressure
in anticipation of 4.2.0.
there is no link to it from anywhere yet.
The folder is both to allow the very short URL,
<http://openoffice.org/java>
in messages, and the possibility that there might be further more-
technical detail in order to keep the main page straightforward.
We'll know better in trying it out.
</orcmid>
> D. The current content/download/common/java.html can be redirected to
> content/java/ Or E. The adjusted default messages that link to the
> site will link to http://openoffice.org/java and be in the build in
> time to test (4.1.2?) developer builds with the new messages and the
> new site pages.
Correct.
> How am I doing?
Well, except one detail: as I wrote earlier today, we cannot do it for
4.1.2 since strings in Pootle have already been updated and translators
are already working on 4.2.0; so at the moment we have no way to add a
string between 4.1.1 and 4.1.2 (also, 4.1.2 is not meant for string
changes).
<orcmid>
I missed the message about timing and 4.1.2 versus 4.2.0 somehow.
So, we can we discuss changes to the messages and maybe make
bugzilla issues but changes should not be made to the trunk until
4.1.2 is out the door?
Whenever the messages are adjusted, they can refer to web pages
that are already waiting, even if not linked from anywhere else
up until then.
It looks like the redirect from download/common/java.html could
happen at any time it is considered that java/index.html is
ready.
</orcmid>
I'm also curious about the new mechanism Jan described... well, very
likely I'll know more about it at FOSDEM next month!
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Explaining Java (was RE: Java 32)
Posted by "Dennis E. Hamilton" <de...@acm.org>.
I've started working over the six Java-specific messages that are produced by AOO and adjusting the localizable explanation at <http://openoffice.org/xx/java>.
WEB SITE QUESTION:
For page-specific images that I want to include under content/xx/java/, can I simply put them in that directory, since they are only used by the web page(s) there?
I am thinking that will work perfectly for localization, because the localized versions of those folders can replace the images made from screen captures with equivalent ones made from the same-language UI. And for starters, copies of the xx/java/ images can continue to be used until localization-friendlier ones are supplied.
Is this a good way to approach this? Is there different guidance with regard to images having such local context?
- Dennis
-----Original Message-----
From: Marcus [mailto:marcus.mail@wtnet.de]
Sent: Tuesday, December 30, 2014 07:28
To: dev@openoffice.apache.org
Subject: Re: Explaining Java (was RE: Java 32)
Am 12/30/2014 03:54 PM, schrieb Dennis E. Hamilton:
[ ... ]
> <orcmid>
> I thought the idea was to create openoffice.org/java/index.htm and
> seed the xx structure from that. Have I misunderstood how that is
> usually done?
> </orcmid>
I think there was no agreemnt here. However, it's just a commit more
when we all agree that this is the best place. Can be done later as the
page was recently updated by Kay.
> So, now the several error messages need to be updated.
>
> <orcmid>
> Some of the error messages can be essentially unchanged because
> they happen when the JRE is installed or has been intentionally
> avoided. I will put up a suggested list when I am feeling better.
> </orcmid>
That would be great. I'm a bit lost to resolve which text part is
combined with what and in which case.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Marcus <ma...@wtnet.de>.
Am 12/30/2014 03:54 PM, schrieb Dennis E. Hamilton:
> [fuzzy-headed with the flu]
>
> -- replying below to --
> From: Marcus [mailto:marcus.mail@wtnet.de]
> Sent: Tuesday, December 30, 2014 03:35
> To: dev@openoffice.apache.org
> Subject: Re: Explaining Java (was RE: Java 32)
>
> Am 12/29/2014 10:30 AM, schrieb Andrea Pescetti:
>> On 28/12/2014 Marcus wrote:
>>> Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
>>>> In "xx" we try to avoid too many subdirectories. The Java file could
>>>> find a place in the "product" directory, and be referenced from the
>>>> leftnav in that directory (extended a few hours ago).
>>> in general, I would agree with you. However in this well-known case
>>> "I've a problem with Java resp. JRE - What to do?" I would make an
>>> exception here as it is easier for the average user to remember
>>> "openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
>>> dialog box but IMHO not clickable
>>
>> OK, good point. And now it is well past time this conversation had to
>> stop and turn into action, so I highly recommend that you open an issue
>> and that we have further discussion there if needed, or that we just get
>> it done!
>
> sure, the issue is #125981:
>
> The webpage is now copied from .../download/common/java.html" to
> ".../xx/java/index.html".
>
> <orcmid>
> I thought the idea was to create openoffice.org/java/index.htm and
> seed the xx structure from that. Have I misunderstood how that is
> usually done?
> </orcmid>
I think there was no agreemnt here. However, it's just a commit more
when we all agree that this is the best place. Can be done later as the
page was recently updated by Kay.
> So, now the several error messages need to be updated.
>
> <orcmid>
> Some of the error messages can be essentially unchanged because
> they happen when the JRE is installed or has been intentionally
> avoided. I will put up a suggested list when I am feeling better.
> </orcmid>
That would be great. I'm a bit lost to resolve which text part is
combined with what and in which case.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Explaining Java (was RE: Java 32)
Posted by "Dennis E. Hamilton" <de...@acm.org>.
[fuzzy-headed with the flu]
-- replying below to --
From: Marcus [mailto:marcus.mail@wtnet.de]
Sent: Tuesday, December 30, 2014 03:35
To: dev@openoffice.apache.org
Subject: Re: Explaining Java (was RE: Java 32)
Am 12/29/2014 10:30 AM, schrieb Andrea Pescetti:
> On 28/12/2014 Marcus wrote:
>> Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
>>> In "xx" we try to avoid too many subdirectories. The Java file could
>>> find a place in the "product" directory, and be referenced from the
>>> leftnav in that directory (extended a few hours ago).
>> in general, I would agree with you. However in this well-known case
>> "I've a problem with Java resp. JRE - What to do?" I would make an
>> exception here as it is easier for the average user to remember
>> "openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
>> dialog box but IMHO not clickable
>
> OK, good point. And now it is well past time this conversation had to
> stop and turn into action, so I highly recommend that you open an issue
> and that we have further discussion there if needed, or that we just get
> it done!
sure, the issue is #125981:
The webpage is now copied from .../download/common/java.html" to
".../xx/java/index.html".
<orcmid>
I thought the idea was to create openoffice.org/java/index.htm and
seed the xx structure from that. Have I misunderstood how that is
usually done?
</orcmid>
So, now the several error messages need to be updated.
<orcmid>
Some of the error messages can be essentially unchanged because
they happen when the JRE is installed or has been intentionally
avoided. I will put up a suggested list when I am feeling better.
</orcmid>
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Marcus <ma...@wtnet.de>.
Am 12/29/2014 10:30 AM, schrieb Andrea Pescetti:
> On 28/12/2014 Marcus wrote:
>> Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
>>> In "xx" we try to avoid too many subdirectories. The Java file could
>>> find a place in the "product" directory, and be referenced from the
>>> leftnav in that directory (extended a few hours ago).
>> in general, I would agree with you. However in this well-known case
>> "I've a problem with Java resp. JRE - What to do?" I would make an
>> exception here as it is easier for the average user to remember
>> "openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
>> dialog box but IMHO not clickable
>
> OK, good point. And now it is well past time this conversation had to
> stop and turn into action, so I highly recommend that you open an issue
> and that we have further discussion there if needed, or that we just get
> it done!
sure, the issue is #125981:
The webpage is now copied from .../download/common/java.html" to
".../xx/java/index.html".
So, now the several error messages need to be updated.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Andrea Pescetti <pe...@apache.org>.
On 28/12/2014 Marcus wrote:
> Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
>> In "xx" we try to avoid too many subdirectories. The Java file could
>> find a place in the "product" directory, and be referenced from the
>> leftnav in that directory (extended a few hours ago).
> in general, I would agree with you. However in this well-known case
> "I've a problem with Java resp. JRE - What to do?" I would make an
> exception here as it is easier for the average user to remember
> "openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
> dialog box but IMHO not clickable
OK, good point. And now it is well past time this conversation had to
stop and turn into action, so I highly recommend that you open an issue
and that we have further discussion there if needed, or that we just get
it done!
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Explaining Java (was RE: Java 32)
Posted by "Dennis E. Hamilton" <de...@acm.org>.
-- reply below to --
From: Marcus [mailto:marcus.mail@wtnet.de]
Sent: Sunday, December 28, 2014 11:13
To: dev@openoffice.apache.org
Subject: Re: Explaining Java (was RE: Java 32)
Am 12/28/2014 07:38 PM, schrieb Dennis E. Hamilton:
[ ... ]
> I am a bit wary of live links in dialog boxes. Unlike browser
> links, it is not easy for the user to know that the link is to
> the location indicated in the message.
When you remember the text you have suggested I'm pretty sure the user
will know that the URL is directly connected with the text. ;-)
<orcmid>
Oh. I was not clear. I meant that the live link might go to a
different place than is shown in the message box. For example,
as a form of malware or a way of tracking users.
In my browser I can always tell where a static link goes (unless
JavaScript is being used to hide it, and then I am very careful).
I don't know if this is a significant risk, but it does increase
the threat surface unnecessarily. (Silently pinging for updates
is similar in not having the user in charge of what is
happening.)
</orcmid>
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Marcus <ma...@wtnet.de>.
Am 12/28/2014 07:38 PM, schrieb Dennis E. Hamilton:
> +1
>
> -- replying below to --
> From: Marcus [mailto:marcus.mail@wtnet.de]
> Sent: Sunday, December 28, 2014 10:06
> To: dev@openoffice.apache.org
> Subject: Re: Explaining Java (was RE: Java 32)
>
> Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
>> On 25/12/2014 Dennis E. Hamilton wrote:
>>> A. Is this a potential way to do it?
>>> 1. Create an ooo-site/trunk/content/xx/java/ directory.
>>> 2. Create leftnav.mdtext and index.mdtext files there.
>>> 3. The content/xx/java/index.mdtext would become the English Language
>>> version that
>>> We adopt for the target.
>>> If further "breakout" is required, it can be handled in that directory
>>> at a later time.
>>
>> In "xx" we try to avoid too many subdirectories. The Java file could
>> find a place in the "product" directory, and be referenced from the
>> leftnav in that directory (extended a few hours ago).
>
> in general, I would agree with you. However in this well-known case
> "I've a problem with Java resp. JRE - What to do?" I would make an
> exception here as it is easier for the average user to remember
> "openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
> dialog box but IMHO not clickable - as long no core developer will
> create this functionality.
>
> <orcmid>
> I think there is the same problem with java.html versus java.htm
> as well. "openoffice.org/java" is just easier and more-flexible
> at the destination.
>
> Concerning message boxes. I don't think there is an east way to use
> standard message-box resources to produce a URL. We are talking
> about GUI work instead, and having it be internationalized. I
> think this takes us too far from the least that can possibly
> work -- and assist users immediately.
>
> [Side Note: This might be possible with a button for Help
> though. Or put the URL in a button label. I have not
> checked further, but the idea came up in the WinForms case
> at<http://stackoverflow.com/questions/1833747/clickable-url-in-a-winform-message-box>.
>
> I am a bit wary of live links in dialog boxes. Unlike browser
> links, it is not easy for the user to know that the link is to
> the location indicated in the message.
When you remember the text you have suggested I'm pretty sure the user
will know that the URL is directly connected with the text. ;-)
> We are also creating a small problem with having a URL at all,
> since derivatives and knock-offs probably won't change the
> messages. In this case, having users taken care of seems to have
> clear precedence.
> </orcmid>
Ah, yes. Another argument to separate the Java text into an own webpage
and sub-dir. Then we can control, change or delete it without
influencing other files in other dirs.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Explaining Java (was RE: Java 32)
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1
-- replying below to --
From: Marcus [mailto:marcus.mail@wtnet.de]
Sent: Sunday, December 28, 2014 10:06
To: dev@openoffice.apache.org
Subject: Re: Explaining Java (was RE: Java 32)
Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
> On 25/12/2014 Dennis E. Hamilton wrote:
>> A. Is this a potential way to do it?
>> 1. Create an ooo-site/trunk/content/xx/java/ directory.
>> 2. Create leftnav.mdtext and index.mdtext files there.
>> 3. The content/xx/java/index.mdtext would become the English Language
>> version that
>> We adopt for the target.
>> If further "breakout" is required, it can be handled in that directory
>> at a later time.
>
> In "xx" we try to avoid too many subdirectories. The Java file could
> find a place in the "product" directory, and be referenced from the
> leftnav in that directory (extended a few hours ago).
in general, I would agree with you. However in this well-known case
"I've a problem with Java resp. JRE - What to do?" I would make an
exception here as it is easier for the average user to remember
"openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
dialog box but IMHO not clickable - as long no core developer will
create this functionality.
<orcmid>
I think there is the same problem with java.html versus java.htm
as well. "openoffice.org/java" is just easier and more-flexible
at the destination.
Concerning message boxes. I don't think there is an east way to use
standard message-box resources to produce a URL. We are talking
about GUI work instead, and having it be internationalized. I
think this takes us too far from the least that can possibly
work -- and assist users immediately.
[Side Note: This might be possible with a button for Help
though. Or put the URL in a button label. I have not
checked further, but the idea came up in the WinForms case
at <http://stackoverflow.com/questions/1833747/clickable-url-in-a-winform-message-box>.
I am a bit wary of live links in dialog boxes. Unlike browser
links, it is not easy for the user to know that the link is to
the location indicated in the message.
We are also creating a small problem with having a URL at all,
since derivatives and knock-offs probably won't change the
messages. In this case, having users taken care of seems to have
clear precedence.
</orcmid>
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Marcus <ma...@wtnet.de>.
Am 12/27/2014 12:44 AM, schrieb Andrea Pescetti:
> On 25/12/2014 Dennis E. Hamilton wrote:
>> A. Is this a potential way to do it?
>> 1. Create an ooo-site/trunk/content/xx/java/ directory.
>> 2. Create leftnav.mdtext and index.mdtext files there.
>> 3. The content/xx/java/index.mdtext would become the English Language
>> version that
>> We adopt for the target.
>> If further "breakout" is required, it can be handled in that directory
>> at a later time.
>
> In "xx" we try to avoid too many subdirectories. The Java file could
> find a place in the "product" directory, and be referenced from the
> leftnav in that directory (extended a few hours ago).
in general, I would agree with you. However in this well-known case
"I've a problem with Java resp. JRE - What to do?" I would make an
exception here as it is easier for the average user to remember
"openoffice.org/java/" resp. "openoffice.org/xx/java/". Yes, it's in the
dialog box but IMHO not clickable - as long no core developer will
create this functionality.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Andrea Pescetti <pe...@apache.org>.
On 25/12/2014 Dennis E. Hamilton wrote:
> A. Is this a potential way to do it?
> 1. Create an ooo-site/trunk/content/xx/java/ directory.
> 2. Create leftnav.mdtext and index.mdtext files there.
> 3. The content/xx/java/index.mdtext would become the English Language version that
> We adopt for the target.
> If further "breakout" is required, it can be handled in that directory at a later time.
In "xx" we try to avoid too many subdirectories. The Java file could
find a place in the "product" directory, and be referenced from the
leftnav in that directory (extended a few hours ago).
> B. Having done that, and having the message be agreeable,
> internationalization can commence.
> C. At an appropriate time, the
> content/java/ directory is created and it is arranged that this and
> content/xx/java/ are synchronized. (I have no idea what order this
> has to be in and which is the master.)
"xx" is generated from the English content, so steps are: write English
page; copy to xx (structure, i.e., filenames and directories, may
change); translators add it.
> D. The current content/download/common/java.html can be redirected to
> content/java/ Or E. The adjusted default messages that link to the
> site will link to http://openoffice.org/java and be in the build in
> time to test (4.1.2?) developer builds with the new messages and the
> new site pages.
Correct.
> How am I doing?
Well, except one detail: as I wrote earlier today, we cannot do it for
4.1.2 since strings in Pootle have already been updated and translators
are already working on 4.2.0; so at the moment we have no way to add a
string between 4.1.1 and 4.1.2 (also, 4.1.2 is not meant for string
changes).
I'm also curious about the new mechanism Jan described... well, very
likely I'll know more about it at FOSDEM next month!
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by Marcus <ma...@wtnet.de>.
Am 12/25/2014 12:42 AM, schrieb Dennis E. Hamilton:
> I finished checking on the Java-specific messages and the six messages only have a single place where each is produced.
>
> It appears that a single (default en) page could provide the necessary information for reference from any messages in the installed binaries.
>
> Andrea suggests
>
> The page could be included in the set of "standard pages" (the
> "xx pages", see http://openoffice.apache.org/website-native.html
> and then each translation team can decide whether to use the
> English one or their translated one.
>
> A. Is this a potential way to do it?
>
> 1. Create an ooo-site/trunk/content/xx/java/ directory.
>
> 2. Create leftnav.mdtext and index.mdtext files there.
>
> 3. The content/xx/java/index.mdtext would become the English Language version that
> We adopt for the target.
>
> If further "breakout" is required, it can be handled in that directory at a later time.
>
> B. Having done that, and having the message be agreeable, internationalization can commence.
>
> C. At an appropriate time, the content/java/ directory is created and it is arranged that this and content/xx/java/ are synchronized. (I have no idea what order this has to be in and which is the master.)
>
> D. The current content/download/common/java.html can be redirected to content/java/
> Or
>
> E. The adjusted default messages that link to the site will link to http://openoffice.org/java and be in the build in time to test (4.1.2?) developer builds with the new messages and the new site pages.
>
>
> How am I doing?
sounds good. To have this ready for a 4.1.2 sounds also be feasible.
Marcus
> -----Original Message-----
> From: Andrea Pescetti [mailto:pescetti@apache.org]
> Sent: Monday, December 22, 2014 00:12
> To: dev@openoffice.apache.org
> Subject: Re: Java 32
>
> On 22/12/2014 Dennis E. Hamilton wrote:
>> I am assuming that we can do the job with a single text. So I
>> see no problem with where it is kept.
>> One consideration might be the maintenance of the different-language
>> versions and how browsers are routed to the correct one.
>
> The page could be included in the set of "standard pages" (the "xx
> pages", see http://openoffice.apache.org/website-native.html and then
> each translation team can decide whether to use the English one or their
> translated one.
>
> Regards,
> Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Explaining Java (was RE: Java 32)
Posted by jan i <ja...@apache.org>.
On 25 December 2014 at 00:42, Dennis E. Hamilton <de...@acm.org>
wrote:
> I finished checking on the Java-specific messages and the six messages
> only have a single place where each is produced.
>
> It appears that a single (default en) page could provide the necessary
> information for reference from any messages in the installed binaries.
>
> Andrea suggests
>
> The page could be included in the set of "standard pages" (the
> "xx pages", see http://openoffice.apache.org/website-native.html
> and then each translation team can decide whether to use the
> English one or their translated one.
>
> A. Is this a potential way to do it?
>
> 1. Create an ooo-site/trunk/content/xx/java/ directory.
>
> 2. Create leftnav.mdtext and index.mdtext files there.
>
> 3. The content/xx/java/index.mdtext would become the English Language
> version that
> We adopt for the target.
>
> If further "breakout" is required, it can be handled in that directory at
> a later time.
>
> B. Having done that, and having the message be agreeable,
> internationalization can commence.
>
> C. At an appropriate time, the content/java/ directory is created and it
> is arranged that this and content/xx/java/ are synchronized. (I have no
> idea what order this has to be in and which is the master.)
>
> D. The current content/download/common/java.html can be redirected to
> content/java/
> Or
>
> E. The adjusted default messages that link to the site will link to
> http://openoffice.org/java and be in the build in time to test (4.1.2?)
> developer builds with the new messages and the new site pages.
>
>
> How am I doing?
>
Without being an expert, I can only say your suggestion looks pretty much
like how I would have done it.
Remark, Infra (==me) work on moving translations to a new service. This
service will also offer webpage translation (through the same interface) so
we can ask all our translators to translate relevant parts.
We have to change every page slightly (add a special css and js) and the it
just works. I hope to be able to present this at FOSDEM.
rgds
jan i.
>
> -----Original Message-----
> From: Andrea Pescetti [mailto:pescetti@apache.org]
> Sent: Monday, December 22, 2014 00:12
> To: dev@openoffice.apache.org
> Subject: Re: Java 32
>
> On 22/12/2014 Dennis E. Hamilton wrote:
> > I am assuming that we can do the job with a single text. So I
> > see no problem with where it is kept.
> > One consideration might be the maintenance of the different-language
> > versions and how browsers are routed to the correct one.
>
> The page could be included in the set of "standard pages" (the "xx
> pages", see http://openoffice.apache.org/website-native.html and then
> each translation team can decide whether to use the English one or their
> translated one.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>