Closed Bug 65253 Opened 24 years ago Closed 24 years ago

Profile Creation: Need a user interface for Regional Content

Categories

(SeaMonkey :: Startup & Profiles, defect, P2)

x86
Other
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.1

People

(Reporter: jaimejr, Assigned: jbetak)

References

Details

(Keywords: helpwanted, intl, Whiteboard: r=nhotta sr=alecf need a=)

Attachments

(8 files)

Creating new bug to remove Netscape Confidential information. Formerly bugzilla 64147.
We are planning on seprating the language UI from the content in Customization Packs (aka Language Packs). When we do this, we will need to provide the user with a means to edit their Regional Content in Profile Manager. Nominating for nsbeta1. ------- Additional Comments From Jaime Rodriguez, Jr. 2001-01-02 18:11 ------- Adding msanz, vishy, blee and tpringle to cc: list. Adding nsbeta1 and intl keywords.
Assignee: asa → tao
QA Contact: doronr → gbush
------- Additional Comments From Jaime Rodriguez, Jr. 2001-01-08 10:57 ------- Reassigning to Tao per Nav Triage team. ------- Additional Comments From tao@netscape.com 2001-01-08 11:56 ------- Hi, Jaime: Would you like to drive the UI design first? IMO, ProfileManager, Prefs dlg, and "View" menu should be consistent and mutual complementary. ------- Additional Comments From Jaime Rodriguez, Jr. 2001-01-08 16:56 ------- I concur with your opinion. Yup, guess I could lock down the UI stuff first . . . fair enough.
Reassing to Jaime for UI design
Assignee: tao → jaime
Vishy - I'm gonna need some help from German and Ben on this one (i.e. UI work). Adding German and Ben to cc: list.
this was assigned to the WRONG jaime at Netscape. reassigning to the reporter
Assignee: jaime → jaimejr
Can somebody tell me how this is being used, ie. how often do users switch this setting, when do they switch and what is the trigger/motivation. It's much easier to design this once their is a clear understanding on these items.
Depends on: 62171
Met with German on Wednesday, 02.21.01. We reviewed the feature and its future versioning. Addtionally, we provided him the original Language Pack doucment for his use. Next steps, will be for German to propose new UI specification to address the separation of Language and Content.
I have better understanding now what the separation of UI Language and Regional content packs mean. I am now of the belief that the change of the UI Language is probably much less frequent than that of regional packs, meaning the UI language selection should prob be a pref which is then peristed in the profile. Regional Content Packs however are envisioned to be changed frequently, thus I would assume they are similar to themes, meaning we should add them to the View menu similar to "Apply Theme". Adding them to prefs is optional.
Reassigning to German for UI specification.
Assignee: jaimejr → german
Summary: Need a user interface for Regional Content → ProfileCreation: Need a user interface for Regional Content
This one also needs to be fixed ASAP.
Severity: normal → blocker
Keywords: intl, nsbeta1
Priority: -- → P2
Target Milestone: --- → mozilla0.9.1
reassigning to nhotta.
Assignee: german → nhotta
Added Asa to the cc: list. Jaime, would you say that this bug depends on the questions in 65241 being resolved first?
I'm confused. This bug was assigned to German for a UI specification. A UI proposal (which until a few minutest ago was not publically available) has landed in bug 79551. The proposal has standing objections from both mpt and Ben Goodger. Why has this bug been handed to someone for implementation when the design phase has not been completed?
German - Do you want to walk people through the proposal and review process for the design phase? I think Ben was cc:'d on all the proposals.
Reassign to vishy.
Assignee: nhotta → vishy
jaime, I cannot commit to doing this work for mozilla0.9.1 in light of the points asa has raised and its too late to start this.
Target Milestone: mozilla0.9.1 → Future
Vishy - Suggest we accept German's proposal, and accpet the fix for this one, as MPT and others are in agreement, that this is the most likely place users would change the Language UI. If not here, then where?
Jaime, as I think we want users to *be able* to switch their UI language on an existing profile, we should also have it in prefs IMO (bug 65251).
Agreed!
This should be marked M0.9.2, not "Future".
Summary: ProfileCreation: Need a user interface for Regional Content → Profile Creation: Need a user interface for Regional Content
clobbering milestone for recondisderation.
Component: Browser-General → Profile Manager FrontEnd
Target Milestone: Future → ---
setting m0.9.2, I'll try and find the right owner in my group for this one.
Target Milestone: --- → mozilla0.9.2
thanks vishy.
per mpt's comments in bug 65251: adding related UI bugs to the dependency tree to provide better way of cross- referencing the somewhat disparate sources of information. Here are pointers to Tao's localization project, which will hopefully provide a path of enlightenment on the topic of language and regional content bundling: Regional Content Bundling http://www.mozilla.org/projects/l10n/mlp_regional.html Please note that Mozilla has divided up the original language pack from en- US.jar into en.jar (language pack), US.jar (regional content pack) and en- XXX.jar (platform-related en-linux, en-win, ... ). Click below for the gory details: L10n Packaging http://www.mozilla.org/projects/l10n/mlp_what2.html#chrome_files http://www.mozilla.org/projects/l10n/mlp_packaging.html German's UI (image references are now functional): http://www.mozilla.org/projects/ui/communicator/framework/langcontentui/
Depends on: 65241
vishy, I'm the owner of a commercial tree dup - http://bugscape.netscape.com/show_bug.cgi?id=4942. I'm tentatively assigning to myself.
Assignee: vishy → jbetak
ben, alecf, blizzard: could you please r/sr? i18n really wants this UI modification in Beta1 - your help/comments are greatly appreciated! I believe that unlike with the "View" menu, there was a consensus on including region packs in the Mozilla Profile Manager...
Status: NEW → ASSIGNED
Whiteboard: fix in hand, awaiting r/sr - 05/18/2001 - 7:30 pm
yuck. can you please just insert it into the wizard sequence? Does ui object to it being in the wizard sequence?
timeless, I'd be more than happy to implement whatever UI requirements the Mozilla community will arrive at - for starters, the current patch conforms with German's UI proposal. I can only hope that you've read the prior discussion including the (however crude) UI prototype. If so, I'm surprised why are you voicing you opinion only now - with the 0.9.1 branch and Beta1 on the horizon? I don't like the popup either, although I'm not sure, what other folks are thinking of a third wizard.
sorry. at the time someone or german attached a url that didn't include pictures. I read the url. it was useless. I didn't read the url after it got pictures. Personally, i think i requested in one of these (perhaps languages and not content -- *shrug*) bugs that we recycle code, so if you've already done the 'using Prefs' panel, please recycle its code into the profile manager.
>so if you've already done the 'using Prefs' panel, please recycle its code >into the profile manager Timeless, let me repeat what I already pointed out to Gerv - I'm finding both the form and content of the so-called "UI consensus building process" very disturbing. I also suspect, that some of the Mozilla contributors are neither aware, nor appreciative of i18n and l10n requirements. Let me provide you some more factual information: although I've not read your previous requests, I too suggested to reuse the prefs code in an internal i18n discussion at Netscape. However, the new pref panel is not yet finished and we are running against some hard deadlines. Would you like to help? If not, please at least try to keep this discussion more pleasant, which would be to everyone's benefit.
selectLang.xul @@ -36,9 +39,30 @@ those look like tabs. asside from that you can have an r=timeless and someone can spear me for it. > the form and content of the so-called "UI consensus building process" > very disturbing. I'd expect you're in the minority, I don't know if I could name someone who disagrees w/ your statement. > I also suspect, that some of the Mozilla contributors are neither aware, > nor appreciative of i18n and l10n requirements. This is an accurate statement. However just as we frustrate your work, we frustrate theirs. My r= is only valid in conjunction w/ an sr= from blake, ben or someone who is staff@mozilla.org -- sorry. My comments are in bug 65251, please read them even if just to know what I have written. You might also look at attachment 21647 [details] which should be suffering from bitrot but is probably rehabilitatable.
Keywords: approval, patch
Whiteboard: fix in hand, awaiting r/sr - 05/18/2001 - 7:30 pm → fix in hand, awaiting sr - 05/21/2001 - 5:37 pm
Cc rchen@netscape.com, the change affects localization.
Sending to DanielMC for L10N approval.
Addressed timeless concern of unnecessary patches by attaching an expanded diff -t. Awaiting sr= per offline discussion with Vishy and Jaime. Working on a commercial-only fix, which is be more extensive, since the the /profile directory in the /ns tree is currently pretty bare...
Whiteboard: fix in hand, awaiting sr - 05/21/2001 - 5:37 pm → fix in hand, second request for sr - 05/22/2001 - 6:49 pm
put rows=5 on the tree widget, and sr=ben for the FE changes. Do we have the spec's "friendly explanatory text" yet? Are people likely to know what this means?
Jaime, we still need to come up with some explanatory text. I think it's comprehensible as it is right now and I will proceed with the checkin, yet we should make it accessible for just about anyone. Especially given the broad audience Content Packs might cater to in the near future.
Whiteboard: fix in hand, second request for sr - 05/22/2001 - 6:49 pm → Ready to checkin - 7:25 pm
checked in - leaving open to solicit Jaime's feedback
Whiteboard: Ready to checkin - 7:25 pm
sorry, you missed my point [my fault for not being explicit]. @@ -36,9 +39,30 @@ </treerow> </treeitem> ^two character indentation the stuff that i said 'looked like tabs' was certainly not 2 character indentation. I don't care if they're tabs or not, they don't match the indentation style of that part of the file (and i'm guessing they don't match the rule for the file either).
well, you are sorry and I'm sorry :-) looks like the indent in the newly added part is a real mess. I've certainly overlooked it an wonder, how it got there in the first place... 49 //An infinite number of monkeys hacking on an infinite number of terminals 50 //will eventually produce the perfect browser... 51 52 <menulist id="regionList" flex="1"> 53 <menupopup 54 datasources="rdf:chrome" ref="urn:mozilla:locale:root" 55 sortResource="http://www.mozilla.org/rdf/chrome#name" 56 sortDirection="ascending"> 57 <template xmlns:chrome="http://www.mozilla.org/rdf/chrome#"> 58 <rule chrome:localeType="region"> 59 <menuitem class="standard" uri="rdf:*" 60 label="rdf:http://www.mozilla.org/rdf/chrome#displayName" 61 value="rdf:http://www.mozilla.org/rdf/chrome#name"/> 62 </rule> 63 </template> 64 </menupopup> 65 </menulist>
for amusement only, I'll add that I too find it disturbing :)
Oh God, looks like this patch has been made under an unlucky star. Naoki just pointed out that we should tag the default content pack in Mozilla (read mark "US Region" as a content pack). And it also seems that the previous patch didn't contain the changes from selectLang.js - maybe the gremlins ate it. Anyhow, here is a second installment in case we get the approval to sneak it into Beta1. It also addresses the indention issues in selectLang.xul.
moving back to 0.9.1, I'll try to get PDT's approval to get this second installment into Beta1
Target Milestone: mozilla0.9.2 → mozilla0.9.1
sr=alecf, looks fine
r=nhotta
Whiteboard: r=nhotta sr=alecf
Whiteboard: r=nhotta sr=alecf → r=nhotta sr=alecf need a=
Adding jon rubin to cc: list.
a=blizzard for 0.9.1
closing at last - thanks everyone!
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Jon, would you verify this please? thanks
Verified on WinMe-Ja, Ja 060713-0.9.1.
Status: RESOLVED → VERIFIED
Bugscape 6828 has been added for problem where selected region does not take affect after profile creation.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: